010 N ADL <Server>
ESP URL /WsADL/ComprehensiveADL Ok 27d 23h 54m 7s 1/2 2016-06-14 09:46:32 HTTP OK: HTTP/1.1 200 OK - 452 bytes in 0.106 second response time
ESP URL /WsADL/ComprehensiveADL Ok 27d 23h 54m 7s 1/2 2016-06-14 09:46:32 HTTP OK: HTTP/1.1 200 OK - 452 bytes in 0.106 second response time
ESP URL /WsADL/ComprehensiveADL Ok 27d 23h 54m 7s 1/2 2016-06-14 09:46:32 HTTP OK: HTTP/1.1 200 OK - 452 bytes in 0.106 second response time
ESP URL /WsADL/ComprehensiveADL Ok 27d 23h 54m 7s 1/2 2016-06-14 09:46:32 HTTP OK: HTTP/1.1 200 OK - 452 bytes in 0.106 second response time
Multiple parent (PPID) processes are what we need to be concerned about - the Nagios process forks itself to run checks therefor sub-processes are normal.
That being said, you have multiple Nagios processes running, which can cause problems. To resolve, run these commands and after a period of monitoring,
let us know of the outcome.
There is something which is causing the Nagios services to start back up. I used the below command to kill all the nagios processes.
ps -ef | grep nagios | awk '{print $2}' | xargs kill -9
Having 2 nagios processes is OK, one parent and one child is normal.
It could be that having multiple processes running, the configs became out of sync, try going through this process and see if that removes the duplicates for you.
Go to the Core Config Manager
Under "Tools", click "Write Config Files"
Click the "Delete" button then click the "Write" button and then the "Verify" button
If you get any errors, resolve them and click on the "Write", "Verify" until all of the errors are resolved.
Click the Apply Configuration link and click the "Apply Configuration" button
Be sure to check out our Knowledgebase for helpful articles and solutions!