www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Digulla <digu...@fh-konstanz.de>
Subject mod_cgi/3136: Another cause of "Premature end of script headers:"
Date Mon, 05 Oct 1998 08:38:52 GMT

>Number:         3136
>Category:       mod_cgi
>Synopsis:       Another cause of "Premature end of script headers:"
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          support
>Submitter-Id:   apache
>Arrival-Date:   Mon Oct  5 01:40:00 PDT 1998
>Originator:     digulla@fh-konstanz.de
>Release:        1.3.0
Doesn't matter
If you use RLimitCPU and RLimitMem to kill runaway CGI scripts, then you can 
get this error if the limits are too low. 
Add this to http.conf and run a CGI script (eg. cgi-bin/printenv):

RLimitCPU 20
RLimitMem 10000
Add this to the FAQ about "Premature end of script headers".

It might be better to write an error to the error log which says that
the script was killed because of RLimits (I don't know if it is possible to
figure out if it failed because of CPU or Memory, but if that was possible,
it should print that, too).
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]

View raw message