Apache fails - refuses reboot

[sjau]

Hiya

I noticed now 3 times that apache2 suddenly fails.
When I try to restart it I just get this error message:

root@t390:~# /etc/init.d/apache2 restart
Forcing reload of web server: Apache2 ... no pidfile found! not running?(98)Addr
ess already in use: make_sock: could not bind to address [::]:443
no listening sockets available, shutting down
Unable to open logs
root@t390:~#

I don't exactely know what to do. What I did so far is rebooting the whole server. This then makes the server work again just fine.

Has anyone encountered this before?

[platd]

Do you have some sort of software running that monitors your apache service and restarts it if it thinks it is down.
I had one running my self that gave them exact symptoms but i cant remember it's name at the moment . So i ditched it :) it kept getting the wrong end of the stick and restarting apache when it was fine and making a pigs ear of it :)

[vlsimpson]

Something else is listening on port 80 or whatever port you have apache configured for. nmap localhost will show you what's on the port in question;
ps ax to get the pid and kill -9 pid. Restart apache. Maybe :)

[falko]

Anything in the Apache error log?


Unable to open logs
root@t390:~#

Do the log files that Apache tries to log to exist?

[sjau]

Next time it happens I will check :)
Thx for the suggestions so far.

[sjau]

so, same situation:


root@t390:/var/log# nmap localhost

Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2006-07-09 14:39 CEST
Interesting ports on localhost.localdomain (127.0.0.1):
(The 1649 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
25/tcp open smtp
53/tcp open domain
80/tcp open http
110/tcp open pop3
143/tcp open imap
199/tcp open smux
443/tcp open https
783/tcp open hp-alarm-mgr
953/tcp open rndc
993/tcp open imaps
2500/tcp open rtsserv
3306/tcp open mysql


@ Falko
Error log is empty


-rw-r----- 1 root adm 161 2006-04-06 06:25 access.log.5.gz
-rw-r----- 1 root adm 161 2006-03-19 06:25 access.log.6.gz
-rwxr-xr-x 1 root root 171 2006-03-13 06:25 access.log.7.gz*
drwx------ 4 root root 4096 2005-12-22 22:26 confixx/
-rw-r----- 1 root adm 0 2006-07-09 06:26 error.log
-rw-r----- 1 root adm 11775843 2006-07-09 06:26 error.log.1
-rw-r----- 1 root adm 6244362 2006-05-14 06:25 error.log.10.gz
-rw-r----- 1 root adm 313628 2006-05-07 06:25 error.log.11.gz
-rw-r----- 1 root adm 487725 2006-04-30 06:25 error.log.12.gz

[platd]

do a ps aux |grep httpd next time or killall httpd etc or what ever you have to do to kill it then try a clean startup.
Of course you still need need to find why it's going tits in the first place.
There must be some thing in one of the logs. maybe turn on apache debug logging features what ever they maybe a quick squint through the docs should reveal that

[sjau]

I found out what was blocking that damn thing:

http://www.textpaste.net/TextPaste/view.php?kevjt4

However there are two things that keeps worrying me:

1.) Why does syslogd run on apache ports???
2.) Why did apache stop first place???

[falko]

Can you check /etc/logrotate.d/apache if it restarts or just reloads Apache?
I had problems when Apache was just reloaded. A few times it didn't come up again so I modified the script so that it restarts Apache now which is working fine. :)