On Mon, April 29, 2013 09:02, James Hogarth wrote:
It is just the httpd service that stops.
Define 'stops'
Attempts to access the web sites served by that service report Server not Found.
Running 'service httpd start' starts the service.
Are there any httpd processes still running?
No.
What are you doing with the server - php, proxy to tomcat, etc
Straight-up static web sites. Nothing fancy or dynamic. No CGI scripts.
There's very little information to go on in your post...
You have what I have. There is simply no trace of the process by the time my periodic (every 15 minutes) sweep notices that the httpd process is gone and restarts it.
On Mon, April 29, 2013 09:02, James Hogarth wrote:
It is just the httpd service that stops.
Define 'stops'
Attempts to access the web sites served by that service report Server not Found.
Running 'service httpd start' starts the service.
Are there any httpd processes still running?
No.
What are you doing with the server - php, proxy to tomcat, etc
Straight-up static web sites. Nothing fancy or dynamic. No CGI scripts.
There's very little information to go on in your post...
You have what I have. There is simply no trace of the process by the time my periodic (every 15 minutes) sweep notices that the httpd process is gone and restarts it.
This may be a potentially stupid question, but have you looked at your logs?
On Tue, Apr 30, 2013 at 10:59 AM, James B. Byrne byrnejb@harte-lyne.ca wrote:
You have what I have. There is simply no trace of the process by the time my periodic (every 15 minutes) sweep notices that the httpd process is gone and restarts it.
My first guess on mysterious process death on Linux is always the kernel out-of-memory killer. But I think that is logged somewhere.
-- Les Mikesell lesmikesell@gmail.com
On 2013-04-30, Les Mikesell lesmikesell@gmail.com wrote:
My first guess on mysterious process death on Linux is always the kernel out-of-memory killer. But I think that is logged somewhere.
By default the OOM messages should go to the kernel ring buffer (so use dmesg to see). I think that they also go to syslog, so should also be in /var/log/messages.
--keith
Keith Keller wrote:
On 2013-04-30, Les Mikesell lesmikesell@gmail.com wrote:
My first guess on mysterious process death on Linux is always the kernel out-of-memory killer. But I think that is logged somewhere.
By default the OOM messages should go to the kernel ring buffer (so use dmesg to see). I think that they also go to syslog, so should also be in /var/log/messages.
They do, indeed, go to messages. I've seen them *far* too frequently here (serious heavy-duty multi-threaded scientific computing, or R, will eat *everything*).
mark
James B. Byrne wrote:
On Mon, April 29, 2013 09:02, James Hogarth wrote:
It is just the httpd service that stops.
Define 'stops'
Attempts to access the web sites served by that service report Server not Found.
Running 'service httpd start' starts the service.
Are there any httpd processes still running?
<snip>
You have what I have. There is simply no trace of the process by the time my periodic (every 15 minutes) sweep notices that the httpd process is gone and restarts it.
A possibly useful thought for something that almost always, for me, is useless: is crashkernel enabled? Any dumps?
Or, for that matter, since I don't know how it's being run or who has what authorities, anything in sudo.log?
Ooog - is selinux enforcing?
mark
-
James B. Byrne -
Keith Keller -
Les Mikesell -
m.roth＠5-cent.us -
Mike Burger