Re: Apache locking up on WinNT
I added the warns to the scripts and it appears that access to the modules is serialised. Each call to the handler has to run to completion before any other handlers can execute. Yes, on NT all accesses to the perl part are serialized. This will not change before mod_perl 2.0 Oh my ... Indeed this happens. This is horrible ;o( and make mod_perl unusable with NT web site with many visitors ;o( How do you think - for intranet web application is it reasonable to run few Apaches (with mod_perl) on the same box ? [and assign users to the different apache]. How many Apache can I start ? BTW Does anyone know when mod_perl 2.0 is supposed to be released ? Best regards Waldek Grudzien _ http://www.uhc.lublin.pl/~waldekg/ University Health Care Lublin/Lubartow, Poland tel. +48 81 44 111 88 ICQ # 20441796
Re: Apache locking up on WinNT
Oh my ... Indeed this happens. This is horrible ;o( and make mod_perl unusable with NT web site with many visitors ;o( How do you think - for intranet web application is it reasonable to run few Apaches (with mod_perl) on the same box ? yes, but as far as I know that isn't possible as service. You must start them from the DOS prompt. (I didn't look at this since 1.3.6, so there may a change in 1.3.9) [and assign users to the different apache]. How many Apache can I start ? Only a matter of your memory... You should also consider to move long running script to good old (external) cgi scripts BTW Does anyone know when mod_perl 2.0 is supposed to be released ? It should be comming when Apache 2.0 is comming, don't know when this will be, but I don't expect it in the near future Gerald
Re: Apache locking up on WinNT
Oh my ... Indeed this happens. This is horrible ;o( and make mod_perl unusable with NT web site with many visitors ;o( How do you think - for intranet web application is it reasonable to run few Apaches (with mod_perl) on the same box ? yes, but as far as I know that isn't possible as service. You must start them from the DOS prompt. (I didn't look at this since 1.3.6, so there may a change in 1.3.9) In 1.3.9 you can register as many services as you want... ;o) [and assign users to the different apache]. How many Apache can I start ? Only a matter of your memory... How much apaches with mod_perl won't hurt 128 MB NT box ? (for application with 91 scripts and modules with summary PERL code 376 KB) (or how many RAM should I add ?) You should also consider to move long running script to good old (external) cgi scripts I know - now... ;o) BTW Does anyone know when mod_perl 2.0 is supposed to be released ? It should be comming when Apache 2.0 is comming, don't know when this will be, but I don't expect it in the near future It is not good news ;-(. Many fellows can choose meantime PHP instead PERL solutions ;o( (moreover speed charts says PHPis a little bit faster than mod_perl http://www.chamas.com/hello_world.html) I like PERL so much so I wouldn't like to be forced (by boss ;o)) some day to start next web apps with PHP ;o( Best regards, Waldek Grudzien _ http://www.uhc.lublin.pl/~waldekg/ University Health Care Lublin/Lubartow, Poland tel. +48 81 44 111 88 ICQ # 20441796
Apache locking up on WinNT
I am currently in the process of transferring a database driven site from IIS to Apache on NT using mod_perl. Apache seems to lock up after about 10-20 minutes and the only way to get things going again is to restart Apache (Apache is running from the console not as a service). The site isn't particularly heavily loaded, currently handling a request every 5-10 seconds. I have also noticed that on some occasions (after the lock up) the error.log contains an entry stating that one of my content handlers is not defined, the content handler works fine until this point. I have checked the FAQ's etc and I am almost 100% certain that I don't have a problem with my namespace. When the server locks up netstat lists a number of clients who have a TIME_WAIT status on port 8080 but these connections are not listed in /server-status. I am using Apache/1.3.9 (Win32) with mod_perl/1.21 which I downloaded in December last year. My worry is that there is a problem with Apache on NT and mod_perl, given that Apache on NT is multi-threaded. Unfortunately, I am stuck in NT due to parts of the legacy system, otherwise I would move to Linux or FreeBSD. If anyone can offer any suggestions I would be most grateful as the only alternative I have is to re-engineer the site in IIS. If anyone has any suggestions, or would like further specific detail then please let me know. Thanks Matt -- Matthew RobinsonE: [EMAIL PROTECTED] Torrington Interactive Ltd W: www.torrington.net 4 Printing House Yard T: (44) 171 613 7200 LONDON E2 7PR F: (44) 171 613 7201
Re: Apache locking up on WinNT
I am currently in the process of transferring a database driven site from IIS to Apache on NT using mod_perl. Apache seems to lock up after about 10-20 minutes and the only way to get things going again is to restart Apache (Apache is running from the console not as a service). Well - I am using NT distribution (APACHE 1.3.9 / mod_perl 1.21/ PERL 5.005_003) downloaded from : ftp://theoryx5.uwinnipeg.ca/pub/other/ and noticed no problem with it. Maybe the problem lays in your scripts (have you analised entry from apache log you have descibed) ? Regards, Waldek Grudzien _ http://www.uhc.lublin.pl/~waldekg/ University Health Care Lublin/Lubartow, Poland tel. +48 81 44 111 88 ICQ # 20441796
Re: Apache locking up on WinNT
At 12:20 PM 1/17/00 +0100, Waldek Grudzien wrote: I am currently in the process of transferring a database driven site from IIS to Apache on NT using mod_perl. Apache seems to lock up after about 10-20 minutes and the only way to get things going again is to restart Apache (Apache is running from the console not as a service). Well - I am using NT distribution (APACHE 1.3.9 / mod_perl 1.21/ PERL 5.005_003) downloaded from : ftp://theoryx5.uwinnipeg.ca/pub/other/ and noticed no problem with it. Maybe the problem lays in your scripts (have you analised entry from apache log you have descibed) ? I have just gone back and checked the logs. The majority of the time the server locks up without putting anything in the error log. Currently, there are only about 10 content handlers in the system and I am fairly confident they work. When it locks up I can still telnet into the server and get a connection immediately but I don't get a response. I have waited considerably longer than the Timeout (60 secs) and the connections are not terminated. On some occasions /server-status has reported that almost all of the threads are reading (although they don't give the remote addresses). Normally, I would expect a maximum of about 5 threads doing concurrent processing. I am fairly happy to accept that the problem is in my scripts but I am not entirely sure what I am doing wrong. Matt Regards, Waldek Grudzien _ http://www.uhc.lublin.pl/~waldekg/ University Health Care Lublin/Lubartow, Poland tel. +48 81 44 111 88 ICQ # 20441796 -- Matthew RobinsonE: [EMAIL PROTECTED] Torrington Interactive Ltd W: www.torrington.net 4 Printing House Yard T: (44) 171 613 7200 LONDON E2 7PR F: (44) 171 613 7201
RE: Apache locking up on WinNT
I have just gone back and checked the logs. The majority of the time the server locks up without putting anything in the error log. Currently, there are only about 10 content handlers in the system and I am fairly confident they work. When it locks up I can still telnet into the server and get a connection immediately but I don't get a response. I have waited considerably longer than the Timeout (60 secs) and the connections are not terminated. I guess it locks up somewhere in perl part, because perl isn't renetrant, so everythingelse has to wait! On some occasions /server-status has reported that almost all of the threads are reading (although they don't give the remote addresses). Normally, I would expect a maximum of about 5 threads doing concurrent processing. I am fairly happy to accept that the problem is in my scripts but I am not entirely sure what I am doing wrong. I would suggest, put warn "foo" ; allover in your perl code and then look in the error log and see where the last warn came from, then you have the place where it lock up. Gerald
RE: Apache locking up on WinNT
At 01:26 PM 1/17/00 +0100, Gerald Richter wrote: I would suggest, put warn "foo" ; allover in your perl code and then look in the error log and see where the last warn came from, then you have the place where it lock up. Gerald I added the warns to the scripts and it appears that access to the modules is serialised. Each call to the handler has to run to completion before any other handlers can execute. I think the problem I am getting is that somebody on a slow link comes along and effectively limits every user to run at that speed. If I had been more patient I would have got a response. Once the queue of requests cleared. Can anyone verify this to be the case. If this is the case I will have to go back to IIS (for the time being) as I don't have time to work around this. If you look at the following section of the log you will see that all of the accesses are sequential but there is a period when a number of requests appear to be bunched up after a slowish response. Names have been changed to protect the innocent. [Mon Jan 17 13:48:53 2000] [warn] Module::A::handler start [Mon Jan 17 13:48:53 2000] [warn] Module::A::handler exit [Mon Jan 17 13:48:57 2000] [warn] Module::B::handler start [Mon Jan 17 13:48:57 2000] [warn] Module::B::handler exit [Mon Jan 17 13:49:07 2000] [warn] Module::C::handler start [Mon Jan 17 13:49:29 2000] [warn] Module::C::handler exit [Mon Jan 17 13:49:29 2000] [warn] Module::D::handler start [Mon Jan 17 13:49:29 2000] [warn] Module::D::handler exit [Mon Jan 17 13:49:29 2000] [warn] Module::C::handler start [Mon Jan 17 13:50:02 2000] [warn] Module::C::handler exit [Mon Jan 17 13:50:14 2000] [warn] Module::A::handler start [Mon Jan 17 13:50:14 2000] [warn] Module::A::handler exit [Mon Jan 17 13:50:14 2000] [warn] Module::C::handler start [Mon Jan 17 13:50:21 2000] [warn] Module::C::handler exit [Mon Jan 17 13:50:22 2000] [warn] Module::C::handler start [Mon Jan 17 13:50:51 2000] [warn] Module::C::handler exit Matt -- Matthew RobinsonE: [EMAIL PROTECTED] Torrington Interactive Ltd W: www.torrington.net 4 Printing House Yard T: (44) 171 613 7200 LONDON E2 7PR F: (44) 171 613 7201
RE: Apache locking up on WinNT
I added the warns to the scripts and it appears that access to the modules is serialised. Each call to the handler has to run to completion before any other handlers can execute. Yes, on NT all accesses to the perl part are serialized. This will not change before mod_perl 2.0 Gerald I had a horrible feeling it was going to have something to do with the fact that Apache on NT is multi-threaded and perl isn't (yet). I assume that Apache::Registry has the same problems. However, good old fashioned CGI scripts in the /cgi-bin directory should be OK? Does anybody have any performance stats between perl running externally on Apache and PerlIS on IIS? Matt -- Matthew RobinsonE: [EMAIL PROTECTED] Torrington Interactive Ltd W: www.torrington.net 4 Printing House Yard T: (44) 171 613 7200 LONDON E2 7PR F: (44) 171 613 7201
