<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.6.6">
</HEAD>
<BODY>
<BR>
Hi Geoff!<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">I missed the start of this thread, so some of this may be redundant.</FONT></FONT><BR>
</BLOCKQUOTE>
Welcome to the fun! <g> <BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">Does systemctl status mythbackend.service report that the backend is </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">running?</FONT></FONT><BR>
</BLOCKQUOTE>
<BR>
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.<BR>
<BR>
The response to the command was:<BR>
Loaded : not-found (Reason: No such file or directory)<BR>
Active: inactive (dead)<BR>
<BR>
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><BR>
<BR>
OK, 'stupid tangent time'. Ping the IPv6 address (copied and pasted from log) ==> unknown host. Ping the IPv4 address, 0.218 ms, etc.<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">the {/etc|/lib}/systemd/system/mythbackend.service file should have the </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">following at the top:</FONT></FONT><BR>
</BLOCKQUOTE>
This newbie has to go step-by-step... There's potential files in both directories:<BR>
ls /etc/systemd/system/mythtv-backend.service<BR>
nano /etc/systemd/system/mythtv-backend.service says "is not a normal file" and displays a blank screen.<BR>
Same for sudo nano<BR>
<BR>
ls /lib/systemd/system/mythtv-backend.service<BR>
This directory has oodles of *.service files but none with 'myth' nor 'backend' <BR>
<BR>
Ummm. I'm looking at the Frontend.<BR>
<BR>
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!)<BR>
<BR>
And thanks!<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">[Unit]</FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">Description=MythTV backend service</FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">Wants=httpd.service</FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">After=network.target mariadb.service</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">This has been in the Fedora version for at least a year, and I doubt </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">that Ubuntu did not borrow that which already worked, to put into Ubuntu.</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">In that case, the problem should not be NetworkManager. If you think it </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">might be that problem you might see a 'link not ready' line in the boot </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">output. In any case, write a small wrapper script to replace the </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">ExecStart line in NetworkManager,service and stick a 'sleep 5' line </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">before the 'usr/sbin/NetworkManager --no-daemon' line in the wrapper.</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">Then system daemon-reload && systemctl restart NetworkManager.service.</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">This will delay startup by 5 seconds, for network.service and </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">mythbackend.service.</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">Then:</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">mythfrontend should not be started by systemd (ok; unless you are </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">running the box as a kiosk type of setup).</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">Try starting mythfrontend from a console in a window ( -w ) and with a </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">reduced size (using --geometry) so you can see the output of the startup.</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">This might explain any number of other problems, from schema errors to </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">mysql errors to network errors. In that respect, my experience is that </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">it is ALWAYS easier to trace problems when the boxen are on static IP </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">addresses. You don't actually have to make the box static, if you force </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">a fixed DHCP address being served up by the router against the MAC </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">address. (Makes roaming with your laptop/tablets/phones easier, too, as </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">they are not fixed as against any external network you run across).</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">Hard to be sure, but it sorta sounds like you may have that sort of </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">problem. This frontend cannot talk to the mythbackend and reverts to </FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">first steps.</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#3c3c3c">Geoff</FONT></FONT><BR>
<BR>
</BLOCKQUOTE>
</BODY>
</HTML>