Rebuild poller cache in windows

Post support questions that relate to the Windows 2003/2000/XP operating systems.

Moderators: Developers, Moderators

Post Reply
petebc
Posts: 3
Joined: Thu Dec 16, 2010 4:37 pm

Rebuild poller cache in windows

Post by petebc »

Hi, I'm trying to get cacti back on track in windows, and was wondering if I was missing a step here..

I upgraded to the latest version, downloaded all the patch files and put them in place, downloaded the new spine files and upgraded that as well. Loaded up cacti and it seemed to go through the upgrade process just fine.. but... when I go into Utilities-System Utilities, and run Rebuild Poller cache, I just get 489 rows of items...am I supposed to do something additional here to get these cleared out? I don't see any confirmation page, or anything... I thought this might just be how it was, and that it was indeed clearing it out, but when I look at my cacti log I see constant errors like this:

12/16/2010 04:35:02 PM - SYSTEM STATS: Time:2.5230 Method:cmd.php Processes:8 Threads:N/A Hosts:40 HostsPerProcess:5 DataSources:99 RRDsProcessed:52
12/16/2010 04:35:01 PM - CMDPHP: Poller[0] Host[37] DS[228] WARNING: Result from CMD not valid. Partial Result: U
12/16/2010 04:35:01 PM - CMDPHP: Poller[0] Host[33] DS[322] WARNING: Result from CMD not valid. Partial Result: U
12/16/2010 04:35:01 PM - CMDPHP: Poller[0] Host[26] DS[239] WARNING: Result from CMD not valid. Partial Result: U
12/16/2010 04:35:01 PM - CMDPHP: Poller[0] Host[42] DS[223] WARNING: Result from CMD not valid. Partial Result: U
12/16/2010 04:35:00 PM - POLLER: Poller[0] WARNING: Scheduled Task is out of sync with the Poller Interval! The Poller Interval is '60' seconds, with a maximum of a '300' second Scheduled Task, but 300 seconds have passed since the last poll!

...over and over..

Cacti is all I have running on this box along with mysql and it's a pretty hefty box..unless perhaps I AM doing the right thing but the box isn't keeping up...?

Pete
User avatar
BSOD2600
Cacti Moderator
Posts: 12171
Joined: Sat May 08, 2004 12:44 pm
Location: USA

Re: Rebuild poller cache in windows

Post by BSOD2600 »

Any other errors/issues?

When the logging level detail increased, what are the specific errors?
petebc
Posts: 3
Joined: Thu Dec 16, 2010 4:37 pm

Re: Rebuild poller cache in windows

Post by petebc »

Not really..how much would I need to turn this up to see the detail you're asking about? Right now after letting it sit overnight I have the errors below and graphics not coming in...just saying: Current/Avg/Max is -1.#J


