Nagios Support Forum

We have had our Nagios XI environment set up for several years. It appears that the person that set it up previously made some sort of configuration that causes certain users to get updates where the status is UNKNOWN (i.e., it can't figure out what to do). I have been troubleshooting an issue with ...

Good morning! We are running 5.5.2 of Nagios XI, and everything appears to be fine overall. We had an issue with a hung cron job a couple of weeks ago that was causing issues, but outside of that this version has been stable for us. We have noticed a couple of times that we get notifications for pro...

Okay, it's now been two hours and we're not getting any growth at all on that file. Is that cron job that was hung something that we would have caused somehow, or is it indicative of a bigger problem? I just want to have a root cause for it, if that's possible. Either way, I'm ecstatic it's working ...

I've run these commands and will keep an eye on it. It was filling the drive about once very 1.5-2 hrs, so it should be obvious pretty quickly.

I'll update once I know more. Thanks.

Since the original cmdsubset.log file isn't growing (it's the additional), I added the > back into the cron job piece. I have let that file grow a bit (it's only 58K), and I've added it here. This will give more than the one line from the other one.

Thanks.
Scott

Just to be clear, the cmdsubset.log file doesn't grow - it's the cmdsubset.log-20180821 file that continually grows. It doesn't appear that anything else is, though. If I clear that one file with the 2018 date appended to it it drops to a reasonable number used on the volume. So, cmdsubset.log is ok...

Results attached. The cmdsubset.log only has the one line...

Definitely still filling up the other file, too.

I tried removing the > but it is still increasing the size of the file named: cmdsubsys.log-20180821 As far as the monitoring engine and environment, everything looks good. The only issue is that one file that grows ever larger until it fills the disk and everything stops because it can't process.

This is the code from that area (just for the record):


// Verify ndo and core are running and loaded
$data = get_program_status_xml_output(array(), true);
if ($data['is_currently_running'] == 1) {
$is_running = true;
}

Lines 135-141.

Quick update - I tailed the log and found hundreds of lines of this repeated: PHP Notice: Uninitialized string offset: 0 in /usr/local/nagiosxi/html/includes/components/nagiosbpi/api_tool.php on line 138 PHP Warning: Illegal string offset 'is_currently_running' in /usr/local/nagiosxi/html/includes/c...