The symptom of the problem I am having is that the http server for
passenger is not wanting to start on port 80.
[Thu Apr 06 11:04:11.913879 2017] [core:notice] [pid 140387] AH00094:
Command line: '/usr/sbin/httpd -D FOREGROUND'
/usr/share/gems/gems/passenger-4.0.18/helper-scripts/prespawn:105:in
initialize': Connection refused - connect(2) (Errno::ECONNREFUSED) from /usr/share/gems/gems/passenger-4.0.18/helper-scripts/prespawn:105:innew'
from
/usr/share/gems/gems/passenger-4.0.18/helper-scripts/prespawn:105:in
connect' from /usr/share/gems/gems/passenger-4.0.18/helper-scripts/prespawn:86:insocket'
from
/usr/share/gems/gems/passenger-4.0.18/helper-scripts/prespawn:90:in
head_request' from /usr/share/gems/gems/passenger-4.0.18/helper-scripts/prespawn:145:in<main>'
/usr/share/gems/gems/passenger-4.0.18/helper-scripts/prespawn:105:in
initialize': Connection refused - connect(2) (Errno::ECONNREFUSED) from /usr/share/gems/gems/passenger-4.0.18/helper-scripts/prespawn:105:innew'
from
/usr/share/gems/gems/passenger-4.0.18/helper-scripts/prespawn:105:in
connect' from /usr/share/gems/gems/passenger-4.0.18/helper-scripts/prespawn:86:insocket'
from
/usr/share/gems/gems/passenger-4.0.18/helper-scripts/prespawn:90:in
head_request' from /usr/share/gems/gems/passenger-4.0.18/helper-scripts/prespawn:145:in<main>'
[ 2017-04-06 11:04:15.1163 140411/7f8bc9597700 Pool2/Spawner.h:738 ]: [App
140451 stdout]
[ 2017-04-06 11:04:24.8289 140411/7f8bc9597700 Pool2/SmartSpawner.h:301 ]:
Preloader for /usr/share/foreman started on PID 140451, listening on
unix:/var/run/rubygem-passenger/passenger.1.0.140387/generation-1/backends/preloader.140480
Now I thought maybe it was related to a bug discussion I saw about SELinux
and the epel vs foreman ruby. However I had long since switched to
permissive in selinux.
sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: permissive
Mode from config file: permissive
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 28
I did downgrade passenger, this eliminated this message in the httpd log.
App 127275 stdout:
App 127275 stderr: --> passenger_native_support was compiled for Ruby API
version 2.0.0, but you're currently running a Ruby interpreter with API
version 2.2.0.
App 127275 stderr: Refusing to load existing passenger_native_support.
App 127275 stderr: --> No passenger_native_support.so found for current
Ruby interpreter.
App 127275 stderr: This library provides various optimized routines
that make
App 127275 stderr: Phusion Passenger faster. Please run 'sudo yum
install passenger-devel-4.0.53'
App 127275 stderr: so that Phusion Passenger can compile one on the
next run.
App 127275 stderr: --> Continuing without passenger_native_support.so.
However I still get the socket error.
rpm -qa|grep passenger
rubygem-passenger-native-4.0.18-9.11.el7.x86_64
rubygem-passenger-native-libs-4.0.18-9.11.el7.x86_64
tfm-rubygem-passenger-native-4.0.18-9.11.el7.x86_64
rubygem-passenger-4.0.18-9.11.el7.x86_64
tfm-rubygem-passenger-native-libs-4.0.18-9.11.el7.x86_64
mod_passenger-4.0.18-9.11.el7.x86_64
tfm-rubygem-passenger-4.0.18-9.11.el7.x86_64
SSL, ie the main web server for the foreman web interface works fine so I
am not sure why the issue with the httpd server.
Terrence
