Apache problem

Northwest · 02-14-2009, 06:43 AM

Hi, I was brought to this forum due a strange apache problem that occurred this morning. Suddenly my hosted websites weren't reachable anymore. I'm using debian and Direct Admin on a dedicated server. When I try to restart apache I get the following error.

Code:

~$ sudo /etc/init.d/httpd restart
Stopping httpd: 
Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs

the httpd/error_log says the following:

Code:

[Sat Feb 14 00:10:02 2009] [notice] SIGHUP received.  Attempting to restart
[Sat Feb 14 00:10:03 2009] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?
[Sat Feb 14 00:10:03 2009] [warn] Init: SSL server IP/port conflict: ****:443 (/********/httpd.conf:48) vs. www.****.nl:443 (/******/httpd.conf:48)
[Sat Feb 14 00:10:03 2009] [warn] Init: SSL server IP/port conflict: www.*******.com:443 (/*******/httpd.conf:48) vs. www.********.nl:443 (/******/httpd.conf:48)
[Sat Feb 14 00:10:03 2009] [warn] Init: SSL server IP/port conflict: localhost:443 (/etc/httpd/conf/extra/httpd-vhosts.conf:38) vs. www.*******.nl:443 (/******/httpd.conf:48)
[Sat Feb 14 00:10:03 2009] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!!
[Sat Feb 14 00:10:03 2009] [notice] Apache/2.2.10 (Unix) mod_ssl/2.2.10 OpenSSL/0.9.8c DAV/2 PHP/5.2.6 configured -- resuming normal operations
[Sat Feb 14 00:11:01 2009] [notice] caught SIGTERM, shutting down

any ideas anyone?

sleddog · 02-14-2009, 07:34 AM

I'd start by trying to resolve this error message:

Unable to open logs

- Check that logging directives in your vhost configurations are correct.
- Check that the directories exist and have correct permissions & ownership
- Check that log files haven't grown to gargantuan size

Other things to do...

- Issue an httpd stop
- Check the process list (ps aux or something similar) for still-running httpd processes. If any exist kill them off.
- Do an httpd start and see what is logged.

But I think the "Unable to open logs" error may be the root of the problem and is preventing Apache from running. Errors of level [warn] should not prevent Apache from running -- at least I don't think so.