Mailing List Archive: MythTV: Users

Notes from upgrading to mythtv-0.26

Index | Next | Previous | View Threaded

monkeypet at gmail

Sep 1, 2012, 8:24 AM

Post #1 of 9 (1291 views)
Permalink

Notes from upgrading to mythtv-0.26

0. mysql_tzinfo support, maybe point us at the docs, release notes, or
wiki. I had to hunt for the solution :)

2012-09-01 07:59:01.640327 E MySQL time zone support is missing. Please
install it and try again. See 'mysql_tzinfo_to_sql' for assistance.

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'
2012-09-01 08:03:19.501268 E DBUtil: Error backing up database:
/usr/share/mythtv/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:
'/export/data/mythtv/mythconverg-1299-20120901150319.sql'
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

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.

thomas at mashos

Sep 1, 2012, 8:53 AM

Post #2 of 9 (1279 views)
Permalink

Re: Notes from upgrading to mythtv-0.26 [In reply to]

On Sat, Sep 1, 2012 at 8:24 AM, Monkey Pet <monkeypet [at] gmail> wrote:
> 0. mysql_tzinfo support, maybe point us at the docs, release notes, or wiki.
> I had to hunt for the solution :)
>
> 2012-09-01 07:59:01.640327 E MySQL time zone support is missing. Please
> install it and try again. See 'mysql_tzinfo_to_sql' for assistance.
>
> 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'
> 2012-09-01 08:03:19.501268 E DBUtil: Error backing up database:
> /usr/share/mythtv/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:
> '/export/data/mythtv/mythconverg-1299-20120901150319.sql'
> 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
>
> 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.
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>

Are you running Mythbuntu?

Thanks,

Thomas Mashos
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

keemllib at gmail

Sep 1, 2012, 9:41 AM

Post #3 of 9 (1266 views)
Permalink

Re: Notes from upgrading to mythtv-0.26 [In reply to]

On 09/01/2012 10:24 AM, Monkey Pet wrote:

Hi;

Thanks for reporting this.

> 0. mysql_tzinfo support, maybe point us at the docs, release notes, or
> wiki. I had to hunt for the solution :)

This is the 4th bullet in the Special Instructions of the 0.26 release notes.
It was the 2nd 'til a few minutes ago. I points to a Wiki with details.

> 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.
...

I just added a warning to run a backup *before* doing the upgrade, as the user
who will be doing it (which might be mythtv or $USER [or, gag, root].) Picking
the right user for the test is critical, as the backup program uses information
in the .mythtv directory of the user running it. Hope that makes sense.

> 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.

And the a new note after the one above mentions your experience. The conversion to
UTC requires changes to timestamps stored in the database. For example, starttime
and endtime in "recordedseek","recordedmarkup","recordedrating" and "recordedcredits.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

monkeypet at gmail

Sep 1, 2012, 10:53 AM

Post #4 of 9 (1265 views)
Permalink

Re: Notes from upgrading to mythtv-0.26 [In reply to]

3. One more note. My remote frontend uses a custom-identifier
"macmini-ubuntu" . However, after upgrading to 0.26, it ignored it, so I
had to retype it in to the setup->general settings. So the note here might
be to have people write it down, so they remember what to type in, I looked
in my .mythtv/mysql.txt to find my original value. A better solution is to
migration this parameter over.

On Sat, Sep 1, 2012 at 8:24 AM, Monkey Pet <monkeypet [at] gmail> wrote:

> 0. mysql_tzinfo support, maybe point us at the docs, release notes, or
> wiki. I had to hunt for the solution :)
>
> 2012-09-01 07:59:01.640327 E MySQL time zone support is missing. Please
> install it and try again. See 'mysql_tzinfo_to_sql' for assistance.
>
> 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'
> 2012-09-01 08:03:19.501268 E DBUtil: Error backing up database:
> /usr/share/mythtv/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:
> '/export/data/mythtv/mythconverg-1299-20120901150319.sql'
> 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
>
> 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.
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>
>

mtdean at thirdcontact

Oct 22, 2012, 4:23 PM

Post #5 of 9 (937 views)
Permalink

Re: Notes from upgrading to mythtv-0.26 [In reply to]

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:
> '/export/data/mythtv/mythconverg-1299-20120901150319.sql'
> 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.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

gary.buhrmaster at gmail

Oct 22, 2012, 4:48 PM

Post #6 of 9 (935 views)
Permalink

Re: Notes from upgrading to mythtv-0.26 [In reply to]

On Mon, Oct 22, 2012 at 4:23 PM, Michael T. Dean
<mtdean [at] thirdcontact> wrote:
> .... Of course, since no one ever actually reads those "why does it
> ask me twice" upgrade prompts... :)

If the dialog box said:

"Do you want fire and brimstone coming down from the skies,
rivers and seas boiling, forty years of darkness, earthquakes,
volcanoes, the dead rising from the grave, human sacrifice,
dogs and cats living together and mass hysteria"

most people would still click on "OK" (it is the only button
that makes something happen. "Cancel" just means you
get to do it all over again).

Gary
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

keemllib at gmail

Oct 22, 2012, 4:50 PM

Post #7 of 9 (936 views)
Permalink

Re: Notes from upgrading to mythtv-0.26 [In reply to]

On 10/22/2012 06:23 PM, Michael T. Dean wrote:
...
> 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.

Mike;

I wrote this a while ago, but just added it the the Wiki when I saw
your reply:

http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changeing_MythTV_Versions

Doing the test suggested not only makes it likely that the automatic backup will run,
but if completed, creates a backup *before* the upgrade is even attempted.

No matter how obvious, I think a link to it belongs in all future release notes.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

dheianevans at gmail

Oct 22, 2012, 5:40 PM

Post #8 of 9 (935 views)
Permalink

Re: Notes from upgrading to mythtv-0.26 [In reply to]

On Mon, Oct 22, 2012 at 7:48 PM, Gary Buhrmaster
<gary.buhrmaster [at] gmail> wrote:
> If the dialog box said:
>
> "Do you want fire and brimstone coming down from the skies,
> rivers and seas boiling, forty years of darkness, earthquakes,
> volcanoes, the dead rising from the grave, human sacrifice,
> dogs and cats living together and mass hysteria"
>
> most people would still click on "OK" (it is the only button
> that makes something happen. "Cancel" just means you
> get to do it all over again).
>

Gary,

if the Myth devs could actually make fire and brimstone flow through
the TV room, that might work. "Might" being the operative word.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Oct 23, 2012, 5:44 PM

Post #9 of 9 (910 views)
Permalink

Re: Notes from upgrading to mythtv-0.26 [In reply to]

On 10/22/2012 07:50 PM, Bill Meek wrote:
> On 10/22/2012 06:23 PM, Michael T. Dean wrote:
> ...
>> 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.
>
> Mike;
>
> I wrote this a while ago, but just added it the the Wiki when I saw
> your reply:
>
>
> http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changeing_MythTV_Versions
>
> Doing the test suggested not only makes it likely that the automatic
> backup will run,
> but if completed, creates a backup *before* the upgrade is even
> attempted.
>
> No matter how obvious, I think a link to it belongs in all future
> release notes.
>

Yeah, that looks good, and it's a good idea to reference it on release
notes. (I did make one change--fixed the typo of changing in the link,
so it's now at
http://www.mythtv.org/wiki/Database_Backup_and_Restore#The_Role_of_mythconverg_backup.pl_When_Changing_MythTV_Versions
).

Thanks,
Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads