any ideas? polling problem

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

Moderators: Developers, Moderators

Post Reply
BIGHard
Cacti User
Posts: 66
Joined: Mon May 28, 2007 7:32 pm

any ideas? polling problem

Post by BIGHard »

Code: Select all

06/09/2008 01:52:27 PM - CACTID: Poller[0] Host[1048] DS[14387] SNMP: v2: (.. not important ..), dsname: snmp_oid, oid: .1.3.6.1.4.1.2021.8.1.100, value: U
06/09/2008 01:52:27 PM - CACTID: Poller[0] Host[1048] DS[14392] SNMP: v2: (.. not important ..), dsname: mem_cache, oid: .1.3.6.1.4.1.2021.4.15.0, value: 370424

Code: Select all

[root ]# snmpwalk (.. not important ..) .1.3.6.1.4.1.2021.8.1.100
UCD-SNMP-MIB::extResult.1 = INTEGER: 72
[root ]# snmpwalk (.. not important ..) .1.3.6.1.4.1.2021.4.15.0
UCD-SNMP-MIB::memCached.0 = INTEGER: 370448
so - snmp polilng a host works like a charm, the values are returned, the oid is correct, but cacti said - U (nknown value) - why? what to check?
dus001
Posts: 42
Joined: Sun Aug 07, 2005 6:07 am

Re: any ideas? polling problem

Post by dus001 »

Are the not important parts from the log exactly the same as the ones from the test commands ?
Have the test commands have been executed on the very same host cacti's poller is running on ?
BIGHard
Cacti User
Posts: 66
Joined: Mon May 28, 2007 7:32 pm

Post by BIGHard »

d'oh - of course!
BIGHard
Cacti User
Posts: 66
Joined: Mon May 28, 2007 7:32 pm

Post by BIGHard »

any ideas? Reinhard?
dus001
Posts: 42
Joined: Sun Aug 07, 2005 6:07 am

Post by dus001 »

Maybe you could try using snmp V1 ? There has been some threads here about V2, if i remember correctly.
BIGHard
Cacti User
Posts: 66
Joined: Mon May 28, 2007 7:32 pm

Post by BIGHard »

dus do you mind posting constructive replies? im using cacti for a long time and 'm really able to solve problems myself - but i've just stumbled on something strange, and working against any logical explanation...

once more - Reinhard?
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Post by gandalf »

Please do not snmpwalk against .1.3.6.1.4.1.2021.8.1.100 but snmpget against .1.3.6.1.4.1.2021.8.1.100.1
Reinhard
BIGHard
Cacti User
Posts: 66
Joined: Mon May 28, 2007 7:32 pm

Post by BIGHard »

Guys! i'm beggining to think, you're not reading and understanding what my problem is! i'm running proper snmp queries, from the same host, to the same host, with the same credentials. it's not a matter of snmpwalk/snmpget - as a matter of fact, for a single oid, they work the same.

the problem is:

why the fsck can i poll both variables by hand, and cacti can poll one, and cannot the other??
BIGHard
Cacti User
Posts: 66
Joined: Mon May 28, 2007 7:32 pm

Post by BIGHard »

so?
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Post by gandalf »

gandalf wrote:Please do not snmpwalk against .1.3.6.1.4.1.2021.8.1.100 but snmpget against .1.3.6.1.4.1.2021.8.1.100.1
Reinhard
I have to re-phrase: Please make cacti NOT poll .1.3.6.1.4.1.2021.8.1.100 but make it poll .1.3.6.1.4.1.2021.8.1.100.1
Your example from above shows, that the target is responding to .1.3.6.1.4.1.2021.8.1.100.1 and NOT to .1.3.6.1.4.1.2021.8.1.100
Reinhard
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest