On Mon, 17 Sep 2018 19:34:00 +0200
Jonas Smedegaard <jo...@jones.dk> wrote:
> No wait, sorrym, not even that makes sense to me.
>
> Please describe exactly what failed before above change which succeeds
> with that change applied. I.e. which uwsgi file paths were ignored
> before which now gets included?
>
Yes, you are right. In the end after some more test, I found out that the
problem is that if you create a new vm, install uwsgi, configure and such, the
first time you try to start it silently fail:
root@sobenio:~# systemctl start uwsgi
root@sobenio:~# systemctl status uwsgi
● uwsgi.service - LSB: Start/stop uWSGI server instance(s)
Loaded: loaded (/etc/init.d/uwsgi; generated)
Active: active (exited) since Wed 2018-09-19 19:27:15 UTC; 4min 7s ago
Docs: man:systemd-sysv-generator(8)
Tasks: 0 (limit: 4915)
Memory: 0B
CGroup: /system.slice/uwsgi.service
root@sobenio:~# systemctl stop uwsgi
root@sobenio:~# systemctl start uwsgi
root@sobenio:~# systemctl status uwsgi
● uwsgi.service - LSB: Start/stop uWSGI server instance(s)
Loaded: loaded (/etc/init.d/uwsgi; generated)
Active: active (running) since Wed 2018-09-19 19:31:30 UTC; 2s ago
Docs: man:systemd-sysv-generator(8)
Process: 10058 ExecStop=/etc/init.d/uwsgi stop (code=exited, status=0/SUCCESS)
Process: 10098 ExecStart=/etc/init.d/uwsgi start (code=exited,
status=0/SUCCESS)
Tasks: 7 (limit: 4915)
Memory: 76.9M
CGroup: /system.slice/uwsgi.service
├─10206 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini
/etc/uwsgi/apps-enabled/searx.ini --daemoni
├─10212 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini
/etc/uwsgi/apps-enabled/searx.ini --daemoni
└─10213 /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini
/etc/uwsgi/apps-enabled/searx.ini --daemoni
Sorry for the noise. The initial problem (can't open pid file) was caused by
not having set the UWSGI_DEB_* variables, when I launched manually uwsgi.
The more frustrating things is the difficult to debug this kind of problem (I
also hit the bug #900174 during test, and having no autoload=true in
default.ini would help), where uwsgi don't start but no significant output is
given. I suggest to document the way to manually launch, that is very useful to
troubleshooting. You can find in bug #900174, but I repost here:
# UWSGI_DEB_CONFNAME=hello UWSGI_DEB_CONFNAMESPACE=app uwsgi --ini
/usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/hello.ini
Thanks,
Diego.
--
Diego Roversi <die...@tiscali.it>
