POLLER Maximum runtime -error

[_raindrop18]

I have this error every 2-4 hours apart.
POLLER: Poller[0] Maximum runtime of 298 seconds exceeded. Exiting.

this poroblem solely related to spine (on all version) I don't have this issue when cmd.php selected as poller.

I have change my concurrent process, thread parameter, script server and so on different numbers but the problem not go way on any of them.

cacti running on Solaris 10 Zone. I have the same version of cacti and spine on stand alone server, I don't have this issue. my question is anybody use or test spine on solaris Zone env ? or on any other virtual server?

my crontab looks like this

0,5,10,15,20,25,30,35,40,45,50,55 * * * * /opt/cacti/local/php5/bin/php -q /opt/cacti/local/cacti/poller.php --force > /dev/null 2>&1


Thanks.

[kmhendress]

Here are the differences I seen on a RedHat VM box:

07/22/2009 03:05:12 PM - SYSTEM STATS: Time:298.4995 Method:cmd.php Processes:30 Threads:N/A Hosts:18 HostsPerProcess:1 DataSources:5731 RRDsProcessed:2238

07/28/2009 09:20:57 AM - SYSTEM STATS: Time:54.9774 Method:spine Processes:20 Threads:5 Hosts:18 HostsPerProcess:1 DataSources:6184 RRDsProcessed:3439

[_raindrop18]

Thank for your response, the only reason looking spine the expedite the process. cmd.php slow but not close like you may takes between 50-60 seconds and spine only takes 10 second.
I have also noticed also you have 20 process running ( lucky you) I have issue with that when ever put above 2 process at the time I got error for duplicate mysql entry. so 2 process the max I can do even though server has dedicated 4 processor. and 64 gb memory. the cpu usage on my box almost 5% it's very powerful server. however Spine doesn't like it.

[kmhendress]

Is your mysql setup to limit the number of connections or something? I am allowing I believe 250 connections into mysql. I've got 2 CPU's on the box and 2 Gig of Ram, its a VM instance even.

[_raindrop18]

thanks for your response,I did allow 350 connection on mysql.cnf. i think the bottom line is something with spine and virtual server. this is my 4th cacti installation but the first installation on virtual server. I didn't get such issue on my previous 3 installation. as I said actually I did install simultaneously on my old stand alone Solaris box with same apache,php,mysql,cacti and spine version. well no problem on standalone server specially related to time out. I have same issue only when the concurrent processor gone above 3 have duplicate sql entry.but that not a problem since spine doesn't care much about concurrent processor more about thread parameter. time out is a big problem because my graph has a gap because of time out.