You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Goutam Baul <go...@cescltd.com> on 2004/07/20 07:18:25 UTC
[users@httpd] Apache stops responding after some days
Hello List,
I am running apache 2.0.40 with RedHat Linux 8.0. The server is also running
QMAIL and SQUIRREL MAIL. The apache is running only to serve the web mail
requests. The problem is that after running for say 6-7 days the apache
stops responding for some time. After 3-4 minutes it recovers on its own.
During that period the httpd error log reveals that the server was trying to
kill processes that were not in existence. The exact thing is like
"[warn] child process 17130 still did not exit, sending a SIGTERM".
There are several lines like this with different process id. After that we
get
"[notice] caught SIGTERM, shutting down
[Thu Jul 15 12:03:19 2004] [notice] Digest: generating secret for digest
authentication ...
[Thu Jul 15 12:03:19 2004] [notice] Digest: done
[Thu Jul 15 12:03:20 2004] [notice] Apache/2.0.40 (Red Hat Linux) configured
-- resuming normal operations".
Now I have started to regularly check the server status for the last 2 days.
Today I find that there are only 2 processes being served but there are 7
open slots with no current processes. The portion of the status report is
like
Srv PID Acc M CPU SS Req Conn Child Slot
Client VHost Request
0-1 674 0/171/841 _ 14.40 1 0 0.0 1.36
5.97 10.50.44.135 mail.cescltd.com GET
/src/read_body.php?mailbox=INBOX&passed_id=15&startMessage=
1-1 7656 0/450/450 W 36.11 2 0 0.0 2.90
2.90 10.50.17.79 mail.cescltd.com POST /src/redirect.php
HTTP/1.1
2-1 - 0/0/332 . 30.70 88474 0 0.0 0.00 3.01
10.50.11.48 mail.cescltd.com GET /src/left_main.php HTTP/1.1
3-1 - 0/0/999 . 88.83 13461 0 0.0 0.00 9.18
61.2.7.180 mail.cescltd.com GET /images/cesc_ltd.jpg HTTP/1.1
4-1 - 0/0/997 . 94.34 18132 0 0.0 0.00 8.81
10.50.2.14 mail.cescltd.com GET / HTTP/1.0
5-1 - 0/0/1000 . 84.58 14097 0 0.0 0.00
8.40 61.2.5.12 mail.cescltd.com GET /src/login.php HTTP/1.1
6-1 - 0/0/996 . 91.39 13932 0 0.0 0.00 8.78
10.50.2.14 mail.cescltd.com GET / HTTP/1.0
7-1 - 0/0/997 . 87.01 14076 0 0.0 0.00 6.64
61.2.5.12 mail.cescltd.com GET /src/right_main.php HTTP/1.1
8-1 10367 0/882/882 _ 74.36 11 0 0.0 6.69
6.69 10.50.44.135 mail.cescltd.com GET
/plugins/newmail/newmail.php HTTP/1.1
9-1 10370 0/892/892 _ 85.36 12 0 0.0 7.57
7.57 10.50.17.79 mail.cescltd.com GET /src/login.php HTTP/1.1
10-1 10371 0/889/889 _ 87.35 13 0 0.0 8.54
8.54 10.50.44.135 mail.cescltd.com GET /images/sort_none.png
HTTP/1.1
11-1 10379 0/170/170 W 14.56 0 0 0.0 1.08
1.08 10.50.81.22 mail.cescltd.com GET /server-status HTTP/1.1
12-1 10380 0/886/886 _ 84.16 4 0 0.0 8.85
8.85 10.50.17.82 mail.cescltd.com GET
/src/compose.php?mailbox=INBOX HTTP/1.1
13-1 10381 0/897/897 _ 76.62 12 0 0.0 5.90
5.90 10.50.44.135 mail.cescltd.com GET
/plugins/newmail/sounds/Notify.wav HTTP/1.1
14-1 10382 0/889/889 _ 82.67 13 0 0.0 5.28
5.28 10.50.44.135 mail.cescltd.com GET /images/down_pointer.png
HTTP/1.1
The question is : Is there anything wrong in the present status? Why there
are so many slots with no processes assigned? Is it normal ?
Sorry for this long mail. Actually I am a novice and don't know how to
proceed. Please guide me.
With regards,
Goutam
Re: [users@httpd] Apache stops responding after some days
Posted by Joshua Slive <js...@gmail.com>.
On Tue, 20 Jul 2004 10:48:25 +0530, Goutam Baul <go...@cescltd.com> wrote:
> Hello List,
>
> I am running apache 2.0.40 with RedHat Linux 8.0. The server is also running
> QMAIL and SQUIRREL MAIL. The apache is running only to serve the web mail
> requests. The problem is that after running for say 6-7 days the apache
> stops responding for some time. After 3-4 minutes it recovers on its own.
> During that period the httpd error log reveals that the server was trying to
> kill processes that were not in existence. The exact thing is like
>
> "[warn] child process 17130 still did not exit, sending a SIGTERM".
>
> There are several lines like this with different process id. After that we
> get
It seems quite clear that this is not a random happening. Rather,
someone/something is doing a server restart. If you do a non-graceful
restart, you need to except that there will be some amount of
down-time. So figure out what is doing the restart, and either get
rid of it, or change it to graceful. (Hint: start by checking all
your cron jobs.)
Another issue: you should really update to a more recent version of
apache. 2.0.40 is quite old.
Joshua.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org