Apache errors after upgrade to 2.x

P

Phiberop

New member
Joined
Mar 6, 2005
Messages
1
Greetings,

I upgraded to Apache v2 last night. I have a couple of error's that display when I load httpd now, they dont seem to affect any of the sites but I'd just like to know if it's anything I should worry about.

Here's the errors:

[Sun Mar 06 10:28:00 2005] [warn] NameVirtualHost x.x.x.x:443 has no VirtualHosts
(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 no virtualhosts error I dont believe is a problem, there is no SSL sites setup which is probably why that's coming up. I'm not sure about the rest though, any ideas?

Thanks,

Mike
 
Just to make sure, you did have DA rewrite all the httpd.conf files for apache 2 as well as configured DirectAdmin accordingly?
 
I just upgraded as well. Having the exact same problem as you.

Phiberop said:
Greetings,

I upgraded to Apache v2 last night. I have a couple of error's that display when I load httpd now, they dont seem to affect any of the sites but I'd just like to know if it's anything I should worry about.

Here's the errors:

[Sun Mar 06 10:28:00 2005] [warn] NameVirtualHost x.x.x.x:443 has no VirtualHosts
(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 no virtualhosts error I dont believe is a problem, there is no SSL sites setup which is probably why that's coming up. I'm not sure about the rest though, any ideas?

Thanks,

Mike
Click to expand...
 
Just to update, it's fixed.

You'll need to remove the Port lines in your custom domain httpd.conf files.

Apparently apache2 is very very picky and just rolls over and dies if there's MORE than one Listen directive in the httpd.conf as well as all other included files in the httpd.conf.
 
You must log in or register to reply here.
Back
Top