passenger-status no longer works after upgrade to precise
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
passenger (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
After upgrading from Lucid to Precise, passenger itself is working,
but passenger-status no longer works at all:
| root@redcurrant:~# passenger-status
| *** Cleaning stale folder /tmp/passenger.904
| ERROR: Phusion Passenger doesn't seem to be running.
| root@redcurrant:~# passenger-status 904
| /usr/sbin/
| from /usr/sbin/
| from /usr/sbin/
| root@redcurrant:~# ls -lR /tmp/passenger.904/
| /tmp/passenger.
| total 4
| d-ws-wx-wx 2 puppet puppet 4096 Jul 19 12:58 backends
|
| /tmp/passenger.
| total 0
| srw------- 1 root root 0 Jul 19 12:58 backend.
| srw------- 1 root root 0 Jul 19 12:58 backend.
| srw------- 1 root root 0 Jul 19 12:58 backend.
| srw------- 1 root root 0 Jul 19 12:58 backend.
| root@redcurrant:~#
passenger-
The problem seems to be with the PID that is used for the temp-directory:
ps: phusion_ passenger/ ApplicationPool ServerExecutabl e 0 /usr/lib/ phusion_ passenger/ passenger- spawn-server /usr/bin/ruby /tmp/passenger.7538
root 7558 1 0 14:35 ? 00:00:00 /usr/sbin/apache2 -k start
root 7572 7558 0 14:35 ? 00:00:00 /usr/lib/
The directory should be /tmp/passenger.7558 (the PID of the Apache main process) not 7538. If you rename the directory you can successfully execute the passenger-status program and it will return the correct information. But I don't know if this will break the application at some other point.