Two Concurrent Phusion Passengers

[Jonathan Hilgeman]

I have 2 Apache installations. One runs on port 80 and the other on 9080. 

I have Passenger 3.0.1 running on the first Apache server (2.2.6), and I -cannot- mess with this installation in any way.

I have Passenger 5.1.7 installed via a gem and it's installed against the second Apache server (2.4.10), but when it seems to fail to start up with this error in the Apache error log:

*** Passenger could not be initialized because of this error: led with signal SIGSEGV during startup

I really just need to have one site running against one version of Ruby and another site running against a different version of Ruby. I've tried numerous things but cannot figure out a solution. Please help! 

[Camden Narzt]

Set your PassengerLogLevel to 7 and include the entire log of a startup here.

[Jonathan Hilgeman]

Okay, here's what's in the error log after making that change and restarting:

[ 2017-08-15 17:31:25.5571 12825/b7369700 apa/Hooks.cpp:1261 ]: Initializing Phusion Passenger...

[ 2017-08-15 17:31:25.5760 12825/b7369700 WatchdogLauncher.h:376 ]: File descriptor opened: 13

[ 2017-08-15 17:31:25.5760 12825/b7369700 WatchdogLauncher.h:376 ]: File descriptor opened: 14

[ 2017-08-15 17:31:25.5767 12825/b7369700 FileDescriptor.h:94 ]: File descriptor closed: 14

[ 2017-08-15 17:31:25.5767 12825/b7369700 WatchdogLauncher.h:438 ]: File descriptor purpose: 13: WatchdogLauncher: feedback FD

[ 2017-08-15 17:31:25.6901 12825/b7369700 FileDescriptor.h:84 ]: File descriptor closed: 13

[Tue Aug 15 17:31:25.690254 2017] [passenger:error] [pid 12825:tid 3073808128] *** Passenger could not be initialized because of this error: Unable to start the Phusion Passenger watchdog: it seems to have been killed with signal SIGSEGV during startup

[Camden Narzt]

Sorry for the delay, the segfault looks to be early enough that no additional useful logging happens before it. You are compiling your own binaries as described in your other thread, so it's possible that the compilation didn't go as expected. Can you check which openssl and curl your binary linked against?

Something like 

ldd /path/to/buildout/support-binaries/PassengerAgent/PassengerAgent

should do the trick.

Also if your system produces core files you could load that up with gdb and print a backtrace.