Reputation
6,406
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
2 47 88
Impact
~585k people reached

Mar
5
revised sshd running but no PID file
added 209 characters in body
Mar
5
comment sshd running but no PID file
See update in question for what is shown by netstat -lptun. The grep in your script doesn't pick up anything for port 22 for me, but I can see from netstat that it is there.
Mar
5
revised sshd running but no PID file
added 155 characters in body
Mar
5
comment sshd running but no PID file
@cjc - I'm less concerned about Monit here than I am about the general behaviour.
Feb
28
awarded  Popular Question
Feb
27
revised sshd running but no PID file
added 91 characters in body
Feb
27
comment sshd running but no PID file
error: Bind to port 22 on 0.0.0.0 failed: Address already in use. and fatal: Cannot bind any address. Not surprising since sshd is clearly running.
Feb
27
asked sshd running but no PID file
Feb
24
accepted Monit lists Apache as Not Monitored
Feb
24
comment Monit lists Apache as Not Monitored
The PID file was correct, but running monit monitor apache got it started, and now it seems to be working fine after restarting the service. I should also have tried clicking the Enable Monitor button on the web interface.
Feb
24
comment Effects of configuring vm.overcommit_memory
That would be a great function if the PID for an app was static...
Feb
23
revised Monit lists Apache as Not Monitored
added 268 characters in body
Feb
23
comment Monit lists Apache as Not Monitored
Making a request to localhost works fine. I'm not getting Connection Failed - I'm getting "Not Monitored".
Feb
23
comment Monit lists Apache as Not Monitored
Makes no difference quoted or not.
Feb
23
comment Monit lists Apache as Not Monitored
Where are you seeing that output?
Feb
23
comment Monit lists Apache as Not Monitored
It's CentOS 5.4. PID file is correct.
Feb
23
revised Monit lists Apache as Not Monitored
added 64 characters in body
Feb
23
asked Monit lists Apache as Not Monitored
Feb
23
comment Effects of configuring vm.overcommit_memory
Thanks - I'm trying things with overcommit_ratio set to 100 to see what happens. The main problem I have is that when oom-killer starts it invariably kills sshd preventing me from accessing the server and seeing what is going on. I guess what I really need is to stop oom-killer from running and some means of recording what happens when it would have run so I can find the cause of the problem.
Feb
22
asked Effects of configuring vm.overcommit_memory