[solved] Spine errors

[colson]

Running:
Windows Server 2003 SP2
Cacti-0.8.7d
Spine-0.8.7c
PHP - 5.2.9-2
MYSQL - 5.1.33
RRDTOOL - 1.2.30

Followed the installation instructions and things seem to be working except for the poller. The scheduled task kicks off, but the PHP process seems to time out and there aren't any clues in the log file -

04/10/2009 05:18:00 PM - POLLER: Poller[0] NOTE: Poller Int: '300', Scheduled Task Int: '300', Time Since Last: '600', Max Runtime '298', Poller Runs: '1'
04/10/2009 05:18:00 PM - POLLER: Poller[0] WARNING: Scheduled Task is out of sync with the Poller Interval! The Poller Interval is '300' seconds, with a maximum of a '300' second Scheduled Task, but 600 seconds have passed since the last poll!
04/10/2009 05:18:00 PM - POLLER: Poller[0] DEBUG: About to Spawn a Remote Process [CMD: C:/spine/spine.exe, ARGS: 0 2]

I tried to run SPINE manually and I get the following error:
SPINE: Using spine config file [spine.conf]
MYSQL: Connection Failed: Error:'2002', Message:'Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)'
04/10/2009 05:28:41 PM - SPINE: Poller[0] FATAL: Connection Failed, Error:'2002', Message:'Can't connect to local MySQL server through socket '/tmp/mysql.sock'(2)' (Spine init)

I did compile Spine in Cygwin, but it seemed to complete just fine. Currently SNMP appears to be working but no RRD files are being created which I'm assuming is related to the Spine issue. Not sure where to go from here and any assistance would be great.

Thanks.

[BSOD2600]

1) I suggest you use the pre-compiled Spine -- but it (0.8.7c) also has known issues with timouts, snmpv3 and scripts. There is a pre-release in the announcement forum which fixes some of that.

2) Looks like you don't have the correct information in spine.conf.

3) I suggest one starts out with the cmd.php poller and gets everything functional. THEN switch over to spine.

[colson]

Tried with the newest Spine binaries and still have the same issue. My spine.conf settings are correct and the values match those in the config.php file. I did switch back to the command poller (cmd.php) and everything appears to be happy.

Just to clarify, I copied spine.exe and spine.conf to c:\spine and then updated the variables in the conf file. Running a command like:

C:\spine>spine.exe -C spine.conf --stdout -V 3

results in the following error message:

SPINE: Using spine config file [spine.conf]
MYSQL: Connection Failed: Error:'2002', Message:'Can't connect to local MySQL se
rver through socket '/tmp/mysql.sock' (2)'
MYSQL: Connection Failed: Error:'2002', Message:'Can't connect to local MySQL se
rver through socket '/tmp/mysql.sock' (2)'
MYSQL: Connection Failed: Error:'2002', Message:'Can't connect to local MySQL se
rver through socket '/tmp/mysql.sock' (2)'
MYSQL: Connection Failed: Error:'2002', Message:'Can't connect to local MySQL se
rver through socket '/tmp/mysql.sock' (2)'
MYSQL: Connection Failed: Error:'2002', Message:'Can't connect to local MySQL se
rver through socket '/tmp/mysql.sock' (2)'
04/14/2009 11:16:37 AM - SPINE: Poller[0] FATAL: Connection Failed, Error:'2002'
, Message:'Can't connect to local MySQL server through socket '/tmp/mysql.sock'
(2)' (Spine init)

Thanks in advance for the assistance.

[colson]

Just as a point of fact, it appears that Spine is attempting to connect to the MySQL db via a UNIX socket, but I'm running everything on Windows and MySQL is configured to use TCP port 3306 and I don't have named-pipes enabled. Is there a way to override this (thought that MySQL config would take precedence) or is Spine compiled with a particular MySQL connection option?

[erwan.l]

Hi Colson,
You probably checked it out already but make sure :
DB_Host 127.0.0.1
and not
DB_Host localhost

I spent sometime to figure out that I sould read the comments in the conf file...

Regards,
Erwan.

[colson]

THANKS!!!!

yeah missed that comment "IP Address for Windows"

I have to remember to RTFM.

Thanks again.

[henrycao]

THANKS!!!!

yeah missed that comment "IP Address for Windows"

I have to remember to RTFM.

Thanks again.

Thanks the forum, I've made the same mistake