Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am running a uwsgi-python server under ubuntu 10.04. I use upstart to start/stop a uwsgi daemon(daemonize option is set for uwsgi).

Start and stop commands work fine, but when i try to reload my job, it won't work. The reason for this is that upstart associates wrong pid to my job, which is also a uwsgi process but not a master process. Master process is spawned third(two forks for daemonization) and upstart with expect daemon stanza expects second forked process to be the main.

So I was wondering is there a way to force upsart to associate my job with uwsgi master process ID or any other workaround with this issue?

share|improve this question

1 Answer 1

up vote 0 down vote accepted

do not daemonize under upstart, it is not needed

share|improve this answer
    
Thanks! Removing daemonize option and changing to expect fork seems to work fine –  Alex Tsvetkov Sep 26 '11 at 11:18

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.