Error: Service escalation host name or description is NULL

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
ITOMB_IMT
Posts: 181
Joined: Wed Oct 17, 2018 12:55 pm

Error: Service escalation host name or description is NULL

Post by ITOMB_IMT »

hi,
I am using Nagios XI 5.8.1 and when i try to apply configuration, i have the below errors.
Write host configurations ...
Host configuration files successfully written!

Write service configurations ...
Service configuration files successfully written!

Configuration file: hostgroups.cfg successfully written!
Configuration file: servicegroups.cfg successfully written!
Configuration file: hosttemplates.cfg successfully written!
Configuration file: servicetemplates.cfg successfully written!
Configuration file: timeperiods.cfg successfully written!
Configuration file: commands.cfg successfully written!
Configuration file: contacts.cfg successfully written!
Configuration file: contactgroups.cfg successfully written!
Configuration file: contacttemplates.cfg successfully written!
Configuration file: servicedependencies.cfg successfully written!
Configuration file: hostdependencies.cfg successfully written!
Configuration file: serviceescalations.cfg successfully written!
Configuration file: hostescalations.cfg successfully written!
Configuration file: serviceextinfo.cfg successfully written!
Configuration file: hostextinfo.cfg successfully written!
Error: Service escalation host name or description is NULL
Error: Could not register service escalation (config file '/usr/local/nagios/etc/serviceescalations.cfg', starting on line 679)


I tried to repair databases, by disabling the service escalations and applied configuration no way, always the same error,also revert to a past snapshot don't change the situation..

any suggest?

Thanks,
dchurch
Posts: 858
Joined: Wed Oct 07, 2020 12:46 pm
Location: Yo mama

Re: Error: Service escalation host name or description is NU

Post by dchurch »

If you PM me a system profile I can diagnose further. Get one by going to Admin (top menu) => System Profile (in the left menu), then clicking the blue button.

If you're unable to generate the the profile through the web interface, please try generating it from the command line by running these commands as root:

Code: Select all

rm -rf /usr/local/nagiosxi/var/components/profile*
/usr/local/nagiosxi/scripts/components/getprofile.sh SUPPORT
Then send me the resulting /usr/local/nagiosxi/var/components/profile.zip file.
If the profile script fails, please include the ENTIRE output.
If you didn't get an 8% raise over the course of the pandemic, you took a pay cut.

Discussion of wages is protected speech under the National Labor Relations Act, and no employer can tell you you can't disclose your pay with your fellow employees.
ITOMB_IMT
Posts: 181
Joined: Wed Oct 17, 2018 12:55 pm

Re: Error: Service escalation host name or description is NU

Post by ITOMB_IMT »

please see PM with the profile.
dchurch
Posts: 858
Joined: Wed Oct 07, 2020 12:46 pm
Location: Yo mama

Re: Error: Service escalation host name or description is NU

Post by dchurch »

I'm investigating and it seems like this is a bug in how Nagios XI writes out service escalations into config files; it doesn't seem to include the name of the service being escalated in serviceescalations.cfg, which Nagios Core needs in order to escalate a service.

Did this configuration used to work before adding these service escalations?

Did you upgrade Nagios XI versions recently?

One workaround is to disable your service escalations until we can get this fixed in the next release of Nagios XI.
If you didn't get an 8% raise over the course of the pandemic, you took a pay cut.

Discussion of wages is protected speech under the National Labor Relations Act, and no employer can tell you you can't disclose your pay with your fellow employees.
ITOMB_IMT
Posts: 181
Joined: Wed Oct 17, 2018 12:55 pm

Re: Error: Service escalation host name or description is NU

Post by ITOMB_IMT »

Did this configuration used to work before adding these service escalations?
Yes, service escalations were working before upgrade.

Did you upgrade Nagios XI versions recently?
yes, i upgraded recently to 5.8.1.

One workaround is to disable your service escalations until we can get this fixed in the next release of Nagios XI.
we require escalations as we are monitoring our critical applications using Nagios XI. is there any other work around to use escalations?

Even after disabling/deactivating new service escalations, they were still detected in the serviceesaclations.cfg

Thanks,
dchurch
Posts: 858
Joined: Wed Oct 07, 2020 12:46 pm
Location: Yo mama

Re: Error: Service escalation host name or description is NU

Post by dchurch »

ITOMB_IMT wrote:Even after disabling/deactivating new service escalations, they were still detected in the serviceesaclations.cfg
Sorry, I meant disable all the service escalations.

I was able to reproduce your issue in a lab setting. Unfortunately there's a bug causing service escalations not to work. Until that's fixed, work around the issue by disabling all the service escalations.
If you didn't get an 8% raise over the course of the pandemic, you took a pay cut.

Discussion of wages is protected speech under the National Labor Relations Act, and no employer can tell you you can't disclose your pay with your fellow employees.
ITOMB_IMT
Posts: 181
Joined: Wed Oct 17, 2018 12:55 pm

Re: Error: Service escalation host name or description is NU

Post by ITOMB_IMT »

After disabling all the service escalations, i tried to apply configuration. but still the service escalation were showed up in config errors.
dchurch
Posts: 858
Joined: Wed Oct 07, 2020 12:46 pm
Location: Yo mama

Re: Error: Service escalation host name or description is NU

Post by dchurch »

I discovered what's wrong with your Nagios XI server. There's a missing column. If you run this command it should fix it:

Code: Select all

mysql -unagiosql -pn@gweb nagiosql <<< 'alter table tbl_lnkServiceescalationToService add column exclude tinyint(1) not null default 0;'
You should be able to re-activate all your service escalations and apply config after that.
If you didn't get an 8% raise over the course of the pandemic, you took a pay cut.

Discussion of wages is protected speech under the National Labor Relations Act, and no employer can tell you you can't disclose your pay with your fellow employees.
Locked