Hi! So, the problem was that we ran out of disk space. ppl also reported that DEBUG=True... All caused by not working Apache logrotate it seems. This needs further investigation. For the moment: I moved away the access_log and set reserved space on the ext FS to 0. We now have some GB available again.
I'll try to copy over the logs and compress them locally - but this will take some time. Since no logrotate was installed, I installed it now, I guess that's the simple reason why it wasn't working :-[ However, thanks guys for reporting/reaching out! Next time, please try to reach out on Telegram - these messages usually reach my attention faster (esp. when on PTO like currently) :-) Oliver On Tue, May 26, 2020 at 3:27 PM clime <cli...@gmail.com> wrote: > > > On Tuesday, 26 May 2020, Oliver Falk <oli...@linux-kernel.at> wrote: > >> Yes. I just noticed, something is fishy. >> I’ve fixed it for the moment, but will continue with further >> investigations later. >> >> Oliver >> > > > Do you know what went wrong? Sry i didn't catch this earlier. > > >> >> Niklas Poslovski <ni....@yandex.com> schrieb am Di. 26. Mai 2020 um >> 11:46: >> >>> Hey there. >>> we currently have a server outage at Libravatar. >>> Looks like the ivatar software crashed while the reverse proxy is still >>> working. >>> I do not have SSH access to our current server. >>> Can someone who has access please fix that problem? >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~libravatar-fans >>> Post to : libravatar-fans@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~libravatar-fans >>> More help : https://help.launchpad.net/ListHelp >>> >>
_______________________________________________ Mailing list: https://launchpad.net/~libravatar-fans Post to : libravatar-fans@lists.launchpad.net Unsubscribe : https://launchpad.net/~libravatar-fans More help : https://help.launchpad.net/ListHelp