Forums

No changes were made, but server started getting > 100 seconds (not ms) response time. On pc same project works. Constant OS error. And harakiri on worker. Is it some problem on your end? 2025-10-23 09:42:27 DAMN ! worker 1 (pid: 43) died, killed by signal 9 :( trying respawn ... 2025-10-23 09:42:27 Respawned uWSGI worker 1 (new pid: 46) 2025-10-23 09:42:27 spawned 2 offload threads for uWSGI worker 1 2025-10-23 09:42:30 Thu Oct 23 09:42:30 2025 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request / (ip 10.0.0.73) !!! 2025-10-23 09:42:30 Thu Oct 23 09:42:30 2025 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during GET / (10.0.0.73) 2025-10-23 09:42:30 announcing my loyalty to the Emperor... 2025-10-23 09:42:30 Thu Oct 23 09:42:30 2025 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request / (ip 10.0.0.73) !!! 2025-10-23 09:42:30 Thu Oct 23 09:42:30 2025 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during HEAD / (10.0.0.73) 2025-10-23 09:47:31 Thu Oct 23 09:47:30 2025 - *** HARAKIRI ON WORKER 1 (pid: 46, try: 1, graceful: yes) *** 2025-10-23 09:47:32 Thu Oct 23 09:47:30 2025 - HARAKIRI !!! worker 1 status !!! 2025-10-23 09:47:32 Thu Oct 23 09:47:30 2025 - HARAKIRI [core 0] 10.0.0.73 - GET / since 1761201750 2025-10-23 09:47:32 Thu Oct 23 09:47:30 2025 - HARAKIRI !!! end of worker 1 status !!! 2025-10-23 09:47:32 Thu Oct 23 09:47:30 2025 - HARAKIRI triggered by worker 1 core 0 !!! 2025-10-23 09:47:32 Thu Oct 23 09:47:31 2025 - *** HARAKIRI ON WORKER 1 (pid: 46, try: 2, graceful: no) *** 2025-10-23 09:47:32 Thu Oct 23 09:47:31 2025 - HARAKIRI !!! worker 1 status !!! 2025-10-23 09:47:32 Thu Oct 23 09:47:31 2025 - HARAKIRI [core 0] 10.0.0.73 - GET / since 1761201750 2025-10-23 09:47:32 Thu Oct 23 09:47:31 2025 - HARAKIRI !!! end of worker 1 status !!! 2025-10-23 09:47:32 Thu Oct 23 09:47:31 2025 - HARAKIRI triggered by worker 1 core 0 !!! 2025-10-23 09:47:32 DAMN ! worker 1 (pid: 46) died, killed by signal 9 :( trying respawn ... 2025-10-23 09:47:32 Respawned uWSGI worker 1 (new pid: 49) 2025-10-23 09:47:32 spawned 2 offload threads for uWSGI worker 1

Do you know what is slow for you? Is it some computation? Db query? Filesystem operation? Some external API call? Add some logging to your code to check that.

Same here, i start getting 499 and 502 errors all over the place, and response time is super slow when it does not fail

[23/Oct/2025:08:49:58 +0000] "GET / HTTP/1.1" 200 10256 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:144.0) Gecko/20100101 Firefox/144.0" "xxx response-time=46.379

[23/Oct/2025:08:48:38 +0000] "GET / HTTP/1.1" 200 10253 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:144.0) Gecko/20100101 Firefox/144.0" "xxx" response-time=181.520

For comparison, this is how it was before, 0.592 vs 181 and 46 now. No changes, no deploys, no nothing. So surely a bug/outage or something from your side?

[23/Oct/2025:00:12:23 +0000] "HEAD / HTTP/1.1" 200 0 "https://klinikkspiren.no" "Mozilla/5.0+(compatible; UptimeRobot/2.0; http://www.uptimerobot.com/)" "xxx" response-time=0.592

Also 504 loadbalancer error was displayed front end to user after 15 min load but no successful response

Same here. My API requests timing out. Simple python prints in the bash console also take extremely long:

11:52 ~ $ time python -c "print('hello')"
hello
real    0m14.671s
user    0m0.062s
sys     0m0.013s
11:52 ~ $ time python -c "print('hello')"
hello
real    0m1.011s
user    0m0.068s
sys     0m0.009s
11:52 ~ $ time python -c "print('hello')"
hello
real    0m0.292s
user    0m0.062s
sys     0m0.012s

Can't even load a console stucks on (written below) even when the app and all tasks are disabled, so it's likely the issue on pythonanywhere end.

Loading console... Preparing execution environment...

Edit:

Does not stuck, but works so slow that it is impossible to use

Been going on for 6 hours here already according to my monitoring on uptimerobot with top of 23006 ms vs 600 ms yesterday. Insane that no one has answered any of us, I have reached out in 3 different channels. One would think this should have top priority........

We had some storage server issues yesterday, we believe it's been fixed. Please report back if you still have those issues.