[mythtv-users] 0.28 mythfrontends just keep backing up DB and do not start

Michael T. Dean mtdean at thirdcontact.com
Fri Apr 29 14:58:34 UTC 2016


On 04/29/2016 09:54 AM, Tim wrote:
> I upgraded both my BE and 2 FEs (3 different machines) from 0.27 to 0.28. For the BE, I just added the 0.28 ppa and did a dist-upgrade which succeeded after a few dependency issue... Its running on ubuntu-server 14.04. For the 2 FEs, I installed the latest Mythbuntu 16.04 fresh from an ISO.
>
> Each FE is experiencing the same issue, when I open mythfrontend, nothing appears to happen. The mythfrontend.log file says that its taking a backup of the DB, but once that is complete, the mythfrontend process just ends and it will do the exact same thing the next time I try to open mythfrontend.
>
>
> Here is the mythfrontend.log from one of the machines (hostname is orange):
...
> Apr 28 22:30:33 orange mythfrontend.real: mythfrontend[5371]: I CoreContext schemawizard.cpp:120 (Compare) Current MythMusic Schema Version (MusicDBSchemaVer): 1020
> Apr 28 22:30:33 orange mythfrontend.real: mythfrontend[5371]: E CoreContext dbutil.cpp:604 (DoBackup) Backing up database with script: '/usr/share/mythtv/mythconverg_backup.pl'
> Apr 28 22:32:15 orange mythfrontend.real: mythfrontend[5371]: C CoreContext dbutil.cpp:625 (DoBackup) Database Backup complete.
> Apr 28 22:32:15 orange mythfrontend.real: mythfrontend[5371]: C CoreContext dbutil.cpp:656 (DoBackup) Backed up database to file: '/mnt/cLue-NAS/mythtv/db_backups/mythconverg-1344-20160429023033.sql.gz'
>
>

Where's the rest of the frontend logs--specifically after this, the 
MythMusic DB upgrade will be attempted, during which it must fail. The 
logs should tell you what's wrong.  At minimum, if this were a complete 
log, it would at least show the messages MythTV outputs when it shuts 
down.  If there are no messages saying what error caused the shutdown, 
then it means you're selecting the option from the GUI prompt that says 
to not upgrade the database/to shut down. If there are no other messages 
at all--including normal shutdown messages--then something (outside of 
MythTV) is killing the process forcefully and preventing it from doing 
anything at all.

Mike


More information about the mythtv-users mailing list