Mailing List Archive: MythTV: Users

Yet another 'Could not connect to master backend server' post

Index | Next | Previous | View Threaded

bryan.bennetts at gmail

May 8, 2008, 5:16 AM

Post #1 of 6 (601 views)
Permalink

Yet another 'Could not connect to master backend server' post

Hi guys,

I'm trying to divine whats gone awry with my setup w.r.t. the above warning.

My setup :

1 BE+FE machine, using mythwelcome.
1 Remote Frontend

Both are running .21-fixes on Gentoo.

I have the Local server IP set to 192.168.0.102 (the BE+FE IP address) and
likewise for the backend server IP. When I boot my BE+FE machine (so that
mythwelcome automagically starts the frontend) I get a warning dialogue
stating 'Could not connect to the master back server -- is it running yada
yada yada'. If I hit okay the frontend then starts and everything is fine,
if I don't hit okay the backend shuts the machine down as (presumably) no
clients have attached. Obviously this isn't ideal as it means waiting for
the machine to boot and hitting the okay button within a set time frame.
With this setup I can connect to the backend using the stand alone frontend
machine with no warnings.

Does anyone have a setup similar to this, can they confirm that these are the
correct settings? If I set the IP addresses to 127.0.0.1 then everything is
fine on the BE+FE machine, but unsurprisingly I cannot connect using the
stand alone FE machine.

The setup has worked in the past, I'm not sure if I broke it tinkering with
the settings, or whether it happened after updating the software. I'm
guessing the former.

Thanks in advance, Bryan.
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

drayson at net1plus

May 8, 2008, 5:57 AM

Post #2 of 6 (578 views)
Permalink

Re: Yet another 'Could not connect to master backend server' post [In reply to]

-----Original Message-----
From: mythtv-users-bounces[at]mythtv.org
[mailto:mythtv-users-bounces[at]mythtv.org] On Behalf Of Bryan Bennetts
Sent: Thursday, May 08, 2008 8:17 AM
To: mythtv-users[at]mythtv.org
Subject: [mythtv-users] Yet another 'Could not connect to master backend
server' post

Hi guys,

I'm trying to divine whats gone awry with my setup w.r.t. the above warning.

My setup :

1 BE+FE machine, using mythwelcome.
1 Remote Frontend

Both are running .21-fixes on Gentoo.

I have the Local server IP set to 192.168.0.102 (the BE+FE IP address) and
likewise for the backend server IP. When I boot my BE+FE machine (so that
mythwelcome automagically starts the frontend) I get a warning dialogue
stating 'Could not connect to the master back server -- is it running yada
yada yada'. If I hit okay the frontend then starts and everything is fine,
if I don't hit okay the backend shuts the machine down as (presumably) no
clients have attached. Obviously this isn't ideal as it means waiting for
the machine to boot and hitting the okay button within a set time frame.
With this setup I can connect to the backend using the stand alone frontend
machine with no warnings.

Does anyone have a setup similar to this, can they confirm that these are
the
correct settings? If I set the IP addresses to 127.0.0.1 then everything is

fine on the BE+FE machine, but unsurprisingly I cannot connect using the
stand alone FE machine.

The setup has worked in the past, I'm not sure if I broke it tinkering with
the settings, or whether it happened after updating the software. I'm
guessing the former.

Thanks in advance, Bryan.
_______________________________________________

Brian,

I too use Gentoo, I have a Master BE machine and a remote BE+FE. However I
am using trunk not fixes.
I ran into a similar issue once I upgraded past the change to uPnP.
The issue with my machine was due to not having a config.xml setup in the
.mythtv folder on my machine.
Due to having a FE and BE on this machine I needed a config.xml in both the
root and in the mythuser .mythtv folders.

Marc

_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

bryan.bennetts at gmail

May 8, 2008, 7:18 AM

Post #3 of 6 (570 views)
Permalink

Re: Yet another 'Could not connect to master backend server' post [In reply to]

