Bug 47908 - 'invalid result code' in error_log
Summary: 'invalid result code' in error_log
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: All (show other bugs)
Version: 2.2.13
Hardware: Other FreeBSD
: P2 minor (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2009-09-27 10:50 UTC by craig
Modified: 2018-11-07 21:08 UTC (History)
0 users

collection of errors of this type (8.15 KB, application/octet-stream)
2009-09-27 10:50 UTC, craig

Note You need to log in before you can comment on or make changes to this bug.
Description craig 2009-09-27 10:50:02 UTC
Created attachment 24319 [details]
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

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
"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.
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:24 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.