Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V5: passenger_monitor cannot terminate orphan workers in a multi-application environment #338

Open
radamanthus opened this issue Apr 4, 2018 · 0 comments

Comments

@radamanthus
Copy link
Contributor

passenger_monitor calls passenger-status to look for orphaned passenger workers:
https://github.com/engineyard/ey-cookbooks-stable-v5/blob/next-release/cookbooks/passenger5/files/default/passenger_monitor#L103

In a multiple-application environment there will be multiple passenger-standalone processes running. Calling passenger-status without a name parameter will result in an error like this, written to /var/log/syslog:

Apr  4 08:44:02 localhost passenger_monitor: It appears that multiple Phusion Passenger instances are running. Please select a specific one by running:    passenger-status <NAME>  The following Phusion Passenger instances are running:  Name                       PID      Description -------------------------------------------------------------------------- pgnOYJGM                   7081     nginx/1.12.1 Phusion_Passenger/5.1.8 keSiecR1                   16255    nginx/1.12.1 Phusion_Passenger/5.1.8
Apr  4 08:44:02 localhost passenger_monitor: Could not read passenger-status [Status:1]
Apr  4 08:44:02 localhost passenger_monitor: It appears that multiple Phusion Passenger instances are running. Please select a specific one by running:    passenger-status <NAME>  The following Phusion Passenger instances are running:  Name                       PID      Description -------------------------------------------------------------------------- pgnOYJGM                   7081     nginx/1.12.1 Phusion_Passenger/5.1.8 keSiecR1                   16255    nginx/1.12.1 Phusion_Passenger/5.1.8
Apr  4 08:44:15 localhost passenger_monitor: Could not read passenger-status [Status:1]
Apr  4 08:44:15 localhost passenger_monitor: It appears that multiple Phusion Passenger instances are running. Please select a specific one by running:    passenger-status <NAME>  The following Phusion Passenger instances are running:  Name                       PID      Description -------------------------------------------------------------------------- pgnOYJGM                   7081     nginx/1.12.1 Phusion_Passenger/5.1.8 keSiecR1                   16255    nginx/1.12.1 Phusion_Passenger/5.1.8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant