On Sat, Jul 28, 2012 at 7:21 PM, Jorge Gallegos <[email protected]> wrote: > > Hi, > > I am using the below unit file to manage uwsgi in fedora (I maintain the > fedora package, and am working on the systemd integration for f18):
[...] > And I am so far getting two issues: > > 1) stopping/restarting the service throws puts it in "failed state", > like so: [...] > The process appears as "failed" even tho I only did a systemctl stop. At first > I thought it was because of the way uwsgi reacts to TERM, and so that's > why I am using the --stop and --reload calls in the systemd unit file, > but that made no difference. Should I use die-on-term instead? am I > missing something? the problem here i think is due your your using an outside process to kill/reload the service, this is neither necessary or ideal. ... remove `ExecStop` and replace with: KillSignal=SIGINT ... replace `ExecReload` with: ExecReload=/bin/kill -HUP $MAINPID ... you don't even need pidfiles :-) they have never been reliable anyways. > 2) /var/log/messages gets a ton of these log lines: > > Jul 28 17:12:07 localhost systemd[1]: uwsgi.service: Got notification > message from PID 4678, but reception only permitted for PID 4677 > > I assume is because the emperor is polling the location of the configs > (in this case /etc/uwsgi.d) for new config files, but the way it is > interacting with systemd doesn not quite match. I will probably change > this to /var/log/uwsgi.log but wanted to know why this is happening. this one is possibly related to my comments above -- i'm not 100% sure offhand -- might be a bug too, or some other misconfiguration. ... either way, if need be, it can likely be worked around by adding NotifyAccess=all ... to the `uwsgi.service` file. -- C Anthony _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
