[mythtv-users] mythweb unable to connect after upgrade to 028

[George Bingham]

Well,

A few steps forward, and a few steps backward...

I *think* have have it using a proper ipv6 address, however, booting up I
still see problems.

Mythbackend is not coming up during boot, or more precisely, it fails to
connect to the database so it fails.

I am not sure why, but mysql is refusing connections because although it is
"up" it's socket address isn't there yet.

By the time the computer is finished booting, logging me in automatically,
and launching the front end (which complains because sometimes it cannot
connect to the database either, or else it does that OK, but the backend is
still down so it doesn't matter), then if I start the backend, it will come
up OK.

Oh, and the scripts that set the wake-up time before powering off the
computer are working, but since the backend fails at boot time, it doesn't
much matter right now.

I have yet to create a local startup job that would run late in the boot
process that would restart the mythbackend, because I figured there had to
be a way for the startup of things to be tweaked so that the network was
stable before starting mysql, and mysql was able to accept socket
connections before mythbackend attempted one, et. al, but I am not familiar
enough with the boot process nowadays to know what to do about it.

Are you happy with having to restart the backend at the tail end of the
boot process or have you found a way to make it all just "work".

Thanks,


George

-- George

On Thu, May 5, 2016 at 6:04 PM, George Bingham <georgeb1962 at gmail.com>
wrote:

> Bill,
>
> Thanks for the Network Manager checkbox for IPv6 - I checked it as it was
> unchecked - so we will see after my next reboot if that does the trick. I
> won't reboot tonight as I have recordings planned and will be using it
> until late tonight.
>
> I used to have this box configured to shutdown automatically if I was
> logged out and no recordings were happening soon, and to set the "wake-up"
> time so it would automatically restart if a recording was scheduled.
>
> After the upgrade I have not had time to test that out, but I think I will
> do that tonight and set a recording to start in the morning around the time
> I usually get up and see if that works.
>
> Thanks!
>
> -- George
>
> On Thu, May 5, 2016 at 4:56 PM, Bill Meek <keemllib at gmail.com> wrote:
>
>> On 05/05/2016 04:01 PM, George Bingham wrote:
>> ...
>>
>> That ls is odd because the ls has
>> */etc/systemd/system/multi-user.target.wants*
>> in it. Which should contain symbolic links. I can tell you that mine
>> looks like:
>>
>>   /etc/systemd/system/multi-user.target.wants/mythtv-backend.service ->
>> /etc/systemd/system/mythtv-backend.service
>>
>> and correctly points to the service in /etc. How yours got to point to the
>> /lib one I don't know.
>>
>> ls -dl /etc/systemd/system/mythtv-backend.service
>> /lib/systemd/system/mythtv-backend.service
>> should have returned 2 (unlinked) files. Mine looks like this:
>>
>>   -rw-r--r-- 1 root root 971 May  4 08:43
>> /etc/systemd/system/mythtv-backend.service
>>   -rw-r--r-- 1 root root 653 May  5 13:46
>> /lib/systemd/system/mythtv-backend.service
>>
>> Is there something else I can tell it to wait for so that all the inet6
>>> addresses are up before it launches the backend?
>>>
>>
>> If you're actually using IPv6 addresses, ignore the following:
>>
>> I'd verify the Backend IP6 address being used in mythtv-setup. ::1 is
>> typical,
>> and I use a Unique Local Address, but it certainly isn't required. There
>> was a user, recently, that had a Link Local address (fe80::.....) and I
>> don't recommend that. Make sure the Master IP address is the same as the
>> Backend IP address, e.g. 192.168.x.y.
>>
>> If you're using Network Manager, there is a 'box' to check to require IPv6
>> addresses to be used and the nm-online command is supposed to honor that.
>> See the man page for more details.
>>
>>
>> --
>> Bill
>> _______________________________________________
>> 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
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160507/ca0542ab/attachment.html>