[mythtv-users] Help, frontends cannot connect to backend

Paul Harrison mythtv at dsl.pipex.com
Sun Dec 31 16:34:05 UTC 2006


stan wrote:
> Aparently this was too big to ge fowarded to the list, so I've trimed the
> logs a bit.
>
> I've been ffighting this for 2 1/2 days now, so I'd REALLY appreciate ANY
> sugestions.
>
> -----
>
> I'm trying to rebuild my Myth infrastruccture this weekend. Historically,
> I've use KnoppMyth, but I talked mysellf into using Ubuntu this time, as
> I'm moving to Ubuntu workstations, and it seemed that would make keeping
> the versions on the frontends/backend in synch easier.
>
> I'm using Ubuntu 6.10 X86, and I'v mostly gotten teh backend working. It's
> frontend can connect finw. I've got (at the moment) 3 frontends. All of
> these (inclusing  one just built from scratch using the Howto on the Ubuntu
> Help pages), can connect to the MySQL database, just fine. But, they cannot
> seem to connect to the myth backend itslef. nmap shows, what I beleive are
> the correct, ports open on the backend "panda":
>
> Starting Nmap 4.10 ( http://www.insecure.org/nmap/ ) at 2006-12-31 10:05
> EST
> Interesting ports on panda.fas.com (205.159.77.232):
> Not shown: 1674 closed ports
> PORT     STATE SERVICE
> 22/tcp   open  ssh
> 80/tcp   open  http
> 3306/tcp open  mysql
> 6543/tcp open  mythtv
> 6544/tcp open  mythtv
> MAC Address: 00:14:6C:81:E3:9C (Netgear)
> Device type: general purpose
> Running: Linux 2.4.X|2.5.X|2.6.X
> OS details: Linux 2.4.0 - 2.5.20, Linux 2.4.7 - 2.6.11
>
> Yet when I do a tcpdump on the new frontend, after starting the frontend,
> and trying to "Watch V", I don't see any evidence of it trying to originate
> traffic for the Myth backend. I _do_ see the MySQL traffic:
>
>
> 09:43:14.965352 IP boo-boo.fas.com.43901 > panda.fas.com.mysql: S 1793549980:1793549980(0) win 5840 <mss 1460,sackOK,timestamp 6872472 0,nop,wscale 2>
> 09:43:14.965432 IP panda.fas.com.mysql > boo-boo.fas.com.43901: S 466253708:466253708(0) ack 1793549981 win 5792 <mss 1460,sackOK,timestamp 11276762 6872472,nop,wscale 2>
> 09:43:14.965576 IP boo-boo.fas.com.43901 > panda.fas.com.mysql: . ack 1 win 1460 <nop,nop,timestamp 6872472 11276762>
> 09:43:14.966885 IP panda.fas.com.mysql > boo-boo.fas.com.43901: P 1:71(70) ack 1 win 1448 <nop,nop,timestamp 11276763 6872472>
> .
> .
> .
>
> 09:43:28.267115 IP boo-boo.fas.com.43901 > panda.fas.com.mysql: P 44971:45058(87) ack 44901 win 1728 <nop,nop,timestamp 6873802 11280087>
> 09:43:28.267538 IP panda.fas.com.mysql > boo-boo.fas.com.43901: P 44901:44985(84) ack 45058 win 1448 <nop,nop,timestamp 11280088 6873802>
> 09:43:28.268693 IP boo-boo.fas.com.43901 > panda.fas.com.mysql: P 45058:45149(91) ack 44985 win 1728 <nop,nop,timestamp 6873802 11280088>
> 09:43:28.269216 IP panda.fas.com.mysql > boo-boo.fas.com.43901: P 44985:45069(84) ack 45149 win 1448 <nop,nop,timestamp 11280088 6873802>
> 09:43:28.269655 IP boo-boo.fas.com.43901 > panda.fas.com.mysql: P 45149:45235(86) ack 45069 win 1728 <nop,nop,timestamp 6873802 11280088>
> 09:43:28.270043 IP panda.fas.com.mysql > boo-boo.fas.com.43901: P 45069:45153(84) ack 45235 win 1448 <nop,nop,timestamp 11280088 6873802>
> 09:43:28.300755 IP boo-boo.fas.com.43901 > panda.fas.com.mysql: . ack 45153 win 1728 <nop,nop,timestamp 6873806 11280088>
>
> So, I suppose the first question is, How does the frontend know the
> namee/addeess of the Myth backend to atempt to connect to? Is it stored in
> the database (makes sense that it would be, since the backend connects
> directly to that).
>
> What other things can I check to try to resolve this issue?
>
> Thanks fro any help.
>
>   

Have you run mythtv-setup on each frontend to set the Master Server IP? 
First page of the General settings.

Paul H.



More information about the mythtv-users mailing list