On Thursday 08 May 2008 13:57, Marc wrote:
> -----Original Message-----
> From: mythtv-users-bounces[at]mythtv.org
> [mailto:mythtv-users-bounces[at]mythtv.org] On Behalf Of Bryan Bennetts
> Sent: Thursday, May 08, 2008 8:17 AM
> To: mythtv-users[at]mythtv.org
> Subject: [mythtv-users] Yet another 'Could not connect to master backend
> server' post
>
> Hi guys,
>
> I'm trying to divine whats gone awry with my setup w.r.t. the above
> warning.
>
> My setup :
>
> 1 BE+FE machine, using mythwelcome.
> 1 Remote Frontend
>
> Both are running .21-fixes on Gentoo.
>
> I have the Local server IP set to 192.168.0.102 (the BE+FE IP address) and
> likewise for the backend server IP. When I boot my BE+FE machine (so that
> mythwelcome automagically starts the frontend) I get a warning dialogue
> stating 'Could not connect to the master back server -- is it running yada
> yada yada'. If I hit okay the frontend then starts and everything is fine,
> if I don't hit okay the backend shuts the machine down as (presumably) no
> clients have attached. Obviously this isn't ideal as it means waiting for
> the machine to boot and hitting the okay button within a set time frame.
> With this setup I can connect to the backend using the stand alone frontend
> machine with no warnings.
>
> Does anyone have a setup similar to this, can they confirm that these are
> the
> correct settings? If I set the IP addresses to 127.0.0.1 then everything
> is
>
> fine on the BE+FE machine, but unsurprisingly I cannot connect using the
> stand alone FE machine.
>
> The setup has worked in the past, I'm not sure if I broke it tinkering with
> the settings, or whether it happened after updating the software. I'm
> guessing the former.
>
> Thanks in advance, Bryan.
> _______________________________________________
>
>
> Brian,
>
> I too use Gentoo, I have a Master BE machine and a remote BE+FE. However I
> am using trunk not fixes.
> I ran into a similar issue once I upgraded past the change to uPnP.
> The issue with my machine was due to not having a config.xml setup in the
> .mythtv folder on my machine.
> Due to having a FE and BE on this machine I needed a config.xml in both the
> root and in the mythuser .mythtv folders.
>
> Marc
>

Thanks for the suggestion, Marc, but that hasn't fixed it. I already had a
config.xml in ~mythtv/.mythtv :

mythtv[at]stella ~/.mythtv $ cat config.xml
<Configuration>
<UPnP>
<UDN>
<MediaRenderer>134423ce-0364-44b0-bb9d-eedfb4e1ba0e</MediaRenderer>
</UDN>
<MythFrontend>
<DefaultBackend>
<DBHostName>192.168.0.102</DBHostName>
<DBUserName>mythtv</DBUserName>
<DBPassword>mythtv</DBPassword>
<DBName>mythconverg</DBName>
<DBPort>0</DBPort>
</DefaultBackend>
</MythFrontend>
</UPnP>
</Configuration>

but not in the root user's account, I copied the mythtv user's one over but
still get the could not connect dialogue.

Any other ideas out there?

Cheers, Bryan.
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

bryan.bennetts at gmail

May 8, 2008, 8:14 AM

Post #4 of 6 (568 views)
Permalink

Re: Yet another 'Could not connect to master backend server' post [SOLVED] [In reply to]

