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: Spurious error log entries being caused by ExecCGI |
|
| Author |
|
Roger Macrae
Joined: 17 Aug 2007
Posts: 1
|
 Posted: Fri 17 Aug '07 11:19 Post subject: Spurious error log entries being caused by ExecCGI |
 |
|
I’ve just upgraded Apache to 2.2.4 from 2.0.55 – when I say upgraded, I had the opportunity to start from scratch with a clean install on a new machine (therefore not strictly an upgrade – just transitioned all the html and scripting across) and discovered the following intermittent problem:-
[Fri Aug 17 09:25:32 2007] [notice] Apache/2.2.4 (Win32) configured -- resuming normal operations
[Fri Aug 17 09:25:32 2007] [notice] Server built: Jan 9 2007 23:17:20
[Fri Aug 17 09:25:32 2007] [notice] Parent: Created child process 6012
[Fri Aug 17 09:25:32 2007] [notice] Child 6012: Child process is running
[Fri Aug 17 09:25:32 2007] [notice] Child 6012: Acquired the start mutex.
[Fri Aug 17 09:25:32 2007] [notice] Child 6012: Starting 250 worker threads.
[Fri Aug 17 09:25:32 2007] [notice] Child 6012: Starting thread to listen on port 80.
[Fri Aug 17 09:26:54 2007] [error] [client 10.20.8.126] , referer: http://10.20.11.200/
[Fri Aug 17 09:26:55 2007] [error] [client 10.20.8.126] , referer: http://10.20.11.200/
The area where I have a concern is the last two lines.
If I wade back through the access log and match the times, the error events are being caused by an embedded SSI perl exec cgi in web pages (it’s not limited to a specific web page) eg <!--#exec cgi="/cgi-bin/capture1.cgi" -->
Other than the rather cryptic error entries in the error log file, there is no suggestion that there is a problem – the scripts execute and return the information exactly as expected … everything appears normal. Also tried turning on script logging – nothing logged.
I also use other SSI aspects eg <!--#echo var="DATE_LOCAL" --> and have no problems with these.
I revisited the apache config file(s) and can’t find anything amiss. I reviewed the cgi scripting, also can’t find anything amiss.
I backed out of 2.2.4 and reverted to 2.0.55 and hey presto, the cryptic error messages don’t appear.
I did discover the change to the httpd.conf structure between the two versions and have configured accordingly.
Whilst everything is working, I’m tempted to just live with it but there is obviously something causing these spurious errors.
Anybody else had this experience ?
Cheers,
Roger |
|
| Back to top |
|
|
|
|
|
|
