Welcome to Wittenberg!

Author Topic: Webhosting 508 errors  (Read 479 times)

Offline Miestră Schivă, UrN

  • Prime Minister
  • Citizen
  • Posts: 707
  • Large and In Charge
    • Talossan since: 2004-06-12

    • View Profile
    • Free Democrats of Talossa
Webhosting 508 errors
« on: February 22, 2020, 04:49:15 PM »
So, er... is there anything we can do about this?

And that includes the possibility of paying for better service from DeRoyal.


Prime Minister of the Kingdom of Talossa. Ask me anything.

"IS INACTIVITY BAD? I THINK NOT!" - Lord Hooligan
"It probably would be a bit helpful if you resigned and became inactive..." - Sir A. Davinescù

luc

  • Guest
Re: Webhosting 508 errors
« Reply #1 on: February 23, 2020, 04:16:32 PM »
First off, the wording of the 508 error is misleading, and by the way error 508 does not even exist as a standard HTML code. The problem is not bandwidth, it's simply 100% CPU usage on our server. This happens routinely (every Sunday) for a few seconds when Witt and Wiki are backed up.

Regarding yesterday's lengthy outage, it was caused by a number of identical processes clogging up the resources. These processes are all instances of the php-cgi parser, so I assume that something, somewhere, is freezing the parser. (Note that you can't see this through cPanel, you have to manually SSH in.)

There is an "easy" temporary fix, until we troubleshoot further - simply schedule a killall -9 "php" as a cron job, every few minutes. Since normal php requests take less than seconds, you would be very unlucky to kill a legit request (and I don't think it would be a huge hassle if it happened), while you should easily clear away any stuck processes.