Bug 48431 - Error logging doesn't work when configured to use syslog
Summary: Error logging doesn't work when configured to use syslog
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.2.14
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2009-12-22 12:12 UTC by adam.chou
Modified: 2018-11-07 21:08 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description adam.chou 2009-12-22 12:12:36 UTC
When error logging is set to syslog, I can't get any startup errors generated from child processes or threads to show up in syslog. Specifically, I forgot to set User and Group and the only error I would get was that a child process had a fatal error and shut down. This made debugging the issue almost impossible without stepping through the code. 

This happened to me in Event, Worker, and Pre-Fork. The problem appears to be how ap_log_error() calls log_error_core() on certain startup functions. ap_log_error() passes a NULL for parameter const server_rec *s. This is apparently some sort of sentinel value that tells log_error_core() that its in the startup phase then sets logf to stderr_log. This actually seems to be initialized to some proper value too. However, it becomes a problem later on in the syslog logging section that checks if logf is set and since it is, it never logs to syslog.

I was just going to debug it some more and submit a patch but this fix seems to require a bit more rewriting than just changing some booleans. I'm not sure how you guys want to handle this but I'd be glad to fix it if you let me know what your suggested fix for it is.
Comment 1 adam.chou 2009-12-22 12:18:56 UTC
sorry, just realized some of the values i printed while stepping through might be wrong. however, the error messages not showing up in syslog was for sure reproduceable.
Comment 2 William A. Rowe Jr. 2018-11-07 21:08:31 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.