cactid skipping *some* data sources

Post support questions that directly relate to Linux/Unix operating systems.

Moderators: Developers, Moderators

Post Reply
entr0py
Posts: 10
Joined: Wed Oct 19, 2005 3:33 am
Location: Sydney
Contact:

cactid skipping *some* data sources

Post by entr0py »

Hi,

CACTI: Version 0.8.6h
CACTID: Version 0.8.6f

Install has been running fine for about a year, this includes earlier versions of cacti and cactid and a migration from one server to another. Anyway, what seems to be happening is that cactid as compared to cmd.php is skipping certain data sources/metrics specifcally the ones for mysql and latency.

This is not a case of cactid skipping scripts and only getting data from snmp...clearly something has changed I am just having a hard time figuring out what and where.

Have checked for hung processes - none found.

mysql graphs: http://forums.cacti.net/about6108.html&highlight=
latency graphs: http://forums.cacti.net/about10049.html

The exact output from cactid is as follows: (note that increasing or decreasing the timeout makes no difference and that snmp is available and working for all other metrics such as cpu/net/disk/bind etc.)

[/usr/local/cactid]# ./cactid -R --verbosity=DEBUG
CACTID: Using cactid config file [cactid.conf]
CACTID: Version 0.8.6f starting
CACTID: Host[3] DS[38] WARNING: Result from SNMP not valid. Partial Result: ...
CACTID: Host[3] DS[39] WARNING: SNMP timeout detected [500 ms], ignoring host 'web1.switchnetworks.com.au'
CACTID: Host[3] DS[40] WARNING: SNMP timeout detected [500 ms], ignoring host 'web1.switchnetworks.com.au'
CACTID: Host[3] DS[41] WARNING: SNMP timeout detected [500 ms], ignoring host 'web1.switchnetworks.com.au'
CACTID: Host[3] DS[42] WARNING: SNMP timeout detected [500 ms], ignoring host 'web1.switchnetworks.com.au'
CACTID: Host[3] DS[43] WARNING: SNMP timeout detected [500 ms], ignoring host 'web1.switchnetworks.com.au'
CACTID: Host[3] DS[38] WARNING: SNMP timeout detected [500 ms], ignoring host 'web1.switchnetworks.com.au'
CACTID: Host[3] DS[39] WARNING: SNMP timeout detected [500 ms], ignoring host 'web1.switchnetworks.com.au'
CACTID: Host[3] DS[40] WARNING: SNMP timeout detected [500 ms], ignoring host 'web1.switchnetworks.com.au'
CACTID: Host[3] DS[41] WARNING: SNMP timeout detected [500 ms], ignoring host 'web1.switchnetworks.com.au'
CACTID: Host[3] DS[42] WARNING: SNMP timeout detected [500 ms], ignoring host 'web1.switchnetworks.com.au'
CACTID: Host[3] DS[43] WARNING: SNMP timeout detected [500 ms], ignoring host 'web1.switchnetworks.com.au'
phrawzty
Posts: 12
Joined: Fri Apr 21, 2006 3:01 pm
Location: Montreal, Canada

Post by phrawzty »

It would seem that adjusting the timeout value in the cacti web interface doesn't actaully do anything. :P

You can adjust the timeout value manually in the MySQL database. Check the bottom of this thread for details:
http://forums.cacti.net/viewtopic.php?t=12869
entr0py
Posts: 10
Joined: Wed Oct 19, 2005 3:33 am
Location: Sydney
Contact:

Post by entr0py »

thanks for the info phrawzty but the update to the timeout did not change anything. if found an issue with one of the snmp oids i am trying to get information from - in that the oid is 'invalid' though I have no idea as yet as to why it is causing it to skip unrelated graphs.

the failed objects/oids below simply return no values which shouldn't be an issue since this 'should' result in a :U values.

Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.8767.2.1.3.1.4.3

Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.8767.2.1.3.1.5.4

Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.8767.2.1.3.1.4.4

Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.8767.2.1.3.1.5.5

Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.8767.2.1.3.1.4.5

Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.8767.2.1.3.1.5.6

Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.8767.2.1.3.1.4.6
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Post by gandalf »

Please try snmpwalk against those failing OIDs from command line to verify, that the target is correctly responding to those
Reinhard
Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests