[mythtv-users] Upgrade to Mint 21 broke mythweb

[James Abernathy]

On Fri, Apr 14, 2023 at 12:09 AM Douglas Peale <Douglas_Peale at comcast.net>
wrote:

> 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.
> > _______________________________________________
>
>
> 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.
>
>
Since I use networked tuners like HDHomerun on my network as well as
directly connected to a spare RJ45 ethernet port on my computers, I use a
method that supports both.  If you look at the last section of this Mythtv
Forum post you will see the section that talks about fixing the delay.

https://forum.mythtv.org/viewtopic.php?f=46&t=5225

Jim A
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20230414/96e4c279/attachment-0001.htm>