[mythtv-users] I broke my mythTV, help!

[Bill Meek]

On 11/5/18 9:20 PM, Douglas Peale wrote:
> sudo systemctl enable mythtvbackend
> Failed to enable unit: Unit file mythtvbackend.service does not exist.
> 
> Hmm, wrong name.

My typo, but in your previous post (bottom of this) the service
name was mythbackend.service.

You have two instances of the service. The one in the 1st post:

     /etc/systemd/system/mythbackend.service

and the one just below:

     /lib/systemd/system/mythtv-backend.service

Disable one, I'd remove the one in /etc. Do a:

     sudo systemctl daemon-reload

after that.

As to the DB login failure, make sure the password in
~mythtv/.mythtv/config.xml is correct (you may have
config.xml in a different place. The systemctl cat...
mentioned before should help you locate where it is.

> $ sudo systemctl status mythtv-backend
> ● mythtv-backend.service - MythTV Backend
>     Loaded: loaded (/lib/systemd/system/mythtv-backend.service; enabled; vendor preset: enabled)
>     Active: failed (Result: exit-code) since Mon 2018-11-05 08:53:32 PST; 10h ago
>       Docs: https://www.mythtv.org/wiki/Mythbackend
>   Main PID: 2257 (code=exited, status=130)
> 
> Nov 05 08:53:32 Compromise systemd[1]: mythtv-backend.service: Service hold-off time over, scheduling restart.
> Nov 05 08:53:32 Compromise systemd[1]: mythtv-backend.service: Scheduled restart job, restart counter is at 10.
> Nov 05 08:53:32 Compromise systemd[1]: Stopped MythTV Backend.
> Nov 05 08:53:32 Compromise systemd[1]: mythtv-backend.service: Start request repeated too quickly.
> Nov 05 08:53:32 Compromise systemd[1]: mythtv-backend.service: Failed with result 'exit-code'.
> Nov 05 08:53:32 Compromise systemd[1]: Failed to start MythTV Backend.
> 
> sudo systemctl start mythtv-backend
> ● mythtv-backend.service - MythTV Backend
>     Loaded: loaded (/lib/systemd/system/mythtv-backend.service; enabled; vendor preset: enabled)
>     Active: active (running) since Mon 2018-11-05 19:16:21 PST; 5s ago
>       Docs: https://www.mythtv.org/wiki/Mythbackend
>   Main PID: 30521 (mythbackend)
>      Tasks: 8 (limit: 4915)
>     CGroup: /system.slice/mythtv-backend.service
>             └─30521 /usr/bin/mythbackend --quiet --syslog local7
> 
> Nov 05 19:16:22 Compromise mythbackend[30521]: mythbackend[30521]: I CoreContext mythcontext.cpp:607 (LoadDatabaseSettings)
> Using localhost value of Compromise
> Nov 05 19:16:22 Compromise mythbackend[30521]: mythbackend[30521]: I CoreContext mythcontext.cpp:852 (TestDBconnection) Start up
> testing connections. DB localhost, BE , attempt 0, s
> Nov 05 19:16:22 Compromise mythbackend[30521]: mythbackend[30521]: I LogForward loggingserver.cpp:302 (SyslogLogger) Added
> syslogging
> Nov 05 19:16:23 Compromise mythbackend[30521]: mythbackend[30521]: E CoreContext mythdbcon.cpp:242 (OpenDatabase) [DBManager0]
> Unable to connect to database!
> Nov 05 19:16:23 Compromise mythbackend[30521]: mythbackend[30521]: E CoreContext mythdbcon.cpp:243 (OpenDatabase) Driver error
> was [1/1045]:
>                                                 QMYSQL: Unable to connect
>                                                 Database error was:
>                                                 Access denied for user 'mythtv'@'localhost' (using password: YES)
> Nov 05 19:16:24 Compromise mythbackend[30521]: mythbackend[30521]: I CoreContext mythcontext.cpp:971 (TestDBconnection) Start up
> failure. host localhost, status dbStartedFail
> Nov 05 19:16:24 Compromise mythbackend[30521]: mythbackend[30521]: I CoreContext mythcontext.cpp:1127 (UPnPautoconf) UPNP Search
> 2 secs
> Nov 05 19:16:24 Compromise mythbackend[30521]: mythbackend[30521]: I CoreContext mythcontext.cpp:1142 (UPnPautoconf) UPNP Search
> 1 secs
> Nov 05 19:16:24 Compromise mythbackend[30521]: mythbackend[30521]: I CoreContext mythcontext.cpp:1142 (UPnPautoconf) UPNP Search
> 1 secs
> Nov 05 19:16:26 Compromise mythbackend[30521]: mythbackend[30521]: I CoreContext mythcontext.cpp:1152 (UPnPautoconf) No UPnP
> backends found
> 
> So, why would changing the hard drive change the ability to access the database?
> 
> On 11/5/18 9:43 AM, Bill Meek wrote:
>> On 11/5/18 10:55 AM, Douglas Peale wrote:
>>> sudo systemctl status mythbackend <-----------------------------------------
>>> ● mythbackend.service - MythTV backend service
>>>      Loaded: loaded (/etc/systemd/system/mythbackend.service; disabled; vendor preset: enabled)
>>
>> The service is disabled at boot time. sudo systemctl enable mythtvbackend
>>
>> There's nothing wrong with that service name, however mythtv-backend
>> is also common. Just be sure you don't have both. Try:
>> systemctl status myth*.service
>>
>> Hopefully, when you start the backend from the command line, you're using
>> sudo systemctl start mythtvbackend
>>
>> To see where logs are going, you need to look at the service:
>> systemctl cat mythtvbackend

-- 
Bill