passenger-status no longer works after upgrade to precise

[James Troup]

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/passenger-status:43:in `show_status': undefined method `status' for nil:NilClass (NoMethodError)
| from /usr/sbin/passenger-status:121:in `start'
| from /usr/sbin/passenger-status:125
| root@redcurrant:~# ls -lR /tmp/passenger.904/
| /tmp/passenger.904/:
| total 4
| d-ws-wx-wx 2 puppet puppet 4096 Jul 19 12:58 backends
|
| /tmp/passenger.904/backends:
| total 0
| srw------- 1 root root 0 Jul 19 12:58 backend.trololololololololololololololololololololololololololololololololololo
| srw------- 1 root root 0 Jul 19 12:58 backend.trololololololololololololololololololololololololololololololololololo
| srw------- 1 root root 0 Jul 19 12:58 backend.trololololololololololololololololololololololololololololololololololo
| srw------- 1 root root 0 Jul 19 12:58 backend.trololololololololololololololololololololololololololololololololololo
| root@redcurrant:~#

passenger-memory-status also doesn't appear to be working as expected.

[Michael Mönch (michael-moench)]

The problem seems to be with the PID that is used for the temp-directory:

ps:
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/phusion_passenger/ApplicationPoolServerExecutable 0 /usr/lib/phusion_passenger/passenger-spawn-server /usr/bin/ruby /tmp/passenger.7538

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.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Alexander Luetjen (luetjen)]

Is there a confirmed workaround for this issue? Wouldn't renaming the folder break another process already writing to the folder now?

[Caspar Clemens Mierau (leitmedium)]

This problem even leads to a malfucntioning passenger: When you run passenger-status, it removes the tmp directory:

root@janitor ~ # passenger-status
*** Cleaning stale folder /tmp/passenger.1154
ERROR: Phusion Passenger doesn't seem to be running.

This means that processes in need of a tmp dir won't work afterwards - e.g. file upload. Example: puppet:

[ pid=10617 file=ext/apache2/Hooks.cpp:727 time=2014-03-13 11:12:17.642 ]:
  Unexpected error in mod_passenger: An error occured while buffering HTTP upload data to a temporary file in /tmp/passenger.1154/webserver_private. This directory doesn't exist, so please make sure that this directory exists, or set the 'PassengerUploadBufferDir' directive to a directory that exists and can be written to.
  Backtrace:
     in 'boost::shared_ptr<Passenger::BufferedUpload> Hooks::receiveRequestBody(request_rec*, const char*)' (Hooks.cpp:1084)
     in 'int Hooks::handleRequest(request_rec*)' (Hooks.cpp:459)

[Logan Rosen (logan)]

Thank you for reporting this bug to Ubuntu.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

[Launchpad Janitor (janitor)]

[Expired for passenger (Ubuntu) because there has been no activity for 60 days.]