Page 1 of 1

System component error and No ticket generation in S.now

Posted: Tue Apr 16, 2019 6:31 am
by hoegh
Hi All,

We are getting frequent conenction lost between Nagios XI and Service Now.
Automatic ticket is created in service now if any alert is there on nagios .
The XI System Component are showing error as well.
This has been attached as well

But we are receiving this issue as,no ticket generation is there.

Kindly suggest any solution for the above.

Thanks,
Hoegh

Re: System component error and No ticket generation in S.now

Posted: Tue Apr 16, 2019 11:03 am
by benjaminsmith
Hi @Hoegh,

It looks like some of the cron jobs are not processing on your server. Let's try get all the components on the status dashlet at green, and then debug any issues with ticket generation.

1. Check to see that the Nagios user account is not expired

Code: Select all

chage -l nagios
2. Try restarting the cron service ( for RHEL/CentOS 7 ):

Code: Select all

systemctl status crond.service
3. If those services don't restart, please upload the cron log in /var/log/cron

Thanks.

Re: System component error and No ticket generation in S.now

Posted: Wed Apr 17, 2019 7:42 am
by hoegh
Hi @benjaminsmith,

It was found that Linux File system where Nagios is installed [/usr] volume, storage was full.
So we cleared some space & all components came to running state.

Please close this thread.
Thanks.

Re: System component error and No ticket generation in S.now

Posted: Wed Apr 17, 2019 10:31 am
by benjaminsmith
Hi @hoegh,
Please close this thread.
Thanks.
Thanks for the update and glad to hear you found the issue. We'll close this one out.