Sometimes (not always but often) it happens one of the two vassals is never ready to accept requests. Following the logs, in this case djangoapp_uwsgi.ini doesn't accept requests. Do you know how I can obtain info about where uwsgi get stuck?
;uWSGI instance configuration [uwsgi] ini = /etc/djangoapp/uwsgi/emperor.ini emperor = /etc/djangoapp/uwsgi/vassals die-on-term = true offload-threads = 1 uid = www-data gid = www-data logto = /var/log/uwsgi/emperor_uwsgi.log worker-reload-mercy = 2 thunder-lock = true show-config = true reload-mercy = 2 ;end of configuration *** Starting uWSGI 2.0.15 (64bit) on [Tue Feb 13 16:16:52 2018] *** compiled with version: 6.3.0 20170516 on 08 February 2018 15:11:52 os: Linux-4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) nodename: server-master machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 4 current working directory: / detected binary path: /usr/local/bin/uwsgi setgid() to 33 set additional group 4 (adm) setuid() to 33 *** WARNING: you are running uWSGI without its master process manager *** your processes number limit is 15277 your memory page size is 4096 bytes detected max file descriptor number: 1024 *** starting uWSGI Emperor *** *** has_emperor mode detected (fd: 7) *** [uWSGI] getting INI configuration from djangoapp_uwsgi.ini *** has_emperor mode detected (fd: 8) *** [uWSGI] getting INI configuration from djangoapp_ws_uwsgi.ini Tue Feb 13 16:17:02 2018 - [emperor] vassal djangoapp_uwsgi.ini has been spawned Tue Feb 13 16:17:12 2018 - [emperor] vassal djangoapp_ws_uwsgi.ini has been spawned Tue Feb 13 16:17:12 2018 - [emperor] vassal djangoapp_ws_uwsgi.ini is ready to accept requests Thanks, Luigi _______________________________________________ uWSGI mailing list uWSGI@lists.unbit.it http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
