These look to be stuck in my Outbox, is there a reason for that?
Thanks.
CPU Usage in performance graph is not working
- Nagios Support
- Posts: 36
- Joined: Thu Sep 04, 2014 12:16 pm
Re: CPU Usage in performance graph is not working
Things will be put in the Outbox until the account owner reads the message. I have retrieved the files and placed them on our shared drive.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: CPU Usage in performance graph is not working
I didn't see anything weird in the configs you sent us. I noticed however, that logging in disabled in the npcd.cfg. Change this line:
to this:
save, exit and restart npcd:
Next, post the tail of the npcd.log:
Most probably, we will need to do a remote session in order to further troubleshoot this issue. Is opening an email ticket in our system an option for you?
Code: Select all
log_level = 0Code: Select all
log_level = 2Code: Select all
service npcd restartCode: Select all
tail -100 /usr/local/nagios/var/npcd.logBe sure to check out our Knowledgebase for helpful articles and solutions!
Re: CPU Usage in performance graph is not working
I can open an email ticket, what is the process for that? i have not had to do that yet.
Thanks.
Thanks.
Re: CPU Usage in performance graph is not working
Send us an email at [email protected]. Type "CPU Usage in performance graph is not working" in the subject line, and provide a URL link to this post in the email's body. Thanks!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: CPU Usage in performance graph is not working
The issue was resolved. I had multiple Host folders with similar names due to renaming the hosts. After deleting all the .rrd and .xml files for the CPU the issue was resolved. When i had originally deleted them i must have been in a host folder that was not in use any longer.
Please close the case.
Thanks.
Please close the case.
Thanks.
Re: CPU Usage in performance graph is not working
Thanks for that update and glad to hear this is resolved. We'll lock this thread now but feel free to open another should you require assistance with anything else.
Be sure to check out the Knowledgebase for helpful articles and solutions!