I just upgraded my server running Red Hat 7.2 from Apache 1.3.20 to Apache 1.3.24 and for some reason it won't start Apache. Here's what happens when I try to restart httpd:

[root@domain /]# /etc/rc.d/init.d/httpd start
Starting httpd: [Sat Jun 8 14:22:13 2002] [warn] NameVirtualHost MYIPADDRESS:80 has no VirtualHosts
[ OK ]
[root@domain /]

Here's a copy of the last few lines in my error log:

[Sat Jun 8 13:58:46 2002] [error] (88)Socket operation on non-socket: accept: (client socket)
[Sat Jun 8 13:58:46 2002] [error] (88)Socket operation on non-socket: accept: (client socket)
[Sat Jun 8 13:58:46 2002] [error] (88)Socket operation on non-socket: accept: (client socket)
[Sat Jun 8 13:58:46 2002] [notice] caught SIGTERM, shutting down
[Sat Jun 8 14:01:04 2002] [warn] NameVirtualHost MYIPADDRESS:80 has no VirtualHosts
[Sat Jun 8 14:01:05 2002] [crit] (98)Address already in use: make_sock: could not bind to port 209
[Sat Jun 8 14:02:55 2002] [warn] NameVirtualHost MYIPADDRESS:80 has no VirtualHosts
[Sat Jun 8 14:02:55 2002] [crit] (98)Address already in use: make_sock: could not bind to port 209
[Sat Jun 8 14:14:29 2002] [warn] NameVirtualHost MYIPADDRESS:80 has no VirtualHosts
[Sat Jun 8 14:14:29 2002] [crit] (98)Address already in use: make_sock: could not bind to port 209
[Sat Jun 8 14:22:26 2002] [warn] NameVirtualHost MYIPADDRESS:80 has no VirtualHosts
[Sat Jun 8 14:22:26 2002] [crit] (98)Address already in use: make_sock: could not bind to port 209
[Sat Jun 8 14:38:43 2002] [warn] NameVirtualHost MYIPADDRESS:80 has no VirtualHosts
[Sat Jun 8 14:38:43 2002] [crit] (98)Address already in use: make_sock: could not bind to port 209


There's also at least a hundred lines of those (88)Socket operation errors as well.

Does anybody know what I need to do to fix this? Before I upgrade Apache it was working fine so I'm hoping its just something simple.


JTM

What are you running on port 209?

netstat -anp | grep 209

This will show whatever is holding that port. Kill the process, and restart apache.

I entered netstat -anp | grep 209 and this is what came up:

tcp 0 0 MYDEDSERVERIPADDRESS:22 MYISPSIPADDRESS:13201 ESTABLISHED 1003/sshd

Can you tell what is holding the port from that? If so, what is it?

How do I kill the process?

Thanks for your help. :)


JTM

Since there is no 209 in that snippet, we'll have to presume that 209 is part of either your server IP or your remote host IP. So, the next question is: what is your apache config defining that it wants to attach to port 209? Since it appears that 209 might be part of your server IP, I'd suggest looking through the apache config for a typo. If you run

/usr/local/apache/bin/apachectl configtest

(or wherever your particular apachectl is located), what do you get back?

Yes, 209 is the first set of numbers for my servers's IP address.

I ran the test command you said to try and here is what came up:

[root@domain /]# /usr/local/apache/bin/apachectl configtest
Syntax OK
[root@domain /]#


Any ideas?


JTM

Unfortunately, it looks like a line by line review for you. Do you have the ServerType set to Standalone (common cause for the (88) Socket errors)? If you look through the apache config, are there any strange definitions for any of the VirtualHosts (especially as NameVirtualHost IP:209 or even a partial NameVirtualHost 209 without terminating information)? Without looking at the complete httpd.conf, it's difficult to offer anything but generic things for errors like this, sorry.

The ServerType set to something other than Standalone is a common cause of the (88) socket errors.

I just figured out the problem. In one of my DNS configurations I had tried to point a domain name to an IP address that was assigned to another server. Apparantly, that was what was keeping it from starting. After I removed it, it started right up!

Thanks for your help Annette!


JTM

Glad to hear it. It's amazing how the tiniest things will bite you in the butt. Better than Windows, though. :)