[pkg-uWSGI-devel] Bug#969372: uwsgi-emperor: SysV init script does nothing

[Sam]

Hi there

I encounter the exact same behaviour with:

/etc/debian_version: bullseye/sid

dpkg -l | grep uwsgi:
ii  uwsgi-core                        2.0.19.1-3+b1                  amd64        fast, self-healing application container server (core)
ii  uwsgi-emperor                     2.0.19.1-3+b1                  amd64        fast, self-healing application container server (emperor scripts)
ii  uwsgi-plugin-python3              2.0.19.1-3+b1                  amd64        WSGI plugin for uWSGI (Python 3)

changes in /etc/uwsgi-emperor/emperor.ini:

    + emperor-on-demand-directory = /var/uwsgi

Sam


Quoting Vlastimil Zima (2020-11-06 15:36:47)
> Package: uwsgi-emperor
> Version: 2.0.19.1-3+b1
> Followup-For: Bug #969372
> 
> Hi Thomas,
> 
> indeed, I have a number of vassals configured, actually I use emperor
> for web development for several years now.
> 
> At first, I noticed that the emperor haven't start after reboot.
> I have tried to start it with systemd, but with no success. Systemd
> only reports the process as "started" but it's not running
> (`ps -ef | grep uwsgi`).
> 
> 
> Here's a relevant output of terminal commands:
> 
> $ sudo service uwsgi-emperor start
> $ sudo service uwsgi-emperor status
> ● uwsgi-emperor.service - LSB: Start/stop uWSGI server instance(s)
>      Loaded: loaded (/etc/init.d/uwsgi-emperor; generated)
>      Active: active (exited) since Fri 2020-11-06 09:23:17 CET; 1s ago
>        Docs: man:systemd-sysv-generator(8)
>     Process: 889151 ExecStart=/etc/init.d/uwsgi-emperor start (code=exited, status=0/SUCCESS)
> 
> Nov 06 09:23:17 queeg-500 systemd[1]: Starting LSB: Start/stop uWSGI server instance(s)...
> Nov 06 09:23:17 queeg-500 systemd[1]: Started LSB: Start/stop uWSGI server instance(s).
> $ ps -ef | grep uwsgi
> vzima     889177  887414  0 09:23 pts/5    00:00:00 grep uwsgi
> 
> 
> Despite this, I can start the emperor manually using command composed on /etc/init.d/uwsgi-emperor:
> 
> $ sudo /usr/bin/uwsgi --ini /etc/uwsgi-emperor/emperor.ini --die-on-term --pidfile /run/uwsgi-emperor.pid --daemonize /var/log/uwsgi/emperor.log
> 
> I also encounter the PID file bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934731,
> so I need to delete PID file manually.
> 
> Regards,
> 
> Vlastimil Zíma
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (500, 'testing'), (90, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads)
> Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
> Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages uwsgi-emperor depends on:
> ii  uwsgi-core  2.0.19.1-3+b1
> 
> uwsgi-emperor recommends no packages.
> 
> uwsgi-emperor suggests no packages.
> 
> -- Configuration Files:
> /etc/uwsgi-emperor/emperor.ini changed:
> [uwsgi]
> master = true
> workers = 2
> no-orphans = true
> log-date = true
> uid = www-data
> gid = www-data
> emperor = /etc/uwsgi-emperor/vassals
> emperor-tyrant = true
> cap = setgid,setuid
> 
> 
> -- no debconf information
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-uwsgi-devel/attachments/20201106/9dba74fb/attachment.sig>