Refresh of Data Query Section Went Haywire

[PitSpaniel]

Just did a refresh on the Data Query Section for SNMP Interface Statistics under new graphs for one of my hosts.

The description of the interfaces used to have plane language descriptions like "3Com Gigabit LOM - Packet Scheduler Miniport".

Now they are just jibberish. For example:
33:43:6F:6D:20:47:69:67:61:62:69:74:20:4C:4F:4D:20:28:33:43:39:34:30:29:20:2D:20:50:61:63:6B:65:74:20:53:63:68:65:64:75:6C:65:72:20:4D:69:6E:69:70:6F:72:74:00

No errors are listed in the logfile. Anyone know what gives?

I upgraded to 0.8.6h from 6g three days ago. Switched to MySQL 5.0. Things have been just fine until now.

[BSOD2600]

1) install the patches for 0.8.6h
2) you using php 5.1.1 per chance?
3) only that network interface messed up, or are all snmp queries?

[PitSpaniel]

Installed the patches. I am using PHP 5.1.1.

When you do a refresh all the network interface descriptions go haywire for that host. The other hosts are fine.

Things go back to normal if you take the host offline, wait until it shows a down status; then bring it back online. When the host is shown as recovering the interface descriptions are back to something readable.

[BSOD2600]

Well I know there are some issues with PHP 5.1.1 and SNMP... try 5.1.0 and see if you have the same results.

[PitSpaniel]

Same results with PHP 5.1.0. This isn't a big problem for me. Things go back to normal when a re-cache event is triggered for the affected host.

Thanks.

[PitSpaniel]

Also, FWIW, only the Windows XP hosts are affected. No others.

[BSOD2600]

Very odd. I'm monitoring a few WinXP Pro hosts and have never experienced this problem. Maybe you've got a problem with your database. Try running: mysqlcheck --auto-repair --databases cacti

[PitSpaniel]

Tried mysqlcheck. Everything OK.

Backed up and dropped original database installed a new empty one from cacti.sql file. When XP hosts are added I instantly get the same jibberish in the description. Once again, after a recache event, things are back to normal.

Intersting finding: If I take the jibberish and use it as an index for ifDescr, It works just as well as the plain language description. The jibberish is starting to look like some sort of HEX code.

I used MySQL 5.0.16 with installer. When I get time, I'll try MySql 5.0.18 without the installer to see if it makes a difference.

[BSOD2600]

Weirdness. A dev is going to have to take a look what is wrong.