[mythtv-users] Upgrade to Mint 21 broke mythweb

Douglas Peale Douglas_Peale at Comcast.net
Fri Apr 14 04:07:25 UTC 2023


On 4/13/23 20:52, Stephen Worthington wrote:
> On Thu, 13 Apr 2023 19:32:58 -0700, you wrote:
>
>> On 4/10/23 13:42, Jay Harbeston wrote:
>>>> On Apr 10, 2023, at 3:28 PM, Douglas Peale <Douglas_Peale at Comcast.net> wrote:
>>>>
>>>> I have upgraded my computer to Mint 21
>>>>
>>>> MythTV front end and back end are working
>>>>
>>>> Browser says "Unable to connect" when trying to access https://localhost/mythweb/
>>> Sounds like apache service is not running. That would be the first step.
>> Update to this issue:
>>
>> I have done a clean install of mint 21, and restored my home directory (that was a nightmare caused by odd behavior of "BackInTime")
>>
>> I have installed the ppa for MythTV 33, and installed mythTV
>>
>> I have restored the database to MythTV and adjusted the passwords as required.
>>
>> Everything appears to be working, including mythweb.
>>
>> I did have a bit of trouble with the network tuners not being found, fixed after re-scanning for channels.
>>
>> has the race between MythBackEnd starting and the network starting been fixed in 33? or do I need to look through my notes on
>> how to fix that?
>>
>>
>> Thanks.
> No, the network race condition has not been fixed.  The systemd unit
> mythtv-backend.service as installed by the packages is designed to
> work with the majority of systems where they do not use network tuners
> or have external frontends.  So if you do need mythbackend to wait for
> the network to be fully up, you still need to do a fix for that.
>
> However, mythbackend now does signal to systemd that it has fully
> started up, so things that need to wait for mythbackend can now rely
> on waiting for systemd to tell them that the mythtv-backend unit has
> started.  To make it do this, you need to change the Type= line in the
> [service] section to "Type=notify" (do this in an override file).
> After that change, you will notice that when you manually run
> "systemctl start mythtv-backend", the command will not return until
> mythbackend has fully started up, so it will take much longer to get a
> command prompt back again.
> _______________________________________________
> 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

Is there a document that shows the best way to fix the race condition?

Last time I did this there was a bit of an argument going on about how to do it the correct way.

I think I solved it last time with a simple delay which annoyed some people.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x7B9B5178E6AE112A.asc
Type: application/pgp-keys
Size: 2452 bytes
Desc: OpenPGP public key
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20230413/da047db7/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 203 bytes
Desc: OpenPGP digital signature
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20230413/da047db7/attachment.sig>


More information about the mythtv-users mailing list