Hello, Generally you have to wait until the next - I forget what it is called - "modelling cycle" ? "zenmodel period" ? Did your new devices start collecting data eventually? Check the daemon logs, something obvious might be wrong.
Look in Settings - Daemons and log for zenperfsnmp: http://myzenoss:8080/zport/About/viewDaemonLog?daemon=zenperfsnmp For immeduiate gratification (and for extra debug info if something is wrong) you can test any new devices on the command-line. e.g. for snmp: Code: $ zenperfsnmp run -v4 -d <devicename> I am much more familliar with debugging zencommands (as they go wrong much more often bercause I am creating them!) Play with zenperfsnmp and you will have lots of fun and get some info as well. Devicename has to be exactly the same as in zenoss. e.g. Code: [EMAIL PROTECTED]: ~ $ zenperfsnmp run -v5 -d balder DEBUG:zen.zenperfsnmp:run DEBUG:zen.zenperfsnmp:Connecting to localhost DEBUG:zen.zenperfsnmp:Logging in as admin WARNING:zen.zenperfsnmp:Reconnected to ZenHub DEBUG:zen.zenperfsnmp:setting up services EventService, SnmpPerfConfig DEBUG:zen.zenperfsnmp:chaining getInitialServices with d2 DEBUG:zen.zenperfsnmp:callback after getting service EventService DEBUG:zen.zenperfsnmp:callback after getting service SnmpPerfConfig DEBUG:zen.zenperfsnmp:Calling connected. DEBUG:zen.zenperfsnmp:connected DEBUG:zen.zenperfsnmp:Sending event {'severity': 0, 'component': 'zenperfsnmp', 'agent': 'zenperfsnmp', 'summary': 'started', 'manager': 'localhost', 'device': 'balder', 'eventClass': '/App/Start'} INFO:zen.zenperfsnmp:fetching property items DEBUG:zen.zenperfsnmp:Updated configCycleInterval config to 360 INFO:zen.zenperfsnmp:getting threshold classes DEBUG:zen.zenperfsnmp:Loading classes ['Products.ZenModel.MinMaxThreshold'] INFO:zen.zenperfsnmp:checking for outdated configs INFO:zen.zenperfsnmp:fetching configs for ['balder']... INFO:zen.zenperfsnmp:fetching default RRDCreateCommand INFO:zen.zenperfsnmp:fetching snmp status INFO:zen.zenperfsnmp:Initiating incremental device load DEBUG:zen.zenperfsnmp:Fetching configs for 1 devices DEBUG:zen.zenperfsnmp:Fetching config for ['balder'] DEBUG:zen.zenperfsnmp:getting device ping issues DEBUG:zen.zenperfsnmp:received config for balder DEBUG:zen.thresholds:Updating threshold ('CPU Utilization', ('balder', '')) DEBUG:zen.thresholds:Updating threshold ('Free Space 90 Percent', ('balder', '/db')) . . DEBUG:zen.thresholds:Updating threshold ('Utilization 75 perc', ('balder', 'ipge0')) DEBUG:zen.thresholds:Updating threshold ('Utilization 75 perc', ('balder', 'lo0')) DEBUG:zen.zenperfsnmp:Finished fetching configs for 1 devices DEBUG:zen.zenperfsnmp:Gathering performance data for balder INFO:zen.zenperfsnmp:Configured 1 of 1 devices DEBUG:zen.zenperfsnmp:unresponsive devices: [['slaine.ie.commprove.internal', 1, 7568], ['sengann', 1, 5097], ['fodbgen', 1, 5097]] INFO:zen.zenperfsnmp:Count 1 good 0 bad 0 time 0.000208 Cannot find module (IP-MIB): At line 0 in (none) ERROR:netsnmp:Cannot find module (IP-MIB): At line 0 in (none) . . DEBUG:zen.RRDUtil:/usr/local/zenoss/perf/Devices/balder/os/filesystems/var/usedBlocks_usedBlocks.rrd: 3314826 (GAUGE) DEBUG:zen.thresholds:Checking value 3314826 on Devices/balder/os/filesystems/var/usedBlocks_usedBlocks DEBUG:zen.MinMaxCheck:Checking usedBlocks_usedBlocks 3314826 against min None and max 5445883.8 . . DEBUG:zen.MinMaxCheck:Checking usedBlocks_usedBlocks 10835162 against min None and max 9984322.8 DEBUG:zen.zenperfsnmp:Sending event {'severity': 3, 'component': '/export/data', 'agent': 'zenperfsnmp', 'summary': 'balder /export/data threshold of Free Space 90 Percent exceeded: current value 10835162.00', 'manager': 'localhost', 'eventKey': '.1.3.6.1.2.1.25.2.3.1.6.30', 'device': 'balder', 'eventClass': '/Perf/Filesystem'} DEBUG:zen.RRDUtil:/usr/local/zenoss/perf/Devices/balder/os/filesystems/export_data/usedBlocks_usedBlocks.rrd: 0 (GAUGE) . . DEBUG:zen.RRDUtil:/usr/local/zenoss/perf/Devices/balder/memAvailReal_memAvailReal.rrd: 5049824 (GAUGE) DEBUG:zen.RRDUtil:/usr/local/zenoss/perf/Devices/balder/memAvailSwap_memAvailSwap.rrd: 2050456 (GAUGE) INFO:zen.zenperfsnmp:sent 44 OID requests INFO:zen.zenperfsnmp:collected 1 of 1 devices in 0.26 DEBUG:zen.zenperfsnmp:Sending event {'severity': 3, 'component': 'zenperfsnmp', 'agent': 'zenperfsnmp', 'summary': 'stopped', 'manager': 'localhost', 'device': 'balder', 'eventClass': '/App/Stop'} INFO:zen.zenperfsnmp:Count 1 good 1 bad 0 time 0.261645 DEBUG:zen.zenperfsnmp:removing service EventService DEBUG:zen.zenperfsnmp:removing service SnmpPerfConfig INFO:zen.zenperfsnmp:zenperfsnmp shutting down If I have problems with a COMMAND collector I can debug like this: Code: $ zencommand run -v10 -d <devicename> Where devicename is one of your new devices, -v10 for debug verbosity. e.g. here is one which causes a new rrd file to be created Code: DEBUG:zen.zencommand:rrd save result: 191.414962162 DEBUG:zen.zencommand:storing PROBE12_JFRate = 261.0 in: Devices/x.x.x.x/iubTGPROBE12_PROBE12_JFRate DEBUG:zen.RRDUtil:create new rrd /usr/local/zenoss/perf/Devices/x.x.x.x/iubTGPROBE12_PROBE12_JFRate.rrd or storing data: Code: DEBUG:zen.zencommand:Command: '/bin/sh -c exec /opt/zenoss/libexec/check_ntp -H 192.168.x.x' DEBUG:zen.zencommand:Output: 'NTP OK: Offset -9.399751434e-05 secs|offset=-9.399751434e-05\n' DEBUG:zen.zencommand:Process check_ntp -H 192.168.x.x stopped (0), 0.022398 elapsed DEBUG:zen.zencommand:The result of "/opt/zenoss/libexec/check_ntp -H 192.168.x.x" was "NTP OK: Offset -9.399751434e-05 secs|offset=-9.399751434e-05" DEBUG:zen.zencommand:storing offset = -9.399751434 in: Devices/192.168.x.x/check_ntp_offset DEBUG:zen.RRDUtil:/usr/local/zenoss/perf/Devices/192.168.x.x/check_ntp_offset.rrd: -9.3997514340000006 DEBUG:zen.zencommand:rrd save result: -9.399751434 Okay, good luck >;) James. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=22013#22013 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
