Nagios Support Forum

It sounds like there's a service with a config named '0' pointing to a host that doesn't exist. Does the 'XXXX' host exist? Do you see a service with a config name '0' under Configure > Core Config Manager > Monitoring > Services ? If so, edit it to review the config and/or disable it.

Do you see usernames in the http access logs? You may need to add the "require valid-user" line to the naigos.conf file to make the username available and then define the user as user01@REALM in the cgi.cfg file.

The unassigned primary shard for the nagioslogserver_log is the reason you see the RED status. Restarting elasticsearch _may_ help fix it: service elasticsearch restat If this doesn't help then you can try restoring from a backup. From page 8 of https://assets.nagios.com/downloads/nagios-log-server/...

What OS and XI version?

Anything logged in /var/log/cron or /var/log/secure when the cron tried to run before the log was put in place?

Does the nagios user ahve write permissions on the /usr/local/nagiosxi/ directory ?

https://assets.nagios.com/downloads/nag ... ios-XI.pdf covers migrating from core to XI. Review it and let us know if you have any questions or run into any issues.

Please PM me profile from the system. It can be gathered under Admin > System > System Status > Download System Profile or from the command line with: /usr/local/nagioslogserver/scripts/profile.sh This will create /tmp/system-profile.tar.gz. Note that this file can be very large and may not be able ...

bheden and anyone else troubleshooting a MTR, I've found /var/log/api.log on the MTR useful in troubleshooting. A successful test message is logged like: 2019-08-26T18:11:25.578528+00:00 mtr API: [SESSION] Starting FCGI Request [46812] 2019-08-26T18:11:25.579702+00:00 mtr API: [SESSION] count 48 to...

Edit the 172.16.24.1 host(Configure > Core Config Manager > Monitoring > Hosts) and remove xi_default_contact from the contacts list or add a contact called xi_default_contact(Configure > Core Config Manager > Alerting > Contacts), and the try running the upgrade script again.

I was able to reproduce the behavior and it appears to be a bug. I would suggest spinning up a current version of XI, verify this functionality works in your environment, an then perform an upgrade to take advantage of this fix. https://assets.nagios.com/downloads/nagiosxi/docs/XI-Upgrade-Instructio...

It looks like it is having an issue with the characters in the SerialNo field that is being sent over. Are you able to view the logs on the device? I'd be curious what the logs look like there as well the raw data being sent. The raw data can be gathered with: yum -y tcpdump tcpdump -s 0 -i any port...