LinHES Forums :: View topic - MySQL suddenly reverted to last week

2005-11-13 23:50:41.456 Using runtime prefix = /usr
2005-11-13 23:50:41.473 New DB connection, total: 1
2005-11-13 23:50:41.476 Total desktop dim: 1024x768, with 2 screen[s].
2005-11-13 23:50:41.478 Using screen 0, 800x600 at 0,0
2005-11-13 23:50:41.483 Setting Lock for Database Schema upgrade. If you see a long pause here it means the Schema is already locked and is being upgraded by another Myth process.
2005-11-13 23:50:41.484 New DB connection, total: 2
2005-11-13 23:50:41.486 Told to create a NEW database schema, but the database already has 55 tables. If you are sure this is a good mythtv database, verify that the settings table has the DBSchemaVer variable.
2005-11-13 23:50:41.486 Database Schema upgrade FAILED, unlocking.
2005-11-13 23:50:41.486 Couldn't upgrade database to new schema, exiting.

Author:	cmaines [ Thu Nov 10, 2005 11:16 pm ]
Post subject:	MySQL suddenly reverted to last week
After watching a DVD using xine, my MythTV box suddenly rebooted itself. When it came back up, it was as if it was last week. The list of recorded shows was from last week and included ones that I had already deleted. I followed the procedure in one of the earlier posts about checking to see if the MySQL database tables were corrupted, and everything checked out just fine. Does anyone have any suggestions as to how I can proceed from here? All of the .nuv files from my shows recorded over the past few days are still there of course, but all the changes to the database I've made in the past seven days are no longer there. Thanks.

Author:	cmaines [ Fri Nov 11, 2005 10:37 am ]
Post subject:
I think somehow, I initiated a restore of the KnoppMyth database. The recorded shows and times that are now present in the database, are identical to what they were the last time I backed everything up. I realize I'm now officially scr%$#d, but I'd at least like to try to bring back whatever I can. I can't get the myth.rebuilddatabase.pl script to work - it claims it "can't connect to the MySQL database on 'box' " although that is the host name (I'm pretty sure), as is mythconverg the name of the database. Any suggestions?

Author:	Gnarl [ Fri Nov 11, 2005 6:01 pm ]
Post subject:
That happened to me one time. Turns out there were 2 frontends running and the one in the background restored while i was doing something else with the one in the foreground.

Author:	cmaines [ Sun Nov 13, 2005 1:15 pm ]
Post subject:
Update: I just decided to live with the bolluxed state of affairs. After getting the mythlink.sh script to work, I searched through the orphaned files, saved the ones I wanted to /myth/video and deleted the rest. I also made the alteration to the frontend menus that moves the Backup and Restore selections down one further submenu (see http://mysettopbox.tv/phpBB2/viewtopic.php?t=3959). Last night I was reminded of the sequence of events that caused the original unintended database restore - XINE! As I was exiting from xine after watching a DVD (while the backend was recording something), the system briefly locked up and then a whole bunch of xine setup menus for various functions appeared. After closing all xine menus, I heard Myth's shutdown music, the shutdown sequence kicked in and the system shutdown. This is exactly what happened the first time, except instead of shutting down, the Restore function was activated.

Author:	cmaines [ Sun Nov 13, 2005 11:04 pm ]
Post subject:
Now I'm totally screwed. Xine did it again. When trying to exit a DVD, it dumped me briefly into the MythTV screen before starting a backup or shutdown sequence (I heard the "music" again). However this time, the system hung for quite a while before finally shutting down by itself. When I rebooted, the mythfrontend will not start. I get error messages when I try to start another instance of mythfrontend: Code: 2005-11-13 23:50:41.456 Using runtime prefix = /usr 2005-11-13 23:50:41.473 New DB connection, total: 1 2005-11-13 23:50:41.476 Total desktop dim: 1024x768, with 2 screen[s]. 2005-11-13 23:50:41.478 Using screen 0, 800x600 at 0,0 2005-11-13 23:50:41.483 Setting Lock for Database Schema upgrade. If you see a long pause here it means the Schema is already locked and is being upgraded by another Myth process. 2005-11-13 23:50:41.484 New DB connection, total: 2 2005-11-13 23:50:41.486 Told to create a NEW database schema, but the database already has 55 tables. If you are sure this is a good mythtv database, verify that the settings table has the DBSchemaVer variable. 2005-11-13 23:50:41.486 Database Schema upgrade FAILED, unlocking. 2005-11-13 23:50:41.486 Couldn't upgrade database to new schema, exiting. What can I do now? Thanks.

LinHES Forums http://forum.linhes.org/

MySQL suddenly reverted to last week http://forum.linhes.org/viewtopic.php?f=6&t=6873	Page 1 of 1

Author:	cesman [ Sun Nov 13, 2005 11:16 pm ]
Post subject:
Perhaps Xine is giving focus after an exit. The keypress are unseem, so you don't know what you are doing. This cause the restore and your other issues. I being there is a thread on the forum about xine and focus.

Author:	cmaines [ Sun Nov 13, 2005 11:27 pm ]
Post subject:
Thanks for the response. Except what can I do now? I can't get the frontend to start and I don't know how to restore the mysql database without the frontend running. I tried doing mythsetup as user mythtv, but it won't retain any of the information I put into it. When I exit mythtv-setup, it says that 'table mythcoverg.settings doesn't exist.' HELP! Thanks.

Author:	cesman [ Sun Nov 13, 2005 11:44 pm ]
Post subject:
Code: mythrestore

Author:	cmaines [ Sun Nov 13, 2005 11:55 pm ]
Post subject:
THANKS! That restored everything up to this evening (after I restarted the backend, which I guess also wasn't running). I've now gotten into the habit of backing everything up at least once a day - sometimes two or three. Now on to solve the xine and focus issue.....

Page 1 of 1	All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/