Jason Young
2007-11-14 19:23:41 UTC
Hey,
Anyone using Locomotive and Mongrel 1.1.1? (Leopard, with a bundle
derived from the Mar 07 bundle with an updated gem set).
I've had a devil of a time today getting Locomotive to start mongrel
1.1.1 - clicking start/restart would given me nothing, no logs,
nothing, the STDERR.write in run_mongrel in the launch script would
happily write the "Starting mongrel on... " line to the system.log -
but that's it.
Running mongrel_rails from the terminal itself was perfectly fine -
other than the warning you'll get with Ruby 1.8.5 written to stderr:
** Ruby version is not up-to-date; loading cgi_multipart_eof_fix
I finally added a:
STDERR.write "stderr : #{ stderr.read.strip }"
to see if there was anything else on the stderr handle returned by the
Open4.popen4 - to see if there were other errors.
Lo and behold, that made things happy. All this stdout/stderr
opening and closing is honestly a bit over my head (or rather
experience) - the only thing I can figure is that the popen4 pulled
stderr out from underneath ruby and/or mongrel_rails itself? And not
until that out ** Ruby version is not up-to-date; loading
cgi_multipart_eof_fix text is pulled off that file handle can it
proceed?
Jason
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jason Young -- Systems Manager, eXtension
http://about.extension.org/wiki/Jason_Young
______________________________________
Anyone using Locomotive and Mongrel 1.1.1? (Leopard, with a bundle
derived from the Mar 07 bundle with an updated gem set).
I've had a devil of a time today getting Locomotive to start mongrel
1.1.1 - clicking start/restart would given me nothing, no logs,
nothing, the STDERR.write in run_mongrel in the launch script would
happily write the "Starting mongrel on... " line to the system.log -
but that's it.
Running mongrel_rails from the terminal itself was perfectly fine -
other than the warning you'll get with Ruby 1.8.5 written to stderr:
** Ruby version is not up-to-date; loading cgi_multipart_eof_fix
I finally added a:
STDERR.write "stderr : #{ stderr.read.strip }"
to see if there was anything else on the stderr handle returned by the
Open4.popen4 - to see if there were other errors.
Lo and behold, that made things happy. All this stdout/stderr
opening and closing is honestly a bit over my head (or rather
experience) - the only thing I can figure is that the popen4 pulled
stderr out from underneath ruby and/or mongrel_rails itself? And not
until that out ** Ruby version is not up-to-date; loading
cgi_multipart_eof_fix text is pulled off that file handle can it
proceed?
Jason
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jason Young -- Systems Manager, eXtension
http://about.extension.org/wiki/Jason_Young
______________________________________