TECHZEN Zenoss User Community ARCHIVE  

POSKeyError - Unable to Delete Device

Subject: POSKeyError - Unable to Delete Device
Author: [Not Specified]
Posted: 2015-03-29 23:12

Hi,
We have an issue with a device, but now unable to delete.
Have run zodbscan and comes up with 2 dangling references, for missing objects: macaddress and _lastPollSnmpUpTime
So run findposkeyerror but does not find or fix the error, also ran zenrelationscan & zencatalogscan which come up clean.
The error code get POSKeyError: 0x034d8b
How can I fix this
Chris.



Subject: POSKeyErrors happen,
Author: Andrew Kirch
Posted: 2015-03-31 13:58

POSKeyErrors happen, unfortunately. This is easily fixed though with the Zenoss Toolbox: https://github.com/zenoss/zenoss.toolbox

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard



Subject: Hello,
Author: [Not Specified]
Posted: 2015-04-02 07:50

Hello,

I have the same issue as Bartercardnz, the same error are present. I run all Zenoss Toolbox script and issue is stil present. Do you now samo other way to fix this error

Scripts that I started:

zodbscan
findposkeyerror -f
zenrelationscan -f
zencatalogscan -f
zenindextool -t Devices
zennetworkclean -f

zodbscan log:

--------------------------------------------------------------------------------------
2015-04-02 13:45:06,550 INFO zodbscan: Initializing zodbscan
2015-04-02 13:45:06,551 INFO zodbscan: Command line options: {'debug': True}
2015-04-02 13:45:06,551 DEBUG zodbscan: Acquired 'zenoss.toolbox' execution lock
2015-04-02 13:45:06,743 INFO zodbscan: Examining 796264 items in zodb database
2015-04-02 13:45:45,833 CRITICAL zodbscan: DANGLING REFERENCE (POSKeyError) FOUND:
PATH: zport/dmd/Devices/Network/xxxx/Cisco/Globalno/devices/yyyy
TYPE:
OID: 0x000b1738 '\x00\x00\x00\x00\x00\x0b\x178' 726840
Refers to a missing object:
NAME: _lastPollSnmpUpTime
TYPE:
OID: 0x000b173e '\x00\x00\x00\x00\x00\x0b\x17>' 726846
2015-04-02 13:45:45,835 CRITICAL zodbscan: DANGLING REFERENCE (POSKeyError) FOUND:
PATH: zport/dmd/Devices/Network/xxxx/Cisco/Globalno/devices/yyyy
TYPE:
OID: 0x000b1738 '\x00\x00\x00\x00\x00\x0b\x178' 726840
Refers to a missing object:
NAME: macaddresses
TYPE:
OID: 0x000b1a6a '\x00\x00\x00\x00\x00\x0b\x1aj' 727658
2015-04-02 13:48:29,707 INFO zodbscan: 2 Dangling References were detected
2015-04-02 13:48:29,708 INFO zodbscan: zodbscan completed in 203.16 seconds
--------------------------------------------------------------------------------------

Toliceli



Subject: You might want to take a look
Author: [Not Specified]
Posted: 2015-04-02 09:42

You might want to take a look at this thread: http://www.zenoss.org/forum/2601

I and a couple others had Poskey issues with these same exact fields _lastPollSnmpUpTime (type Products.ZenModel.ZenStatus.ZenStatus) and macaddresses (type BTrees.OOBTree.OOSet). The toolbox doesn't fix these. I had to do it "by hand" in the database.

I am pretty sure "zenossdbpack" is what causes these. I turned that off back in November haven't had a single PosKeyError since. I opened a ticket ZEN-15669 and was told it would be fixed in 5.0.1. (I think it should be fixed in 4.2.x if 4.2.x is still being supported but...)

Dave



Subject: Thanks, that solved my
Author: [Not Specified]
Posted: 2015-04-07 03:19

Thanks, that solved my problem.

Toliceli



< Previous
Zenoss Core 5 - What is the best practice to manage / run custom scripts in Core ...
  Next
Clearing Interface Data
>