Fedora Account System
Red Hat Associate
Red Hat Customer
Trying a fresh install of cacti on a fresh install of F27: $ rpm -qa | egrep '(cacti|rrd)' rrdtool-1.7.0-4.fc27.x86_64 cacti-1.1.24-1.fc27.noarch After setting up two hosts, I have noticed that the graphs do not update. From debugging the poller, I see the first loop works fine: 2017/10/10 15:00:02 - POLLER: Poller[1] NOTE: Poller Int: '300', Cron Int: '300', Time Since Last: '301.11', Max Runtime '298', Poller Runs: '1' Waiting on 1 of 2 pollers. OK u:0.00 s:0.01 r:0.00 OK u:0.00 s:0.01 r:0.00 OK u:0.00 s:0.01 r:0.00 .... OK u:0.01 s:0.02 r:1.30 OK u:0.01 s:0.02 r:1.30 2017/10/10 15:00:04 - SYSTEM STATS: Time:2.4305 Method:cmd.php Processes:4 Threads:N/A Hosts:2 HostsPerProcess:1 DataSources:30 RRDsProcessed:24 The second and any further run of the poller will error with time problems: 2017/10/10 15:05:01 - POLLER: Poller[1] NOTE: Poller Int: '300', Cron Int: '300', Time Since Last: '299.93', Max Runtime '298', Poller Runs: '1' Waiting on 1 of 2 pollers. ERROR: /usr/share/cacti/rra/spin-gw_crc_id_au_cpu_nice_1.rrd: illegal attempt to update using time 1507608302 when last update time is 1507647602 (minimum one second step) ERROR: /usr/share/cacti/rra/spin-gw_crc_id_au_cpu_system_2.rrd: illegal attempt to update using time 1507608302 when last update time is 1507647602 (minimum one second step) ERROR: /usr/share/cacti/rra/spin-gw_crc_id_au_cpu_user_3.rrd: illegal attempt to update using time 1507608302 when last update time is 1507647602 (minimum one second step) ..... 2017/10/10 15:05:03 - SYSTEM STATS: Time:1.2364 Method:cmd.php Processes:4 Threads:N/A Hosts:2 HostsPerProcess:1 DataSources:30 RRDsProcessed:24 I'm not sure if this is fixed in 1.1.25 - which I note was released on Sept 27 - as I don't see anything in the changelog that may relate to this. I'm also not 100% sure if this is related to cacti or rrdtool. The error message is from rrdtool - but that's about all I've been able to find out.
Added link to github issue
Seems this is related to a new install not having the datetime.timezone set in /etc/php.ini. I'm unsure why it picked the offsets it did - but it seems to be operating now. Will discuss upstream re detecting this - or maybe changing the debugging around it.