[mythtv-users] today's mythtv update for v31 failed

Jim Abernathy jfabernathy at gmail.com
Sun Feb 6 11:47:53 UTC 2022


On 2/6/22 00:02, Bill Meek wrote:
> On 2/3/22 10:47, James Abernathy wrote:
>> I think this failure is mine alone but it seems to fail because of an override.conf file I have in the mythtv-backend.service.  It worked until
>> this update this morning.
>>
>> I don't see this reason for the error:
>> jim at kubuntu-closet:/etc/systemd/system/mythtv-backend.service.d$ sudo systemctl cat mythtv-backend.service
>> # /lib/systemd/system/mythtv-backend.service
>> [Unit]
>> Description=MythTV Backend
>> Documentation=https://www.mythtv.org/wiki/Mythbackend <https://www.mythtv.org/wiki/Mythbackend>
>> After=mysql.service network.target
>>   
>> [Service]
>> User=mythtv
>> EnvironmentFile=-/etc/mythtv/additional.args
>> ExecStart=/usr/bin/mythbackend --quiet --syslog local7 $ADDITIONAL_ARGS
>> StartLimitBurst=10
>> StartLimitInterval=10m
>> Restart=on-failure
>> RestartSec=1
>>   
>> [Install]
>> WantedBy=multi-user.target
>>
>> # /etc/systemd/system/mythtv-backend.service.d/override.conf
>> [Service]
>> ExecStartPre=/usr/local/bin/hdhomerun_check.py
>>
>> I think the error with the upgrade is during the post processing. when it tried to restart mythtv-backend.service. Here's the output from the
>> restart failure.
>>
>> jim at kubuntu-closet:/etc/systemd/system/mythtv-backend.service.d$ sudo systemctl status mythtv-backend
>> × mythtv-backend.service - MythTV Backend
>>       Loaded: loaded (/lib/systemd/system/mythtv-backend.service; enabled; vendor preset: enabled)
>>      Drop-In: /etc/systemd/system/mythtv-backend.service.d
>>               └─override.conf
>>       Active: failed (Result: exit-code) since Thu 2022-02-03 11:39:01 EST; 14s ago
>>         Docs: https://www.mythtv.org/wiki/Mythbackend <https://www.mythtv.org/wiki/Mythbackend>
>>      Process: 3711 ExecStartPre=/usr/local/bin/hdhomerun_check.py (code=exited, status=1/FAILURE)
>>          CPU: 86ms
>>
>> Feb 03 11:39:01 kubuntu-closet systemd[1]: mythtv-backend.service: Scheduled restart job, restart counter is at 10.
>> Feb 03 11:39:01 kubuntu-closet systemd[1]: Stopped MythTV Backend.
>> Feb 03 11:39:01 kubuntu-closet systemd[1]: mythtv-backend.service: Start request repeated too quickly.
>> Feb 03 11:39:01 kubuntu-closet systemd[1]: mythtv-backend.service: Failed with result 'exit-code'.
>> Feb 03 11:39:01 kubuntu-closet systemd[1]: Failed to start MythTV Backend.
>>
>> I'll temporarily remove the override for now.
>>
>> Any ideas?
> OK, here's what really happened. The mythtv-common.postinst script changes
> everything /var/log/mythtv to user:group syslog:adm here:
>
>    https://github.com/MythTV/packaging/blob/master/deb/debian/mythtv-common.postinst#L79
>
> Since the logging for MythTV programs is --syslog local7, rsyslog expects to
> see that owner and group.
>
> Moving the log under /tmp remains the easiest solution. Plus, there's no need to add
> an entry in logrotate.d as /tmp/* will get cleaned out on reboot.


Thanks, I knew I originally installed the override.conf correctly. So I 
will move the HDHR_discover.log to /tmp to avoid all this because I 
don't want to fix it back after each update.

Jim A




More information about the mythtv-users mailing list