Apache fails to start after domain name change

Earlier today, I changed the domain name within a virtual host. I also updated the SSL cert to correspond to the new domain name. Then I stopped apache (using virtualmin) and when I attempted to restart it again, I got the following message:

Failed to start apache : Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using 184.106.224.191 for ServerName [Wed Mar 20 17:37:30 2013] [warn] default VirtualHost overlap on port 443, the first has precedence [FAILED]

I have been madly searching for solutions and have yet to find any success. I'm in a really tight spot in that ALL sites are down. I tried to perform a restore on the virtualhost in question, but that failed. Perhaps because it was backed up as a different file name. I was simply looking to restore the apache settings....

I'm feeling quite anxious at this point. Your help is DEEPLY appreciated.

  • John.
Status: 
Closed (fixed)

Comments

I've attached a copy of the httpd.conf for reference.

Howdy -- the output you see during startup is just some warnings, they're not likely the cause of the problem you're seeing.

Do any errors show up in the Apache error log in /var/log/httpd/error_log when trying to start Apache?

Here are the last bunch of lines.

[Wed Mar 20 12:48:07 2013] [warn] mod_fcgid: process 2593 graceful kill fail, sending SIGKILL [Wed Mar 20 12:48:13 2013] [notice] mod_fcgid: process /home/mirimage/public_html/index.php(2593) exit(communication error), get stop signal 9 [Wed Mar 20 12:51:52 2013] [notice] mod_fcgid: call /home/tcpadmin/public_html/index.php with wrapper /home/tcpadmin/fcgi-bin/php5.fcgi [Wed Mar 20 13:00:05 2013] [notice] mod_fcgid: call /home/mirimage/public_html/index.php with wrapper /home/mirimage/fcgi-bin/php5.fcgi [Wed Mar 20 13:31:40 2013] [notice] mod_fcgid: process /home/mirimage/public_html/index.php(2679) exit(communication error), terminated by calling exit(), return code: 255 [Wed Mar 20 13:45:49 2013] [notice] mod_fcgid: call /home/mirimage/public_html/index.php with wrapper /home/mirimage/fcgi-bin/php5.fcgi [Wed Mar 20 13:46:40 2013] [warn] mod_fcgid: process 3282 graceful kill fail, sending SIGKILL [Wed Mar 20 13:46:46 2013] [notice] mod_fcgid: process /home/mirimage/public_html/index.php(3282) exit(communication error), get stop signal 9 [Wed Mar 20 13:51:40 2013] [notice] mod_fcgid: call /home/salesbooster/public_html/wp-cron.php with wrapper /home/salesbooster/fcgi-bin/php5.fcgi [Wed Mar 20 13:55:14 2013] [notice] caught SIGTERM, shutting down [Wed Mar 20 13:55:15 2013] [notice] mod_fcgid: process /home/salesbooster/public_html/wp-login.php(2556) exit(shutting down), terminated by calling exit(), return code: 0 [Wed Mar 20 13:55:15 2013] [notice] mod_fcgid: process /home/tcpadmin/public_html/index.php(2840) exit(shutting down), terminated by calling exit(), return code: 0 [Wed Mar 20 13:55:15 2013] [notice] mod_fcgid: process /home/sdsadmin/public_html/index.php(2677) exit(shutting down), terminated by calling exit(), return code: 0 [Wed Mar 20 13:55:15 2013] [notice] mod_fcgid: process /home/mirimage/public_html/index.php(4663) exit(shutting down), terminated by calling exit(), return code: 0 [Wed Mar 20 13:55:15 2013] [notice] mod_fcgid: process /home/salesbooster/public_html/wp-login.php(4856) exit(shutting down), terminated by calling exit(), return code: 0 [Wed Mar 20 13:55:20 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 13:55:39 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 13:56:27 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 14:03:04 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 14:04:31 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 14:11:19 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 14:13:35 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 14:17:08 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 15:41:55 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 15:47:32 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 16:00:45 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 16:21:35 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 16:25:17 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 16:27:24 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 16:28:23 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 16:30:18 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 16:31:09 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 16:31:37 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 17:16:26 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 17:18:55 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 17:34:20 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 17:35:41 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 17:37:30 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 17:49:15 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Mar 20 18:06:32 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)

Hmm, those errors don't appear to be related either.

You mentioned making some SSL related changes today -- could you go to the logs directory for that particular domain, and review the error_log within it?

That's typically either $HOME/logs/error_log, or $HOME/domains/domain.tld/logs/error_log.

Apache may be throwing an error into that particular log file when you attempt to start Apache.

You're quite right. I reverted back to a set of ssl cert files I am confident of, and everything works fine.

This is strange. I have run into hiccups with installing ssl cert files before, but I don't remember it hosing apache entirely...

thanks for your help.

Automatically closed -- issue fixed for 2 weeks with no activity.