sudo-sys February 2023

sudo-sys@sudoroom.org

8 participants
12 discussions

Cron <root@humans> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )

by root＠humans.sudoroom.org

/etc/cron.daily/logrotate: Job for apache2.service failed. See 'systemctl status apache2.service' and 'journalctl -xn' for details. error: error running shared postrotate script for '/var/log/apache2/*.log ' run-parts: /etc/cron.daily/logrotate exited with return code 1

1 year, 10 months

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

by root＠humans.sudoroom.org

Failed to renew certificate bayareapublicschool.org with error: Some challenges have failed. Failed to renew certificate every.cat with error: Some challenges have failed. Failed to renew certificate stuff.sudoroom.org with error: Some challenges have failed. Failed to renew certificate sudoroom.org with error: Some challenges have failed. All renewals failed. The following certificates could not be renewed: /etc/letsencrypt/live/bayareapublicschool.org/fullchain.pem (failure) /etc/letsencrypt/live/every.cat/fullchain.pem (failure) /etc/letsencrypt/live/stuff.sudoroom.org/fullchain.pem (failure) /etc/letsencrypt/live/sudoroom.org/fullchain.pem (failure) 4 renew failure(s), 0 parse failure(s)

1 year, 10 months

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

by root＠humans.sudoroom.org

Failed to renew certificate bayareapublicschool.org with error: Some challenges have failed. Failed to renew certificate every.cat with error: Some challenges have failed. Failed to renew certificate stuff.sudoroom.org with error: Some challenges have failed. Failed to renew certificate sudoroom.org with error: urn:ietf:params:acme:error:serverInternal :: The server experienced an internal error :: Unable to update challenge All renewals failed. The following certificates could not be renewed: /etc/letsencrypt/live/bayareapublicschool.org/fullchain.pem (failure) /etc/letsencrypt/live/every.cat/fullchain.pem (failure) /etc/letsencrypt/live/stuff.sudoroom.org/fullchain.pem (failure) /etc/letsencrypt/live/sudoroom.org/fullchain.pem (failure) 4 renew failure(s), 0 parse failure(s)

1 year, 10 months

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

by root＠humans.sudoroom.org

1 year, 10 months

Your Site: sudo humans Is Now Back Up

by StatusCake Team

StatusCake Alert -- statuscake.com Website Monitoring Your website sudo humans has recovered. Total downtime: 00:10:12 To view more details about why your test went down, log into your account: https://app.statuscake.com/

1 year, 10 months

Your Site: sudo humans Is Currently Down

by StatusCake Team

StatusCake Alert -- statuscake.com Website Monitoring Your website sudo humans has encountered an error. Reason: Timeout / Connection Refused To view more details about this error, log into your account now: https://app.statuscake.com/

1 year, 10 months

Sudo Room account request

by Sudo Room

Joe Turner 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, 10 months

double messages to keys list?

by Jake

can we figure out why messages are coming through twice on the keys list? The following message arrived yesterday, I dealt with it and responded, and then it came through today again. This has happened before and it's very confusing. Two copies of the email can be seen in the archives; the second one was sent before 7:53PM and needless to say the was not another card swipe event to go with it, this is some sort of bug that is happening. here are links to the two instances of this message in the archives: https://omnicommons.org/lists/private/keys/2023-February/000870.html https://omnicommons.org/lists/private/keys/2023-February/000872.html I would like for us to fix this because I take these messages very seriously and respond to them, and it's a burden when another one comes through and I have to figure out whether I dealt with it already or not. A day later? -jake ---------- Forwarded message ---------- Date: Mon, 20 Feb 2023 08:59:55 -0800 (PST) From: keys(a)omnicommons.org Reply-To: Brian Houstle <bahoustle(a)gmail.com> To: keys(a)omnicommons.org Subject: [omni-keys] KEY CARD REQUEST: Brian Houstle Name: Brian Houstle Pseudonym: Brian Relation to omni: CCL Member Working groups: CCL I need a key because: Access to ccl lab Email: bahoustle(a)gmail.com Contact info: 3013568987 Swipe time: 7:53 pm This email was generated by the form at: https://omnicommons.org/keys/ _______________________________________________ keys mailing list keys(a)lists.omnicommons.org https://omnicommons.org/lists/listinfo/keys

1 year, 10 months

Your Site: sudo humans Is Now Back Up

by StatusCake Team

StatusCake Alert -- statuscake.com Website Monitoring Your website sudo humans has recovered. Total downtime: 00:06:23 To view more details about why your test went down, log into your account: https://app.statuscake.com/

1 year, 10 months

Your Site: sudo humans Is Currently Down

by StatusCake Team

StatusCake Alert -- statuscake.com Website Monitoring Your website sudo humans has encountered an error. Reason: String Match Failed. String Not Found To view more details about this error, log into your account now: https://app.statuscake.com/

1 year, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

sudo-sys February 2023