I had a zenpack install that was taking hours, so I was adviced to stop it, restart zenoss, and try again. I stopped the install and got this one error: 2013-11-25 12:39:30,971 CRITICAL txn.140714171467520: A storage error occurred during the second phase of the two-phase commit. Resources may be in an inconsistent state.
I then went to restart zenoss, and that's when everything blew up. Here's everything it spit out, it looks long but most of it is the same error + traceback getting repeated for each daemon trying to start: http://fpaste.org/56658/13854050/
I have a backup, but attempting to run 'zenrestore' or most any other zen* command yields that same error. I do have access to zendmd, and attempted to run http://wiki.zenoss.org/Removing_Broken_ZenPacks . Phase 1 of this just told me all my zenpacks are fine, so I ran phase 2 and it then told it deleted all zenpacks. Running 'zenoss restart' from this point yeilds me the same output as before. I'm kind of stumped. All I need to do is get this system to a point where I can at least run 'zenrestore' to bring it all back to a stable point. It's a physical box, so snapshots are no option.
I need some help from someone who is skilled enough in zendmd to be able to help me fix this issue.
I am running Zenoss 4.2.4 on SP174. RHEL6 box. ZenPack that caused this issue was BarracudaMonitor http://wiki.zenoss.org/ZenPack:Barracuda_Monitor
