You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2005/12/28 20:24:59 UTC
DO NOT REPLY [Bug 38065] New: - Apache2 rapidly consumes a lot of memory and crashes the server
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38065>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38065
Summary: Apache2 rapidly consumes a lot of memory and crashes the
server
Product: Apache httpd-2
Version: 2.0.55
Platform: PC
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P2
Component: worker
AssignedTo: bugs@httpd.apache.org
ReportedBy: ruby@joker.linuxstuff.pl
We're running Apache 2.0.55 (from Debian testing package ver 2.0.55-3) on Linux
2.6.14.3. We use worker MPM, mod_actions, mod_rewrite, mod_layout and fastcgi
running php. Box serves about 40-50 requests per second. Once in a while one of
apache2 processes rapidly starts to consume lot of memory, freezing the system
and finally crashing it, without any chance to stop it or trace it. We wasn't
able to find out what is causing this, error.log doesn't say anything useful and
because of sudden apache2 process behaviour tracing is also very hard.
Below is attached 'top' screen right before the actual crash, as well as some
syslog output before another server reboot.
----------
top - 21:15:21 up 1:29, 2 users, load average: 17.18, 9.77, 6.55
Tasks: 116 total,2 running, 114 sleeping,0 stopped,0 zombie
Cpu(s): 1.3% us, 5.3% sy, 0.0% ni, 0.0% id, 90.7% wa, 1.3% hi, 1.3% si
Mem:905776k total,898128k used,7648k free,404k buffers
Swap:0k total,0k used,0k free,18236k cached
PID USERPR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
130 root150000 S 3.0 0.00:00.13 pdflush
6485 www-data 210 881m 600m 1100 S 1.3 67.90:04.83 apache2
9959 www-data 160 284m 8404 1124 S 1.0 0.90:00.57 apache2
1483 root170 2620 544 412 D 0.3 0.10:01.05 syslogd
4789 www-data 250 293m 16m 1136 S 0.3 1.90:06.94 apache2
7270 root160 2196 1100 820 R 0.3 0.10:01.30 top
9790 www-data 170 17500 5552 1272 D 0.3 0.60:00.43 php
10015 www-data 160 284m 8448 1096 S 0.3 0.90:00.59 apache2
----------
Dec 28 03:13:35 werewolf kernel: Out of Memory: Killed process 1080 (apache2).
Dec 28 03:13:35 werewolf kernel: Out of Memory: Killed process 25021 (apache2
).
Dec 28 03:13:55 werewolf kernel: Out of Memory: Killed process 25084 (apache2).
Dec 28 03:13:55 werewolf kernel: Out of Memory: Killed process 25116 (apache2).
Dec 28 03:14:28 werewolf kernel: Out of Memory: Killed process 25087 (apache2).
Dec 28 03:14:29 werewolf kernel: Out of Memory: Killed process 25164 (apache2).
----------
apache2.conf (parts):
ServerLimit 12
<IfModule worker.c>
StartServers 3
MaxClients 384
MinSpareThreads 20
MaxSpareThreads 50
ThreadsPerChild 32
MaxRequestsPerChild 10000
</IfModule>
AddOutputFilterByType LAYOUT text/html application/x-httpd-php
LayoutEndTag </BODY>
LayoutFooter /some_document.html
FastCgiServer /usr/lib/cgi-bin/php4
FastCgiConfig -idle-timeout 15
AddHandler php-fastcgi .php .php3 .php4
<Location /cgi-bin/php>
SetHandler fastcgi-script
</Location>
Action php-fastcgi /cgi-bin/php
AddType application/x-httpd-php .php .php3 .php4
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 38065] - Apache2 rapidly consumes a lot of memory and crashes the server
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38065>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38065
------- Additional Comments From rob@alterlinks.fr 2007-02-12 11:05 -------
Sorry, it's not my intention to change the bug report into some sort of
discussion forum.
I've upgraded yesterday PHP 5.2.0 to 5.2.1 and the problem disappeared. The
other three Apache instances are using PHP 4.4.4, only the one instance having
this memory problem was using 5.2.0.
Rob starts to look into the direction of PHP ...
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 38065] - Apache2 rapidly consumes a lot of memory and crashes the server
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38065>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38065
wrowe@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
------- Additional Comments From wrowe@apache.org 2007-02-26 01:23 -------
1. you don't have to reopen the bug to add a question/comment, and your email
addresses are all out there to share experiences (users@httpd.a.o is a great
place to do this, too). Bugzilla isn't a user support forum, it's a defect
tracing forum :)
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 38065] - Apache2 rapidly consumes a lot of memory and crashes the server
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38065>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38065
rpluem@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
------- Additional Comments From rpluem@apache.org 2005-12-28 22:59 -------
Please try to limit the memory of the httpd processes by setting ulimit -m
before starting httpd and limit the memory of processes created by the httpd
childs via RLimitMEM. This should give you a chance to do traces and get more
information about the root cause. For debugging httpd please see
http://httpd.apache.org/dev/debugging.html.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 38065] - Apache2 rapidly consumes a lot of memory and crashes the server
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38065>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38065
ruby@joker.linuxstuff.pl changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution| |INVALID
------- Additional Comments From ruby@joker.linuxstuff.pl 2006-01-20 21:43 -------
This bug was caused by hardware problem and wasn't Apache fault. Sorry for
inconvience.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 38065] - Apache2 rapidly consumes a lot of memory and crashes the server
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38065>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38065
gabriel@oxeva.fr changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
------- Additional Comments From gabriel@oxeva.fr 2007-02-07 07:15 -------
(In reply to comment #5)
> This bug was caused by hardware problem and wasn't Apache fault. Sorry for
> inconvience.
What is this hardware problem ?
I have exactly the same problem, using apache 2.2.4 and the worker MPM. On in a
while one of the httpd children consume all the memory in a few seconds. I am
running a pool of apache servers, and the problem occurs randomly on these,
which make me thinks it's not a hardware issue. (I had some bad memory problem
and the kernel panics, triggered by Machine Check events in my case, no weird
process behavior or things like a process eating up memory).
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 38065] - Apache2 rapidly consumes a lot of memory and crashes the server
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38065>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38065
------- Additional Comments From rpluem@apache.org 2005-12-30 02:10 -------
(In reply to comment #2)
[..cut..]
>
> I've added this two lines:
>
> ulimit -S -m 25600
> ulimit -H -m 25600
>
> on top of apache2ctl script (which actually only calls "/usr/sbin/apache2 -k
> start"), without any result. Top still shows apache2 processes with resident
> size >= 30Mb. It already crashed our server two times, here's top output in last
Ups. I just traced ulimit of bash and it does not seem to set the correct limit.
It sets RLIMIT_RSS. ulimit -v sets RLIMIT_AS which also does not seem completely
correct to me, but this is at least checked by the brk syscall. So please try
again with ulimit -v.
Anyway it may be hard to find out the cause for this as you are using a fastcgi
module as a third party module.
[..cut..]
>
> We have some info that may be useful though. From time to time appear apache
> processes consuming a lot of memory. They grow in time, mostly exiting normally,
> so I'm not sure they're related to this bug. But I guess that's better than
> nothing. Below is a trace of one of this kind of processes.
Can you catch such processes with gdb and sent a backtrace or even better try to
catch the whole flow with ltrace?
[..cut..]
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 38065] - Apache2 rapidly consumes a lot of memory and crashes the server
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38065>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38065
------- Additional Comments From juice@tpi.pl 2005-12-30 18:21 -------
i work with Michal (first post author) to solve this bug on our server.
Today i moved to prefork apache + mod_php and the bug is still there, so this
is not about fastcgi or threads issue.
Its free hosting server, so it is likely somebody is doing something strange
to make it happen.
I tried limiting apache with -v, and it works, but to even load it i need to
incrase its virtual memory to around 40 MB or something to load all libs and
such, and so even simple scripts can run. (when i set it so high though, a lot
of apache process eating memory are still there, but it should stop the one
that is crashing the box)
I think the problem has two parts:
One is a lot of apache process that has more than initial 4MB (thats how much
prefork apache process has when i start it), are in memory. In just few
minutes they have usually around 10-15MB each, and are moving from 4MB to 15MB
slowly. (some of them are moving there faster, some slower)
of course this is just making this box work slow, but not crashing.
Another issue is happening few times per day, one apache process is going
crazy, taking all available memory, crashing the box in around 3-4 seconds.
Its hard to trace it, becouse there are other not-so-dangerous too big apache
process (also some kind of bug or misconfiguration issue i guess). Hard to
predict which one will sudennly go crazy and trace it, we would have to trace
all new processes, and thats not possible.
now, since i set -v limit, i hope this box-crashing bug (the first one) wont
happen again, but i still have no idea why these apache processes are growing
with time, from 4MB to even 15MB... looks like some memory leak, becouse when
i strace them, they are sometimes doing nothing, and still taking 15MB of
memory, compared to 4MB memory.
It seems similar to apache-mpm-worker, but with other numbers - with worker it
was around 10MB or so initially growing up to 70MB. And also one crazy
happening few times a day.
thanks for the -v tip, now i wait to see if server is still crashing or not,
but the other memory eating apach processes issue is still there. I dont know
is it connected to the one that is taking ALL memory in seconds, but it might
be.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 38065] - Apache2 rapidly consumes a lot of memory and crashes the server
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38065>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38065
------- Additional Comments From ruby@joker.linuxstuff.pl 2005-12-29 23:53 -------
(In reply to comment #1)
> Please try to limit the memory of the httpd processes by setting ulimit -m
> before starting httpd and limit the memory of processes created by the httpd
> childs via RLimitMEM. This should give you a chance to do traces and get more
> information about the root cause. For debugging httpd please see
> http://httpd.apache.org/dev/debugging.html.
I've added this two lines:
ulimit -S -m 25600
ulimit -H -m 25600
on top of apache2ctl script (which actually only calls "/usr/sbin/apache2 -k
start"), without any result. Top still shows apache2 processes with resident
size >= 30Mb. It already crashed our server two times, here's top output in last
4 seconds:
top - 22:03:16 up 1 day, 1:33, 2 users, load average: 8.26, 6.90, 4.71
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
23439 www-data 19 0 372m 94m 1820 S 28.3 10.7 0:08.90 apache2
top - 22:03:18 up 1 day, 1:33, 2 users, load average: 9.76, 7.23, 4.83
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
23439 www-data 19 0 551m 273m 1820 S 53.1 30.9 0:09.97 apache2
132 root 15 0 0 0 0 D 9.9 0.0 0:27.16 kswapd0
This apache process was spawned after 22:03:14, then it consumed 273Mb of memory
in about 4 seconds, and finally frozen our box (probably taking rest of memory).
In this situation you understand it's hard to deliver any debug information. I'm
suprised that ulimit doesn't work with apache, maybe we use it the wrong way?
We have some info that may be useful though. From time to time appear apache
processes consuming a lot of memory. They grow in time, mostly exiting normally,
so I'm not sure they're related to this bug. But I guess that's better than
nothing. Below is a trace of one of this kind of processes.
# ls /proc/9200/task
9200 9211 9214 9215 9224 9233
# strace -p 9200
Process 9200 attached - interrupt to quit
read(4, 0xbfc73f57, 1) = ? ERESTARTSYS (To be restarted)
--- SIGTERM (Terminated) @ 0 (0) ---
sigreturn() = ? (mask now HUP INT QUIT USR1 ALRM
STKFLT CHLD CONT TSTP TTIN TTOU URG XCPU XFSZ VTALRM PROF WINCH IO PWR?)
futex(0xb7024bf8, FUTEX_WAIT, 9202, NULL) = 0
futex(0xb6824bf8, FUTEX_WAIT, 9203, NULL) = 0
futex(0xb5824bf8, FUTEX_WAIT, 9205, NULL) = 0
munmap(0xb7025000, 8388608) = 0
futex(0xb5024bf8, FUTEX_WAIT, 9206, NULL) = 0
munmap(0xa6825000, 8388608) = 0
munmap(0xb6825000, 8388608) = 0
munmap(0xb6025000, 8388608) = 0
munmap(0xb5825000, 8388608) = 0
munmap(0xb5025000, 8388608) = 0
futex(0xb2824bf8, FUTEX_WAIT, 9211, NULL) = 0
munmap(0xb4825000, 8388608) = 0
munmap(0xb4025000, 8388608) = 0
munmap(0xb3825000, 8388608) = 0
munmap(0xb3025000, 8388608) = 0
== more than 100 entries ==
munmap(0xa562d000, 430080) = 0
munmap(0xa5a07000, 360448) = 0
munmap(0xa5d5e000, 315392) = 0
munmap(0xa604d000, 274432) = 0
munmap(0xa63dc000, 221184) = 0
munmap(0xa6547000, 180224) = 0
munmap(0xa6724000, 139264) = 0
brk(0x894d000) = 0x894d000
brk(0x889e000) = 0x889e000
brk(0x87ef000) = 0x87ef000
brk(0x87e5000) = 0x87e5000
brk(0x84c2000) = 0x84c2000
brk(0x84c0000) = 0x84c0000
brk(0x828a000) = 0x828a000
brk(0x8286000) = 0x8286000
brk(0x81a3000) = 0x81a3000
brk(0x819b000) = 0x819b000
write(7, "www.example.com 84."..., 1018) = 1018
write(8, "111.111.111.111 - - [28/Dec/2005:"..., 3930) = 3930
exit_group(0) = ?
Process 9200 detached
# strace -p 9211
Process 9211 attached - interrupt to quit
poll({fd=24, events=POLLOUT, revents=POLLOUT}?, 1, 60000) = 1
sendfile(24, 25, [1982387], 1012962) = 13140
poll({fd=24, events=POLLOUT, revents=POLLOUT}?, 1, 60000) = 1
sendfile(24, 25, [1995527], 999822) = 13140
== about 70 entries more ==
poll({fd=24, events=POLLOUT, revents=POLLOUT}?, 1, 60000) = 1
sendfile(24, 25, [2967887], 27462) = 13140
poll({fd=24, events=POLLOUT, revents=POLLOUT}?, 1, 60000) = 1
sendfile(24, 25, [2981027], 14322) = 13140
poll({fd=24, events=POLLOUT, revents=POLLOUT}?, 1, 60000) = 1
sendfile(24, 25, [2994167], 1182) = 1182
gettimeofday({1135804066, 798228}, NULL) = 0
gettimeofday({1135804066, 798456}, NULL) = 0
times({tms_utime=82, tms_stime=79, tms_cutime=0, tms_cstime=0}) = 1718650698
gettimeofday({1135804066, 798886}, NULL) = 0
shutdown(24, 1 /* send */) = 0
poll({fd=24, events=POLLIN, revents=POLLIN?, 1, 2000) = 1
read(24, "", 512) = 0
close(24) = 0
close(25) = 0
gettimeofday({1135804068, 189043}, NULL) = 0
gettimeofday({1135804068, 189074}, NULL) = 0
_exit(0) = ?
Process 9211 detached
This poll/sendfile pattern is similar to all of them.
Please help us. :) We'll be happy with any sane workaround.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
DO NOT REPLY [Bug 38065] - Apache2 rapidly consumes a lot of memory and crashes the server
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38065>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38065
------- Additional Comments From rob@alterlinks.fr 2007-02-09 13:45 -------
Me too I'm interrested in the answer if it was a hardware problem.
I'm using 4 Apache 1.3.37 instances on one machine and have the same problem;
Only one of them forks every now and then a child that eats 2Gb (=all) RAM in
about 4 seconds time, then fills up the swap, slowing down the machine.
Eventually, I have the same message in syslog;
Feb 9 22:07:17 diana kernel: Out of Memory: Killed process 32002 (httpd).
I have a hard time believing it's a hardware problem; only one of the 4 apache
installs is doing this, about 10 to 15 times a day. This "problem" started
about three weeks ago, never happened before.
The other three Apache instances are running fine.
Rob
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org