Nagios Support Forum

Hello,

I've recently amended the charting configuration on our Nagios Core from npcmod to Bulk Mode with NPCD, although graphs are being displayed I'm seeing alot of the below error messages in the perfdata.log which I didn't see in the dev environment. Any ideas what this relates to? I've checked that only one instance of Nagios is running and double checked the config changes made but cannot find the reason for these errors. I get these for various hosts all of which display graphs ok.

RRDs::update ERROR /usr/local/pnp4nagios/var/perfdata/xxxxxxxxx/_HOST_.rrd: illegal attempt to update using time 1394728452 when last update time is 1394728452 (minimum one second step)

Any help would be greatly appreciated.

Thanks,

You may want to check the system time. If NTP pushes the time back by a couple of seconds, you may see this issue. Additionally, if you have more than 1 check configured that writes to the same RRD, you may experience this error as well.

Thanks for the feedback.

System time seems fine on the box and also there doesn't appear to be any duplicate checks, is there any other reason you would see this message?

Let's make certain your time is correct:

# ntpstat
synchronised to NTP server () at stratum 4
time correct to within 103 ms
polling server every 1024 s
# ntpq -pn
remote refid st t when poll reach delay offset jitter
==============================================================================
*xxxxxxxxxxxxx xxxxxxxxxxxxx 3 u 795 1024 377 0.581 0.147 0.116
+xxxxxxxxxxxxx xxxxxxxxxxxxx 3 u 512 1024 377 0.471 -0.661 1.576

How frequently is the host xxxxxxxxx performing a check or receiving check results? The error is suggesting that a result with performance data has already been entered this second for the host, and that is the maximum frequency that can be put in an RRD

Apologies if the below isn't what you're after...i'm fairly new to Nagios as you can probably tell

# HOST AND SERVICE CHECK REAPER FREQUENCY
# This is the frequency (in seconds!) that Nagios will process
# the results of host and service checks.

check_result_reaper_frequency=10

# INTERVAL LENGTH
# This is the seconds per unit interval as used in the
# host/contact/service configuration files. Setting this to 60 means
# that each interval is one minute long (60 seconds). Other settings
# have not been tested much, so your mileage is likely to vary...

interval_length=60


in the hosts file the seetings are:

check_interval 5
retry_interval 1

Nope, that is exactly what he was looking for, and then some! Unfortunately it looks like everything is correct, provided this was an active check that resulted in the error.
Was this from scheduling an immediate check, or passive results coming in?
Are you seeing this with any other rrd files?
How often do you have npcd updating? (npcd.cfg)
Do your graphs still seem to be updating properly or are they static from when this started happening?