Hi Chet, Sorry I didn't get back to you sooner about this.
The supplied pach didn't solve the problem: [EMAIL PROTECTED]:~$ zenmodeler run -v 1 --debug --device device01.vestas.net 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 device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.ifconfig on device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.swap on device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.memory on device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.memory on device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.cpu on device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.process on device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.ifconfig on device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.netstat_rn on device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.cmd.darwin.netstat_an on device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.netstat_an on device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.cmd.linux.process on device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.cmd.df on device01.vestas.net DEBUG:zen.ZenModeler:skipping zenoss.cmd.uname for device01.vestas.net INFO:zen.ZenModeler:no cmd plugins found for device01.vestas.net DEBUG:zen.ZenModeler:using zenoss.snmp.CiscoHSRP on device01.vestas.net DEBUG:zen.ZenModeler:skipping zenoss.snmp.IpServiceMap for device01.vestas.net DEBUG:zen.ZenModeler:skipping zenoss.snmp.InformantHardDiskMap for device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.snmp.SysedgeMap on device01.vestas.net DEBUG:zen.ZenModeler:using zenoss.snmp.CiscoMap on device01.vestas.net DEBUG:zen.ZenModeler:using zenoss.snmp.DeviceMap on device01.vestas.net DEBUG:zen.ZenModeler:using zenoss.snmp.InterfaceMap on device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.snmp.NewDeviceMap on device01.vestas.net DEBUG:zen.ZenModeler:condition failed zenoss.snmp.SysedgeFileSystemMap on device01.vestas.net DEBUG:zen.ZenModeler:using zenoss.snmp.NewRouteMap on device01.vestas.net DEBUG:zen.ZenModeler:skipping zenoss.snmp.HRSWRunMap for device01.vestas.net DEBUG:zen.ZenModeler:skipping zenoss.snmp.InterfaceAliasMap for device01.vestas.net 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 device01.vestas.net INFO:zen.ZenModeler:plugins: zenoss.snmp.CiscoHSRP, zenoss.snmp.CiscoMap, zenoss.snmp.DeviceMap, zenoss.snmp.InterfaceMap, zenoss.snmp.RouteMap, zenoss.snmp.NewRouteMap DEBUG:zen.SnmpClient:Starting SNMP info for device01.vestas.net at 10.20.5.2:161 timeout: 2.5 tries: 2 version: v1 community: uspdxsnmp DEBUG:zen.SnmpClient:Testing SNMP configuration DEBUG:zen.ZenModeler:skipping zenoss.portscan.IpServiceMap for device01.vestas.net INFO:zen.ZenModeler:no portscan plugins found for device01.vestas.net DEBUG:zen.SnmpClient:lastpolluptime = 236668370 DEBUG:zen.SnmpClient:lastchange = 236682512 INFO:zen.SnmpClient:snmp client finished collection for device01.vestas.net DEBUG:zen.ZenModeler:client for device01.vestas.net finished collecting DEBUG:zen.ApplyDataMap:processing data for device device01.vestas.net INFO:zen.ApplyDataMap:no change detected INFO:zen.ZenModeler:scan time: 0.36 seconds INFO:zen.ZenModeler:stopping... > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Chet Luther > Sent: Wednesday, 05 December, 2007 9:23 > To: General discussion of using zenoss system > Subject: Re: [zenoss-users] Modeling devices automagically? > > > I can reliably reproduce a bug where, even after verifying that the > > "ccmHistoryRunningLastChanged" OID has been updated, the > device isn't > > fully remodeled: > > > > [EMAIL PROTECTED]:~$ zenmodeler run --debug --device > uspdxvg01.vestas.net > > INFO:zen.ZenModeler:starting collector loop > > INFO:zen.ZenModeler:collecting for device uspdxvg01.vestas.net > > INFO:zen.ZenModeler:no cmd plugins found for uspdxvg01.vestas.net > > INFO:zen.ZenModeler:snmp collection device uspdxvg01.vestas.net > > INFO:zen.ZenModeler:plugins: zenoss.snmp.CiscoHSRP, > > zenoss.snmp.CiscoMap, zenoss.snmp.DeviceMap, > zenoss.snmp.InterfaceMap, > > zenoss.snmp.RouteMap > > INFO:zen.ZenModeler:no portscan plugins found for > uspdxvg01.vestas.net > > lastpolluptime = 134937116 > > lastchange = 134965132 > > INFO:zen.SnmpClient:snmp client finished collection for > > uspdxvg01.vestas.net > > INFO:zen.ApplyDataMap:no change detected > > INFO:zen.ZenModeler:scan time: 0.42 seconds > > INFO:zen.ZenModeler:stopping... > > > > note "lastpolluptime" and "lastchange" are different, yet I > have to > > use > > the -F flag in order for the modeler to update the device. > > Thanks for the report. This is definitely wrong. I've created > a ticket > for this issue, and notated it with a patch that may fix it. > Could you > please test this out and let me know if it does indeed work > correctly > with this change? > > Ticket: http://dev.zenoss.org/trac/ticket/2436 > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users > _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
