Strange log entry, Apache child messed up afterwards
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. Distributions: Red Hat Linux release 6.2 (Zoot) Kernel 2.2.16-3smp on a 2-processor i686 [www@s10 www]$ rpm -q mod_perl mod_perl-1.23-3 [www@s10 www]$ rpm -q perl perl-5.00503-10 [www@s10 www]$ rpm -q apache apache-1.3.14-2.6.2 Thanks to all in advance! - Gerd. begin:vcard n:Kortemeyer;Gerd tel;fax:(517) 432-2175 tel;work:(517) 432-5468 x-mozilla-html:TRUE url:http://www.lite.msu.edu/kortemeyer/ org:Michigan State University;LITE Lab adr:;;123 North Kedzie Labs;East Lansing;Michigan;48824;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Instructional Technology Specialist x-mozilla-cpt:;3 fn:Gerd Kortemeyer end:vcard
RE: Strange log entry, Apache child messed up afterwards
I see it also. However, I only see it after I get an entry of 200 - in the access log, i.e. the page returned status code 200, but the content-length is not recorded. I'm still in the process of investigating. BTW the above log entry occurs 90% of the time with a script that does a file upload. -P > -Original Message- > From: Gerd Kortemeyer [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 05, 2001 7:14 PM > To: [EMAIL PROTECTED] > Subject: Strange log entry, Apache child messed up afterwards > > > 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. > > Distributions: > > Red Hat Linux release 6.2 (Zoot) > Kernel 2.2.16-3smp on a 2-processor i686 > [www@s10 www]$ rpm -q mod_perl > mod_perl-1.23-3 > [www@s10 www]$ rpm -q perl > perl-5.00503-10 > [www@s10 www]$ rpm -q apache > apache-1.3.14-2.6.2 > > Thanks to all in advance! > > - Gerd. >
Re: Strange log entry, Apache child messed up afterwards
* Gerd Kortemeyer ([EMAIL PROTECTED]) [010105 19:20]: > 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. > Here is good, maybe: http://perl.apache.org/guide/debug.html#Curing_The_Internal_Server_Erro Here is also good, maybe (the sequel): http://perl.apache.org/guide/debug.html#Helping_error_log_to_Help_Us I hear this may also be good (the next generation): http://perl.apache.org/guide/debug.html#The_Importance_of_Warnings If all else fails, this may be good (generations): http://perl.apache.org/guide/debug.html#Sometimes_My_Script_Works_Somet I don't know, but it could help (the obligatory "We are all broke and can't handle our money, so we need more work" sequel): http://perl.apache.org/guide/debug.html#Code_Debug If none of this helps, try Stallone, he makes more sequels. -- J. J. Horner [EMAIL PROTECTED] Apache, Perl, mod_perl, Web security, Linux PGP signature
Re: Strange log entry, Apache child messed up afterwards
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?
