ran yum update, now httpd not working properly

V

verruckt

Verified User
Joined
Mar 8, 2004
Messages
52
I've CentOS5, and ran yum update, not thinking...

Anyway, everything is fine, except httpd not working properly. It is serving up pages, but only by IP/accountname, not by domain name. When I try to restart httpd, i get this output...

Code: 
[root@sexton sbin]# ./httpd
[Fri May 29 06:20:24 2009] [warn] The Alias directive in /etc/httpd/conf/httpd.conf at line 178 will 
probably never match because it overlaps an earlier Alias.
[Fri May 29 06:20:24 2009] [warn] NameVirtualHost xx.xx.xx.xx:80 has no VirtualHosts
[Fri May 29 06:20:24 2009] [warn] NameVirtualHost xx.xx.xx.xx:443 has no VirtualHosts
[Fri May 29 06:20:24 2009] [warn] NameVirtualHost xx.xx.xx.xx:80 has no VirtualHosts
[Fri May 29 06:20:24 2009] [warn] NameVirtualHost xx.xx.xx.xx:443 has no VirtualHosts
[Fri May 29 06:20:24 2009] [warn] NameVirtualHost xx.xx.xx.xx:80 has no VirtualHosts
[Fri May 29 06:20:24 2009] [warn] NameVirtualHost xx.xx.xx.xx:443 has no VirtualHosts
[Fri May 29 06:20:24 2009] [warn] NameVirtualHost xx.xx.xx.xx:80 has no VirtualHosts
[Fri May 29 06:20:24 2009] [warn] NameVirtualHost xx.xx.xx.xx:443 has no VirtualHosts
(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

Looks as though the httpd.conf is jacked up? I do NOT know my way around httpd for anything. So a little unsure of where to look or begin. Can I reinstall the setup.sh for Directadmin to rewrite the settings to solve this, or will that destroy all my current 'good' settings? Can I just replace the httpd conf file with someone elses working file, or are the settings specific to each server, and not DA in general?
 
Last edited:
Apache is not starting because of this error:

Code: 
Address already in use: make_sock: could not bind to address [::]:80 (98)Address already in 
use:

Besides, you shouldn't be starting Apache just by typing "./httpd". There is an init script that handles starting Apache and giving it all of the proper arguments and such.

Try this:

1. Stop Apache using the proper init script: /etc/init.d/httpd stop
2. verify that all httpd processes stopped: ps auxf | grep http
3. If http processes stopped, start it using: /etc/init.d/httpd start
 
rootbsd said:
Apache is not starting because of this error:

Code: 
Address already in use: make_sock: could not bind to address [::]:80 (98)Address already in 
use:

Besides, you shouldn't be starting Apache just by typing "./httpd". There is an init script that handles starting Apache and giving it all of the proper arguments and such.

Try this:

1. Stop Apache using the proper init script: /etc/init.d/httpd stop
2. verify that all httpd processes stopped: ps auxf | grep http
3. If http processes stopped, start it using: /etc/init.d/httpd start
Click to expand...

I stopped it, and then checked that it was not running. I had one process which i killed, then checked it again, and i had several more running. I tried to stop again, and still had a few processes running. I tried to restart, but same issue. Technically, httpd is 'running', as the web pages are accessible, just not by domain name. I was using ./httpd command, as when i did 'service httpd stop', it returned 'command not found'
 
jdlitson said:
What is the bind/named status in DA?
Click to expand...

appreciate your help!

In service monitor, it showed as stopped. I tried starting it, and it returned this error..
Code: 
An error has occurred
Details
/sbin/service named start 2>&1

So apparently my update has wiped my named.conf? I thought that it would keep my settings. :confused:

Is there an easy way to fix the file, or can I run the DA install script to fix this?
 
You got me pointed in the right direction, and I think I got it figured out.

In /etc/init.d my old named was renamed to named.rpmsave. I took the new named and renamed it to named.backup and renamed named.rpmsave to named and restarted named. Everything is back to normal. Thanks for the help.
 
Hi,
Glad you got it working. Now to avoid this in the future you can add this line to you /etc/yum.conf file.

Code: 
exclude=bind-chroot httpd* mysql* php* perl* apache* mod_* MySQL* *ftp* exim* sendmail* php* da_*

Just remember you have this line otherwise when you go to install a specific package yum will skip it. For example one day you may wish to install php-devel, but your yum exclude will have the php*.
 
You must log in or register to reply here.
Back
Top