Another WARNING: Result from SNMP not valid. Partial Result

Post general support questions here that do not specifically fall into the Linux or Windows categories.

Moderators: Developers, Moderators

Post Reply
scorgatelli
Posts: 2
Joined: Wed Apr 29, 2009 4:48 pm

Another WARNING: Result from SNMP not valid. Partial Result

Post by scorgatelli »

I know this has been posted about a lot. I've went through most of these posts and the NaN debugging guide but have not been able to solve my problem.

I'm using the following custom SNMP Data query:

Code: Select all

<?xml version="1.0"?>
<interface>
  <name>Get SNMP Exec Status</name>
  <description>Queries a host for a list of commands executed by the
  snmpd daemon using the exec command. Monitors the exit code of these
  processes.</description>
  <oid_index>.1.3.6.1.4.1.2021.8.1.1</oid_index>
  <index_order>extNames:extIndex</index_order>
  <index_order_type>numeric</index_order_type>
  <index_title_format>|chosen_order_field|</index_title_format>
  
  <fields>
    <extIndex>
      <name>Index</name>
      <method>walk</method>
      <source>value</source>
      <direction>input</direction>
      <oid>.1.3.6.1.4.1.2021.8.1.1</oid>
    </extIndex>
    <extNames>
      <name>Name</name>
      <method>walk</method>
      <source>value</source>
      <direction>input</direction>
      <oid>.1.3.6.1.4.1.2021.8.1.2</oid>
    </extNames>
    <extCommand>
      <name>Command</name>
      <method>walk</method>
      <source>value</source>
      <direction>input</direction>
      <oid>.1.3.6.1.4.1.2021.8.1.3</oid>
    </extCommand>
    <extResult>
      <name>Result</name>
      <method>walk</method>
      <source>value</source>
      <direction>output</direction>
      <oid>.1.3.6.1.4.1.2021.8.1.100</oid>
    </extResult>
    <extOutput>
      <name>Output</name>
      <method>walk</method>
      <source>value</source>
      <direction>input</direction>
      <oid>.1.3.6.1.4.1.2021.8.1.101</oid>
    </extOutput>
  </fields>
</interface>
I'm using this for two different servers. It works for one and partially works for the other. I think it may be a time out issue. This is what I get in my log for the problem data source:

Code: Select all

04/29/2009 03:55:39 PM - CMDPHP: Poller[0] Host[5] DS[259] WARNING: Result from 
SNMP not valid.  Partial Result: 
04/29/2009 03:55:39 PM - CMDPHP: Poller[0] Host[5] DS[259] SNMP: v1: xxxxx, dsname: extResult, oid: .1.3.6.1.4.1.2021.8.1.100.1, output: U
04/29/2009 03:55:39 PM - CMDPHP: Poller[0] DEBUG: SQL Exec: "insert into poller_
output (local_data_id, rrd_name, time, output) values (259, 'extResult', '2009-0
4-29 15:55:03', 'U')"
snmpget:

Code: Select all

snmpget -v1 -c xxxx xxxxx .1.3.6.1.4.1.2021.8.1.100.1
UCD-SNMP-MIB::extResult.1 = INTEGER: 1
The three rrd files related to this query all show the following from info:

Code: Select all

ds[extResult].type = "GAUGE"
ds[extResult].minimal_heartbeat = 600
ds[extResult].min = 0.0000000000e+00
ds[extResult].max = NaN
Cacti Info:
Cacti Version 0.8.7b
Cacti OS unix
SNMP Version net-snmp
RRDTool Version RRDTool 1.2.x
Interval 300
Type cmd.php
Items Action[0]: 51
Action[1]: 58
Total: 109
Concurrent Processes 3
Max Threads 1
PHP Servers 1
Script Timeout 25
Max OID 10
Last Run Statistics Time:40.1494 Method:cmd.php Processes:3 Threads:N/A Hosts:4 HostsPerProcess:2 DataSources:109 RRDsProcessed:86

Does anyone have any ideas on how to fix this?

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

Post by gandalf »

This looks like an snmp exec script. If my assumption is correct, please pay attention to the runtime of that script
Reinhard
scorgatelli
Posts: 2
Joined: Wed Apr 29, 2009 4:48 pm

[SOLVED] Result from SNMP not valid. Partial Result

Post by scorgatelli »

You're correct. It is an snmp exec script.

Basically this is the result of me being dumb. :) One of the first things I did was increase the SNMP Timeout value in the cacti settings, but I forgot that it doesn't affect existing devices. I've increased the timeout in the device settings and now everything is working fine.

Thanks
Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests