When I try to 'Check for Updates' it takes a while to respond - but it does come back with:
"You're running the latest version of Network Analyzer."
I believe this might be because it does not have access to the internet, as we only allow access by proxy. How do we configure Nagios Network Analyzer to access the internet via a proxy?
Checking the following page does indeed indicate that there is a version 2.4.1:
Checking the crontab, it looks OK to me - so I expect the DNS cache to be refresh on the hour, every hour since my Hostname Cache Timeout is set to 3600.
Here is an example where the current epoch time is more than 3600 from the 'time' value for the entry, but it has not been updated (I had added PTR record entry for the IP ADDRESS).
There is not a setting in the Web interface for configuring a Proxy server but here are the instructions for upgrading in an offline environment. https://support.nagios.com/kb/article.php?id=738
I have been trying to recreate the issue but is seems to function correctly.
The empty cache.log is OK, as it only logs errors and every time it runs, it will overwrite the log file anyways.
If you run the following, does it update the entries?
I noticed that the /var/log/cron did not have any entries for the 'cache' cron entry, but it did have entries for the 'cmdsubsys' crontab entry.
I swapped the two entries in /etc/cron.d/nagiosna to make the 'cache' one appear first and now it does appear in /var/log/cron.
It did seem to update on the first time cron was run. Then I changed a DNS PTR recorded and waited for the next hourly cron run. But the entry did not update in NNA, even though the DNS entry did update - I checked using "getent hosts <IP Address>" and "resolveip <IP address>". I will give it another hour and check again.
As stated in my previous posts - it does seem to work when I run the php cache command manually, and when I truncate the table.
The issues seems to be that it does not seem to run properly when it is activated by cron. It is strange that I had to swap the entries before it appeared in the cron logs, but this might suggest some issue related to cron. Also, the cron log timestamp seem to be about 6 hours behind, even though the system and hardware clock time is correct. Again, there are a few things about cron that makes me suspect it is related to it.
Because cron was not running the job, it would not update the entries, that would be the cause for sure.
What OS and release is your server running?
Can you update the cron daemon to the latest version to see if that kicks off all of the jobs?
Be sure to check out our Knowledgebase for helpful articles and solutions!
