Monday, June 6, 2016

monitoring - failure daemon and changing pid number



proftpd, sshd and apache processes run with /etc/init.d/its-script on linux distro.



I was monitoring 21, 22 and 80 ports with farm monitoring service: every 5 minutes service check each port and notify only failure. The failures were 5-6 times on 24h. It seems that someone kicks the switch sometimes..



I add monit and collectd monitoring and the monitoring about 21, 22 and 80 ports is every 1 minute. I do not receive farm monitoring service notify. I receive only monit notify about failure and/or succeed/changing pid number of proftpd, sshd or apache process. The failures are still 5-6 times on 24h. collectd monitoing about cpu, load average and each process is regular and there are no peaks. There is nothing kicks the switch but there is something which determines failure monitoring. is it a simple interference or is it indicative of some abnormality?



What could cause these failures?



Answer



The thing to do here is to start digging through the system logs to see if the causes of these restarts are associated with funny stuff. It could be that you're running into the Linux Out Of Memory killer, or maybe the processes are throwing stack-dumps when they crash. Both of these will be visible in the system log.


No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...