|
|
| Subject: | Corrupt zodb - tools cannot fix it |
| Author: | [Not Specified] |
| Posted: | 2015-09-22 05:25 |
After a disk-full event, the ZODB has become corrupt (POSKeyError) and I can't fix it with the zenoss-toolkit
findposkeyerror -f and zenrelationscan -f both fail with a POSKeyError.
The forum spam filter prevents me posting the details, but you can find them at
https://gist.github.com/candlerb/df0543b43a4ca70891bc
Any suggestions I could try using zope's fsrecover.py but I don't even know the path to the database file(s)
Thanks, Brian.
| Subject: | You have a backup, right? |
| Author: | [Not Specified] |
| Posted: | 2015-09-22 06:35 |
You have a backup, right
| Subject: | Sure, but the sysadmin who |
| Author: | [Not Specified] |
| Posted: | 2015-09-22 06:49 |
Sure, but the sysadmin who normally deals with this is away this week. It would be nice to fix the corrupt database; if not we will revert to backup next week.
I'm not impressed at a database which cannot cope with a disk full error though :-(
| Subject: | You're actually pretty lucky |
| Author: | [Not Specified] |
| Posted: | 2015-09-22 08:21 |
You're actually pretty lucky if this is your first unfixable PosKeyError. :-)
| < |
Previous Zenoss 4.2.5 - Accessing Raw Data |
Next SNMP trap mapping issue |
> |