[mythtv-users] FrontEnd will connect if feels like it

[Barry Martin]

Hi Geoff!


> I missed the start of this thread, so some of this may be redundant.

Welcome to the fun! <g>    



> Does systemctl status mythbackend.service report that the backend is 
> running?


Hmm: no, and before I go on some times this Frontend works/connects and
some times it doesn't.  The other Frontends don't seem to have a
problem.

The response to the command was:
    Loaded : not-found (Reason: No such file or directory)
    Active: inactive (dead)

When I do 'mythfrontend' at Terminal the log shoes "Found 1 UPnP
backends" and the next line is about the SOAPClient not finding the IPv6
address.  When it connects it seems to be via the IPv4 address.   I'm a
newbie and think that seems to be significant. <g>

OK, 'stupid tangent time'.  Ping the IPv6 address (copied and pasted
from log) ==> unknown host.   Ping the IPv4 address, 0.218 ms, etc.






> the {/etc|/lib}/systemd/system/mythbackend.service file should have
> the 
> following at the top:

This newbie has to go step-by-step...  There's potential files in both
directories:
    ls /etc/systemd/system/mythtv-backend.service
    nano /etc/systemd/system/mythtv-backend.service  says "is not a
normal file" and displays a blank screen.
    Same for sudo nano

    ls /lib/systemd/system/mythtv-backend.service
        This directory has oodles of *.service files but none with
'myth' nor 'backend' 

Ummm. I'm looking at the Frontend.

OK, looks like I either need additional clarification (which is a nice
way to say 'hand holding! <g> or something's screwed up with  the
nonexistent  /etc/systemd/system/mythbackend.service file or the
potentially screwed up  mythtv-backend.service file I found.  So will
post these findings and leave the remainder in so you can copy and
paste.  (Plus off to the next reply!)

And thanks!







> [Unit]
> Description=MythTV backend service
> Wants=httpd.service
> After=network.target mariadb.service
> 
> This has been in the Fedora version for at least a year, and I doubt 
> that Ubuntu did not borrow that which already worked, to put into
> Ubuntu.
> 
> In that case, the problem should not be NetworkManager. If you think
> it 
> might  be that problem you might see a 'link not ready' line in the
> boot 
> output. In any case, write a small wrapper script to replace the 
> ExecStart line in NetworkManager,service and stick a 'sleep 5' line 
> before the 'usr/sbin/NetworkManager --no-daemon' line in the wrapper.
> 
> Then system daemon-reload && systemctl restart NetworkManager.service.
> 
> This will delay startup by 5 seconds, for network.service and 
> mythbackend.service.
> 
> Then:
> 
> mythfrontend should not be started by systemd (ok; unless you are 
> running the box as a kiosk type of setup).
> 
> Try starting mythfrontend from a console in a window ( -w ) and with
> a 
> reduced size (using --geometry) so you can see the output of the
> startup.
> 
> This might explain any number of other problems, from schema errors
> to 
> mysql errors to network errors.  In that respect, my experience is
> that 
> it is ALWAYS easier to trace problems when the boxen are on static IP 
> addresses. You don't actually have to make the box static, if you
> force 
> a fixed DHCP address being served up by the router against the MAC 
> address. (Makes roaming with your laptop/tablets/phones easier, too,
> as 
> they are not fixed as against any external network you run across).
> 
> Hard to be sure, but it sorta sounds like you may have that sort of 
> problem. This frontend cannot talk to the mythbackend and reverts to 
> first steps.
> 
> Geoff
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160708/17ba1a5d/attachment.html>