I'm on a brand-new CentOS7 machine, running Passenger 5.0.27 under apache 2.4.6.
The passenger-memory-stats command works fine, but passenger-status claims Passenger is not running.
I found this answer on Stack Overflow regarding the registry tmp directory:
I traced down where Passenger is putting its tmp dir, and when I tried the command below (as root), the passenger-status command starts, but then dies with an error about the overly long socket name.
How can I predict what this crazy tmp directory name will be? It changes every time I restart apache. Should I instead I hard-code /tmp into my mod_passenger.conf file?
env PASSENGER_INSTANCE_REGISTRY_DIR=/tmp/systemd-private-1d789f50b42240af9af182fc689cbe1f-httpd.service-pbTEyd/tmp passenger-status
Version : 5.0.27
Date : 2016-04-09 23:19:24 +0000
Instance: a3MYkCBR (Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips Phusion_Passenger/5.0.27)
/usr/local/rvm/gems/ruby-2.3.0/gems/passenger-5.0.27/src/ruby_supportlib/phusion_passenger/admin_tools/instance.rb:94:in `initialize': too long unix socket path (114bytes given but 108bytes max) (ArgumentError)
from /usr/local/rvm/gems/ruby-2.3.0/gems/passenger-5.0.27/src/ruby_supportlib/phusion_passenger/admin_tools/instance.rb:94:in `new'
from /usr/local/rvm/gems/ruby-2.3.0/gems/passenger-5.0.27/src/ruby_supportlib/phusion_passenger/admin_tools/instance.rb:94:in `http_request'
from /usr/local/rvm/gems/ruby-2.3.0/gems/passenger-5.0.27/bin/passenger-status:113:in `show_status'