Forum Moderators: phranque

Message Too Old, No Replies

apache exploding silently

         

blakmonk

2:20 pm on May 30, 2005 (gmt 0)

10+ Year Member



Hi,

I have this weird problem. Sometime httpd dies, without say why, nothing in the logs, not even a coredump.

On the web users end, the page just stops being displayed.

On the server side, The script just stops executing.

At first I thought it was a code issue, so I put traces in a cgi script to try to find out where the script would end. The traces would not even be writen when the problem happened, so I open/write/close the log file at every trace statement I put. With that approach I saw that the script would end at any point, even in the middle of a print statement.

This would bring me to beleive that the httpd just dies. But I get nothing in the logs, absolutely nothing.

It happens on servers doing mod_perl, on others doing cgi/perl, on apache 1.3. I haven't tested on mod_php n or on apache 2.0.

As anyone seen this?

Any hints as to were to look?

blakMonk

sitz

12:37 am on May 31, 2005 (gmt 0)

10+ Year Member



define 'dies'; does the process actually disappear from the process table, or is it running and just not responding? When this happens, can you telnet to port 80 on the server...

$ telnet server.example.net 80
Trying 192.168.1.1...
Connected to server.example.net.
Escape character is '^]'.

...or just hang...


$ telnet offlineserver.example.net 80
Trying 192.168.1.2...

...or something else? If apache is running, how many Apache children are running? What is 'MaxClients' set to in your httpd.conf?

blakmonk

12:58 am on May 31, 2005 (gmt 0)

10+ Year Member



define, death...

Well Only one httpd instance (child) dies, the other instances work perfectly.
I'm not anything ear MaxClients. I'm about 50 on a max of 200.

here is an example.

a script.cgi that writes this to a log file :

1
2
3
4
5
6
7

well, sometimes, it only gets to 4.

blakMonk