[mythtv-users] connection issue

[Daryl McDonald]

On Wed, Sep 18, 2013 at 3:56 PM, HP-mini <blm-ubunet at slingshot.co.nz> wrote:
> On Wed, 2013-09-18 at 10:01 -0400, Daryl McDonald wrote:
>> Greetings Mythizens, whenever I boot the box, manually or
>> automatically, the FE can't connect to the BE and asks if it is
>> running. A "status" query shows it is running, but FE will not connect
>> until I shutdown and restart the BE. I'm running 0.25 fixes in a
>> Ubuntu 1204 LTS desktop. A Ubuntu forum thread suggested a "sleep 10"
>> in the "/usr/bin/mythfrontend" could work, but not in my case.
>>
>
> /usr/bin/mythfrontend is an executable file except for the mythbuntu
> distro (which uses some scripted hack).
> So adding "sleep 10" to that file location is not useable for most..
>
> How do you stop & restart the BE ?
> sudo service mythtv-backend stop/status/start ??

I used "sudo stop mythtv-backend" or "start" and "status mythtv-backend"
>
> The backend logfiles should show if the BE started successfully. Mysql &
> network status are likely problems.
>
> I would have a long look at/study of the mythtv-backend upstart job
> script example on mythtv wiki.
> http://www.mythtv.org/wiki/Upstart_mythbackend_Configuration

I looked at the link and notice immediately that I do not have a
"mythtv-backend.conf" file in the "/etc/init" directory...Is that
because I used the GUI instead of the teminal?

>
> Please that note that the script requires you to choose between various
> options.
> You must study the options carefully before attempting any changes.
> You could post the differences between your system upstart job and the
> wiki example.
>
> It is possible that your system is still using the older start scripts.
> (The upstart scripts can still be manually used)
>
> That upstart script/method works well with ubuntu 10.04 & latest mythtv.
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users

What I have just tried as a work around is adding a stop and start
command to the mythtv-frontend script, which worked on a manual boot,
I'll see how it works on the auto-boot at 19:00, next sched record.

Thank-you for the next direction to look into for a proper fix.  Daryl