[mythtv] [mythtv-commits] Ticket #10148: mythbackend dies at end of HDHR Prime recording with "terminate called without an active exception"

Michael T. Dean mtdean at thirdcontact.com
Sat Dec 3 21:52:13 UTC 2011

On 11/04/2011 01:32 PM, MythTV wrote:
> #10148: mythbackend dies at end of HDHR Prime recording with "terminate called
> without an active exception"
> -------------------------------------------------+-------------------------
>   Reporter:  Don Lewis<dl-mythtv@…>               |          Owner:
>       Type:  Bug Report - Crash                   |  silicondust
>   Priority:  minor                                |         Status:
> Component:  MythTV - HDHomeRun                   |  infoneeded_new
>   Severity:  medium                               |      Milestone:  unknown
>   Keywords:  mythbackend crash HDHomeRun          |        Version:  0.24.1
>                                                   |     Resolution:
>                                                   |  Ticket locked:  0
> -------------------------------------------------+-------------------------
> Comment (by Don Lewis<dl-mythtv@…>):
>   It would be difficult for me to test against master since once I upgrade
>   there is no going back.

Actually, this should more properly be said, "Once I upgrade, I can only 
go back if I properly planned and prepared for the temporary upgrade."

Don, all you need to do is:

a) Shut down all MythTV applications on all hosts.
b) Back up your 0.24-fixes database ( 
http://www.mythtv.org/wiki/Database_Backup_and_Restore )
c) Upgrade to your distro's unstable/development/master/0.25pre/whatever 
d) Start up the master backend and allow it to upgrade the database to 
current schema version (then, if required, start up a remote backend 
that uses the HDHR Prime)
e) Test to see if you have issues with master

If so:

f) Shut down all MythTV applications on all hosts
g) Downgrade to your distros 0.24-fixes packages
h) Restore the 0.24-fixes database, replacing the upgraded 
unstable/development database in the process ( 
i) Restart your MythTV applications and enjoy using 0.24-fixes

If your HDHR Prime seems to work with master, you must decide whether to 
keep using master (and live with/work on/fix any other issues that crop 
up) or perform steps f-i, above, and wait for 0.25 to be released 
(knowing that when it is, you'll be able to use your HDHR Prime without 

Granted, this does require some effort on your part, but if it's between 
doing nothing and being unable to use your HDHR Prime until at least 
0.25 release date or putting in a little effort to see if there are 
other options/if you can help with the fix, it may be worth the effort.

The main point of this post, however, being that it's not true that 
"once you upgrade, you can't go back."  Instead, you just have to go all 
the way back to the last good pre-upgrade database backup*.  Therefore, 
upgrading for a test just requires a bit of planning (and some downtime 
for your system).


*And you can't pull in new data from the upgraded database, so if you 
didn't make a decision, right away, to go back to the 0.24-fixes backup 
and instead you actually performed some recordings and/or changed 
configuration and/or modified other data in the database, you'd have to 
put new recordings into MythVideo, re-do the configuration changes, or ...

More information about the mythtv-dev mailing list