jessuppi
commented
3 years ago Hello thanks for the feedback @corzel
It sounds like perhaps your stack is outdated, because we no longer have the ss-purge parent script. Instead we now have only the child scripts, and the shortcut command ss purge instead. We've been doing some thinking on how best to organize the bash scripts so if you have feedback on this change please let us know here or in Discord.
About UFW we had updated some of the configuration a few months back and it caused some issues for some, you can simply reinstall that module again to fix it e.g. ss install ufw should do the trick.
corzel
Hello! I have 2 issues in terminal.
$>sudo journalctl -xe May 08 22:13:56 server-one systemd[1]: Starting Uncomplicated firewall... -- Subject: A start job for unit ufw.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support
-- A start job for unit ufw.service has begun execution.
-- The job identifier is 968. May 08 22:13:56 server-one ufw-init[23929]: Could not find /etc/default/ufw (aborting) May 08 22:13:56 server-one systemd[1]: ufw.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support
-- An ExecStart= process belonging to unit ufw.service has exited.
-- The process' exit code is 'exited' and its exit status is 1. May 08 22:13:56 server-one systemd[1]: ufw.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Support: http://www.ubuntu.com/support
-- The unit ufw.service has entered the 'failed' state with result 'exit-code'. May 08 22:13:56 server-one systemd[1]: Failed to start Uncomplicated firewall. -- Subject: A start job for unit ufw.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support
-- A start job for unit ufw.service has finished with a failure.
-- The job identifier is 968 and the job result is failed. May 08 22:13:56 server-one sudo[23733]: pam_unix(sudo:session): session closed for user root May 08 22:14:01 server-one CRON[23937]: pam_unix(cron:session): session opened for user root by (uid=0) May 08 22:14:01 server-one CRON[23938]: (root) CMD (/usr/bin/flock -w 0 /tmp/02-cron-regular.lock /var/www/crons/02-cron-regular > /dev/null 2>&1) May 08 22:14:01 server-one CRON[23937]: pam_unix(cron:session): session closed for user root May 08 22:15:01 server-one CRON[23952]: pam_unix(cron:session): session opened for user root by (uid=0) May 08 22:15:01 server-one CRON[23953]: pam_unix(cron:session): session opened for user root by (uid=0) May 08 22:15:01 server-one CRON[23954]: (root) CMD (/usr/bin/flock -w 0 /tmp/01-cron-often.lock /var/www/crons/01-cron-often > /dev/null 2>&1) May 08 22:15:01 server-one CRON[23955]: (root) CMD (/usr/bin/flock -w 0 /tmp/03-cron-quarter-hourly.lock /var/www/crons/03-cron-quarter-hourly > /dev/null 2>&1) May 08 22:15:01 server-one CRON[23953]: pam_unix(cron:session): session closed for user root May 08 22:15:01 server-one CRON[23952]: pam_unix(cron:session): session closed for user root May 08 22:15:15 server-one sudo[23966]: master : TTY=pts/0 ; PWD=/var/www ; USER=root ; COMMAND=/usr/bin/journalctl -xe May 08 22:15:15 server-one sudo[23966]: pam_unix(sudo:session): session opened for user root by master(uid=0)