"Ladies and gentlemen: the story you are about to hear is true. Only the names have been changed to protect the innocent."
I have just installed version 2.1.0 and am trying to add a Cisco 7206. ZenModeler is timing out after 180 seconds and not populating any info for the device or the interfaces on it. Here is the output from: Code: zenmodeler run -v10 -d XXXX.XXXXXX.XXXX.XXX Here is the responce: Code: DEBUG:zen.ZenModeler:Run in foreground, starting immediately. DEBUG:zen.ZenModeler:in debug mode starting apply in main thread. INFO:zen.ZenModeler:starting collector loop INFO:zen.ZenModeler:collecting for device XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.ifconfig on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.swap on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.memory on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.memory on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.cpu on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.process on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.ifconfig on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.netstat_rn on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.netstat_an on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.netstat_an on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.process on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.cmd.df on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.cmd.uname for XXXX.XXXXXX.XXXX.XXX INFO:zen.ZenModeler:no cmd plugins found for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.snmp.CiscoHSRP on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.IpServiceMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.InformantHardDiskMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.snmp.SysedgeMap on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.snmp.CiscoMap on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:using zenoss.snmp.DeviceMap on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:using zenoss.snmp.InterfaceMap on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:using zenoss.snmp.NewDeviceMap on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.HPDeviceMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.snmp.PowerwareDeviceMap on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.snmp.APCDeviceMap on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.UCDHardDiskMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:condition failed zenoss.snmp.SysedgeDiskMap on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.DellCPUMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.HRFileSystemMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.CpuMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.HPCPUMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.DellPCIMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.DellDeviceMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:using zenoss.snmp.RouteMap on XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.HRSWInstalledMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.NewRouteMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.HRSWRunMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.ZenModeler:skipping zenoss.snmp.InterfaceAliasMap for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.DbConnectionPool:Creating a new connection; Pool size: 0 DEBUG:zen.DbConnectionPool:Returned a connection; Pool size: 1 INFO:zen.ZenModeler:snmp collection device XXXX.XXXXXX.XXXX.XXX INFO:zen.ZenModeler:plugins: zenoss.snmp.DeviceMap, zenoss.snmp.InterfaceMap, zenoss.snmp.NewDeviceMap, zenoss.snmp.RouteMap DEBUG:zen.SnmpClient:timeout=1193795578.35, tries=2 DEBUG:zen.SnmpClient:Testing SNMP configuration DEBUG:zen.ZenModeler:skipping zenoss.portscan.IpServiceMap for XXXX.XXXXXX.XXXX.XXX INFO:zen.ZenModeler:no portscan plugins found for XXXX.XXXXXX.XXXX.XXX DEBUG:zen.SnmpClient:running <zenoss.snmp.DeviceMap.DeviceMap instance at 0x8afc32c> DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.DeviceMap DEBUG:zen.SnmpClient:running <zenoss.snmp.InterfaceMap.InterfaceMap instance at 0x8ae2b8c> DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.InterfaceMap DEBUG:zen.SnmpClient:running <zenoss.snmp.NewDeviceMap.NewDeviceMap instance at 0x86a75cc> DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.NewDeviceMap DEBUG:zen.SnmpClient:running <zenoss.snmp.RouteMap.RouteMap instance at 0x8afc22c> DEBUG:zen.SnmpClient:sending queries for plugin zenoss.snmp.RouteMap WARNING:zen.ZenModeler:client XXXX.XXXXXX.XXXX.XXX timeout INFO:zen.ZenModeler:scan time: 180.46 seconds INFO:zen.ZenModeler:stopping... I see that there is a bug that involves some of the Dell and HP Maps. Is this issue related? Is there something that I can do on my end to get this fixed? -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=12507#12507 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
