For some reason it didn't seem like it went through to the list
On October 8, 2014 10:35:43 AM CDT, Hon1nbo <hon1nbo.l...@gmail.com> wrote:
>My one.db appears to have become corrupted (sqlite3 says it is
>malformed, and onedb -fsck says it does not appear to be generated by
>OpenNebula since it can't find the user table).
>
>I caught it because I restarted the service after the scheduler log
>reports shoed the standard user authentication error from not being
>able to match the password for oneadmin in the DB with that of the
>one_auth file).
>Since the system kept running like this for a while, even with the
>error, the corruption managed to get put into my backup store so I have
>no clean backups.
>From what I can tell once the DB is corrupt there is nothing that can
>be done. I can't even get a basic INSERT schema exported to try to
>recreate it manually.
>
>In a panic I am configuring a new server to try and get my systems up
>and the VMs imported, but I am needing some help.
>
>I have a new OpenNebula server created to import VMs into. I checked
>and all the VMs from the deployment are themselves still stable and
>running.
>Is there anything I can do to import them into the new deployment? What
>about saving their disk state in case I have to recreate and
>instantiate them?
>
>Any other advice? To prevent this in the future I'm implementing
>integrity checking in my backup routine, but before I do that I need to
>try to recover as best as I can.
>
>Thanks in advance.
>
>-Jim
>
>
>--
>Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
