illegal attempt to update using time rrd...

[eterzella.r.t]

Plz help, in cacti.log show this error:


ERROR: illegal attempt to update using time 1193684528 when last update time is 1193684528 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684529 when last update time is 1193684529 (minimum one second step)
ERROR: illegal attempt to update using time 1193684527 when last update time is 1193684527 (minimum one second step)
ERROR: illegal attempt to update using time 1193684528 when last update time is 1193684528 (minimum one second step)
ERROR: illegal attempt to update using time 1193684528 when last update time is 1193684528 (minimum one second step)
ERROR: illegal attempt to update using time 1193684530 when last update time is 1193684530 (minimum one second step)
ERROR: illegal attempt to update using time 1193684530 when last update time is 1193684530 (minimum one second step)
ERROR: illegal attempt to update using time 1193684530 when last update time is 1193684530 (minimum one second step)
ERROR: illegal attempt to update using time 1193684530 when last update time is 1193684530 (minimum one second step)

[gandalf]

It is very likely that you hit the "double poller issue" described at the second link of my signature
Reinhard

[eterzella.r.t]

I execute rrdtool fetch <rrd file> AVERAGE, and show....

1193798520: 2.5756666667e+02
1193798580: 1.6115000000e+02
1193798640: 1.7880000000e+02
1193798700: nan
1193798760: nan
1193798820: nan
1193798880: 3.0500000000e+02
1193798940: 3.6530000000e+02
1193799000: 3.7650000000e+02
1193799060: 3.1803333333e+02
1193799120: 4.4200000000e+02
1193799180: 4.5276666667e+02
1193799240: 4.5300000000e+02
1193799300: 4.5300000000e+02
1193799360: 3.9700000000e+02
1193799420: 2.6380000000e+02
1193799480: 1.8423333333e+02
1193799540: 1.8423333333e+02
1193799600: 1.5773333333e+02
1193799660: 1.5233333333e+02

[eterzella.r.t]

When the poller, Poller Runs:'1 'appears the error of ERROR: illegal attempt to update using time. I do not know if that can help solve my problem. I did everything that is described in the link you I spent more my problem still exists

10/31/2007 09:52:01 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '60', Time Since Last: '58', Max Runtime '58', Poller Runs: '1'
10/31/2007 09:51:03 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '300', Time Since Last: '242', Max Runtime '298', Poller Runs: '5'
10/31/2007 09:50:01 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '240', Time Since Last: '180', Max Runtime '238', Poller Runs: '4'
10/31/2007 09:49:03 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '180', Time Since Last: '122', Max Runtime '178', Poller Runs: '3'
10/31/2007 09:48:02 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '120', Time Since Last: '61', Max Runtime '118', Poller Runs: '2'
10/31/2007 09:47:01 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '300', Time Since Last: '240', Max Runtime '298', Poller Runs: '5'
10/31/2007 09:46:01 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '240', Time Since Last: '180', Max Runtime '238', Poller Runs: '4'
10/31/2007 09:45:02 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '180', Time Since Last: '121', Max Runtime '178', Poller Runs: '3'
10/31/2007 09:44:01 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '120', Time Since Last: '60', Max Runtime '118', Poller Runs: '2'
10/31/2007 09:43:01 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '60', Time Since Last: '59', Max Runtime '58', Poller Runs: '1'
10/31/2007 09:42:02 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '300', Time Since Last: '241', Max Runtime '298', Poller Runs: '5'
10/31/2007 09:41:01 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '240', Time Since Last: '180', Max Runtime '238', Poller Runs: '4'
10/31/2007 09:40:01 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '180', Time Since Last: '120', Max Runtime '178', Poller Runs: '3'
10/31/2007 09:39:02 AM - POLLER: Poller[0] DEBUG: Poller Int: '60', Cron Int: '120', Time Since Last: '61', Max Runtime '118', Poller Runs: '2'

[eterzella.r.t]

