Ad blocker detected: Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker on our website.
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 ?
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...
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??
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