CODEWITHSUNDEEP
ruby-on-railsapachepassenger
ylluminate
ylluminate

Reputation: 12369

Vague error from Apache and Phusion Passenger on failed Rails apps - how to address such a non-verbose issue?

I'm using Apache 2.4 along with Phusion Passenger 4.0.5 and for some reason I am seeing errors come up from time to time for Rails apps without any real seeming rhyme or reason. When I look into the Apache error logs, I only see the following very vague error:

[ 2013-07-01 10:56:01.0046 26104/7ff716d317c0 apache2/Hooks.cpp:757 ]: Unexpected error in mod_passenger: Cannot connect to the helper agent
  Backtrace:
     (empty)

Any way to force more verbosity from Apache and Passenger to facilitate troubleshooting here?

Upvotes: 4

Views: 1533

Answers (2)

Rodrigo Moya
Rodrigo Moya

Reputation: 31

This is a bug in Passenger 4.0.7, Update to 4.0.8 or the lasted version of passenger and run again :

passenger-install-apache2-module

then update your apache config file. source

Upvotes: 1

Hongli
Hongli

Reputation: 18924

This error message is printed when the HelperAgent has crashed. The code in Apache will wait until the Watchdog restarts the HelperAgent, after which the connection is reestablished. If anything goes wrong, this is the message you get. What you should look for are the earlier messages. Are there any messages from earlier that may tell you why the HelperAgent crashed in the first place, or why it failed to restart? If you look at passenger-memory-stats, do you see the PassengerHelperAgent and PassengerWatchdog?

Upvotes: 4

Related Questions