The wiki went down at ~9am this morning and showed an error page that said it couldn't access the database.
It took me quite a while to find the cause, which was that unattended-upgrades updated all the mysql packages this morning, which immediately broke the wiki. I was able to roll all packages back to their previous version in order to get the wiki working again.
I then added configs for pinning those package versions until we've figured out what the problem is with upgrading them. (I guess a server restart into the new kernel might be the solution). See /etc/apt/preferences.d/ for those config files.
The wiki went down at ~9am this morning and showed an error page that said it couldn't access the database.
It took me quite a while to find the cause, which was that unattended-upgrades updated all the mysql packages this morning, which immediately broke the wiki. I was able to roll all packages back to their previous version in order to get the wiki working again.
I then added configs for pinning those package versions until we've figured out what the problem is with upgrading them. (I guess a server restart into the new kernel might be the solution). See `/etc/apt/preferences.d/` for those config files.
raucao
self-assigned this 2019-07-26 13:39:54 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The wiki went down at ~9am this morning and showed an error page that said it couldn't access the database.
It took me quite a while to find the cause, which was that unattended-upgrades updated all the mysql packages this morning, which immediately broke the wiki. I was able to roll all packages back to their previous version in order to get the wiki working again.
I then added configs for pinning those package versions until we've figured out what the problem is with upgrading them. (I guess a server restart into the new kernel might be the solution). See
/etc/apt/preferences.d/for those config files.