That is very strange. Is there anything special about the devices? For a while we had some issues with devices that responded from addresses other than their management IP address. Recently we found that modern Windows boxes had small (or no) buffers for SNMP packets... parallel requests were being dropped. Both of those should be fixed.

Send the strace results if you continue to have problems.

-Eric

Todd Michael Hebert wrote:
The command you gave caused the proper directories and RRD files to be created and hopefully they'll start populating. (So far there's no data for the network interfaces.)

So.. hopefully that's fixed.. although the reason it didn't create the files in the first place is a mystery to me.

Now..the only mystery I'm left with is that I keep getting messages from this device saying that SNMP is down.. but if you look at the monitor on the status page.. it says SNMP is up, and on the OS page.. it says SNMP is up.. but I keep getting events saying SNMP is down.

I just find it odd that there isn't any problem with collecting the data from the SNMP agent on the box..

The zenperfsnmp.log file just says that the SNMP agent is down on both devices, and that everything else was collected properly.

Todd M. Hebert


Eric Newton wrote:
These errors simply mean that the expected RRD files are not there... which we can infer from the lack of graphs.

How about log messages for zenperfsnmp?

What do you get when you run:

   $ zenperfsnmp run -v 10 -d 'suspicious device'

If you get timeout errors, send me the result of this:

$ strace -s 1000 -e trace=network zenperfsnmp run -v 10 -d 'suspicious device'

That will give me packets to decode.   Please send off-list.

-Eric


Todd Michael Hebert wrote:

I've had 2 devices that were previously monitored that just refuse to monitor properly now.

The services are monitored, but I keep getting messages about the SNMP service being down, even though I can collect the configuration.

I went as far as to delete the two from the system, delete the folders containing their perf information, and then re-add them in Zenoss.. but it still won't monitor the network activity. Nothing in the machine's configuration has changed as far as SNMP goes.

I'm able to snmpwalk the systems without any problems, from the box running Zenoss.

I'm getting these for errors in the log:

2006-08-14T15:52:34 ERROR Zope.SiteErrorLog http://admin.iil.ie:8080/zport/RenderServer/render
Traceback (most recent call last):
File "/usr/local/zenoss/lib/python/ZPublisher/Publish.py", line 114, in publish
    request, bind=1)
File "/usr/local/zenoss/lib/python/ZPublisher/mapply.py", line 88, in mapply
    if debug is not None: return debug(object,args,context)
File "/usr/local/zenoss/lib/python/ZPublisher/Publish.py", line 40, in call_object result=apply(object,args) # Type s<cr> to step into published object. File "/usr/local/zenoss/Products/ZenRRD/RenderServer.py", line 82, in render
    rrdtool.graph(*gopts)
error: opening '/usr/local/zenoss/perf/Devices/<servername>/os/interfaces/eth0/ifInOctets.rrd': No such file or directory
------
2006-08-14T15:52:34 ERROR RenderServer failed generating graph
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenRRD/RenderServer.py", line 82, in render
    rrdtool.graph(*gopts)
error: opening '/usr/local/zenoss/perf/Devices/<servername>/os/interfaces/eth0/ifInUcastPackets.rrd': No such file or directory
------
2006-08-14T15:52:34 WARNING RenderServer /tmp/renderserver/graph-279977be9456419fb553a58ba8a7fbe118000.png --start=1155548854 --end=1155566854 --img format=PNG -F -E --height=100 --width=500 --vertical-label=Pkts/sec DEF:ds0=/usr/local/zenoss/perf/Devices/<servername>/os/interfaces/eth0/ ifInUcastPackets.rrd:ds0:AVERAGE AREA:ds0#00cc00:ifInUcastPackets GPRINT:ds0:LAST:cur\:%0.2lf%s GPRINT:ds0:AVERAGE:avg\:%0.2lf%s GPRINT:ds0:MAX:max\ :%0.2lf%s\j DEF:ds1=/usr/local/zenoss/perf/Devices/<servername>/os/interfaces/eth0/ifOutUcastPackets.rrd:ds0:AVERAGE LINE1:ds1#0000ff:ifOut UcastPackets GPRINT:ds1:LAST:cur\:%0.2lf%s GPRINT:ds1:AVERAGE:avg\:%0.2lf%s GPRINT:ds1:MAX:max\:%0.2lf%s\j
------
2006-08-14T15:52:34 ERROR RenderServer failed generating graph
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenRRD/RenderServer.py", line 82, in render
    rrdtool.graph(*gopts)
error: opening '/usr/local/zenoss/perf/Devices/<servername>/os/interfaces/eth0/ifInErrors.rrd': No such file or directory
------
2006-08-14T15:52:34 WARNING RenderServer /tmp/renderserver/graph-bff1960d4d8c4a84a85236d8f73a7bc718000.png --start=1155548854 --end=1155566854 --img format=PNG -F -E --height=100 --width=500 --vertical-label=Errors/sec DEF:ds0=/usr/local/zenoss/perf/Devices/<servername>/os/interfaces/eth 0/ifInErrors.rrd:ds0:AVERAGE AREA:ds0#00cc00:ifInErrors GPRINT:ds0:LAST:cur\:%0.2lf%s GPRINT:ds0:AVERAGE:avg\:%0.2lf%s GPRINT:ds0:MAX:max\:%0.2lf%s\ j DEF:ds1=/usr/local/zenoss/perf/Devices/<servername>/os/interfaces/eth0/ifOutErrors.rrd:ds0:AVERAGE LINE1:ds1#0000ff:ifOutErrors GPRINT:ds 1:LAST:cur\:%0.2lf%s GPRINT:ds1:AVERAGE:avg\:%0.2lf%s GPRINT:ds1:MAX:max\:%0.2lf%s\j
------
2006-08-14T15:52:40 ERROR RenderServer failed generating summary
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenRRD/RenderServer.py", line 122, in currentValues
    values = rrdtool.graph(*gopts)[2]
error: opening '/usr/local/zenoss/perf/Devices/<servername>/sysUpTime.rrd': No such file or directory
------
2006-08-14T15:52:40 WARNING RenderServer /dev/null DEF:x0_r=/usr/local/zenoss/perf/Devices/<servername>/sysUpTime.rrd:ds0:AVERAGE VDEF:v0=x
0_r,LAST PRINT:v0:%.2lf --end=now --start=now-300
------
2006-08-14T15:52:40 ERROR zen.RRDView Unable to cache value for sysUpTime


Any ideas on how to track this down?
I am, as the Zenoss user, and the root user, able to create files on the filesystem.

Todd M. Hebert


_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to