This website is deprecated, and remains online only for historic access to old issues and docs for historic versions of Virtualmin. It has been unmaintained for several years, and should not be relied on for up-to-date information. Please visit www.virtualmin.com instead.

Apache will not start - cannot determine the server's fully qualified domain name

3 posts / 0 new

Topic locked

Last post

#1 Sat, 12/28/2013 - 16:03

calderwood

Apache will not start - cannot determine the server's fully qualified domain name

Everything was fine. Server was up for 90+ days. Updated one virtual server on the CP (changed the DNS MX for the mail server to off-site mail) and then I guess the system restarts Apache automatically, but apache did not restart. All other services are running without issue.

I have tried to restart Apache, have re-booted the server, doubled checked all settings - found that the /etc/hosts only had local hosts listed so manually added the IP and NS. Still can't start Apache or access any IP address via a browser.

[root@ip-68-178-130-21 ~]# /etc/init.d/httpd restart Stopping httpd: [FAILED] Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using ip-68-178-130-21.ip.secureserver.net for ServerName [FAILED]

[root@ip-68-178-130-21 ~]# hostname
ip-68-178-130-21.ip.secureserver.net

I am totally stumped as to what is is. Also have flushed iptables

Runing V GPL 4.4 on Appache COS6 on VPS

#2 Sun, 12/29/2013 - 09:54

Locutus

The message about the "fully qualified domain name" is not a fatal error, Apache should start anyway. Anything in the syslog and Apache's error log?

What's the output for

hostname
hostname -f
cat /etc/hosts
netstat -tpln | grep :80

#3 Sun, 12/29/2013 - 18:20 (Reply to #2)

calderwood

I got apache to start by adding the line "severname ip-68-178-130-21.ip.secureserver.net" to /etc/httpd/conf/httpd.conf

Apache restarted but still with warning. I'm still not sure if that was the issue. I have also noticed that the network configuration is not installing the eth0:1 and :2 interfaces after reboot, even though they are listed in the boot config.

One other change I made to get it to restart was in the DNS Client Option - I changed the order to DNS, Hosts, Local Hosts. The previous setting was Localhost, DNS.

So I am running but unsure why I was down for 6 hours.

# hostname
ip-68-178-130-21.ip.secureserver.net

# hostname -f
ip-68-178-130-21.ip.secureserver.net

THE IP LINES I ADDED MANUALLY AS THEY WERE MISSING
# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4 ip-68-178-130-21.ip.secureserver.net
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6 ip-68-178-130-21.ip.secureserver.net
68.178.130.21 ns1.epdigital.biz ns1
68.178.131.108 ns2.epdigital.biz ns2
50.62.34.152 ns1.shoots.com shooots
# Auto-generated hostname. Please do not remove this comment.
127.0.0.1 ip-68-178-130-21.ip.secureserver.net ip-68-178-130-21

# netstat -tpln | grep :80
tcp        0      0 :::80                       :::*                        LISTEN      2025/httpd

David Calderwood - Euro-Pacific Digital Media

Topic locked