Service httpd restart FAILED what is wrong ?

B

benzersiz

Verified User
Joined
Jun 11, 2008
Messages
25
Location
Ankara
[root@ns1 ~]# service httpd restart
Stopping httpd: [FAILED]
Starting httpd: Warning: DocumentRoot [/home/alkoliyiz/domains/alkoliyiz.info/pu blic_html] does not exist
Warning: DocumentRoot [/home/alkoliyiz/domains/alkoliyiz.info/private_html] does not exist
Warning: DocumentRoot [/home/knight/domains/knight-silkroadonline.com/public_htm l] does not exist
Warning: DocumentRoot [/home/knight/domains/knight-silkroadonline.com/private_ht ml] does not exist
Warning: DocumentRoot [/home/mardin/domains/mardinli.net/public_html/mp3ara] doe s not exist
Warning: DocumentRoot [/home/mardin/domains/mardinli.net/public_html/programlar] does not exist
Warning: DocumentRoot [/home/mardin/domains/mardinli.net/public_html/video] does not exist
Warning: DocumentRoot [/home/bekir/domains/malatyaforum.com/public_html/haber] d oes not exist
Warning: DocumentRoot [/home/bekir44/domains/productionsz.net/public_html/forum] does not exist
Warning: DocumentRoot [/home/bekir44/domains/productionsz.net/public_html/haber] does not exist
Warning: DocumentRoot [/home/bekir44/domains/productionsz.net/public_html/m\xfcz ik] does not exist
Warning: DocumentRoot [/home/bekir44/domains/productionsz.net/public_html/oyun] does not exist
Warning: DocumentRoot [/home/bekir44/domains/productionsz.net/public_html/radyo] does not exist
Warning: DocumentRoot [/home/bekir44/domains/productionsz.net/public_html/video] does not exist
Warning: DocumentRoot [/home/eceerken/domains/eceerken.gen.tr/public_html/sohbet ] does not exist
Warning: DocumentRoot [/home/ecesohbet/domains/ecesohbet.com/public_html/radyo] does not exist
[Sun Feb 15 01:12:36 2009] [warn] NameVirtualHost 212.174.173.133:80 has no VirtualHosts
[Sun Feb 15 01:12:36 2009] [warn] NameVirtualHost 212.174.173.133:443 has no VirtualHosts
[Sun Feb 15 01:12:36 2009] [warn] NameVirtualHost 212.174.173.132:80 has no VirtualHosts
[Sun Feb 15 01:12:36 2009] [warn] NameVirtualHost 212.174.173.132:443 has no VirtualHosts
[Sun Feb 15 01:12:36 2009] [warn] NameVirtualHost 212.174.173.131:80 has no VirtualHosts
[Sun Feb 15 01:12:36 2009] [warn] NameVirtualHost 212.174.173.131: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


HOW CAN I FIX IT ?
 
benzersiz said:
yeah i saw it there are logs dhould i send to here ?
Click to expand...

Saw what in the logs?

I am asking you run the command to see what is listening on port 80 that is preventing apache from binding to port 80.
 
