Performance graphs not performing

[tpwebb]

Hello,

I have recently experienced problems with the performance graphs on Nagios, most are report 0,not getting any data, we also use statseeker and this appears to be working.

Current version is 5.7.1 updated 14/06/2020
Version 5.7 updated 10/06/2020

Problems started around the 12/06/2020.

Regards

Terry

[scottwilkerson]

You are hitting a load threshold in NPCD

Lets edit /usr/local/nagios/etc/pnp/npcd.cfg
change this

Code: Select all

load_threshold = 10.0

to this

Code: Select all

load_threshold = 40.0

save file and restart NPCD

Code: Select all

service npcd restart

[tpwebb]

Hello,

I have applied the fix to the system and restarted it. We are still not bandwidth receiving into our graphs. I bumped it up to 80 with steps in-between with not luck.

Your assistance is appreciated.

[lmiltchev]

If you have having issues with bandwidth graphs in particular, I would recommend troubleshooting the issue by following the KB article below:

https://support.nagios.com/kb/article/n ... hs-29.html

Let us know if this helped. Thank you!

[tpwebb]

Hello,

The link was very useful, after following I found my issue.

It related to MRTG running longer then 5 minutes, after running the command I found on 16 forks it was running for 8 minutes. I modified the file to have 48 and this resolved my problem. Is there a limit to how many can be added?

Also do you have a document of maintenance activities that should be checked periodically to ensure the system will continue to operate?

Again, thanks for your assistance.

[lmiltchev]

The link was very useful, after following I found my issue.

It related to MRTG running longer then 5 minutes, after running the command I found on 16 forks it was running for 8 minutes. I modified the file to have 48 and this resolved my problem.

I am glad I could help!

Is there a limit to how many can be added?

I didn't find any information on the topic in the MRTG documentation. You can view the documentation here:

https://oss.oetiker.ch/mrtg/doc/mrtg-re ... -UNIX-only

That being said, I don't believe there is an actual limit, but the number of forks should be kept in check. Too many of them will actually degrade performance and eat system resources. The number of forks you could use would depend on your specific environment.

Also do you have a document of maintenance activities that should be checked periodically to ensure the system will continue to operate?

We don't have a specific document on the issue. All maintenance should be performed automatically by the system. You can view DB maintenance in Admin > System Config > Performance Settings.

[tpwebb]

Thanks,

My problem is now resolved and this ticket can be closed.

[scottwilkerson]

Thanks,

My problem is now resolved and this ticket can be closed.

Great

Locking