[mythtv-users] Help! MythTV Backend not starting

jeff at lotussevencars.com jeff at lotussevencars.com
Sat Dec 31 19:27:31 UTC 2016


Quoting jeff at lotussevencars.com:

> Quoting Stephen Worthington <stephen_agent at jsw.gen.nz>:
>
>> On Sat, 31 Dec 2016 08:02:17 -0700, you wrote:
>>
>>>
>>> I have set up and got working a standalone mythtv box.  In the process
>>> of trying to open up the access to the database for a second remote
>>> frontend, I have broken the primary backend and don't know how.
>>>
>>> The mysql database is running:
>>>
>>> ? mysql.service - MySQL Community Server
>>>    Loaded: loaded (/lib/systemd/system/mysql.service; enabled;
>>> vendor preset: enabled)
>>>    Active: active (running) since Fri 2016-12-30 17:32:35 EST; 16h ago
>>>   Process: 2531 ExecStartPost=/usr/share/mysql/mysql-systemd-start
>>> post (code=exited, status=0/SUCCESS)
>>>   Process: 2527 ExecStartPre=/usr/share/mysql/mysql-systemd-start
>>> pre (code=exited, status=0/SUCCESS)
>>>  Main PID: 2530 (mysqld)
>>>    CGroup: /system.slice/mysql.service
>>>            ??2530 /usr/sbin/mysqld
>>>
>>> Dec 30 17:32:34 MythBuntu-Server systemd[1]: Starting MySQL Community
>>> Server...
>>> Dec 30 17:32:35 MythBuntu-Server systemd[1]: Started MySQL  
>>> Community Server.
>>>
>>> The mythTV backend, however, is not
>>> ? mythtv-backend.service - MythTV Backend
>>>    Loaded: loaded (/lib/systemd/system/mythtv-backend.service;
>>> enabled; vendor preset: enabled)
>>>    Active: inactive (dead) (Result: exit-code) since Sat 2016-12-31
>>> 09:40:24 EST; 14s ago
>>>      Docs: https://www.mythtv.org/wiki/Mythbackend
>>>   Process: 9026 ExecStart=/usr/bin/mythbackend --quiet --syslog
>>> local7 $ADDITIONAL_ARGS (code=exited, status=130)
>>>  Main PID: 9026 (code=exited, status=130)
>>>
>>> Dec 31 09:40:23 MythBuntu-Server systemd[1]: mythtv-backend.service:
>>> Unit entered failed state.
>>> Dec 31 09:40:23 MythBuntu-Server systemd[1]: mythtv-backend.service:
>>> Failed with result 'exit-code'.
>>> Dec 31 09:40:24 MythBuntu-Server systemd[1]: mythtv-backend.service:
>>> Service hold-off time over, scheduling restart.
>>> Dec 31 09:40:24 MythBuntu-Server systemd[1]: Stopped MythTV Backend.
>>> Dec 31 09:40:24 MythBuntu-Server systemd[1]: mythtv-backend.service:
>>> Start request repeated too quickly.
>>> Dec 31 09:40:24 MythBuntu-Server systemd[1]: Failed to start  
>>> MythTV Backend.
>>>
>>> The database server settings are
>>> Hostname 127.0.0.1
>>> Port 3306
>>> Database name mythconverg
>>> User mythtv
>>>
>>> I've tried disabling and enabling mysql service on ethernet interfaces
>>> from mythbuntu control center, but neither option resolves my problem.
>>>
>>> Here are the results of journalctl -xe
>>>
>>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>> --
>>> -- Unit systemd-hostnamed.service has finished starting up.
>>> --
>>> -- The start-up result is done.
>>> Dec 31 09:56:02 MythBuntu-Server sudo[2945]:     jeff : TTY=pts/0 ;
>>> PWD=/home/jeff ; USER=root ; COMMAND=/etc/init.d/mythtv-backend restart
>>> Dec 31 09:56:02 MythBuntu-Server sudo[2945]: pam_unix(sudo:session):
>>> session opened for user root by jeff(uid=0)
>>> Dec 31 09:56:02 MythBuntu-Server systemd[1]: Stopped MythTV Backend.
>>> -- Subject: Unit mythtv-backend.service has finished shutting down
>>> -- Defined-By: systemd
>>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>> --
>>> -- Unit mythtv-backend.service has finished shutting down.
>>> Dec 31 09:56:02 MythBuntu-Server systemd[1]: mythtv-backend.service:
>>> Start request repeated too quickly.
>>> Dec 31 09:56:02 MythBuntu-Server systemd[1]: Failed to start  
>>> MythTV Backend.
>>> -- Subject: Unit mythtv-backend.service has failed
>>> -- Defined-By: systemd
>>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>> --
>>> -- Unit mythtv-backend.service has failed.
>>
>> The first thing to do is to check the mysql log files to see if there
>> is an error message about the changes you have been doing to its
>> configuration.  Then run this command to see where mysql is listening:
>>
>> netstat -pl | grep mysqld
>>
>> If all seems well there, then you need to look in mythbackend.log to
>> see what error message is showing up there.
>>
>> Are you only having this problem when you boot?  Does it work properly
>> if you manually restart mythbackend after booting is complete?  If so,
>> then you need to do the systemd fixes for getting mythbackend to start
>> up properly when using external networking.  See here:
>>
>> http://mythtvinstall.blogspot.com/2016/12/how-to-install-mythbuntu-16041.html
>>
>> or here:
>>
>> https://www.mythtv.org/wiki/Install_Mythbuntu_16.04.01
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
>
> Manual restart of mythbackend after booting doesn't fix the problem.
>
> the netstat command returns this
> tcp        0      0 localhost:mysql         *:*                      
> LISTEN      1051/mysqld
> unix  2      [ ACC ]     STREAM     LISTENING     20561     
> 1051/mysqld         /var/run/mysqld/mysqld.sock
>
> The mysql log does appear to point to a password problem
> 2016-12-31T18:02:09.112069Z 26 [Note] Access denied for user  
> 'mythtv'@'localhost' (using password: YES)
>
> Password seems to be the culprit from mythbackend.log
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: C  
> thread_unknown mythcommandlineparser.cpp:2599 (ConfigureLogging)  
> mythbackend version: fixes/0.28 [v0.28-102-g9befb42] www.mythtv.org
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: C  
> thread_unknown mythcommandlineparser.cpp:2601 (ConfigureLogging) Qt  
> version: compile: 5.5.1, runtime: 5.5.1
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: N  
> thread_unknown mythcommandlineparser.cpp:2603 (ConfigureLogging)  
> Enabled verbose msgs:  general
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: N  
> thread_unknown logging.cpp:920 (logStart) Setting Log Level to  
> LOG_INFO
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: I  
> Logger logging.cpp:313 (run) Added logging to the console
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: I  
> thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup  
> Interrupt handler
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: I  
> thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup  
> Terminated handler
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: I  
> thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup  
> Segmentation fault handler
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: I  
> thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup  
> Aborted handler
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: I  
> thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup Bus  
> error handler
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: I  
> thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup  
> Floating point exception handler
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: I  
> thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup  
> Illegal instruction handler
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: I  
> thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup  
> Real-time signal 0 handler
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: I  
> thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) Setup  
> Hangup handler
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: N  
> thread_unknown mythdirs.cpp:192 (InitializeMythDirs) Using runtime  
> prefix = /usr
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: N  
> thread_unknown mythdirs.cpp:194 (InitializeMythDirs) Using  
> configuration directory = /home/mythtv/.mythtv
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: I  
> CoreContext mythcorecontext.cpp:266 (Init) Assumed character  
> encoding: en_US.UTF-8
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: N  
> CoreContext mythcontext.cpp:505 (LoadDatabaseSettings) Empty  
> LocalHostName.
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: I  
> CoreContext mythcontext.cpp:513 (LoadDatabaseSettings) Using  
> localhost value of MythBuntu-Server
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: E  
> CoreContext mythdbcon.cpp:229 (OpenDatabase) [DBManager0] Unable to  
> connect to database!
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: E  
> CoreContext mythdbcon.cpp:230 (OpenDatabase) Driver error was  
> [1/1045]:#012QMYSQL: Unable to connect#012Database error  
> was:#012Access denied for user 'mythtv'@'localhost' (using password:  
> YES)
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: C  
> CoreContext main.cpp:132 (main) Failed to init MythContext.
> Dec 31 13:02:09 MythBuntu-Server mythbackend: mythbackend[23089]: I  
> LogForward loggingserver.cpp:295 (SyslogLogger) Added syslogging
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

So, thinking that the database user access is the problem, I tried to  
follow the instructions here:
https://www.mythtv.org/wiki/Category:MySQL
When I try to enter the set password command, I get the error
ERROR 1054 (42S22): Unknown column 'Password' in 'field list'







More information about the mythtv-users mailing list