RRD Files no updates after time set backwards

[usermf]

Hello,

We are running Cacti cacti-0.8.6j

- Suse 9.x
- Mysql 4.0.18
- rrd 1.2.x

After system time has been set back one hour and a following reboot, ALL rrd files don't receive any more updates, even newly configured
devices dont't receive updates and their files are not created.

As far as I know the rrdtool updates should proceed to work as soon as current time is greater than the last update timestamp.

The situation after two days is:

- All previously recorded data can be viewed via CACTI without problems.

- I do not encounter any error messages within the cacti log which would indicate that the files cannot be updated, but they are not when I dump the rrd dataset, there is no further data included.

- the cacti log shows, that the snmp data can be retrieved

- the behaviour was the same before I upgraded from 0.8.6.h to .j


Any help for troubleshooting this is very much appreciated

usermf

[BSOD2600]

This is by design of rrdtool. It thinks you already have valid data for an hour, so will not overwrite existing data. Either move the clock back to where it was, or wait until the elapsed time has expired.

[usermf]

Hello thanks a lot !

We have already three days without new data, so I believe the clock issue is not caused by rrd because:

- As I understood your answer, rrd would start to write new data as soon as the time stamp is newer than the one in the rrd file ( last updated ).

- even newly created devices don't get updated.


==> I can move the clock back to the old timestamp - which would be one hour ahead, but I don't think this makes sense.

Anyway thanks a lot

[BSOD2600]

Change the logging level to debug and look for what error(s) are occurring.

[usermf]

Hello,

I have activated Debugging Level and cannot see something which is related to the problem that the records dont get updated - see attached Log

Is there a possibility to check what rrdtool is doing during the update ?

Cheers, Marcel

[BSOD2600]

1) looks like you don't have sockets enabled in php, why not?

2) Yea, eventually cacti should get around to actually updating the rrd files. These are prefaced with CACTI2RRD in the log file and show exactly what cacti is doing with rrdtool. Was that all that got logged from a polling cycle?

[usermf]

Hello,

1.) There is no reason why sockets are not enabled, how can I do this ?

2.) Yes indeed this is all I received from one polling cycle, I'll check again if I can spot the
CACTI2RRD messages.

Marcel

[usermf]

Hello,

I double checked and there are no CACTI2RRD Messages. So it seems that CACTI does not call rrd to update the records whatever the reason is.

This even so, I have upgraded to the lastest version, so there might be some other issues....

Cheers, Marcel

[BSOD2600]

Well for windows at least, one enables the php_sockets extension. Not sure for linux if you have to compile it or what.

Try clearing the poller cache. So with debugging mode set in Cacti, using the cmd.php poller and running php cmd.php, you don't have any cacti2rrd entries in the log/screen?

[usermf]

Hello,

Sorry I was off on vacation for couple of days, that's why I write so lately.

I have re-installed cacti on another 'fresh' platform, dumped and restored the rrd files and now it works again.

So I believe the issue was not caused by the time but be the reboot which might have activated some anti-features.

I believe we can close it with the statement, that rrd actually can handle the time issues and this issue has been caused by some other changes on the same platform.

When you mentioned the Cacti2rrd missing log entries and nothing else complained I decided to move ahead.

Many thanks