passenger: Passenger does not log anything if Apache has "ErrorLog syslog" set
From flameeyes@flameeyes.eu on January 22, 2012 21:07:26
This seems to be a less critical issue from the similar one in mod_perl (which instead decides to crash Apache), but still bothersome.
Without going to look through the code, just by checking the lsof -p $pid output, I see that STDOUT/STDERR of the Rails applications are set to output to the log set in ErrorLog or PassengerDebugLogFile… but without further warnings it simply drops the whole output if ErrorLog is set to “syslog” in Apache.
I’m not sure if there is a decent way to solve this but at least it should be throwing some kind of warning or error if PassengerDebugLogFile is not set and ErrorLog is set to syslog so that one knows what is going on.
Thanks, Diego Elio Pettenò
_Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=733_
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Comments: 18 (9 by maintainers)
To be clear, you are talking about Nginx’s original stderr, before Nginx has redirected stderr to a blackhole as part of its syslog setup, correct? It is definitely possible, just not easy. Hence the decision to close is more the result of a cost-benefit analysis, rather than declaring a technical impossibility.