[BlueOnyx:14309] Re: Can't get the HTTPD process started

[Stephanie Sullivan]

Marty,

If you get an error about port 80 when restarting httpd (/etc/init.d/httpd restart) then find out how is using port 80 or 443 (ssl):
netstat –avpn|grep \:80
netstat –avpn|grep \:443

This may give you a hint in those cases. The grep expressions might catch a few irrelevant lines but will narrow the output volume to something useful.

Hope this helps.

        -Stephanie



From: marty at gofigurski.com [mailto:marty at gofigurski.com] 
Sent: Friday, January 24, 2014 12:33 PM
To: blueonyx at blueonyx.it
Subject: [BlueOnyx:14306] Can't get the HTTPD process started

Hi List,
Have a strange issue with our 5106 that is fully updated.  
This morning at 4:30am CST and then at 7:30am CST we received the following alert from Active Monitor: 
Active Monitor has detected recent changes in the state of your server appliance.
For more details, please see the Active Monitor section of the Server Desktop.

Summary of changes:

* The Web Server is not running and could not be restarted. Try rebooting the server by clicking the Reboot Now button in the Power menu under System Settings. If you are still unable to access the Web Server, please visit http://BlueOnyx.it/ for technical support.

Rebooted the server but httpd service did not come back up.  Checked the httpd error log and this is the only thing that comes up:
[Fri Jan 24 04:28:47 2014] [notice] SIGHUP received. Attempting to restart
[Fri Jan 24 04:28:50 2014] [notice] Digest: generating secret for digest authentication ...
[Fri Jan 24 04:28:50 2014] [notice] Digest: done
[Fri Jan 24 04:28:50 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 04:30:07 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 04:30:07 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 04:45:06 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 04:45:06 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 05:00:06 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 05:00:06 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 05:15:06 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 05:15:06 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 05:30:10 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 05:30:10 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 05:45:06 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 05:45:06 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 06:00:06 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 06:00:06 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 06:15:06 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 06:15:06 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 06:30:06 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 06:30:06 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 06:45:06 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 06:45:06 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 07:00:06 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 07:00:06 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 07:09:07 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 07:09:07 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 07:15:11 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 07:15:11 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 07:26:34 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 07:26:34 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 07:30:13 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 07:30:13 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 07:34:01 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 07:34:01 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 07:36:43 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 07:36:43 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Fri Jan 24 07:45:06 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jan 24 07:45:06 2014] [warn] No JkShmFile defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status

Anyone has any ideas.  Have been struggling with this for a while now.

Thank you,
Marty