FS#43249 - [uwsgi] systemd configuration for emperor

Attached to Project: Community Packages
Opened by Matthew G (djmattyg007) - Saturday, 27 December 2014, 16:09 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 10 January 2015, 02:00 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Daniel Wallace (gtmanfred)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

The systemd configuration for the uwsgi emperor has two issues.

Firstly, there is no systemd-tmpfiles configuration file for the emperor. This makes it more difficult to use a unix socket (rather than a TCP socket) than it needs to be. From what I can tell, it should be as simple as copying the existing tmpfiles config file in the Arch package a 2nd time, with a filename that matches that of the emperor service unit file. My reasoning for this is that the example provided here matches that of the currently available file:
https://github.com/unbit/uwsgi-docs/blob/master/Systemd.rst#putting-sockets-in-run

Secondly, when using the emperor with a unix socket, this message gets spammed into the syslog: "Got notification message from PID 123, but reception only permitted for main PID 456". This issue is described more fully at the following URL:
https://github.com/unbit/uwsgi/issues/797
To summarise, a patch to the documentation that provides an example service unit file has been submitted and committed, and it would be great if the unit file in the Arch package could also be updated (as this appears to be a distro's responsibility and is not provided out of the uwsgi box).
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Saturday, 10 January 2015, 02:00 GMT
Reason for closing:  Fixed
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 28 December 2014, 18:13 GMT
/run/uwsgi is already being created! Why isn't that all you need? You don't need a second systemd-tmpfiles config file for that.

I did fix the other problem though.
Comment by Matthew G (djmattyg007) - Sunday, 28 December 2014, 20:58 GMT
I seem to recall that /run/uwsgi isn't created if you never start/enable the main uwsgi service (ie you only ever use the emperor).
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 30 December 2014, 15:21 GMT
I don't think that's the case. Can you test?

Loading...