mtdean at thirdcontact
Oct 22, 2012, 4:23 PM
Post #5 of 9
On 09/01/2012 11:24 AM, Monkey Pet wrote:
> 1. Launched mythtv-setup, DB backup failed. However, I didn't get a
> screen telling me that the backup failed, unless it flashed by too
> quickly. Maybe have a more obvious warning.
> 2012-09-01 08:03:18.889374 I Current MythTV Schema Version
> (DBSchemaVer): 1299
> 2012-09-01 08:03:18.911089 E Backing up database with script:
> '/usr/share/mythtv/mythconverg_backup.pl <http://mythconverg_backup.pl>'
> 2012-09-01 08:03:19.501268 E DBUtil: Error backing up database:
> /usr/share/mythtv/mythconverg_backup.pl <http://mythconverg_backup.pl>
> /tmp/mythtv_db_backup_conf_YX1ktQ (255)
> 2012-09-01 08:03:19.501298 C Script-based database backup failed.
> Retrying with internal backup.
> 2012-09-01 08:03:19.503418 C Backing up database to file:
> 2012-09-01 08:03:19.601428 E DBUtil: Error backing up database:
> 'mysqldump --defaults-extra-file='/tmp/mythtv_db_backup_conf_oICdgw'
> --host='localhost' --port='3306' --user='mythtv' --add-drop-table
> --add-locks --allow-keywords --complete-insert --extended-insert
> --lock-tables --no-create-db --quick 'mythconverg' >
> '/export/data/mythtv/mythconverg-1299-20120901150319.sql' 2>/dev/null' (1)
> 2012-09-01 08:03:30.988033 C Upgrading to MythTV schema version 1300
> 2012-09-01 08:03:31.147892 C Upgrading to MythTV schema version 1301
> 2012-09-01 08:03:31.308097 C Upgrading to MythTV schema version 1302
> 2012-09-01 08:03:31.427821 C Upgrading to MythTV schema version 1303
> 2012-09-01 08:08:25.526633 C Upgrading to MythTV schema version 1304
This is why no one should rely on the automatic backup--which was put in
place as a last resort for users who don't properly plan their upgrades
and do a manual backup /and/ put a copy of that manually-created backup
in a safe place on a different file system/computer/network/disconnected
drive/... I wrote the code that does the backup and I don't trust it,
so I recommend no one else should, either.
That said, GUI apps (like mythtv-setup) will ask you 2x if you want to
upgrade the database. Both prompts will tell you if MythTV was unable
to back up the database for you ("MythTV was unable to backup your
database."). And, in the event that a backup was created, the second
prompt will tell you where to find the backup ("If your system becomes
unstable, a database backup file called <whatever> is located in
<directory>"). If you didn't do a backup on your own, and you notice
the "unable to backup" message or you don't notice the "backup file is
in <directory>" message, you should cancel the upgrade. Of course,
since no one ever actually reads those "why does it ask me twice"
upgrade prompts... :)
(Unfortuantely, I can't read it for you... Festival could, but...)
> 2. When i clicked on the big db "upgrade" button, it remained
> highlighted during the upgrade process. So users who are not paying
> attention to the terminal output might have thought it was stuck. It
> took over 5 mins for the upgrade to finish. Add a screen saying
> something like "upgrade in process".
> I'll add more once I have more usage time on 0.26.
Yes, we can't currently display anything on screen until the DB upgrade
wizard is converted to MythUI. It will happen, eventually... I just
haven't had time.
mythtv-users mailing list
mythtv-users [at] mythtv