On Thu, Nov 15, 2012 at 3:40 PM, Karl Newman <span dir="ltr"><<a href="mailto:newmank1@asme.org" target="_blank">newmank1@asme.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=""><div class="h5"><div class="gmail_quote">On Thu, Nov 15, 2012 at 2:42 PM, Darethehair <span dir="ltr"><<a href="mailto:darethehair@gmail.com" target="_blank">darethehair@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
This one is extremely subtle, and all my sleuthing skills have not
helped me so far <img src="cid:part1.02010605.09090506@gmail.com" alt="" title="Sad" border="0"><br>
<br>
Running 0.25 on a fresh LMDE (Linux Mint Debian Edition) server.
Local Backend/frontend work fine, and remote frontend also now works
fine. Noticed that install has set up automatic start for
mysql/mythtv-backend (verified by 'chkconfig') and scripts in
'/etc/init.d'.<br>
<br>
However, upon rebooting, noticed that the remote frontend was no
longer able to connect to the backend, with non-helpful messages:<br>
<br>
<div>
<div>Code:</div>
<pre style="min-height:36px">I MythCoreContext: Connecting to backend server: <a href="http://192.168.1.101:6543" target="_blank">192.168.1.101:6543</a> (try 1 of 1)
E Connection to master server timed out.
Either the server is down or the master server settings
in mythtv-settings does not contain the proper IP address
</pre>
</div>
<br>
Oddly, a remote 'mysql' connect still works, right owner is running
the processes, correct ports are open (verified by 'nmap'), so what
is the problem?<br>
<br>
If I then <b>manually</b> restart mythbackend via the command line:<br>
<br>
<div>
<pre style="min-height:36px">sudo /etc/init.d/mythtv-backend restart</pre>
</div>
...then the remove frontend starts working again!<br>
<br>
I have done a lot of Googling, but the problems I see only have to
do with <b>failures</b> of an auto-started backend -- in my case,
the backend starts up (mostly) fine.<br>
<br>
Why would an auto-started backend not work with a remote frontend,
but a manually-started one does? If this some subtle timing issue?<br>
<br>
Help would be appreciated! <img src="cid:part2.05060505.01060300@gmail.com" alt="" title="Smile" border="0">
</div><br></blockquote></div><br></div></div>To diagnose a timing issue, could you add a delay (60 seconds?) to the init.d script? The thing that comes to mind is a possible networking issue (binding to the wrong interface or something?)<span class=""><font color="#888888"><br>
<br>Karl<br>
</font></span><br>_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<br></blockquote></div><br></div><div class="gmail_extra">If I recall correctly (wagnerrp will correct me if I'm wrong :) ), if the backend starts before networking is up, it will only listen on localhost (and won't check again if other interfaces come up). So a delay in the script should fix this (or having it depend on eth0 which IMO is better).<br class="">
<br clear="all">Thanks,<br><br>Thomas Mashos<br></div>