You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by "Nelson, Ben" <bn...@rightnow.com> on 2001/12/11 21:01:38 UTC
Apache mysteriously stops answering requests
I have several servers that I have installed Apache 1.3.22 on and I'm seeing
some interesting problems. The httpd daemon(s) start up just fine and start
answering requests just fine as well. The problem is that after some amount
of time ( it's not consistent ) the daemons stop answering http requests.
Sometimes it stays up for 16-17 hours, other times only for 3-4 hours.
Sometimes it'll serve up to ~180,00 hits before it dies, other times it'll
serve as few as ~50,000.
The httpd daemons are running, but when I try to connect to the machine
using lynx I get the following errors:
<lynx snip>
Looking up localhost.
Making HTTP connection to localhost.
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Unexpected network read error; connection aborted.
Can't Access `http://localhost/'
Alert!: Unable to access document.
</lynx snip>
The machine is listening on port 80, however :
<shell snip>
root@websc05:/var/log/httpd# telnet localhost 80
Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.
GET / HTTP/1.0
Connection closed by foreign host.
root@websc05:/var/log/httpd#
</shell snip>
netstat -an also show that the machine is listening on 80.
Nothing unusual shows up in the error_log or the access logs. When I attach
strace to the running httpd process I get the following over and over again:
<strace snip>
select(0, NULL, NULL, NULL, {0, 790000}) = 0 (Timeout)
time(NULL) = 1008090657
wait4(-1, 0xbffffa9c, WNOHANG, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
time(NULL) = 1008090658
wait4(-1, 0xbffffa9c, WNOHANG, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
time(NULL) = 1008090659
wait4(-1, 0xbffffa9c, WNOHANG, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
time(NULL) = 1008090660
wait4(-1, 0xbffffa9c, WNOHANG, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
time(NULL) = 1008090661
wait4(-1, 0xbffffa9c, WNOHANG, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
time(NULL) = 1008090662
wait4(-1, 0xbffffa9c, WNOHANG, NULL) = 0
select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
time(NULL) = 1008090663
select(7, NULL, [4 6], NULL, {0, 0}) = 2 (out [4 6], left {0, 0})
</strace snip>
vmstat also shows that we are not exhausting our resources.
<vmstat snip>
root@websc05:~# vmstat 1
procs memory swap io system
cpu
r b w swpd free buff cache si so bi bo in cs us sy
id
2 0 0 0 1801224 175736 51956 0 0 0 2 27 20 2 1
28
0 0 0 0 1801224 175736 51956 0 0 0 0 119 51 0 2
98
0 0 0 0 1801224 175736 51956 0 0 0 23 120 24 0 2
98
0 0 0 0 1801224 175736 51956 0 0 0 0 113 21 0 4
96
0 0 0 0 1801224 175736 51956 0 0 0 4 178 115 5 5
90
0 0 0 0 1801224 175736 51956 0 0 0 0 122 57 0 3
97
0 0 0 0 1801224 175736 51956 0 0 0 5 119 58 0 3
97
</vmstat snip>
I have run Apache 1.3.12 on this same machine with the same httpd.conf and
it stays up with no problems at all. I have many other web servers running
1.3.12 and they all run very reliably.
The machine is a dual PIII 700, 2G RAM, running linux kernel 2.2.14.
Has anyone else seen anything similar or heard of anything similar??? I'd
like to upgrade all of my machines to 1.3.22, but not until I can get it
running reliably.
--Ben
---------------------------------------------------------------------
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
For additional commands, e-mail: users-help@httpd.apache.org
Re[2]: Apache mysteriously stops answering requests
Posted by Manuel Carrara <ap...@w3suite.com>.
> On Tuesday 11 December 2001 20:01, you wrote:
>> I have several servers that I have installed Apache 1.3.22 on and I'm
>> seeing some interesting problems. The httpd daemon(s) start up just fine
>> and start answering requests just fine as well. The problem is that after
>> some amount of time ( it's not consistent ) the daemons stop answering http
>> requests. Sometimes it stays up for 16-17 hours, other times only for 3-4
>> hours. Sometimes it'll serve up to ~180,00 hits before it dies, other times
>> it'll serve as few as ~50,000.
+1 but I use apache 1.3.22 with php on Mandrake 8.1 with selfbulid
2.4.13 Kernel.
>> Nothing unusual shows up in the error_log or the access logs. When I
>> attach strace to the running httpd process I get the following over and
>> over again: <strace snip>
There is also nothing of this in my logfiles
>> vmstat also shows that we are not exhausting our resources.
+1
So what next, tell what additional informations do you need
-Manuel
---------------------------------------------------------------------
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
For additional commands, e-mail: users-help@httpd.apache.org
Re: Apache mysteriously stops answering requests
Posted by Derek Conniffe <de...@rivertower.ie>.
What O/S are you using?
I've also had (hopefully not have :) ) this problem over the last few months.
I'm using sun os 5.8 and I think the problem is either with SYSV shared
memory or posix threads (I think only LWP threads work correctly under 5.8).
I'm very interested in seeing how you get along...
Derek
On Tuesday 11 December 2001 20:01, you wrote:
> I have several servers that I have installed Apache 1.3.22 on and I'm
> seeing some interesting problems. The httpd daemon(s) start up just fine
> and start answering requests just fine as well. The problem is that after
> some amount of time ( it's not consistent ) the daemons stop answering http
> requests. Sometimes it stays up for 16-17 hours, other times only for 3-4
> hours. Sometimes it'll serve up to ~180,00 hits before it dies, other times
> it'll serve as few as ~50,000.
>
> The httpd daemons are running, but when I try to connect to the machine
> using lynx I get the following errors:
>
> <lynx snip>
> Looking up localhost.
> Making HTTP connection to localhost.
> Sending HTTP request.
> HTTP request sent; waiting for response.
> Alert!: Unexpected network read error; connection aborted.
> Can't Access `http://localhost/'
> Alert!: Unable to access document.
> </lynx snip>
>
> The machine is listening on port 80, however :
>
> <shell snip>
> root@websc05:/var/log/httpd# telnet localhost 80
> Trying 127.0.0.1...
> Connected to localhost.localdomain.
> Escape character is '^]'.
> GET / HTTP/1.0
>
> Connection closed by foreign host.
> root@websc05:/var/log/httpd#
> </shell snip>
>
> netstat -an also show that the machine is listening on 80.
>
> Nothing unusual shows up in the error_log or the access logs. When I
> attach strace to the running httpd process I get the following over and
> over again: <strace snip>
> select(0, NULL, NULL, NULL, {0, 790000}) = 0 (Timeout)
> time(NULL) = 1008090657
> wait4(-1, 0xbffffa9c, WNOHANG, NULL) = 0
> select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
> time(NULL) = 1008090658
> wait4(-1, 0xbffffa9c, WNOHANG, NULL) = 0
> select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
> time(NULL) = 1008090659
> wait4(-1, 0xbffffa9c, WNOHANG, NULL) = 0
> select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
> time(NULL) = 1008090660
> wait4(-1, 0xbffffa9c, WNOHANG, NULL) = 0
> select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
> time(NULL) = 1008090661
> wait4(-1, 0xbffffa9c, WNOHANG, NULL) = 0
> select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
> time(NULL) = 1008090662
> wait4(-1, 0xbffffa9c, WNOHANG, NULL) = 0
> select(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
> time(NULL) = 1008090663
> select(7, NULL, [4 6], NULL, {0, 0}) = 2 (out [4 6], left {0, 0})
> </strace snip>
>
> vmstat also shows that we are not exhausting our resources.
> <vmstat snip>
> root@websc05:~# vmstat 1
> procs memory swap io system
> cpu
> r b w swpd free buff cache si so bi bo in cs us sy
> id
> 2 0 0 0 1801224 175736 51956 0 0 0 2 27 20 2
> 1 28
> 0 0 0 0 1801224 175736 51956 0 0 0 0 119 51 0
> 2 98
> 0 0 0 0 1801224 175736 51956 0 0 0 23 120 24 0
> 2 98
> 0 0 0 0 1801224 175736 51956 0 0 0 0 113 21 0
> 4 96
> 0 0 0 0 1801224 175736 51956 0 0 0 4 178 115 5
> 5 90
> 0 0 0 0 1801224 175736 51956 0 0 0 0 122 57 0
> 3 97
> 0 0 0 0 1801224 175736 51956 0 0 0 5 119 58 0
> 3 97
> </vmstat snip>
>
> I have run Apache 1.3.12 on this same machine with the same httpd.conf and
> it stays up with no problems at all. I have many other web servers running
> 1.3.12 and they all run very reliably.
>
> The machine is a dual PIII 700, 2G RAM, running linux kernel 2.2.14.
>
> Has anyone else seen anything similar or heard of anything similar??? I'd
> like to upgrade all of my machines to 1.3.22, but not until I can get it
> running reliably.
>
> --Ben
>
> ---------------------------------------------------------------------
> 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
> For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
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
For additional commands, e-mail: users-help@httpd.apache.org