Sorry, I didn't received your reply. No, it is not in the spam :)
Anyway this is the vassal log:
**
*** Starting uWSGI 2.0.16 (64bit) on [Wed Feb 14 11:40:01 2018] ***
compiled with version: 6.3.0 20170516 on 14 February 2018 09:21:34
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: /etc/djangoapp/uwsgi/vassals
detected binary path: /usr/local/bin/uwsgi
dropping root privileges as early as possible
chdir() to /var/www/djangoapp/djangoapp/
your processes number limit is 15277
your memory page size is 4096 bytes
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /tmp/django.socket fd 3
dropping root privileges after socket binding
Python version: 2.7.13 (default, Nov 24 2017, 17:33:09) [GCC 6.3.0 20170516]
Set PythonHome to /var/www/djangoapp/venv/
*** Python threads support is disabled. You can enable it with
--enable-threads ***
Python main interpreter initialized at 0x55e54fe9a420
dropping root privileges after plugin initialization
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 1209231 bytes (1180 KB) for 8 cores
*** Operational MODE: preforking ***
WSGI app 0 (mountpoint='') ready in 10 seconds on interpreter
0x55e54fe9a420 pid: 29736 (default app)
dropping root privileges after application loading
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 29736)
spawned uWSGI worker 1 (pid: 3, cores: 1)
spawned uWSGI worker 2 (pid: 30001, cores: 1)
spawned uWSGI worker 3 (pid: 30002, cores: 1)
spawned uWSGI worker 4 (pid: 30003, cores: 1)
spawned uWSGI worker 5 (pid: 30004, cores: 1)
spawned uWSGI worker 6 (pid: 30005, cores: 1)
spawned uWSGI worker 7 (pid: 30006, cores: 1)
spawned uWSGI worker 8 (pid: 30007, cores: 1)
***
This is the log when the vassal is not ready to accept requests, but
it is perfectly the same when it works with exception of ids and time.
Thanks,
Luigi
On Wed, Feb 14, 2018 at 12:00 PM, <uwsgi-requ...@lists.unbit.it> wrote:
> Send uWSGI mailing list submissions to
> uwsgi@lists.unbit.it
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
> or, via email, send a message with subject or body 'help' to
> uwsgi-requ...@lists.unbit.it
>
> You can reach the person managing the list at
> uwsgi-ow...@lists.unbit.it
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of uWSGI digest..."
>
>
> Today's Topics:
>
> 1. How to debug uwsgi configurations? (Luigi Cirillo)
>2. Re: How to debug uwsgi configurations? (Riccardo Magliocchetti)
>
>
> --
>
> Message: 1
> Date: Wed, 14 Feb 2018 09:18:18 +0000
> From: Luigi Cirillo <appo...@gmail.com>
> To: uwsgi@lists.unbit.it
> Subject: [uWSGI] How to debug uwsgi configurations?
> Message-ID:
> <CAG0Ki35dAwX4a+3odHOSexR3Zcm=4g5hy8qqf6pz55kw6vh...@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> 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 d
