Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: How to rid my error log of this crap? |
|
| Author |
|
glsmith
Moderator
Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA
|
 Posted: Sat 29 Dec '07 23:08 Post subject: How to rid my error log of this crap? |
 |
|
Is this intended, or a bug. I skipped 2.0 pretty much so I am used to NOT having this crap in 1.3.
LogLevel set to "warn" but I get tons of notice crap in my error log everytime restarting the server, and then it looks like the server restarts all the time.
[Sat Dec 29 12:45:12 2007] [notice] Child 3884: Process exiting because it reached MaxRequestsPerChild. Signaling the parent to restart a new child process.
[Sat Dec 29 12:45:12 2007] [notice] Parent: Received restart signal -- Restarting the server.
[Sat Dec 29 12:45:13 2007] [notice] Child 3884: Released the start mutex
[Sat Dec 29 12:45:13 2007] [notice] Child 3884: Waiting for 250 worker threads to exit.
[Sat Dec 29 12:45:13 2007] [notice] Child 3884: All worker threads have exited.
[Sat Dec 29 12:45:13 2007] [notice] Child 3884: Child process is exiting
[Sat Dec 29 12:45:15 2007] [notice] Apache/2.2.6 (Win32) mod_ssl/2.2.6 OpenSSL/0.9.8g mod_deflate/1.2.3 PHP/5.2.5 mod_security2/2.1.4-2.2.6 configured -- resuming normal operations
[Sat Dec 29 12:45:15 2007] [notice] Server built: Oct 20 2007 01:55:46
[Sat Dec 29 12:45:15 2007] [notice] Parent: Created child process 580
[Sat Dec 29 12:45:15 2007] [notice] Disabled use of AcceptEx() WinSock2 API
[Sat Dec 29 12:45:16 2007] [notice] ModSecurity for Apache 2.1.4 configured
[Sat Dec 29 12:45:17 2007] [notice] Child 580: Child process is running
[Sat Dec 29 12:45:17 2007] [notice] Child 580: Acquired the start mutex.
[Sat Dec 29 12:45:17 2007] [notice] Child 580: Starting 250 worker threads.
[Sat Dec 29 12:45:17 2007] [notice] Child 580: Listening on port 443.
[Sat Dec 29 12:45:17 2007] [notice] Child 580: Listening on port 80.
This is one that I did not initiate. I hate this mess, buries real errors in the log and makes them hard to find.
any ideas? |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7373
Location: Germany, Next to Hamburg
|
| Posted: Sun 30 Dec '07 0:19 Post subject: |
|
|
You can disable logging that with log level
See the docs LogLevel
I think you want
I've never changed that, so I'm not sure about which errors will be stored. Good luck. |
|
| Back to top |
|
tdonovan
Moderator
Joined: 17 Dec 2005
Posts: 611
Location: Milford, MA, USA
|
| Posted: Sun 30 Dec '07 1:50 Post subject: |
|
|
Unfortunately, there is a special note in the docs about the "notice" log level which says: | Quote: | | When logging to a regular file - messages of the level notice cannot be suppressed, and thus are always logged. However, this doesn't apply when logging is done using syslog. |
The "notice" level is intended for one-time messages, like Apache startup and shutdown messages.
On Windows, MaxRequestsPerChild defaults to zero (i.e. unlimited), so these messages usually only appear at Apache startup and shutdown.
The Windows mpm prints these "notice" messages based on the presumption that only one Apache child process will exist between Apache startup and shutdown.
Are you setting MaxRequestsPerChild to a non-zero value in order to work around some specific problem?
If so, the downside of setting MaxRequestsPerChild > 0 is this set of messages occurs whenever Apache kills off the child process and starts a new one.
-tom- |
|
| Back to top |
|
glsmith
Moderator
Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA
|
| Posted: Sun 30 Dec '07 6:05 Post subject: |
|
|
Hey Tom and James,
James,
I thought it was default at warn, at least it was in 1.3. Looking at the default conf files in the source trees I see that is also the case for both 2.x flavors as well. I have no problem with "error" however.
Tom,
I see that is now stated in the 1.3 Docs, however, this was never the case right up to 1.3.37 with LL set to warn. Looking at the loggin done during testing of my 1.3.39 build it is still the case. In both cases I have a few warns and many error level entries, but then I see my MRPC there was zero, yet still not one of these in the old 1.3 logs ever. Only DSO's not being compiled EAPI (warn), not all the (notice) stuff.
I did raise MRPC for a reason but I do not remember the reason. May have been stab in the dark that turned out to be a memory leak in another piece of software that was in use on the server. Since it was at 64 I'm going to assume I blew it in dyslexic moment between reading and doing since that is the default for TPC under mpm_winnt which I am going to leave at 250 anyway (again, the actual default from the default conf files).
I want "error" events since I do so much in perl. Every once it awhile I actually get more usefull info out of the error log than in the script log. I had set LL to error with same results. So OK, MRPC back to zero, I can live with these spattered throughout, and as stated with a 0, I should only get one per start/stop/restart ... correct?
Changed and restarted, will keep an eye on it.
Thanks,
Gregg |
|
| Back to top |
|
|
|
|
|
|
