Justin Simmons
2014-02-24 22:33:29 UTC
Justin Simmons [http://community.zenoss.org/people/jmsimmons] created the discussion
"FindPosKeyError script issue"
To view the discussion, visit: http://community.zenoss.org/message/75692#75692
--------------------------------------------------------------
Over the last couple weeks, I've had a number of devices coming up with POSKeyError messages. I discovered the "FindPosKeyError.py" script that was available on http://wiki.zenoss.org/PosKey_Error_Fixture http://wiki.zenoss.org/PosKey_Error_Fixture. I'd like to say for the record that this script works about 99% of the way, and that I was highly impressed! It cleared up a number of my errors, however, it doesn't appear to clear up problems with "componentSearch". When running "python ./FindPosKeyerror.py --fixrels /zport/dmd/Devices", about 16 odevices come up with a "POSKeyError:Â 0x###### on attribute 'componentSearch' of app.zport.dmd.Devices.<+remainder of path>".+
Would someone have a solution for me to clear up the remaining POSKeyError's I'm receiving? I'd hate to rebuild/restore for 16 devices that are causing me grief!+
+
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/75692#75692]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"FindPosKeyError script issue"
To view the discussion, visit: http://community.zenoss.org/message/75692#75692
--------------------------------------------------------------
Over the last couple weeks, I've had a number of devices coming up with POSKeyError messages. I discovered the "FindPosKeyError.py" script that was available on http://wiki.zenoss.org/PosKey_Error_Fixture http://wiki.zenoss.org/PosKey_Error_Fixture. I'd like to say for the record that this script works about 99% of the way, and that I was highly impressed! It cleared up a number of my errors, however, it doesn't appear to clear up problems with "componentSearch". When running "python ./FindPosKeyerror.py --fixrels /zport/dmd/Devices", about 16 odevices come up with a "POSKeyError:Â 0x###### on attribute 'componentSearch' of app.zport.dmd.Devices.<+remainder of path>".+
Would someone have a solution for me to clear up the remaining POSKeyError's I'm receiving? I'd hate to rebuild/restore for 16 devices that are causing me grief!+
+
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/75692#75692]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]