You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2009/09/27 19:50:05 UTC

DO NOT REPLY [Bug 47908] New: 'invalid result code' in error_log

https://issues.apache.org/bugzilla/show_bug.cgi?id=47908

           Summary: 'invalid result code' in error_log
           Product: Apache httpd-2
           Version: 2.2.13
          Platform: Other
        OS/Version: FreeBSD
            Status: NEW
          Severity: minor
          Priority: P2
         Component: All
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: craig@animalhead.com


Created an attachment (id=24319)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=24319)
collection of errors of this type

Upgraded from 2.2.11 to .13 recently.  A new class of error message began to
appear in the error_log, once every day or two:
Handler for type-map returned invalid result code 53
The associated entry in access_log was:
 "GET /1n/warthog.jpg HTTP/1.1" 500 - 

I posted this to the apache user mailing list, but there was no reply. 
Meanwhile I augmented the error message routine in the Apache source and
rebuilt.  Since then there was one such new error message:

Handler for type-map (file
/usr/local/apache2/error/HTTP_INTERNAL_SERVER_ERROR.html.var, type text/html;
charset=iso-8859-1) returned invalid result code 53

Once again the access_log entry was for one of the thumbnails that accompanies
our front page:
GET /1n/serval.jpg HTTP/1.1" 500 - 

This looks like chickens and eggs.  Something in apache decided to post a 500,
and then there was a problem with serving the multilingual 500 page.

Looks like the type in the error message isn't of much use.  Should I change
the error message to display the handler and file from the 'prev' request
record (if any)?  Any other suggestions for looking at this problem would be
appreciated.

The jpg's in the two examples are cached by:
CacheFile /usr/local/apache2/htdocs/1n/aardvark.jpg

One fixup handler of mine is active for such jpg's, but it for sure only
returns OK :-)    

There was also one message that was different:
Handler for modperl returned invalid result code 53
unable to include "/navbar2?cont=32" in parsed file
/usr/local/apache2/htdocs/springbuck.html
access_log:
"GET /springbuck.html HTTP/1.1" 200 11360

There were no such error messages on substantially the same site for many
months under 2.2.11.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org