![]() |
![]() |
Subject: | Error Removing Devices |
Author: | [Not Specified] |
Posted: | 2014-05-14 07:19 |
Hey,
I am getting the following error in the event log when I try to remove a few devices from Zenoss:
2014-05-14T07:59:44 INFO extdirect Direct request failed: 'BAD_ABC': DeviceRouter.removeDevices [{'uids': ['BAD_ABC'], 'deletePerf': True, 'hashcheck': 1, 'deleteEvents': True, 'action': 'delete', 'uid': '/zport/dmd/Groups'}]
------
2014-05-14T07:59:44 INFO extdirect DirectRouter suppressed the following exception (Response e12c5161-60eb-4a13-af8a-48fd22ffa6bd):
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenUtils/extdirect/router.py", line 179, in _processDirectRequest
response.result = _targetfn(**data)
File "/opt/zenoss/Products/Zuul/routers/device.py", line 1092, in removeDevices
uids = filterUidsByPermission(self.context.dmd, ZEN_DELETE_DEVICE, uids)
File "/opt/zenoss/Products/Zuul/__init__.py", line 195, in filterUidsByPermission
obj = dmd.unrestrictedTraverse(uid)
File "/opt/zenoss/lib/python/OFS/Traversable.py", line 299, in unrestrictedTraverse
raise e
KeyError: 'BAD_ABC'
I have run every integrity tool and check I could get my hands on, but I can't get rid of it or fix it.
Any ideas on how I might be able to rid myself of this device
Thanks,
Chris
Subject: | Take a look at these wiki |
Author: | [Not Specified] |
Posted: | 2014-05-14 11:07 |
Take a look at these wiki articles:
http://wiki.zenoss.org/Fixing_ZODB_Integrity_Issues
http://wiki.zenoss.org/Repairing_Poskey_Errors
Hydruid
Subject: | Hey, |
Author: | [Not Specified] |
Posted: | 2014-05-14 14:15 |
Hey,
Thanks for getting back to me.
The first zopedb scan errors out that it can't find the device. I'm not sure what ID I should search for. Everything I plug in returns the same result.
The second returns this exception:
INFO:zen.CheckRelations:Checking relations...
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenUtils/CheckRelations.py", line 70, in
tmbk.rebuild()
File "/opt/zenoss/Products/ZenUtils/CheckRelations.py", line 38, in rebuild
object.checkRelations(repair=repair)
File "/opt/zenoss/Products/ZenRelations/RelationshipManager.py", line 257, in checkRelations
rel.checkRelation(repair)
File "/opt/zenoss/Products/ZenRelations/ToManyContRelationship.py", line 319, in checkRelation
rrel = getattr(obj, remoteName)
AttributeError: 'HttpMonitorDataSource' object has no attribute 'rrdTemplate'
The zenoss-repairdevice script looks like it ran through every device except the broken ones.
The FindPosKeyError script throws a bunch of KeyErrors on the devices with issues, but with the --fixrels flag, it doesn't seem to fix them.
Something really odd happened to this database.
Are there any other ways I can get rid of this broken data
Thanks,
Chris
Subject: | A little more investigation, |
Author: | [Not Specified] |
Posted: | 2014-05-14 14:27 |
A little more investigation, the FindPosKeyError script fails to do anything because it fails the isinstance() check before the repair call.
Thanks,
Chris
< |
Previous Trigger/Notification Contents Help |
Next Send Events using a REST call |
> |