12/17/2010 09:45:00 AM - POLLER: Poller[0] WARNING: Scheduled Task is out of sync with the Poller Interval! The Poller Interval is '60' seconds, with a maximum of a '300' second Scheduled Task, but 300 seconds have passed since the last poll!
12/17/2010 09:45:00 AM - POLLER: Poller[0] NOTE: Poller Int: '60', Scheduled Task Int: '60', Time Since Last: '300', Max Runtime '58', Poller Runs: '1'
12/17/2010 09:40:59 AM - SYSTEM STATS: Time:58.6808 Method:spine Processes:8 Threads:1 Hosts:40 HostsPerProcess:5 DataSources:97 RRDsProcessed:0
12/17/2010 09:40:59 AM - POLLER: Poller[0] Maximum runtime of 58 seconds exceeded. Exiting.
12/17/2010 09:40:00 AM - POLLER: Poller[0] WARNING: Scheduled Task is out of sync with the Poller Interval! The Poller Interval is '60' seconds, with a maximum of a '300' second Scheduled Task, but 300 seconds have passed since the last poll!
12/17/2010 09:35:59 AM - SYSTEM STATS: Time:58.6706 Method:spine Processes:8 Threads:1 Hosts:40 HostsPerProcess:5 DataSources:97 RRDsProcessed:0
12/17/2010 09:35:59 AM - POLLER: Poller[0] Maximum runtime of 58 seconds exceeded. Exiting.
12/17/2010 09:35:00 AM - POLLER: Poller[0] WARNING: Scheduled Task is out of sync with the Poller Interval! The Poller Interval is '60' seconds, with a maximum of a '300' second Scheduled Task, but 300 seconds have passed since the last poll!
12/17/2010 09:30:59 AM - SYSTEM STATS: Time:58.6703 Method:spine Processes:8 Threads:1 Hosts:40 HostsPerProcess:5 DataSources:97 RRDsProcessed:0
12/17/2010 09:30:59 AM - POLLER: Poller[0] Maximum runtime of 58 seconds exceeded. Exiting.
12/17/2010 09:30:00 AM - POLLER: Poller[0] WARNING: Scheduled Task is out of sync with the Poller Interval! The Poller Interval is '60' seconds, with a maximum of a '300' second Scheduled Task, but 300 seconds have passed since the last poll!
12/17/2010 09:25:59 AM - SYSTEM STATS: Time:58.6518 Method:spine Processes:8 Threads:1 Hosts:40 HostsPerProcess:5 DataSources:97 RRDsProcessed:0
12/17/2010 09:25:59 AM - POLLER: Poller[0] Maximum runtime of 58 seconds exceeded. Exiting.
12/17/2010 09:25:00 AM - POLLER: Poller[0] WARNING: Scheduled Task is out of sync with the Poller Interval! The Poller Interval is '60' seconds, with a maximum of a '300' second Scheduled Task, but 300 seconds have passed since the last poll!
12/17/2010 09:20:59 AM - SYSTEM STATS: Time:58.5623 Method:spine Processes:8 Threads:1 Hosts:40 HostsPerProcess:5 DataSources:97 RRDsProcessed:0
12/17/2010 09:20:59 AM - POLLER: Poller[0] Maximum runtime of 58 seconds exceeded. Exiting.
12/17/2010 09:20:00 AM - POLLER: Poller[0] WARNING: Scheduled Task is out of sync with the Poller Interval! The Poller Interval is '60' seconds, with a maximum of a '300' second Scheduled Task, but 300 seconds have passed since the last poll!
12/17/2010 09:15:59 AM - SYSTEM STATS: Time:58.6537 Method:spine Processes:8 Threads:1 Hosts:40 HostsPerProcess:5 DataSources:97 RRDsProcessed:0
12/17/2010 09:15:59 AM - POLLER: Poller[0] Maximum runtime of 58 seconds exceeded. Exiting.
12/17/2010 09:15:00 AM - POLLER: Poller[0] WARNING: Scheduled Task is out of sync with the Poller Interval! The Poller Interval is '60' seconds, with a maximum of a '300' second Scheduled Task, but 300 seconds have passed since the last poll!
12/17/2010 09:10:59 AM - SYSTEM STATS: Time:58.6708 Method:spine Processes:8 Threads:1 Hosts:40 HostsPerProcess:5 DataSources:97 RRDsProcessed:0
12/17/2010 09:10:59 AM - POLLER: Poller[0] Maximum runtime of 58 seconds exceeded. Exiting.
12/17/2010 09:10:00 AM - POLLER: Poller[0] WARNING: Scheduled Task is out of sync with the Poller Interval! The Poller Interval is '60' seconds, with a maximum of a '300' second Scheduled Task, but 300 seconds have passed since the last poll!
12/17/2010 09:05:59 AM - SYSTEM STATS: Time:58.6861 Method:spine Processes:8 Threads:1 Hosts:40 HostsPerProcess:5 DataSources:97 RRDsProcessed:0
12/17/2010 09:05:59 AM - POLLER: Poller[0] Maximum runtime of 58 seconds exceeded. Exiting.
12/17/2010 09:05:00 AM - POLLER: Poller[0] WARNING: Scheduled Task is out of sync with the Poller Interval! The Poller Interval is '60' seconds, with a maximum of a '300' second Scheduled Task, but 300 seconds have passed since the last poll!
12/17/2010 09:00:59 AM - SYSTEM STATS: Time:58.6859 Method:spine Processes:8 Threads:1 Hosts:40 HostsPerProcess:5 DataSources:97 RRDsProcessed:0
12/17/2010 09:00:59 AM - POLLER: Poller[0] Maximum runtime of 58 seconds exceeded. Exiting.
12/17/2010 09:00:00 AM - POLLER: Poller[0] WARNING: Scheduled Task is out of sync with the Poller Interval! The Poller Interval is '60' seconds, with a maximum of a '300' second Scheduled Task, but 300 seconds have passed since the last poll!
12/17/2010 08:55:59 AM - SYSTEM STATS: Time:58.6855 Method:spine Processes:8 Threads:1 Hosts:40 HostsPerProcess:5 DataSources:97 RRDsProcessed:0
12/17/2010 08:55:59 AM - POLLER: Poller[0] Maximum runtime of 58 seconds exceeded. Exiting.
User avatar
BSOD2600
Cacti Moderator
Posts: 12171
Joined: Sat May 08, 2004 12:44 pm
Location: USA

Re: Rebuild poller cache in windows

Post by BSOD2600 »

Was your 60 sec polling interval working before the upgrade or did you change that too? You can't simply change the poller time with out doing a lot more work, fyi. Looks like you need to change it back to the default of 5 min, since your scheduled task is set to that too atm.

Looks like the polling is taking longer than 60 seconds, which is also another possible problem.
petebc
Posts: 3
Joined: Thu Dec 16, 2010 4:37 pm

Re: Rebuild poller cache in windows

Post by petebc »

I wonder if I'm better wiping everything..stinks because it was still working even though it was graphing all the wrong ports on my routers/switches (everything has been moved around since this originally went in). But now it seems like I can't get it back on track after the upgrade to 8.7g or really get much else working... wondering if I'm better off wiping this thing and maybe setting up a linux box and fumbling through it there.. I never quite seem to get cacti working 100%..it's always 'sort of of doing something helpful' and in the end i'm back on some commercial thing to do basic ping and lite snmp monitoring..frustrating

Pete
Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests