sudo-sys April 2023

sudo-sys@sudoroom.org

6 participants
18 discussions

Cron <root@humans> /root/bin/new-certbot -q renew

by root＠humans.sudoroom.org

Failed to renew certificate humans.sudoroom.org with error: Could not bind TCP port 80 because it is already in use by another process on this system (such as a web server). Please stop the program in question and then try again. All renewals failed. The following certificates could not be renewed: /etc/letsencrypt/live/humans.sudoroom.org/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s)

1 year

Cron <root@humans> /root/bin/new-certbot -q renew

by root＠humans.sudoroom.org

1 year

Cron <root@humans> /root/bin/new-certbot -q renew

by root＠humans.sudoroom.org

1 year

Cron <root@humans> /root/bin/new-certbot -q renew

by root＠humans.sudoroom.org

1 year

Cron <root@humans> /root/bin/new-certbot -q renew

by root＠humans.sudoroom.org

1 year

Sudo Room account request

by Sudo Room

Tomrlopes has requested an account and is waiting for confirmation. The email address has been confirmed. You can confirm the request here: https://sudoroom.org/wiki/Special:ConfirmAccounts

1 year

Re: help setup apache2 on new sudogateway

by Sven Pedersen

I’m new here, but I build this kind of tech infrastructure in my job. I agree with Yardena that it makes sense not to put a web server function directly on an internet front line of defense; if possible you want it somewhere else to avoid opening holes for attackers. You can simply forward (proxy) the needed ports as suggested. If you’re wanting to retire the older server or just avoid complexity of maintaining them both that’s also reasonable, but it isn’t as safe in case Omni or Sudo Room become targets. As an alternative related to the earlier discussion about logging changes, it might make sense to use some infrastructure tools like cfengine to track changes as code and simultaneously make it possible to trivially rebuild a system if it fails, but maybe not yet as it isn’t familiar to everybody who might be helping. Sven

1 year, 1 month

Cron <www-data@sudoroom> [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.monthly /usr/share/mailman3-web/manage.py runjobs monthly

by root＠sudoroom.org

ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_extensions/management/commands/runjobs.py", line 40, in runjobs job().execute() File "/usr/lib/python3/dist-packages/hyperkitty/jobs/update_and_clean_index.py", line 37, in execute run_with_lock(update_index, remove=True) File "/usr/lib/python3/dist-packages/hyperkitty/lib/utils.py", line 181, in run_with_lock log.exception("Failed to update the fulltext index: %s", e) File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 447, in __exit__ self.unlock() File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 398, in unlock raise NotLockedError('Already unlocked') flufl.lock._lockfile.NotLockedError: Already unlocked

1 year, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

sudo-sys April 2023