|Summary:||"piped log program '(null)' failed unexpectedly" error message on restart|
|Product:||Apache httpd-2||Reporter:||Glenn Nielsen <glenn>|
|Component:||Core||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
|Attachments:||Remove piped log program '(null)' failed unexpectedly error on apache restart|
Description Glenn Nielsen 2003-07-16 12:11:44 UTC
A "piped log program '(null)' failed unexpectedly" error message for each configured piped log is reported when you do an apache restart. Looking at the source, this is expected on a restart. Logging it gives the impression something is breaking. Attached will be a small patch to prevent this from being logged on a restart.
Comment 1 Glenn Nielsen 2003-07-16 12:13:50 UTC
Created attachment 7328 [details] Remove piped log program '(null)' failed unexpectedly error on apache restart
Comment 2 Jeff Trawick 2003-11-21 22:29:01 UTC
FYI... this can happen at apachectl stop too*... another PR, another patch which should close this hole as well :) incidentally, part of this other patch is some infrastructure to get your marvelous cgid restart patch working with prefork, which in turn will let us merge it to stable *whether any of this happens seems to be timing related... number of piped loggers, OS, MPM, each are inputs to a function I cannot understand that determines if this bogosity occurs
Comment 3 Jeff Trawick 2003-12-13 22:21:29 UTC
Fix committed to 2.1-dev. Hopefully it can be committed to stable branch before too terribly long.