[EMAIL PROTECTED]:~$ sudo lsof -nP -i tcp:80
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
apache21372 www-data3u IPv6 13782 TCP *:80 (LISTEN)
apache21413 www-data3u IPv6 13782 TCP *:80 (LISTEN)
apache21464 www-data3u IPv6 13782 TCP
Which apache2-mpm-* package are you using?
[EMAIL PROTECTED]:~$ dpkg -l apache2-mpm-prefork
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
Hi Paul,
it seems if there is a large number of child processes, apache can
take a long time to close all the listening sockets. If this is your
problem, then apache should die some time after an unsuccessful
restart. In this case, you could try to increase the wait time in the
init script
Hi Stefan,
It was already set to 4, I read in the script it something about
increasing it to atleast 12, So to be on the safe side I increased it to
30.
That makes it take abit longer to restart but thats a better solution than
forcing it to stop and then having to reboot to clean
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=366124
You can use lsof or netstat -tlnp (as root) to determine which
processes keep the listening sockets open. Does this fit your
problem?
Stefan
I have restarted apache to capture some more information
sudo /etc/init.d/apache2 restart
On Thursday 19 June 2008, Paul wrote:
Is there any traces or dumps I can do to provide more information.
Maybe the output of
sudo lsof -nP -i tcp:80
sudo sh -x /etc/init.d/apache2 restart
sudo lsof -nP -i tcp:80
can give more information. You might have to install lsof first.
Which
On Tuesday 17 June 2008, Paul wrote:
Some times I have noticed the system is abit sluggish when I
restart apache, the main problem is with apache, it creates lots
of child processes that refuse to die, the biggest problem is it
then locks up the ports it is using and the only way to kill
package: apache2
version: 2.2.9-1
Severity: Critical
Why does apache2 refuse to restart or reload the configuration and if you
attempt it then the whole system needs to be rebooted. Any package that
dies bad enough to require a reboot has something badly broken in it.
waitpid(6285,
Hi,
On Tue, 17 Jun 2008, Paul wrote:
Why does apache2 refuse to restart or reload the configuration and if you
attempt it then the whole system needs to be rebooted. Any package that dies
bad enough to require a reboot has something badly broken in it.
Please be more verbose. What happens
My apologies for the brief bug, it was sent after a 13 hour day at work.
Some times I have noticed the system is abit sluggish when I restart
apache, the main problem is with apache, it creates lots of child
processes that refuse to die, the biggest problem is it then locks up the
ports it
10 matches
Mail list logo
