Apache mysteriously stopped and will not start

[keith smith]

Hi,

I'm run a web server out of my home office.  It is CentOS 6.x with no real 
modifications.  It is a standard LAMP config.  It has been running since March w/o any issues.  


All of a sudden Apache shutdown.   

When I run /etc/init.d/httpd start the only response is [FAILED] same for /etc/init.d/httpd stop

apachectl configtest returns "Syntax OK".


I found these in the /var/lib/httpd/error_log  ( read this has to do with the SSL)


[Sun Oct 20 03:37:44 2013] [notice] Digest: generating secret for digest authentication ...
[Sun Oct 20 03:37:44 2013] [notice] Digest: done
[Sun Oct 20 20:47:53 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Oct 20 20:48:07 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Oct 20 20:55:14 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Oct 20 20:58:36 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Oct 20 22:01:34 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Oct 20 22:11:18 2013] [notice] suEXEC mechanism enabled (wrapper:
 /usr/sbin/suexec)
[Sun Oct 20 22:11:30 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Oct 20 22:12:07 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Oct 20 22:14:34 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Oct 20 22:15:22 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Oct 20 22:17:26 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Oct 20 22:17:26 2013] [info] Init: Initialized OpenSSL library
[Mon Oct 21 07:41:11 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)



I don't know what to make of this /var/log/messages :  ( I read this has to do with IPv6)


Oct 20 03:37:44 E520 rsyslogd: [origin software="rsyslogd" 
swVersion="5.8.10" x-pid="1212" x-info="http://www.rsyslog.com"] 
rsyslogd was HUPed
Oct 20 03:37:44 E520 named[19169]: error (network 
unreachable) resolving '30.233.143.188.in-addr.arpa/PTR/IN': 
2001:660:3006:1::1:1#53
Oct 20 03:37:44 E520 named[19169]: error (network unreachable) resolving
 '30.233.143.188.in-addr.arpa/PTR/IN': 2001:dc0:2001:a:4608::59#53
Oct
 20 03:37:45 E520 named[19169]: error (network unreachable) resolving 
'13.113.153.194.in-addr.arpa/PTR/IN': 2001:660:3006:1::1:1#53
Oct 20 03:37:45 E520 named[19169]: error (network unreachable) resolving '13.113.153.194.in-addr.arpa/PTR/IN': 2001:500:2e::1#53
Oct
 20 03:37:45 E520 named[19169]: error (network unreachable) resolving 
'13.113.153.194.in-addr.arpa/PTR/IN': 2001:dc0:2001:a:4608::59#53

There is a whole bunch of these.

Dig returns what appears to be the correct DNS.

There is lots of disk space.


The last 3 changes I made were  7-10 days ago.

Last change was to run   


cd /etc/pki/tls/certs
./make-dummy-cert localhost.crt

I did that because I was trying to configure a new website.  I had done 
the Apache part weeks before and the site was working.  I wanted to add 
some email accounts.  I'm running Postfix with Dovecot.
So I added the email accounts in the config and when I went to add them to my Thunderbird, I received an error because the SSL was expired.  I am 
using a self signed SSL.  


A little research brought me to 


cd /etc/pki/tls/certs
./make-dummy-cert localhost.crt

However that was 7 - 10 days before Apache just up and stopped.

I am running this server as a learning experience.  Someone helped me with the Bind config and the Postfix/Dovecot config.

I rebooted the server last night in the hopes that something was corrupted and would be fixed by a reboot.  No such luck.


I am at loss for what to look at next.  


Thank you very much for all your help!!


 
------------------------
Keith Smith
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20131021/b210d799/attachment.html>