sudo-sys

sudo-sys@sudoroom.org

2 participants
874 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)

2 years, 2 months

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

by root＠humans.sudoroom.org

2 years, 2 months

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

by root＠humans.sudoroom.org

2 years, 2 months

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

by root＠humans.sudoroom.org

2 years, 2 months

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

by root＠humans.sudoroom.org

2 years, 3 months

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

by root＠humans.sudoroom.org

2 years, 3 months

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

2 years, 3 months

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 … [View More]

2 years, 3 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 … [View More]

2 years, 3 months

omnidoor issues

by Jake

i got a call that the front door system wasn't working this morning and i guess something went wrong with the USB stuff, also I noticed a lot of stuff like this in syslog which i doubt is related: localhost avahi-daemon[647]: Invalid response packet from host 100.64.66.172. since it was fully clogging syslog (2-5 messages per minute?) I did /etc/init.d/avahi-daemon stop then I saw the reason doorjam was upset, which i believe was the USB hub having a bad day: localhost kernel: [1013706.… [View More]296645] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity localhost kernel: [1013706.312473] usb 1-1.1: usbfs: usb_submit_urb returned -19 localhost kernel: [1013706.312542] usb 1-1.1: usbfs: usb_submit_urb returned -19 localhost kernel: [1013706.312573] usb 1-1.1: usbfs: usb_submit_urb returned -19 localhost kernel: [1013706.312604] usb 1-1.1: usbfs: usb_submit_urb returned -19 localhost kernel: [1013706.312629] usb 1-1.1: usbfs: usb_submit_urb returned -19 localhost kernel: [1013706.312653] usb 1-1.1: usbfs: usb_submit_urb returned -19 localhost kernel: [1013706.317080] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate localhost node[10334]: Magstripe reader not found. Exiting. localhost kernel: [1013706.331416] ftdi_sio ttyUSB0: urb failed to clear flow control localhost kernel: [1013706.337926] ftdi_sio ttyUSB0: usb_serial_generic_submit_read_urb - usb_submit_urb failed: -19 localhost kernel: [1013706.348097] ftdi_sio ttyUSB0: error from flowcontrol urb localhost systemd[1]: doorjam.service: main process exited, code=exited, status=1 localhost systemd[1]: doorjam.service holdoff time over, scheduling restart. localhost systemd[1]: Unit doorjam.service entered failed state. localhost systemd[1]: doorjam.service start request repeated too quickly, refusing to start. so I rebooted it. But then it didn't come up on the network, so I asked Sierk to power cycle it, which he did (by unplugging and replugging both USB plugs from the white USB power supply) and then he tested that his card was working. and then I did rwroot chmod a-x /etc/init.d/avahi-daemon but I understand this will stop us broadcasting omnidoor.local until it's fixed. I also modified /etc/init.d/boot_scripts.sh to disable "timestamp" which was adjusting the system clock to May 15 2014 for no good reason. also, and this has been an issue for a while, ntpd fails when it runs (once at boot), even though it works if run after the network and dns is stable. It gets called from /etc/init.d/timesync it would be great if this system had reliable timestamps since we need to look at the log so much for door card activity (when people register new cards they tell us when they swiped their new card) anyone want to help? -jake [View Less]

2 years, 3 months

← Newer
1
...
20
21
22
23
24
25
26
...
88
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

sudo-sys