The culprit was the php5-fpm process. Restarting it fixed it.
Error output from apache:
[Mon May 20 15:36:53.945158 2019] [proxy_fcgi:error] [pid 20480:tid
139913676658432] [client 50.57.61.7:62769] AH01067: Failed to read
FastCGI header
[Mon May 20 15:36:53.945213 2019] [proxy_fcgi:error] [pid 20480:tid
139913676658432] (104)Connection reset by peer: [client
50.57.61.7:62769] AH01075: Error dispatching request to :
Looks like someone set up some kind of status checker that locally
hits blah.sudoroom.org every second?
2019-05-20 15:39:45 127.0.0.1 blah.sudoroom.org "GET
/server-status?auto HTTP/1.1" 200
Was it supposed to inform us that sudoroom.org was down?
--
marc/juul
StatusCake Alert -- statuscake.com
Website Monitoring
Your website https://sudoroom.org has encountered an error.
Reason: Timeout / Connection Refused
To view more details about this error, log into your account now: https://app.statuscake.com/
A few minutes ago, there was a period of a few minutes when the Omni Commons WiFi network stopped working. I wasn’t able to gather any useful details about exactly what went wrong before it got better.
Sent from ProtonMail Mobile
I've now had two odd things happen from Omni over the past few weeks:
First I couldn't log into linkedin. Even accessing the site just
directed me to a weird warning page saying they don't allow Chinese
IPs and giving a phone number (?!) to call for support. At first I
thought it was because they had seen my computer from china, but then
I tried a clean browser which did nothing and then I tried through a
VPN which resolved the issue.
Then I couldn't log into NameCheap but I could reset the password
fine, and then I would just get the same "wrong username or password
message". After contacting support they told me that our IP had been
banned because someone had tried to log into many different accounts
from our IP unsuccessfully.
I'm beginning to suspect that we may have e.g. a rogue windows machine
on our network (could it be the one hooked up to the x-ray machine in
sudo? or one of the machines in CCL?)
Just wanted to put it out there in case we get more data.
--
marc/juul
cron (3.0pl1-127+deb8u2) jessie-security; urgency=medium
* As a reasonable protective measure, crontabs are now limited to 1000 lines
in length per crontab.
The maintainers find it very unlikely that longer crontabs exist; however,
if you do have a use case, please file a bug report with a brief rationale,
and we will consider raising this limit.
-- Christian Kastner <ckk(a)debian.org> Sun, 10 Mar 2019 17:44:13 +0100
