Skip to content

Instantly share code, notes, and snippets.

@jgarber

jgarber/why does passenger die randomly?

Created May 27, 2009 17:24
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jgarber/118763 to your computer and use it in GitHub Desktop.
Save jgarber/118763 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
why does passenger die randomly?
[Wed May 27 10:48:29 2009] [error] cgid daemon process died, restarting
[Wed May 27 10:48:29 2009] [warn] long lost child came home! (pid 10881)
[ pid=10888 file=ext/apache2/Hooks.cpp:566 time=2009-05-27 10:48:31.874 ]:
Unexpected error in mod_passenger: The ApplicationPool server unexpectedly closed the connection while we're reading a response for the 'g
et' command.
Backtrace:
(empty)
[ pid=10888 file=ext/apache2/Hooks.cpp:566 time=2009-05-27 10:48:31.875 ]:
Unexpected error in mod_passenger: The ApplicationPool server unexpectedly closed the connection while we're reading a response for the 'g
et' command.
Backtrace:
(empty)
[ pid=10886 file=ext/apache2/Hooks.cpp:566 time=2009-05-27 10:48:31.875 ]:
Unexpected error in mod_passenger: The ApplicationPool server unexpectedly closed the connection while we're reading a response for the 'g
et' command.
Backtrace:
(empty)
[ pid=10886 file=ext/apache2/Hooks.cpp:566 time=2009-05-27 10:48:31.875 ]:
Unexpected error in mod_passenger: The ApplicationPool server unexpectedly closed the connection while we're reading a response for the 'g
et' command.
Backtrace:
(empty)
[ pid=10886 file=ext/apache2/Hooks.cpp:566 time=2009-05-27 10:48:31.875 ]:
Unexpected error in mod_passenger: The ApplicationPool server unexpectedly closed the connection while we're reading a response for the 'g
et' command.
Backtrace:
(empty)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment