sudo-sys

sudo-sys@sudoroom.org

2 participants
890 discussions

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

2 years, 11 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/

2 years, 11 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/

2 years, 11 months

Re: [sudo-info] Re: Sudo Room account request

by Yardena Cohen

Looks like Jake did it. Any current bureaucrat who knows your username can promote you at https://sudoroom.org/wiki/Special:UserRights Also FYI I noticed this automated email was going to "Array(a)sudoroom.org" because we had: $wgConfirmAccountContact = array('sudo-sys(a)lists.sudoroom.org', 'juul(a)labitat.dk'); which is not a supported syntax! They only allow one email as a string. I removed Marc's email but also set this, so that all bureaucrats will get notified anyway: $wgGroupPermissions['bureaucrat']['confirmaccount-notify'] = true; It seems like we've had this bug since at least 2015. Amazing none of us had caught it before. On Mon, Feb 6, 2023 at 9:29 AM Andrew R Gross <arg5029(a)gmail.com> wrote: > > I got this email, but when I tried to complete the request the wiki gave me this error: > > " > > Permission error > > Jump to navigationJump to search > > You do not have permission to review and accept accounts, for the following reason: > > The action you have requested is limited to users in the group: Bureaucrats." > > > Who is in the group Bureaucrats? > > > Andrew R Gross, (he/him) > 412.657.5332 - shrad.org > > > On Mon, Feb 6, 2023 at 9:20 AM Sudo Room <apache(a)sudoroom.org> wrote: >> >> Rajah 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 >> >> >> NOTE: emails to the Info list were sent to an individual email address (such as info(a)sudoroom.org) with the PRESUMPTION OF PRIVACY. They may include personal information which the sender would not have sent to a public list (such as sudo-discuss). If you must forward messages to a public list, please take great care to REMOVE SENSITIVE INFORMATION! >> >> _______________________________________________ >> Info mailing list -- info(a)sudoroom.org >> To unsubscribe send an email to info-leave(a)sudoroom.org > > > NOTE: emails to the Info list were sent to an individual email address (such as info(a)sudoroom.org) with the PRESUMPTION OF PRIVACY. They may include personal information which the sender would not have sent to a public list (such as sudo-discuss). If you must forward messages to a public list, please take great care to REMOVE SENSITIVE INFORMATION! > > _______________________________________________ > Info mailing list -- info(a)sudoroom.org > To unsubscribe send an email to info-leave(a)sudoroom.org

2 years, 11 months

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

2 years, 11 months

https://sudoroom.org - SSL Certificate Valid!

by StatusCake Team

This is an HTML mail. Please use a mail-client that supports this message

3 years

ipv6 issues on saros aka room.sudoroom.org

by Jake

I tried to ssh to room.sudoroom.org on port 54321 which is forwarded to 100.64.64.27 (the TV computer) and it took a really long time, and so I did it with -vvv and it said: debug1: Connecting to room.sudoroom.org [2001:470:66:147::2] port 54321. debug1: connect to address 2001:470:66:147::2 port 54321: Connection timed out debug1: Connecting to room.sudoroom.org [142.254.26.9] port 54321. so in other words...it tried on ipv6 and failed and then it went on ipv4 and worked. note: it works fine to ssh to saros (the router) like this: ssh -p40629 jerkey@2001:470:66:147::2 but times out if I try to go to the forwarded port like this: ssh -p54321 jerkey@2001:470:66:147::2 any idea why this is happening and where the problem is? my guess is that the port is forwarded on ipv4 and not on ipv6? I tried to learn how iptables works on saros but i can't find any notes so i guess I never learned anything. thank you -jake

3 years

https://sudoroom.org - SSL Certificate Expiring Soon!

by StatusCake Team

This is an HTML mail. Please use a mail-client that supports this message

3 years

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

3 years

*** SECURITY information for sudoroom.org ***

by zootboy＠sudoroom.org

sudoroom.org : Jan 1 00:19:13 : zootboy : a password is required ; TTY=pts/8 ; PWD=/home/zootboy ; USER=root ; COMMAND=/usr/bin/less /var/log/apache2/error.log

3 years

← Newer
1
...
24
25
26
27
28
29
30
...
89
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

sudo-sys