I have recently gone from 2.3 to 2.4 (and now 2.4.1). Once I made the jump from 2.3 to 2.4.x zenbatchloader only partially works. The device gets created, but when it comes to collecting the device via the dmd.Devices.collectDevice python call, the following is returned: <><><> [zen...@nmcdns191 zenoss]$ zenbatchload /tmp/test.txt INFO:zen.BatchDeviceLoader:Creating device x.x.x.x INFO:zen.Device:device name 'x.x.x.x' for ip 'x.x.x.x' INFO:zen.Device:setting performance monitor to localhost INFO:zen.DeviceLoader:Device x.x.x.x loaded! INFO:zen.Utils:Executing command: /opt/zenoss/bin/zenmodeler run --now --monitor localhost -F -d x.x.x.x INFO:zen.ZenModeler:Connecting to localhost:8789 INFO:zen.ZenModeler:Connected to ZenHub INFO:zen.ZenModeler:Collecting for device x.x.x.x INFO:zen.ZenModeler:Scan time: 0.00 seconds INFO:zen.ZenModeler:Daemon ZenModeler shutting down INFO:zen.ZenModeler:zenmodeler shutting down INFO:zen.PerformanceConf:configuration collected INFO:zen.BatchDeviceLoader:Processed 1 of 1 devices <><><> Notice that is does not believe that there are any plugins to collect.
Once zenbatchloader has finished processing, the device is created, and placed in the proper organization. If I then go into the Web UI and hit Model Device, the zenmodeler runs correctly. Has anyone else seen this or know how to fix it? Of course I got this to work in 2.4 by adding a commit() within BatchDeviceLoader.py but I neglected to mark the line down on where it needs to be. I also figured I would post this as it would appear to be some kind of bug Thanks. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=35326#35326 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
