Yes that does fix the problem but why does it happen? I have amended my script and now it looks like this:
firefox "http://localhost:8080/zport/dmd/DeviceLoader?deviceName=10.x.x.x&devicePath=/Network/Router&discoverProto=snmp&loadDevice:method=1"; ping -w 50000 10.0.0.0 I have also added a delay (via ping) so they don't get fired up all at once. When I do try to fire it all up at once I get the following error: Traceback (most recent call last): File "/opt/zenoss/Products/ZenModel/ZDeviceLoader.py", line 117, in loadDevice transaction.commit() File "/opt/zenoss/lib/python/transaction/_manager.py", line 84, in commit self.get().commit(sub) File "/opt/zenoss/lib/python/transaction/_transaction.py", line 381, in commit self._saveCommitishError() # This raises! File "/opt/zenoss/lib/python/transaction/_transaction.py", line 379, in commit self._commitResources() File "/opt/zenoss/lib/python/transaction/_transaction.py", line 424, in _commitResources rm.commit(self) File "/opt/zenoss/lib/python/ZODB/Connection.py", line 462, in commit self._commit(transaction) File "/opt/zenoss/lib/python/ZODB/Connection.py", line 495, in _commit raise ConflictError(object=obj) ConflictError: database conflict error (oid 0x100f, class Products.ZenModel.StatusMonitorConf.StatusMonitorConf) -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=13970#13970 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
