Nagios Support Forum

Hello,

Our closed secure network has Nagios XI running but the performance grapher seems to not be working. I cannot provide a screenshot due to it being on a sensitive network enclave. When I click on "System Status", the XI System Component Status shows the Monitoring Engine and the Database Backend as the only two items with a green status. The rest of the status indications show red exclamation point. When I click on the Action gear beside Performance Grapher, the check times out and say "Your request was not processed in a timely manner. It may still execute, as the server may be temporarily busy". But, nothing ever happens. When I "systemctl status npcd", it shows it as running but it also indicates "Failed to read PID from file /usr/local/nagiosxi/var/subsys/npcd.pid: Invalid argument". This made me believe it could be a permissions issue, but I do not know if this is the case and what files to check.

I read through some of the before entries about this issue, and I've adjusted the load threshold on the npcd.cfg file so that the thread processes won't time out. But, this has still not fixed the performance grapher issue. Please assist, as I cannot figure out what to do next.

Sorry, just thought I should include:

OS: CentOS 7.2.1511 (64bit)
No special configurations
NagiosXI version: 5.4.4

Let me also add that if I try to use Core Config Manager and apply any new configurations, it just times out and does not apply the configuration. It just keeps adding ............. (periods) but never does anything.

Sarg0n wrote:Let me also add that if I try to use Core Config Manager and apply any new configurations, it just times out and does not apply the configuration. It just keeps adding ............. (periods) but never does anything.

Lets start here because nothing is going to work if we don't get the apply configuration corrected.

Please go through all the steps in the article and return all output to this post

https://support.nagios.com/kb/article.php?id=34

Additionally return the results of the folloing

Scott, thanks for replying and I apologize for not responding immediately. I tried going through the article and it seems that the issues mentioned are not showing what the articles is stating (there is no cmdsubsys.log file, there is no permissions issue when running the script, etc.) There are a few issues with this build that has motivated me to create a fresh build in my lab...primarily because this version is so outdated (5.4.4) and needs updated to the latest, and we need higher storage for our build, as we have close to 300 sources our team is wanting to add for monitoring. Plus, our lab is net accessible and therefore I can post any build issues I have on here and we can work it out. I will start a new thread on my build...as the installation script is not working....

Thanks again.

That all sound like a good idea as this is really bad...

there is no cmdsubsys.log file

that should always exist and is written to constantly via a cron job.