Archived community.zenoss.org | full text search
Skip navigation
176 Views 1 Reply Latest reply: Feb 24, 2014 5:35 PM by Justin Simmons RSS
Justin Simmons Rank: White Belt 19 posts since
Sep 26, 2012
Currently Being Moderated

Feb 24, 2014 5:33 PM

FindPosKeyError script issue

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. 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!

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points