|Summary:||CustomLog with pipe spawns process during config|
|Product:||Apache httpd-2||Reporter:||Martin Vilcans <martin>|
|Component:||mod_log_config||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
|Attachments:||Patch to fix Hanging pipe logger processes.|
Description Martin Vilcans 2003-02-04 15:58:50 UTC
This bug appears when running the command apache -k install or apache -k config if there are CustomLog entries in the configuration that pipe to an external program (e.g. rotatelogs.exe). For each piping CustomLog, Apache creates the corresponding process. Then the Apache process exits, leaving the logging processes alive, probably waiting for input on stdin (which will never come, since the process isn't attached to a console). To reproduce the bug, change the CustomLog line in the default httpd.conf to: CustomLog "|/apache2/bin/rotatelogs.exe logs/access_%Y-%m-%d.log 86400 +60" combined Then execute apache -k install -f conf/httpd.conf. When the command is finished, check the Task Manager (or a better tool, such as Process Explorer) for a rotatelogs.exe process which must be killed manually. This bug also appears with a simple test logger, so the bug is not specific to rotatelogs.exe.
Comment 1 Scott Parker 2003-03-09 22:23:27 UTC
I confirm this behavior with v2.0.44/Win2k. It also leaves a hung process when service starts up and does not send to the stdin on the log processor. This behavior is with "rotatelogs.exe" or "cronolog.exe" So I don't think it is anything to do with the external programs either. It does not have the problem with the ErrorLog directive. This works properly piped to an external program.
Comment 2 Scott Parker 2003-03-10 04:04:51 UTC
v2.0.43 is not affected... compiled and tested on same system as 2.0.44.
Comment 3 Kenneth Golomb 2006-02-09 17:37:01 UTC
Created attachment 17630 [details] Patch to fix Hanging pipe logger processes. It looks like on Win32 of log.c the piped log always starts the piped process thru a cmd.exe shell. Which seems to be the root of this hanging piped CustomLog / ErrorLog. Changing the process creation from: apr_procattr_cmdtype_set(procattr, APR_SHELLCMD_ENV) to: apr_procattr_cmdtype_set(procattr, APR_PROGRAM_ENV) Will cause it to act the way it used and make it worrk correctly. CMD.exe will then only be utilize for .cmd and .bat loggers where it is necessary.
Comment 4 Liam Hoekenga 2006-08-16 15:13:45 UTC
We've run into this problem on linux w/ httpd 2.2.x using ErrorLog - both with rotatelogs and cronolog.
Comment 5 toadie 2006-10-31 10:18:41 UTC
The proposed patch seems to work for us on Apache 2.2.3.
Comment 6 Ruediger Pluem 2006-10-31 11:32:00 UTC
(In reply to comment #4) > We've run into this problem on linux w/ httpd 2.2.x using ErrorLog - both with > rotatelogs and cronolog. Have you checked if your problem is solved by the patch for Bug 40651 (http://svn.apache.org/viewvc?view=rev&revision=452431)?
Comment 7 William A. Rowe Jr. 2018-11-07 21:08:26 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.