On Thursday 08 May 2008 13:16, Bryan Bennetts wrote:
> Hi guys,
>
> I'm trying to divine whats gone awry with my setup w.r.t. the above
> warning.
>
> My setup :
>
> 1 BE+FE machine, using mythwelcome.
> 1 Remote Frontend
>
> Both are running .21-fixes on Gentoo.
>
> I have the Local server IP set to 192.168.0.102 (the BE+FE IP address) and
> likewise for the backend server IP. When I boot my BE+FE machine (so that
> mythwelcome automagically starts the frontend) I get a warning dialogue
> stating 'Could not connect to the master back server -- is it running yada
> yada yada'. If I hit okay the frontend then starts and everything is fine,
> if I don't hit okay the backend shuts the machine down as (presumably) no
> clients have attached. Obviously this isn't ideal as it means waiting for
> the machine to boot and hitting the okay button within a set time frame.
> With this setup I can connect to the backend using the stand alone frontend
> machine with no warnings.
>
> Does anyone have a setup similar to this, can they confirm that these are
> the correct settings? If I set the IP addresses to 127.0.0.1 then
> everything is fine on the BE+FE machine, but unsurprisingly I cannot
> connect using the stand alone FE machine.
>
> The setup has worked in the past, I'm not sure if I broke it tinkering with
> the settings, or whether it happened after updating the software. I'm
> guessing the former.
>
> Thanks in advance, Bryan.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users[at]mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Turns out to be a timing issue, mythwelcome is coming up before the backend is
ready. Sticking a 'sleep 2' before mythwelcome is invoked 'solved' the
issue.

I guess it'd be nice if mythContext continued checking for the backend whilst
displaying the warning dialogue so if one becomes available it could take the
dialogue down and continue merrily on its way...

Thanks, Bryan.
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

John.Veness.myth at pelago

May 9, 2008, 2:28 PM

Post #5 of 6 (523 views)
Permalink

Re: Yet another 'Could not connect to master backend server' post [SOLVED] [In reply to]

Bryan Bennetts wrote:
> On Thursday 08 May 2008 13:16, Bryan Bennetts wrote:
>> Hi guys,
>>
>> I'm trying to divine whats gone awry with my setup w.r.t. the above
>> warning.
>>
>> My setup :
>>
>> 1 BE+FE machine, using mythwelcome.
>> 1 Remote Frontend
>>
>> Both are running .21-fixes on Gentoo.
>>
>> I have the Local server IP set to 192.168.0.102 (the BE+FE IP address) and
>> likewise for the backend server IP. When I boot my BE+FE machine (so that
>> mythwelcome automagically starts the frontend) I get a warning dialogue
>> stating 'Could not connect to the master back server -- is it running yada
>> yada yada'. If I hit okay the frontend then starts and everything is fine,
>> if I don't hit okay the backend shuts the machine down as (presumably) no
>> clients have attached. Obviously this isn't ideal as it means waiting for
>> the machine to boot and hitting the okay button within a set time frame.
>> With this setup I can connect to the backend using the stand alone frontend
>> machine with no warnings.
>>
>> Does anyone have a setup similar to this, can they confirm that these are
>> the correct settings? If I set the IP addresses to 127.0.0.1 then
>> everything is fine on the BE+FE machine, but unsurprisingly I cannot
>> connect using the stand alone FE machine.
>>
>> The setup has worked in the past, I'm not sure if I broke it tinkering with
>> the settings, or whether it happened after updating the software. I'm
>> guessing the former.
>>
>> Thanks in advance, Bryan.
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users[at]mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
> Turns out to be a timing issue, mythwelcome is coming up before the backend is
> ready. Sticking a 'sleep 2' before mythwelcome is invoked 'solved' the
> issue.
>
> I guess it'd be nice if mythContext continued checking for the backend whilst
> displaying the warning dialogue so if one becomes available it could take the
> dialogue down and continue merrily on its way...
>
> Thanks, Bryan.

Ah yes, I have exactly this same problem with mythwelcome starting
before the backend (or possibly mysql, I haven't checked) on my combined
BE/FE machine. I have stuck a sleep command in too, but I have had to
increase the delay it when I increased the number of tuners, as I guess
things took longer to start up. Even then, if I boot the machine while
there is a DVD in the drive, this seems to affect the timing such that
mythbackend takes even longer to start.

The whole thing seems a little messy and fragile (and the "sleep 8" I
currently have makes the user experience of startup speed annoying). As
you say, it would be good if mythwelcome could retry automatically.

Cheers,

John

--
John Veness, MythTV user, UK, DVB-T
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

John.Veness.myth at pelago

May 9, 2008, 2:36 PM

Post #6 of 6 (521 views)
Permalink

Re: Yet another 'Could not connect to master backend server' post [SOLVED] [In reply to]

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com