Nagios

|^^|

Performance Graph.

To further analyze the issue, we would like to request these following log files. Kindly attach it to your next mail.

/usr/local/nagios/var/npcd.log

Kindly run this commands as well. Provide us the results of these commands.

ls /usr/local/nagios/var/spool/xidpe | wc -l ls /usr/local/nagios/var/spool/perfdata | wc -l ls /usr/local/nagios/var/spool/checkresults | wc -l service ncpd status

===========================================================================

===========================================================================

Based on the logs that you provided, it seems that it was processing too much performance data.

The possible caused of the issue is that the processing the performance data was having a timeout. The default timeout for the processing was only 5 seconds.

To adjust timeout processing of performance data, kindly follow these procedures.

1. Edit the perfdata configuration file. /usr/local/nagios/etc/pnp/process_perfdata.cfg 2. Find the TIMEOUT settings. TIMEOUT = 5 3. Change the value to 20 seconds TIMEOUT = 20

After changing the value, kindly wait for 30 minutes, then try to recheck the affected performance graph.

next:

Kindly follow these procedures.

1. Edit /usr/local/nagios/etc/pnp/npcd.cfg. Then set this value. log_level = 2 2. Edit /usr/local/nagios/etc/pnp/process_perfdata.cfg. Then set this value. LOG_LEVEL = 2 3. Run this command. service npcd restart

After running that commands, kindly run these for further checking.

service npcd status tail -n 100 /usr/local/nagios/var/npcd.log

Kindly provide us the output of these commands.

next:

SEE NPCD_Logs file attched.

Can you now check the performance data?

Based on the logs that you provided, it seems that the performance data were being successfully processed.

[01-14-2016 17:36:14] NPCD: DEBUG: load 1.840000/10.000000 [01-14-2016 17:36:14] NPCD: ThreadCounter 0/5 File is 1452764156.perfdata.host [01-14-2016 17:36:14] NPCD: Regular File: 1452764156.perfdata.host [01-14-2016 17:36:14] NPCD: A thread was started on thread_counter = 0 [01-14-2016 17:36:14] NPCD: DEBUG: load 1.840000/10.000000 [01-14-2016 17:36:14] NPCD: Processing file 1452764156.perfdata.host with ID 140529408472832 - going to exec /usr/local/nagios/libexec/process_perfdata.pl -n -b /usr/local/nagios/var/spool/perfdata//1452764156.perfdata.host [01-14-2016 17:36:14] NPCD: ThreadCounter 1/5 File is 1452764156.perfdata.service [01-14-2016 17:36:14] NPCD: Processing file '1452764156.perfdata.host' [01-14-2016 17:36:14] NPCD: Regular File: 1452764156.perfdata.service [01-14-2016 17:36:14] NPCD: A thread was started on thread_counter = 1 [01-14-2016 17:36:14] NPCD: Processing file 1452764156.perfdata.service with ID 140529397982976 - going to exec /usr/local/nagios/libexec/process_perfdata.pl -n -b /usr/local/nagios/var/spool/perfdata//1452764156.perfdata.service [01-14-2016 17:36:14] NPCD: Have to wait: Filecounter = 5 - thread_counter = 2 [01-14-2016 17:36:14] NPCD: Processing file '1452764156.perfdata.service' [01-14-2016 17:36:14] NPCD: No more files to process... waiting for 15 seconds

The logs were indicating that the perfdata was being successfully processed and it was able to process all the perfdata.

If there was still no performance graph data on NagiosXI page, kindly advise us.

next: Requesting a remote session

This is to give you a report with regards to the conducted remote session with your NagiosXI server.

    1. Checked the performance data of the affected host.

    2. Checked the performance data history of the affected service.

    3. Checked the other performance history of the affected host.

    4. Checked the NagiosXI logs.

    5. Checked the NPCD and perfdata logs.

    6. Checked the timezone on the NagiosXI server side.

Based on the checking that conducted, it seems that the issue was not the performance graph itself. The possible issue here was the gathered information by using the SNMP.

To further troubleshoot the issue, we would like to request these following files. It was the logs and configuration files of the affected service.

/usr/local/nagios/var/perfdata.log

/etc/mrtg/conf.d/10.16.2.254.cfg

/usr/local/nagios/var/nagios.log

/usr/local/nagios/etc/services/ASA_CISCO_FW.cfg

/usr/local/nagios/etc/hosts/ASA_CISCO_FW.cfg

If you have concerns with regards to the remote session being conducted, please let us know.

We've checked that the default timeout for the bandwidth monitoring used by NagiosXI was 2 seconds.

Monitoring a high traffic network device may cause a timeout with bandwidth monitoring.

Before we change the default timeout configuration of your NagiosXI server, we would like to request additional configuration file.

/etc/mrtg/mrtg.cfg

Kindly attach the requested configuration file on your next mail.

eof