Page 1 of 1

Alarm output state is different from service state

Posted: Thu Oct 18, 2018 7:55 am
by nms
alarmspage.PNG
ccmalarmoutput.PNG
Hi,

We have a situation where under "All Service Problems", a particular service is listed with unknown state.
When checking the service from CCM, and executing the "Run check command", the output is listed as OK. { state OK for Nagios } .
When checking from the alarm page, and executing the "Force an immediate check", we get that process has been submitted, page is refreshed, however we end up with blank page.

I confirmed that service is under the correct host.

What else can be checked from our side?

Re: Alarm output state is different from service state

Posted: Thu Oct 18, 2018 2:30 pm
by ssax
Please PM me a copy of your profile so that I can look through your configuration, you can download it from Admin > System Profile > Download Profile.

PM me the .sh script that you're running on the remote server as well so that I can see what it contains.

Thank you

Re: Alarm output state is different from service state

Posted: Fri Oct 19, 2018 3:32 am
by nms
Attached are the nagios script and system nagios profile

profile.zip
nagios_cert_expiry.txt

Re: Alarm output state is different from service state

Posted: Fri Oct 19, 2018 4:06 pm
by ssax
Please attach this file (this is likely where the error is coming from):

Code: Select all

/home/nagios/bin/nagios_CommonCheck.sh

Re: Alarm output state is different from service state

Posted: Mon Oct 22, 2018 3:27 am
by nms
Attached
nagios_common_check.txt

Re: Alarm output state is different from service state

Posted: Mon Oct 22, 2018 1:33 pm
by ssax
On the remote server please run these commands and send me the full output:

Code: Select all

su - nagios
uname -a | grep -i linux
find /var/opt/Aspider-NGI/nms/output/cron_T-Linux050-CertificateExpiry.jira.aspider-ngi.com -mmin -250
ls -la /var/opt/Aspider-NGI/nms/output/cron_T-Linux050-CertificateExpiry.jira.aspider-ngi.com