[root@ns1 ~]# netstat -npa | grep LISTEN
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 3031/dovecot
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 3031/dovecot
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 8497/mysqld
tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 8386/exim
tcp 0 0 0.0.0.0:2222 0.0.0.0:* LISTEN 8377/directadmin
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 3031/dovecot
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 3031/dovecot
tcp 0 0 0.0.0.0:975 0.0.0.0:* LISTEN 2913/rpc.statd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 2894/portmap
tcp 0 0 212.174.173.133:53 0.0.0.0:* LISTEN 9201/named
tcp 0 0 212.174.173.132:53 0.0.0.0:* LISTEN 9201/named
tcp 0 0 212.174.173.131:53 0.0.0.0:* LISTEN 9201/named
tcp 0 0 212.174.173.130:53 0.0.0.0:* LISTEN 9201/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 9201/named
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 8418/proftpd: (acce
tcp 0 0 0.0.0.0:631 0.0.0.0:* LISTEN 8252/cupsd
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 9201/named
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 8386/exim
tcp 0 0 :::80 :::* LISTEN 8410/httpd
tcp 0 0 :::22 :::* LISTEN 8346/sshd
tcp 0 0 ::1:953 :::* LISTEN 9201/named
tcp 0 0 :::443 :::* LISTEN 8410/httpd
unix 2 [ ACC ] STREAM LISTENING 13667 8497/mysqld /var/lib/mysql/mysql.sock
unix 2 [ ACC ] STREAM LISTENING 12601 8396/gpm /dev/gpmctl
unix 2 [ ACC ] STREAM LISTENING 13414 8453/dbus-daemon-1 /var/run/dbus/system_bus_socket
unix 2 [ ACC ] STREAM LISTENING 6212 3021/acpid /var/run/acpid.socket
unix 2 [ ACC ] STREAM LISTENING 6238 3031/dovecot /var/run/dovecot/dict-server
unix 2 [ ACC ] STREAM LISTENING 6240 3031/dovecot /var/run/dovecot/login/default
unix 2 [ ACC ] STREAM LISTENING 6245 3031/dovecot /var/run/dovecot/auth-worker.3033
 
floyd said:
Saw what in the logs?

I am asking you run the command to see what is listening on port 80 that is preventing apache from binding to port 80.
Click to expand...
and me i have the same problem last days. Hapen every day.
in port 80 listen:
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 20827/log
 
blueice said:
and me i have the same problem last days. Hapen every day.
in port 80 listen:
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 20827/log
Click to expand...
also this is the prosess for port 80:
apache 20827 0.0 0.0 6316 2736 ? S 08:55 0:00 /usr/sbin/apache/log

but with:
server:~# ls /usr/sbin/apache/log
ls: /usr/sbin/apache/log: No such file or directory
 
blueice said:
also this is the prosess for port 80:
apache 20827 0.0 0.0 6316 2736 ? S 08:55 0:00 /usr/sbin/apache/log

but with:
server:~# ls /usr/sbin/apache/log
ls: /usr/sbin/apache/log: No such file or directory
Click to expand...

This is definitely not normal.

Try:
Code: 
ls -l /proc/20827
 
I have the exact same thing on just one FreeBSD server since feb. 14th.

79369 apache 1 132 0 3904K 3212K RUN 17.4H 97.85% perl5.8.8
The process is hard to kill, but at nightly httpd restart apache will fail to start and will stay down until that process is killed manually.

Does anyone found a cause for this?
 
Last edited:
Meesterlijk said:
I have the exact same thing on just one FreeBSD server since feb. 14th.

79369 apache 1 132 0 3904K 3212K RUN 17.4H 97.85% perl5.8.8
The process is hard to kill, but at nightly httpd restart apache will fail to start and will stay down until that process is killed manually.

Does anyone found a cause for this?

Thanks
Robert
Click to expand...
i have do this:

***************
cd /usr/local/directadmin
mv custombuild custombuild.old
wget http://files.directadmin.com/services/custombuild/1.1/custombuild.tar.gz
tar xvzf custombuild.tar.gz
cd custombuild
./build update_data
#if you want to customize your options.conf (eg, setup suPhp/cgi, do it here.)
./build all d
*****************
(in simple words recompile the apache but with totaly redownload all the files and settings)

Until now all work good.
 
Code: 
I got the same problem every day for 3 days in a row. What to do?

Which OS do you use?
Tell me your httpd version?
Also, do you use atmail, you have an old version of Roundcube left in /var/www/html ?
 
Meesterlijk said:
Code: 
I got the same problem every day for 3 days in a row. What to do?

Which OS do you use?
Tell me your httpd version?
Also, do you use atmail, you have an old version of Roundcube left in /var/www/html ?
Click to expand...

It is Debian

I did the custom build thats suggested in this thread and it does not show any version number now.

Well I got roundcube 0.1.1 in /var/www/html

I also updated DA through the panel update option few days back
 
I did the custom build thats suggested in this thread
Click to expand...
When, today or yesterday and httpd crashed afterwards last night?

You see nothing when you do this on the commandline?: httpd -v
Check the 'system information' in DA.

Aslo, update Roundcube with custombuild.
 
Last edited:
Its also good to check if there is a crontab for apache. There should not be.
 
Apache version is 2.2.9

So the httpd crashed again few hours after the custombuild

I updated the roundcube now

There is no mambo/joomla/xoops installed on that box

There is no .txt file in the /tmp folder

PHP: 
jel:/tmp# ls
mysql.sock                             sess_6b3de4ab193aa4248e0204416572b415
pear                                   sess_7b3da53654947f9898b9444d404504fa
sess_064c1111bfe2688de8468eff08cce2ec  sess_8808b7326557c3b1ae2c154b35c36e9c
sess_10a86ffeaadb9c0bc970433012719333  sess_933c98f96a01ecf9313e9cfe64c93bef
sess_153a30e38bbeb0b3481ce4d57cc38837  sess_984afc1e960648975609195f32f4ca75
sess_343f2cc8d9f4307d7a0c01d7c34f3d7b  sess_9e06a8cc2745db5fb55d14aefa63d9ff
sess_42bf3e40808e4373bd5bb5381bfe7910  sess_a051a3191713fa82101400b3704e8e78
sess_43161c9f393d30bcf67b2aa44ef0d0dd  sess_cc68097ac751dd12fa7e83f377362740
sess_433426b1780986d0f5e1467126ec8646  sess_e64f39d868229f66902b068bec8375b6
sess_5a6393bc4559cde71ae0626225c192d6  sess_ec7f5d79570d5b0b5a7eb4818bb372d9
sess_6aad8419f572d1c532115052f1e428b4

My crontab

PHP: 
jel:/tmp# crontab -l
0 5 15 * 0 /usr/local/sysbk/sysbk -q
 
Hi, I've been having the same problem, on two servers actually. With one we just removed directadmin completely, but with the other one that's not an option.

Every night when Directadmin does the "Tally", it restarts apache. But it doesn't stop apache correctly somehow and port 80 (and sometimes port 443 too) are still in use by a not-working apache process. Apache won't restart because ports in use is a critical error and it just closes again:
Code: 
httpd not running, trying to start
(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

Quick manual fix:
  1. Search for ports in use:
    # lsof -i :80
    COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
    httpd 6617 apache 4u IPv6 527364 TCP *:www (LISTEN)
  2. Kill the process using the PID:
    # kill -9 6617

After that you can restart apache normally. But I'm really hoping directadmin can provide us with a permanent solution.

Here's wat seems to be a solution: http://help.directadmin.com/item.php?id=31. But it's an old help file, those files/paths are not available on my server. Plus I'm using Debian as well, and the commands there are for redhat/freebsd. :( Is this custombuild thing doing the same as described on that help-page?
 
You must log in or register to reply here.
Back
Top