Forums

Django server is unresponsive. How do I solve this?

Something went wrong :-( Something went wrong while trying to load this site; please try again later.

Debugging tips If this is your site, and you just reloaded it, then the problem might simply be that it hasn't loaded up yet. Try refreshing this page and see if this message disappears.

If you keep getting this message, you should check your site's server and error logs for any messages.

Error code: 504-backend

2024-09-05 19:52:40 Thu Sep 5 19:52:40 2024 - received message 0 from emperor 2024-09-05 19:52:40 SIGINT/SIGTERM received...killing workers... 2024-09-05 19:53:13 uwsgi_master_manage_emperor()/read(): Bad file descriptor [core/emperor.c line 2442] 2024-09-05 19:53:13 lost connection with my emperor !!! 2024-09-05 19:53:13 VACUUM: unix socket /var/sockets/hanhyunwook.pythonanywhere.com/socket removed. 2024-09-05 19:53:14 *** Starting uWSGI 2.0.20 (64bit) on [Thu Sep 5 10:53:14 2024] *** 2024-09-05 19:53:14 compiled with version: 9.4.0 on 22 July 2022 18:35:26 2024-09-05 19:53:14 os: Linux-6.5.0-1022-aws #22~22.04.1-Ubuntu SMP Fri Jun 14 16:31:00 UTC 2024 2024-09-05 19:53:14 nodename: blue-liveweb6 2024-09-05 19:53:14 machine: x86_64 2024-09-05 19:53:14 clock source: unix 2024-09-05 19:53:14 pcre jit disabled 2024-09-05 19:53:14 detected number of CPU cores: 4 2024-09-05 19:53:14 current working directory: /home/hanhyunwook 2024-09-05 19:53:14 detected binary path: /usr/local/bin/uwsgi 2024-09-05 19:53:14 *** dumping internal routing table *** 2024-09-05 19:53:14 [rule: 0] subject: path_info regexp: .svgz$ action: addheader:Content-Encoding:gzip 2024-09-05 19:53:14 *** end of the internal routing table *** 2024-09-05 19:53:14 chdir() to /home/hanhyunwook/ 2024-09-05 19:53:14 your processes number limit is 256 2024-09-05 19:53:14 your memory page size is 4096 bytes 2024-09-05 19:53:14 detected max file descriptor number: 123456 2024-09-05 19:53:14 building mime-types dictionary from file /etc/mime.types... 2024-09-05 19:53:14 567 entry found 2024-09-05 19:53:14 lock engine: pthread robust mutexes 2024-09-05 19:53:14 thunder lock: disabled (you can enable it with --thunder-lock) 2024-09-05 19:53:14 uwsgi socket 0 bound to UNIX address /var/sockets/hanhyunwook.pythonanywhere.com/socket fd 3 2024-09-05 19:53:14 Python version: 3.10.5 (main, Jul 22 2022, 17:09:35) [GCC 9.4.0] 2024-09-05 19:53:14 PEP 405 virtualenv detected: /home/hanhyunwook/env_todo 2024-09-05 19:53:14 Set PythonHome to /home/hanhyunwook/env_todo 2024-09-05 19:53:14 *** Python threads support is disabled. You can enable it with --enable-threads *** 2024-09-05 19:53:14 Python main interpreter initialized at 0x56510d795e90 2024-09-05 19:53:14 your server socket listen backlog is limited to 100 connections 2024-09-05 19:53:14 your mercy for graceful operations on workers is 60 seconds 2024-09-05 19:53:14 setting request body buffering size to 65536 bytes 2024-09-05 19:53:14 mapped 334256 bytes (326 KB) for 1 cores 2024-09-05 19:53:14 *** Operational MODE: single process *** 2024-09-05 19:53:14 initialized 38 metrics 2024-09-05 19:53:14 WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x56510d795e90 pid: 1 (default app) 2024-09-05 19:53:14 *** uWSGI is running in multiple interpreter mode *** 2024-09-05 19:53:14 gracefully (RE)spawned uWSGI master process (pid: 1) 2024-09-05 19:53:14 spawned uWSGI worker 1 (pid: 2, cores: 1) 2024-09-05 19:53:14 metrics collector thread started 2024-09-05 19:53:14 spawned 2 offload threads for uWSGI worker 1 2024-09-05 19:53:15 announcing my loyalty to the Emperor... 2024-09-05 19:59:39 Thu Sep 5 19:59:38 2024 - *** HARAKIRI ON WORKER 1 (pid: 2, try: 1) *** 2024-09-05 19:59:39 Thu Sep 5 19:59:38 2024 - HARAKIRI !!! worker 1 status !!! 2024-09-05 19:59:39 Thu Sep 5 19:59:38 2024 - HARAKIRI [core 0] 10.0.5.105 - GET /todos/ since 1725533677 2024-09-05 19:59:39 Thu Sep 5 19:59:38 2024 - HARAKIRI !!! end of worker 1 status !!! 2024-09-05 19:59:39 DAMN ! worker 1 (pid: 2) died, killed by signal 9 :( trying respawn ... 2024-09-05 19:59:39 Respawned uWSGI worker 1 (new pid: 7) 2024-09-05 19:59:39 spawned 2 offload threads for uWSGI worker 1 2024-09-05 20:04:41 Thu Sep 5 20:04:40 2024 - *** HARAKIRI ON WORKER 1 (pid: 7, try: 1) *** 2024-09-05 20:04:41 Thu Sep 5 20:04:40 2024 - HARAKIRI !!! worker 1 status !!! 2024-09-05 20:04:41 Thu Sep 5 20:04:40 2024 - HARAKIRI [core 0] 10.0.5.105 - GET /admin/ since 1725533979 2024-09-05 20:04:41 Thu Sep 5 20:04:40 2024 - HARAKIRI !!! end of worker 1 status !!! 2024-09-05 20:04:41 DAMN ! worker 1 (pid: 7) died, killed by signal 9 :( trying respawn ... 2024-09-05 20:04:41 Respawned uWSGI worker 1 (new pid: 10) 2024-09-05 20:04:41 spawned 2 offload threads for uWSGI worker 1 2024-09-05 20:04:41 Thu Sep 5 20:04:41 2024 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request / (ip 10.0.5.105) !!! 2024-09-05 20:04:41 Thu Sep 5 20:04:41 2024 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during GET / (10.0.5.105) 2024-09-05 20:04:41 announcing my loyalty to the Emperor... 2024-09-05 20:04:41 Thu Sep 5 20:04:41 2024 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request / (ip 10.0.5.105) !!! 2024-09-05 20:04:41 Thu Sep 5 20:04:41 2024 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during GET / (10.0.5.105)

Thanks for letting us know! It looks like after our system maintenance this morning, some SQLite databases were stuck in a "locked" state where processes would hang when they tried to access them. We just restarted the file locking service on the file server associated with your account, and your site is up and running now, so we think that was probably the cause of the issues you were seeing.