On Fri, 5 Jan 2001, Gerd Kortemeyer wrote:
> Hi,
>
> Did anybody ever see a message like this in the error log after an "internal
> server error"?
>
> [error] Undefined subroutine &Apache::lonhomework::handler called at /dev/null
> line 65535.
>
> No further entries.
>
> lonhomework is the mod_perl handler attached to a URL, and is called directly.
> This happens intermittently and seemingly at random; however, after this
> happened once, that Apache child is messed up and will do this again and again
> when hit - so depending on which child happens to answer, you get the correct
> reply or another 500.
i think it's possible that the fix for this is in 1.24_01-dev:
switch usage of hard_timeout() to soft_timeout(), so if SIGALRM
happens during Apache::{print,read}, the script will continue run,
allowing proper cleanup (e.g. DESTROY)
do you see anything in the error_log related to timeouts?
