Opened 13 years ago
Closed 10 years ago
#17081 closed Bug (wontfix)
runfcgi with daemonize=True requires aboslute path for pidfile parameter
| Reported by: | 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 |
Description
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 manage.py runfcgi method=prefork host=localhost daemonize=true port=9000 pidfile=fcgi.pid
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: http://community.webfaction.com/questions/4303/runfcgi-cant-demonize
Observed on Ubuntu 10.10, python 2.6.6
Change History (3)
comment:1 by , 13 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 12 years ago
| Component: | Uncategorized → Core (Management commands) |
|---|
comment:3 by , 10 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
runfcgi is being deprecated in Django 1.7.
Note:
See TracTickets
for help on using tickets.
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.