Today, May31 2024, I went to load my ticket web app to create a ticket for one of my users and encountered the error: “Something went wrong” ending off with “Error Code: 504-backend.”
I looked through my logs on the server and found a issues like the following:
Server Log: Harakiri on Worker
2024-05-31 10:08:25 Fri May 31 10:08:24 2024 - *** HARAKIRI ON WORKER 1 (pid: 2, try: 1) ***
2024-05-31 10:08:25 Fri May 31 10:08:24 2024 - HARAKIRI !!! worker 1 status !!!
2024-05-31 10:08:25 Fri May 31 10:08:24 2024 - HARAKIRI [core 0] 10.0.0.20 - GET / since 1717164203
2024-05-31 10:08:25 Fri May 31 10:08:24 2024 - HARAKIRI !!! end of worker 1 status !!!
2024-05-31 10:08:25 DAMN ! worker 1 (pid: 2) died, killed by signal 9 :( trying respawn ...
After checking my other logs I realized it’s not my application. There is something amiss over at PythonAnywere. Quite a few users in the forums are mentioning similar errors. “504-loadbalancer” and “504-backend” seem to be cropping up most often.
There is no notification of system status on the PythonAnywhere Dashboard. This would be a nice feature to add down the road once this current outage is fixed.
Some chatter over on the @PythonAnywere on X shows that a DDOS seems to have started sometime yesterday. This could answer the question “What’s wrong over at PythonAnywhere”
Error Log: OSError: write error
My error log shows this message a couple of times.
2024-05-31 10:13:27,385: OSError: write errorThis is not a Django or Python problem. Some critical infrastructure isn’t working properly over at PythonAnywhere.
Update: 5/31/24 11:15am
My ticketing site is working. Will check out the forums to see if anything is posted there.