Does this have to do? What this message mean?

Cacti[24913]: POLLER: WARNING: Poller Output Table not Empty. Potential Data Source Issues for Data Sources: ds_status_estado(DS[790]), ds_status_estado(DS[790]), ds_porta_local(DS[822]), ds_porta_local(DS[822]), ds_ping(DS[841]), proc(DS[842]), cpu(DS[843]), cpu(DS[844]), cpu(DS[845]), cpu(DS[846]), hrStorageSize(DS[847]), hrStorageUsed(DS[847]), hrStorageSize(DS[848]), hrStorageUsed(DS[848]), hrStorageSize(DS[849]), hrStorageUsed(DS[849]), hrStorageSize(DS[850]), hrStorageUsed(DS[850]), hrStorageSize(DS[851]), hrStorageUsed(DS[851]), hrStorageSize(DS[852]), hrStorageUsed(DS[852]), hrStorageSize(DS[853]), hrStorageUsed(DS[853]), traffic_in(DS[854]), traffic_out(DS[854]), traffic_in(DS[855]), traffic_out(DS[855]), traffic_in(DS[856]), traffic_out(DS[856]), ds_porta_local(DS[857]), ds_porta_local(DS[858]), ds_porta_local(DS[859]), status(DS[862]), status(DS[862]), status(DS[888]), status(DS[893]), status(DS[893]), status(DS[955]), status(DS[955]), ds_value_gauge(DS[1043]), ds_value_counter(DS[1044]), ds_value_counter(DS[1045]), ds_value_gauge(DS[1046]), ds_value_gauge(DS[1047]), ds_value_gauge(DS[1047]), ds_value_gauge(DS[1050]), ds_value_gauge(DS[1051]), ds_value_gauge(DS[1052]), ds_value_gauge(DS[1053]), ds_value_gauge(DS[1055]), ds_value_gauge(DS[1056]), ds_value_gauge(DS[1057]), ds_value_gauge(DS[1057]), ds_value_gauge(DS[1059]), ds_value_gauge(DS[1059]), ds_value_gauge(DS[1060]), ds_value_gauge(DS[1060]), ds_status_remoto(DS[1062]), ds_status_local(DS[1063]), ds_rem_porta(DS[1064]), ds_cpu(DS[1135]), ds_cpu(DS[1135]), ds_mem(DS[1135]), ds_mem(DS[1135]), ds_num_proc(DS[1135]), ds_num_proc(DS[1135]), ds_cpu(DS[1142]), ds_cpu(DS[1142]), ds_mem(DS[1142]), ds_mem(DS[1142]), ds_num_proc(DS[1142]), ds_num_proc(DS[1142]), ds_cpu(DS[1144]), ds_cpu(DS[1144]), ds_mem(DS[1144]), ds_mem(DS[1144]), ds_num_proc(DS[1144]), ds_num_proc(DS[1144]), ds_value_gauge(DS[1176]), ds_value_gauge(DS[1176]), ds_value_gauge(DS[1177]), ds_value_gauge(DS[1177]), ds_value_gauge(DS[1178]), ds_value_gauge(DS[1178]), ds_value_gauge(DS[1179]), ds_value_gauge(DS[1179]), ds_value_gauge(DS[1180]), ds_value_gauge(DS[1180]), ds_cpu(DS[1181]), ds_mem(DS[1181]), ds_num_proc(DS[1181]), ds_cpu(DS[1182]), ds_mem(DS[1182]), ds_num_proc(DS[1182]), ds_cpu(DS[1183]), ds_mem(DS[1183]), ds_num_proc(DS[1183]), ds_cpu(DS[1184]), ds_cpu(DS[1184]), ds_mem(DS[1184]), ds_mem(DS[1184]), ds_num_proc(DS[1184]), ds_num_proc(DS[1184]), ds_status_remoto(DS[1187]), ds_status_remoto(DS[1187]), ds_status_local(DS[1189]), ds_status_local(DS[1189]), ds_rem_porta(DS[1190]), ds_rem_porta(DS[1190]), ds_rem_porta(DS[1196]), ds_cpu(DS[1221]), ds_cpu(DS[1221]), ds_mem(DS[1221]), ds_mem(DS[1221]), ds_num_proc(DS[1221]), ds_num_proc(DS[1221]), ds_cpu(DS[1222]), ds_cpu(DS[1222]), ds_mem(DS[1222]), ds_mem(DS[1222]), ds_num_proc(DS[1222]), ds_num_proc(DS[1222]), ds_cpu(DS[1223]), ds_cpu(DS[1223]), ds_mem(DS[1223]), ds_mem(DS[1223]), ds_num_proc(DS[1223]), ds_num_proc(DS[1223]), ds_value_gauge(DS[1239]), hrStorageSize(DS[1263]), hrStorageSize(DS[1263]), hrStorageUsed(DS[1263]), hrStorageUsed(DS[1263]), hrStorageSize(DS[1264]), hrStorageSize(DS[1264]), hrStorageUsed(DS[1264]), hrStorageUsed(DS[1264]), hrStorageSize(DS[1265]), hrStorageSize(DS[1265]), hrStorageUsed(DS[1265]), hrStorageUsed(DS[1265]), hrStorageSize(DS[1266]), hrStorageSize(DS[1266]), hrStorageUsed(DS[1266]), hrStorageUsed(DS[1266])

