<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
>> >> MythTV Version : v0.25.2-19-gcf06841<br>
>> >> MythTV Branch : fixes/0.25<br>
>> >><br>
>> >> Combined backend/frontend.<br>
>> >><br>
>> >> My understanding was that a MythTV box can (should?) be configured so<br>
>> >> that<br>
>> >> its network address is static, and that that IP address be told to the<br>
>> >> backend and to the frontend.<br>
>> >><br>
>> >> However, if the network for some reason can't connect (in my case, a<br>
>> >> wireless connection to the router), then the frontend won't start in<br>
>> >> the<br>
>> >> normal manner, and I'm presented with the language selection menu of<br>
>> >> the<br>
>> >> frontend. Attempting to cancel that just restarts the frontend and it<br>
>> >> returns to that menu.<br>
>> >><br>
>> >> Is there an easy way around that (assuming that for some reason the<br>
>> >> network connection can't be quickly re-established, eg., router<br>
>> >> failure)? Or<br>
>> >> have I got the configuration wrong? In other words, must MythTV have a<br>
>> >> working network connection for operation?<br>
>> >><br>
>> >> Thanks.<br>
>> >><br>
>> ><br>
>> > If you look at the upstart configuration, it depends on the non loopback<br>
>> > network being up for the backend service to start:<br>
>> ><br>
>> > start on (local-filesystems and net-device-up IFACE!=lo and started<br>
>> > udev-finish)<br>
>> ><br>
>> > I believe the idea is to ensure that the backend is listening on all<br>
>> > interfaces when it starts so that remote clients can connect.<br>
>> > I do recall some workaround is to just configure a dummy static eth0<br>
>> > interface that always comes up so the script can get on with it, or you<br>
>> > could hack that section out of the upstart config<br>
>> > (/etc/init/mythtv-backend.conf).<br>
>> ><br>
>> ><br>
>> ><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>
>> That is only for the backend, the OP is talking about the frontend.<br>
>> The frontend must be able to talk to the backend for it to start<br>
>> correctly. All the information about the frontend is kept in the<br>
>> database, plus you would need a connection to the backend to playback<br>
>> any content. As frontend local content is going away, I don't see this<br>
>> changing.<br>
>><br>
> I think he is talking about a combined frontend/backend... frontend is<br>
> failing to connect because the backend isn't running yet.<br>
><br>
> I would adjust your frontend to connect on the loopback adapter of<br>
> 127.0.0.1. You may need to make sure that mysql and mythbackend are both<br>
> listening on loopback, but they typically are by default IIRC.<br>
><br><br>
<br>
</div></div>Ah yea he is, not sure how I missed that the first time I read it.<br>
<br>
Thanks,<br>
<br>
Thomas Mashos<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div>it's alright... I misspoke myself... I meant that the frontend isn't connecting because the network hasn't connected yet.</div><div><br></div>
<div>But it could be because the backend hasn't started. Perhaps starting mythwelcome instead of mythfrontend would give you a good result too. Essentially it should wait until the network and the backend are up and allow you to start the frontend. Never used it myself. </div>
</div>