httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phil Smith <>
Subject Re: [users@httpd] unexpected EOF while looking for matching
Date Mon, 20 Feb 2012 16:16:31 GMT
On Mon, Feb 20, 2012 at 8:54 AM, Tom Evans <> wrote:
> On Mon, Feb 20, 2012 at 1:16 PM, Steve Swift <> wrote:
>> Ah, but the "sh" error means that my code never starts executing. If the
>> very first line of my code were to get executed, then the error message
>> would come from the error handlers in my code, but nothing in my code
>> executes under these circumstances.
>> So, without a single byte of my code changing (including the shebang; the
>> file's "last changed" timestamp is usually months in the past), the script
>> will run happily for months on end, encounter one of these weird "sh"
>> errors, then go back to working again.
> I'll try and make it clearer - Apache *does not* invoke sh, *for any
> reason*.

An apache module, maybe?

> If sh is being invoked, your script is doing it. If you see
> sh errors in your error log, then your script is invoking sh
> incorrectly.

Do you agree that if it is a script as you suggest causing the sh
errors, then the request causing that script to run must related to
something in my access log either directly or indirectly? While trying
to debug this I wrote a script that causes an error on my apache
server every second. So, I have a very good set of timestamps being
written to my apache error log. I assume that if it is truly a request
being made to my server, that the sh error should be written to the
error log within a few seconds of the request.

I'm seeing nothing but GET requests in my access log around the time
of the sh error, as such, they are very repeatable and I attempt to
repeat them and no 'sh' error is produced.

Further, quite often the 'sh' errors occur in clusters. As such, I
would expect a group of similar/identical requests to be written to my
access log around the same second and I don't.

On the face of it, I would suggest the same thing as being suggested
here, the problem is with a script being invoked by a request, but the
access log isn't backing it up with evidence.

Do you have any suggestions for some way of mapping the sh error back
to the IP address making the request (assuming it's an external
request)? That would be helpful in attributing the error to a given
request, but I can't think of a way to do that.


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message