Opened 5 years ago

Closed 3 years ago

#17081 closed Bug (wontfix)

runfcgi with daemonize=True requires aboslute path for pidfile parameter

Reported by: bernhard.hollaender@… Owned by: nobody
Component: Core (Management commands) Version: 1.3
Severity: Normal Keywords: runfcgi
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


I was unable to start the fcgi server with the deamonize option set to true. The problem was that the PID file was specified using a relative path:

$ python runfcgi method=prefork host=localhost daemonize=true port=9000

Unfortunately this did not return any error message, the process just returned but no daemon was created. Changin the pidfile option to an absolute path solved the issue.

The same issue was reported here:

Observed on Ubuntu 10.10, python 2.6.6

Change History (3)

comment:1 Changed 5 years ago by Alex Gaynor

Needs documentation: unset
Needs tests: unset
Patch needs improvement: unset
Triage Stage: UnreviewedAccepted

As best I can tell this is because daemonize changes the cwd. Marking as accepted because it sounds right and I have no idea how to run fcgi.

comment:2 Changed 5 years ago by Aymeric Augustin

Component: UncategorizedCore (Management commands)

comment:3 Changed 3 years ago by Tim Graham

Resolution: wontfix
Status: newclosed

runfcgi is being deprecated in Django 1.7.

Note: See TracTickets for help on using tickets.
Back to Top