[eterzella.r.t]

Tried in all my cron's and has only one entry of poller.php.

I made the tunning of mysql and php, thinking that might be something to that effect.

My basis is was the Cacti 0.86, and did the update to 0.87.

[eterzella.r.t]

He was running in version 0.87 ... From 1 to 1 minute and my poller in crond was in 1 in 1 minute. Placed would run from 5 to 5, and solved my problem.

[TheWitness]

Bottom line, until we get this fixed, use a 5 minute Cron or Scheduled Task. You can still have 10 second polling, the poller will simply hang out for all 5 minutes.

TheWitness

[eddievenus]

What does that mean exactly?

Does it mean that if I want 1 minute polling in .8.7 I should set it to 1 minute polling but set my crontab to poll every 5 minutes?

This seems odd, but if you suggest that it will work I will do it because it is one of the best features of Cacti that I can do 1 minute polling or even more frequently if I choose.

I will try setting my cronjob for 5 minutes and see if that works, I get the feeling that I ran into a problem with that in the past though where if cron was set to 5 minutes the 1 minute polling would only really poll every 5 minutes and not tell me.

EddieVenus

[eddievenus]

It is very likely that you hit the "double poller issue" described at the second link of my signature
Reinhard

I could not find a reference to a double poller issue at that page. I did however rule out those problems, more or less. I plan to retest a few after running this on another box.

Can you go into more detail about what this double poller issue is?

[eddievenus]

Bottom line, until we get this fixed, use a 5 minute Cron or Scheduled Task. You can still have 10 second polling, the poller will simply hang out for all 5 minutes.

TheWitness

I am happy to say that I set the crontab to run every 5 minutes and my 1 minute polling is still working. Thats cool.

i will see if this resolves any of the graph issues at all, but it looks promising.

[eddievenus]

It did not last. Eventually it started doing the same thing.

I ran my old cactiEZ0.2 virtual machine on this same server since it came out without this type of problem. I was running 1 minute polling there as well. I upgraded to CactiEZ0.3 then upgraded all the plugins to the latest versions. Now I cannot go more than 20 minutes or so without losing at least 2 polling cycles, usually just 2.

I followed everything the HowTo recommended, though it was for 8.6 which I had no problems with, so i imagine there is something different here that is not yet in the HowTo. Nothing lead to a solution.

I would be happy to post logs if anyone wants to see them, let me know how much you wish to see, I hate it when people just post everything and hope they included what you want. i would rather post what was asked for.

EV