Infinite app load*** HARAKIRI ON WORKER 3 (pid: 16, try: 1) *** : Forums : PythonAnywhere

Start a new topic | Back to all topics | This topic's RSS

Infinite app load* HARAKIRI ON WORKER 3 (pid: 16, try: 1) *

2024-05-31 08:48:07 Fri May 31 08:48:06 2024 - *** HARAKIRI ON WORKER 3 (pid: 16, try: 1) ***

2024-05-31 08:48:08 Fri May 31 08:48:06 2024 - HARAKIRI !!! worker 3 status !!!

2024-05-31 08:48:08 Fri May 31 08:48:06 2024 - HARAKIRI [core 0] 10.0.0.20 - GET /admin/ since 1717144985

2024-05-31 08:48:08 Fri May 31 08:48:06 2024 - HARAKIRI !!! end of worker 3 status !!!

2024-05-31 08:48:08 DAMN ! worker 3 (pid: 16) died, killed by signal 9 :( trying respawn ...

2024-05-31 08:48:08 Respawned uWSGI worker 3 (new pid: 19)

2024-05-31 08:48:08 Fri May 31 08:48:07 2024 - *** HARAKIRI ON WORKER 2 (pid: 13, try: 1) ***

2024-05-31 08:48:08 Fri May 31 08:48:07 2024 - HARAKIRI !!! worker 2 status !!!

2024-05-31 08:48:08 Fri May 31 08:48:07 2024 - HARAKIRI [core 0] 10.0.0.20 - GET /admin/ since 1717144986

2024-05-31 08:48:08 Fri May 31 08:48:07 2024 - HARAKIRI !!! end of worker 2 status !!!

2024-05-31 08:48:08 spawned 2 offload threads for uWSGI worker 3

2024-05-31 08:48:08 DAMN ! worker 2 (pid: 13) died, killed by signal 9 :( trying respawn ...

2024-05-31 08:48:08 Respawned uWSGI worker 2 (new pid: 22)

2024-05-31 08:48:08 spawned 2 offload threads for uWSGI worker 2

2024-05-31 08:48:16 Not Found: /

2024-05-31 08:48:16 announcing my loyalty to the Emperor...

2024-05-31 08:48:38 Not Found: /

What should I do? The app worked correctly yesterday but now I have endless app load

deleted-user-17630876 | 5 posts | May 31, 2024, 8:55 a.m. | permalink

same ,

2024-05-31 10:07:43 announcing my loyalty to the Emperor...
2024-05-31 10:12:45 Fri May 31 10:12:44 2024 - *** HARAKIRI ON WORKER 1 (pid: 2, try: 1) ***
2024-05-31 10:12:45 Fri May 31 10:12:44 2024 - HARAKIRI !!! worker 1 status !!!
2024-05-31 10:12:45 Fri May 31 10:12:44 2024 - HARAKIRI [core 0] 10.0.0.20 - GET /google_sso/login/?next=/ since 1717150063
2024-05-31 10:12:45 Fri May 31 10:12:44 2024 - HARAKIRI !!! end of worker 1 status !!!
2024-05-31 10:12:45 DAMN ! worker 1 (pid: 2) died, killed by signal 9 :( trying respawn ...
2024-05-31 10:12:45 Respawned uWSGI worker 1 (new pid: 10)
2024-05-31 10:12:45 spawned 2 offload threads for uWSGI worker 1
2024-05-31 10:12:46 Fri May 31 10:12:46 2024 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request / (ip 10.0.0.20) !!!
2024-05-31 10:12:46 Fri May 31 10:12:46 2024 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during GET / (10.0.0.20)
2024-05-31 10:12:46 announcing my loyalty to the Emperor...
2024-05-31 10:12:46 Fri May 31 10:12:46 2024 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /api/submission/ (ip 10.0.0.20) !!!
2024-05-31 10:12:46 Fri May 31 10:12:46 2024 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during POST /api/submission/ (10.0.0.20)
2024-05-31 10:12:46 Fri May 31 10:12:46 2024 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request / (ip 10.0.0.20) !!!
2024-05-31 10:12:46 Fri May 31 10:12:46 2024 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during GET / (10.0.0.20)
2024-05-31 10:12:46 Fri May 31 10:12:46 2024 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request / (ip 10.0.0.20) !!!
2024-05-31 10:12:46 Fri May 31 10:12:46 2024 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during GET / (10.0.0.20)
2024-05-31 10:12:46 Fri May 31 10:12:46 2024 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request / (ip 10.0.0.20) !!!
2024-05-31 10:12:46 Fri May 31 10:12:46 2024 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during GET / (10.0.0.20)
2024-05-31 10:15:47 Fri May 31 10:15:46 2024 - *** HARAKIRI ON WORKER 2 (pid: 5, try: 1) ***
2024-05-31 10:15:47 Fri May 31 10:15:46 2024 - HARAKIRI !!! worker 2 status !!!
2024-05-31 10:15:47 Fri May 31 10:15:46 2024 - HARAKIRI [core 0] 10.0.0.20 - GET /google_sso/login/?next=/ since 1717150245
2024-05-31 10:15:47 Fri May 31 10:15:46 2024 - HARAKIRI !!! end of worker 2 status !!!
2024-05-31 10:15:47 DAMN ! worker 2 (pid: 5) died, killed by signal 9 :( trying respawn ...
2024-05-31 10:15:47 Respawned uWSGI worker 2 (new pid: 13)
2024-05-31 10:15:47 spawned 2 offload threads for uWSGI worker 2

deleted-user-17534678 | 3 posts | May 31, 2024, 10:23 a.m. | permalink

Error code: 504-loadbalancer

deleted-user-17630876 | 5 posts | May 31, 2024, 10:25 a.m. | permalink

Not that this adds anything new (this seems to be a widespread issue), but same here:

2024-05-31 09:08:57 DAMN ! worker 2 (pid: 73) died, killed by signal 9 :( trying respawn ...
2024-05-31 09:08:57 Respawned uWSGI worker 2 (new pid: 82)
2024-05-31 09:08:57 spawned 2 offload threads for uWSGI worker 2
2024-05-31 09:37:24 Fri May 31 09:37:23 2024 - *** HARAKIRI ON WORKER 1 (pid: 79, try: 1) ***
2024-05-31 09:37:24 Fri May 31 09:37:23 2024 - HARAKIRI !!! worker 1 status !!!
2024-05-31 09:37:24 Fri May 31 09:37:23 2024 - HARAKIRI [core 0] 10.0.0.20 - GET / since 1717147942
2024-05-31 09:37:24 Fri May 31 09:37:23 2024 - HARAKIRI !!! end of worker 1 status !!!
2024-05-31 09:37:24 DAMN ! worker 1 (pid: 79) died, killed by signal 9 :( trying respawn ...
2024-05-31 09:37:24 Respawned uWSGI worker 1 (new pid: 85)
2024-05-31 09:37:24 spawned 2 offload threads for uWSGI worker 1
2024-05-31 11:33:39 Fri May 31 11:33:38 2024 - *** HARAKIRI ON WORKER 1 (pid: 85, try: 1) ***
2024-05-31 11:33:39 Fri May 31 11:33:38 2024 - HARAKIRI !!! worker 1 status !!!
2024-05-31 11:33:39 Fri May 31 11:33:38 2024 - HARAKIRI [core 0] 10.0.0.20 - GET / since 1717154917
2024-05-31 11:33:39 Fri May 31 11:33:38 2024 - HARAKIRI !!! end of worker 1 status !!!
2024-05-31 11:33:39 DAMN ! worker 1 (pid: 85) died, killed by signal 9 :( trying respawn ...
2024-05-31 11:33:39 Respawned uWSGI worker 1 (new pid: 88)
2024-05-31 11:33:39 spawned 2 offload threads for uWSGI worker 1
2024-05-31 11:55:58 announcing my loyalty to the Emperor...
2024-05-31 12:01:00 Fri May 31 12:00:59 2024 - *** HARAKIRI ON WORKER 1 (pid: 88, try: 1) ***
2024-05-31 12:01:00 Fri May 31 12:00:59 2024 - HARAKIRI !!! worker 1 status !!!
2024-05-31 12:01:00 Fri May 31 12:00:59 2024 - HARAKIRI [core 0] 10.0.0.20 - GET /installer.php/ since 1717156558
2024-05-31 12:01:00 Fri May 31 12:00:59 2024 - HARAKIRI !!! end of worker 1 status !!!
2024-05-31 12:01:00 DAMN ! worker 1 (pid: 88) died, killed by signal 9 :( trying respawn ...
2024-05-31 12:01:00 Respawned uWSGI worker 1 (new pid: 91)
2024-05-31 12:01:00 spawned 2 offload threads for uWSGI worker 1
2024-05-31 12:07:48 Fri May 31 12:07:47 2024 - *** HARAKIRI ON WORKER 2 (pid: 82, try: 1) ***
2024-05-31 12:07:48 Fri May 31 12:07:47 2024 - HARAKIRI !!! worker 2 status !!!
2024-05-31 12:07:48 Fri May 31 12:07:47 2024 - HARAKIRI [core 0] 10.0.0.20 - GET / since 1717156966
2024-05-31 12:07:48 Fri May 31 12:07:47 2024 - HARAKIRI !!! end of worker 2 status !!!
2024-05-31 12:07:48 DAMN ! worker 2 (pid: 82) died, killed by signal 9 :( trying respawn ...

deleted-user-17529889 | 4 posts | May 31, 2024, 1:39 p.m. | permalink

Adding my logs of this event for posterity and any chance it may help PythonAnywhere to get things back online.

Blockquote

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 ... 2024-05-31 10:08:25 Respawned uWSGI worker 1 (new pid: 7) 2024-05-31 10:08:25 spawned 2 offload threads for uWSGI worker 1 2024-05-31 10:13:27 Fri May 31 10:13:26 2024 - *** HARAKIRI ON WORKER 1 (pid: 7, try: 1) *** 2024-05-31 10:13:27 Fri May 31 10:13:26 2024 - HARAKIRI !!! worker 1 status !!! 2024-05-31 10:13:27 Fri May 31 10:13:26 2024 - HARAKIRI [core 0] 10.0.0.20 - GET / since 1717164505 2024-05-31 10:13:27 Fri May 31 10:13:26 2024 - HARAKIRI !!! end of worker 1 status !!! 2024-05-31 10:13:27 DAMN ! worker 1 (pid: 7) died, killed by signal 9 :( trying respawn ... 2024-05-31 10:13:27 Respawned uWSGI worker 1 (new pid: 10) 2024-05-31 10:13:27 spawned 2 offload threads for uWSGI worker 1 2024-05-31 10:13:27 Fri May 31 10:13:27 2024 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request / (ip 10.0.0.20) !!! 2024-05-31 10:13:27 Fri May 31 10:13:27 2024 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during GET / (10.0.0.20) 2024-05-31 10:13:27 announcing my loyalty to the Emperor... 2024-05-31 10:13:27 Fri May 31 10:13:27 2024 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request / (ip 10.0.0.20) !!! 2024-05-31 10:13:27 Fri May 31 10:13:27 2024 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during GET / (10.0.0.20)

dbottaro | 7 posts | May 31, 2024, 2:35 p.m. | permalink

please support! Help us!

deleted-user-17630876 | 5 posts | May 31, 2024, 3:35 p.m. | permalink

Now my app is working but what was problem in? Why did it so long be down?

deleted-user-17630876 | 5 posts | May 31, 2024, 3:39 p.m. | permalink

We've been having problems with the storage server where all of your accounts' files are located. We have a partial mitigation in place, but there will still be times when your file access will be too slow. Would you like us to migrate your account to a different file server? The process we have in place to do that works well, except that any forum posts you have made in the past will have a username like "deleted-user-1234" associated with them, and if you have a paid account, or have had one in the past, you would not be able to download your past invoices from the "Account" page (though we would be able to provide them on request).

If you'd like to go ahead with this, it's best to coordinate it over email: drop us a line (including your username, as it's shown underneath your post above) at support@pythonanywhere.com.

giles | 12766 posts | PythonAnywhere staff | May 31, 2024, 5:58 p.m. | permalink

Hi there, I sent two emails to support@pythonanywhere.com titled "Account Migration to Different Server" last Wednesday and Thursday. Not sure if you received them, at any rate there's been no response in 3 business days so I figured I should post here. Can you go forward with a file migration for this account when you get a chance (account name is the same as in the forums)? I'm ok with the aforementioned consequences, saved all invoices.

Much appreciated!

deleted-user-17529889 | 4 posts | June 10, 2024, 9:29 p.m. | permalink

I'm sorry about that, I'm not sure how that happened! I have replied to your email now.

nkahr | 727 posts | PythonAnywhere staff | June 11, 2024, 8:32 a.m. | permalink