Perl stopped working on Apache 1.3.3, but then starts?
Hi, I had a situation where I had to cycle power to my G5 Mac running Apache 1.3.3 OS X 10.3.7 today. After reboot, I found that Perl scripts no longer reliably run via the web. I can get pages to load a few times, but then I get the Internal error page, but do not see any errors in apache error log. I tested via Terminal calling a Perl script and it seemed to work fine. If you test this link and keep refreshing it, you will see it works, stops, works, etc: http://osx.inno-tech.com/cgi-bin/perltest.cgi I had a customer tell me he was updating something during the reboot, so I figure something got corrupted somewhere. I already fixed permissions and that didn't help. Any ideas on what file(s) to replace to get things working again. I have an image of the system. Thanks in advance! George
Re: Perl stopped working on Apache 1.3.3, but then starts?
On Mon, 7 Feb 2005, InnoTech Support wrote: > I had a situation where I had to cycle power to my G5 Mac running Apache > 1.3.3 OS X 10.3.7 today. After reboot, I found that Perl scripts no longer > reliably run via the web. I can get pages to load a few times, but then I > get the Internal error page, but do not see any errors in apache error log. > I tested via Terminal calling a Perl script and it seemed to work fine. What shows up in the Apache logs when someone hits this page? Do successes & errors look the same in the log? -- Chris Devers
RE: Perl stopped working on Apache 1.3.3, but then starts?
On Tue, 8 Feb 2005, InnoTech Support wrote: > Did not see any errors in Apache error log, nor anything in web log. Today, > all is well, seems to be working fine. > > Yesterday, we were pushing much more traffic than usual out. It appears as > if Apache was too busy dealing with web requests, and could not process cgi > requests until traffic subsided. Perhaps Perl/cgi requests are lower > priority? Who knows? I think your best bet, if the problem appears to have vanished, is to look over the Apache logs for the time frame that the problem was happening to see if there is any record of what the problem may have been. You may or may not see any useful patterns, but it sounds like that's the only data you have to work with now. -- Chris Devers
Re: Perl stopped working on Apache 1.3.3, but then starts?
Apache was too busy dealing with web requests, and could not process cgi requests until traffic subsided. Perhaps Perl/cgi requests are lower priority? I think it's more complex than that, but serving simple html files takes less time, requires less memory, can more easily be cached and so on. If your server is running at 99% CPU capacity or 99% RAM or whatever, it's more likely that errors will occur with dynamic than with static files, surely?
RE: Perl stopped working on Apache 1.3.3, but then starts?
Hi Chris, Did not see any errors in Apache error log, nor anything in web log. Today, all is well, seems to be working fine. Yesterday, we were pushing much more traffic than usual out. It appears as if Apache was too busy dealing with web requests, and could not process cgi requests until traffic subsided. Perhaps Perl/cgi requests are lower priority? Thanks George > -Original Message- > From: Chris Devers [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 08, 2005 10:39 AM > To: InnoTech Support > Cc: macosx@perl.org > Subject: Re: Perl stopped working on Apache 1.3.3, but then starts? > > On Mon, 7 Feb 2005, InnoTech Support wrote: > > > I had a situation where I had to cycle power to my G5 Mac running Apache > > 1.3.3 OS X 10.3.7 today. After reboot, I found that Perl scripts no > longer > > reliably run via the web. I can get pages to load a few times, but then > I > > get the Internal error page, but do not see any errors in apache error > log. > > I tested via Terminal calling a Perl script and it seemed to work fine. > > What shows up in the Apache logs when someone hits this page? > > Do successes & errors look the same in the log? > > > > -- > Chris Devers
