Nagios Support Forum

We would need the complete historical logs during the event from each node to be able to say for sure what caused it. Typically, it's either network issues or some instability on one or many nodes that causes them to crash.

Can you share any documentation you are following? Nagios Core is only meant to be installed on Linux based systems.

Or if you are having troubles installing Nagios Core on a 64-bit Virtual Machine, you might check your motherboard's BIOS setting specific to virtualization.

Replacing /usr/local/nagios/share/images/sblogo.png worked fine for me:
Have you made sure to do a hard-refresh from your web browser to clear out any cached images? Typically CTRL+F5 does the trick.

You may find this documentation useful:
https://assets.nagios.com/downloads/nag ... ios-XI.pdf

I'm actually looking for the command that produces this output: WARNING - (1 warnings) - 08-01 20:36:37.553 Not the command you are using for your notifications. Again, the various OUTPUT macros rely completely and entirely on what the plugin gives you, so it's valuable to know what, if anything, a ...

You might also try altering your check_wmi_plus command to leverage the --forcetruncateoutput argument. By default, this plugin will truncate the data received at 8192 bytes. You might bump it up to something like 65536 instead. I don't have a lab setup readily available, but it might look something...

This is a major change between 0.7.8 and 0.8.0: Try a yum install php-pdo php-mssql and see if that gets 0.8.0 running. If it doesn't, can you share the output of the previously executed yum command?

I want a more detailed message of the error. Is there a way to edit the SERVICEOUTPUT response to display what the warning is?. Try $LONGSERVICEOUTPUT$ . Those macros only return whatever the plugin your check uses returned to stdout . If your plugin isn't returning specific enough data, there's no...

It looks like this functionality has been removed with recent versions (like 0.5.x):
From:
https://github.com/mickem/nscp/blob/mas ... gelog#L581

The last time I helped setup asterisk logs, it was a simple matter of pointing the system's syslog daemon (syslog-ng in this case) to the Asterisk log files. Under the big green "+ Log Source" button in Nagios Log Server (from the index and Administration pages if memory serves), there sho...