ERROR: Phusion Passenger doesn't seem to be running...

661 views
Skip to first unread message

Dean Richardson

unread,
Jun 26, 2014, 4:50:09 PM6/26/14
to phusion-...@googlegroups.com
Hi:

I've installed Passenger 4.0.45 on a new linux server running Ubuntu 12.04 LTS. I'm using rbenv to manage ruby versions. I first attempted to install Passenger using the APT repository, but for reasons I now can't recall, I also ended up also installing using Rubygems. This seems to have worked (I was prompted to select Ruby or Python, and I told at the end what lines to add to my apache2.conf file) but may well be the source of my current problems.

I've made the suggested apache2 config changes, and also followed the passenger instructions for deploying an app to a suburi.

Going to the ip address without the suburi gives the default apache2 page. Going to the ip address/suburi gives a 404 error, presumably because my file in sites-available is not being read correctly.

When I try to view passenger-status, I get the following message:

Version: 4.0.45
Date: 2014-06-26 ....
Instance: 2772
*** ERROR: You are not authorized to query the status... Please try again with 'sudo'.

When I try sudo passenger-status, I get:

ERROR: Phusion Passenger doesn't seem to be running.

The last few lines of /var/log/apache2/error.log say:

[ date... time... 2776/hash agents/Watchdog/Main.cpp:728 ]: All Phusion Passenger agents started!
[ date... time...] [notice] Apache/2.2.22 (Ubuntu) Phusion_Passenger/4.0.45 configured -- resuming normal operations

When I do a ps -ef | grep Passenger i see:

root     2776  2772 0 time ? PassengerWatchdog
root     2779  2776 0 time ? PassengerHelperAgent
nobody 2785 2776 0 time ? PassengerLoggingAgent

no sign of any spawn server...

I'd appreciate any advice for getting Passenger running, debugging my configuration files, etc.

Thanks very much!

Dean Richardson
Molex.com

Tinco Andringa

unread,
Jul 8, 2014, 12:01:36 PM7/8/14
to phusion-...@googlegroups.com
Hi Dean,

Sorry for the late response, did you manage to get it to work? It's
normal for there not to be a SpawnServer process.

Kind regards,
Tinco
> --
> You received this message because you are subscribed to the Google Groups
> "Phusion Passenger Discussions" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to phusion-passen...@googlegroups.com.
> To post to this group, send email to phusion-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/phusion-passenger.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/phusion-passenger/26c548bf-a70e-4c93-879a-84cea09bda07%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
Phusion | Web application deployment, scaling and monitoring solutions

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)

Hongli Lai

unread,
Jul 8, 2014, 1:33:17 PM7/8/14
to phusion-passenger
Yes, the SpawnServer is gone in version 4. It's been replaced by the
HelperAgent.

Anyway, your issue is most likely caused by some /tmp cleaner daemon
removing Passenger files from /tmp, which passenger-status uses to
determine whether Passenger is running. Try setting passenger_temp_dir
to a directory other than /tmp (and set the PASSENGER_TEMP_DIR
environment variable to that same directory so that passenger-status
knows about the change). Let me know whether this works.
> To view this discussion on the web visit https://groups.google.com/d/msgid/phusion-passenger/CAGW%3D8Rpp1LtEmFOvCsO0kLF32NQwpxH3jWA1xajyE%3DM5PS%2BKUQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



--
Phusion | Web Application deployment, scaling, and monitoring solutions
Reply all
Reply to author
Forward
0 new messages