LinHES Forums
http://forums.linhes.org/

FE cannot connect to to BE on same machine
http://forums.linhes.org/viewtopic.php?f=21&t=22373		 Page 1 of 1
Author:  poflynn [ Sun Dec 18, 2011 1:49 pm ]
Post subject:  FE cannot connect to to BE on same machine
Hi all,

Ran an upg from 6.03 -> 6.04 -> 7.1 on my mbe. On the surface, it seemed to run smoothly which impressed me (hats off to cesman & co)! (Normally I wouldn't even attempt to upg systems like this, I prefer fresh installs, but in Myth's case I make an exception due to the whole DB, TV files etc setup that needs to match).

Anyway, I have no front ends with HDs, only diskless booting ones. All of these appear to have been deleted as part of the upg, that's fine. Also, all of my tuners are in a diskless-booting SBE, hence the error below saying that there are no capture cards defined. I am assuming this is not a problem right now. This combo MBE/FE is running as a virtual machine in Oracle's VirtualBox using a bridged virtual network adapter, not that that should matter.

Right now, I'm just trying to get my FE on the MBE to connect to the BE on the MBE. Here's what I have so far:




Code:
[mythtv@mbe ~]$ ifconfig
eth0      Link encap:Ethernet  HWaddr 08:00:27:30:73:13 
          inet addr:10.1.2.21  Bcast:10.1.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe30:7313/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4044 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9770 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1511078 (1.4 Mb)  TX bytes:2994633 (2.8 Mb)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:93444 errors:0 dropped:0 overruns:0 frame:0
          TX packets:93444 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8258366 (7.8 Mb)  TX bytes:8258366 (7.8 Mb)
[mythtv@mbe ~]$ sudo sv status mythbackend
run: mythbackend: (pid 5526) 4s; run: log: (pid 795) 30781s
[mythtv@mbe ~]$ netstat -tunap |grep 6543
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)

[mythtv@mbe ~]$ tail -n 25 /var/log/mythtv/mythbackend.log
2011-12-18 11:45:19.387 Scheduler, Error: No capture cards are defined in the database.
         Perhaps you should re-read the installation instructions?
2011-12-18 11:45:22.272 mythbackend version: 0.24-fixes [g31e9528] www.mythtv.org
2011-12-18 11:45:22.293 Using runtime prefix = /usr
2011-12-18 11:45:22.309 Using configuration directory = /home/mythtv/.mythtv
2011-12-18 11:45:22.311 Empty LocalHostName.
2011-12-18 11:45:22.314 Using localhost value of mbe
2011-12-18 11:45:22.317 Testing network connectivity to '10.1.2.21'
2011-12-18 11:45:22.431 New DB connection, total: 1
2011-12-18 11:45:22.438 Connected to database 'mythconverg' at host: 10.1.2.21
2011-12-18 11:45:22.441 Closing DB connection named 'DBManager0'
2011-12-18 11:45:22.443 Connected to database 'mythconverg' at host: 10.1.2.21
2011-12-18 11:45:22.445 Current locale en_US
2011-12-18 11:45:22.446 Reading locale defaults from /usr/share/mythtv//locales/en_us.xml
2011-12-18 11:45:22.460 Current MythTV Schema Version (DBSchemaVer): 1264
2011-12-18 11:45:22.463 ThreadPool:HTTP: Initial 1, Max 25, Timeout 60000
2011-12-18 11:45:22.472 Enabling Upnpmedia rebuild thread.
2011-12-18 11:45:23.681 MythBackend: Starting up as the master server.
2011-12-18 11:45:23.685 New DB connection, total: 2
2011-12-18 11:45:23.686 Connected to database 'mythconverg' at host: 10.1.2.21
2011-12-18 11:45:23.688 MythBackend, Warning: No valid capture cards are defined in the database.
2011-12-18 11:45:23.689 New DB scheduler connection
2011-12-18 11:45:23.691 Connected to database 'mythconverg' at host: 10.1.2.21
2011-12-18 11:45:23.692 Scheduler, Error: No capture cards are defined in the database.
         Perhaps you should re-read the installation instructions?

[mythtv@mbe ~]$ tail -n 25 /var/log/mythtv/mythfrontend.log
2011-12-18 11:40:14.541 Loading en_us translation for module mythbrowser
2011-12-18 11:40:14.572 MediaMonitorUnix::AddDevice() - empty device path.
2011-12-18 11:40:14.572 MediaMonitorUnix::AddDevice() - empty device path.
2011-12-18 11:40:14.572 MediaMonitorUnix::AddDevice() - empty device path.
2011-12-18 11:40:14.572 MonitorRegisterExtensions(0x100, gif,jpg,png)
2011-12-18 11:40:14.572 Loading en_us translation for module mythgallery
2011-12-18 11:40:14.577 Loading en_us translation for module mythgame
2011-12-18 11:40:14.585 Current MythMusic Schema Version (MusicDBSchemaVer): 1017
2011-12-18 11:40:14.626 MonitorRegisterExtensions(0x40, mp3,mp2,ogg,oga,flac,wma,wav,ac3,oma,omg,atp,ra,dts,aac,m4a,aa3,tta,mka,aiff,swa,wv)
2011-12-18 11:40:14.630 Loading en_us translation for module mythmusic
2011-12-18 11:40:14.636 Loading en_us translation for module mythnews
2011-12-18 11:40:14.638 Error Loading en_us translation for module mythsmolt
2011-12-18 11:40:14.657 Error Loading en_us translation for module mythstream
2011-12-18 11:40:14.662 Current MythVideo Schema Version (mythvideo.DBSchemaVer): 1038
2011-12-18 11:40:14.676 Loading en_us translation for module mythvideo
2011-12-18 11:40:14.681 Loading en_us translation for module mythweather
2011-12-18 11:40:14.688 Loading en_us translation for module mythzoneminder
2011-12-18 11:40:14.689 NetworkControl: Listening for remote connections on port 6546
2011-12-18 11:40:14.717 Found mainmenu.xml for theme 'Graphite'
2011-12-18 11:40:14.756 MythCoreContext: Connecting to backend server: 10.1.2.21:6543 (try 1 of 1)
2011-12-18 11:40:14.756 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

2011-12-18 11:40:14.756 Unable to determine master backend time zone settings.  If those settings differ from local settings, some functionality will fail.



So it seems the BE is running, right? Why does netstat not return anything? Maybe I have the syntax wrong or am misunderstanding something there 'cos it looks like it is running. I have checked and re-checked IP addrs & port numbers to the best of my abilities. Any ideas?

Thanks.
Author:  poflynn [ Sun Dec 18, 2011 2:02 pm ]
Post subject: 
Ok, ran a slightly different version of netstat:


Quote:
[mythtv@mbe ~]$ netstat -tunap |grep myth
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:6546 0.0.0.0:* LISTEN 2935/mythfrontend
tcp 0 0 0.0.0.0:6547 0.0.0.0:* LISTEN 2935/mythfrontend
tcp 0 0 10.1.2.21:43462 10.1.2.21:3306 ESTABLISHED 13287/mythbackend
tcp 0 0 10.1.2.21:43461 10.1.2.21:3306 ESTABLISHED 13287/mythbackend
tcp 0 0 10.1.2.21:37934 10.1.2.21:3306 ESTABLISHED 2935/mythfrontend
tcp 0 0 10.1.2.21:37936 10.1.2.21:3306 ESTABLISHED 2935/mythfrontend
tcp 0 0 10.1.2.21:37931 10.1.2.21:3306 ESTABLISHED 2935/mythfrontend
tcp 0 0 10.1.2.21:43460 10.1.2.21:3306 ESTABLISHED 13287/mythbackend
tcp 0 0 10.1.2.21:37935 10.1.2.21:3306 ESTABLISHED 2935/mythfrontend
udp 11968 0 239.255.255.250:1900 0.0.0.0:* 13287/mythbackend
udp 13120 0 239.255.255.250:1900 0.0.0.0:* 13287/mythbackend
udp 0 0 255.255.255.255:1900 0.0.0.0:* 13287/mythbackend
udp 0 0 239.255.255.250:1900 0.0.0.0:* 13287/mythbackend
udp 0 0 255.255.255.255:1900 0.0.0.0:* 2935/mythfrontend
udp 0 0 239.255.255.250:1900 0.0.0.0:* 2935/mythfrontend
udp 0 0 0.0.0.0:6549 0.0.0.0:* 13287/mythbackend
[mythtv@mbe ~]$


In myth-setup, under 'General' page 1 the network port is definitely set to
6543, in fact, I haven't touched any of the port settings.

Image
Author:  mattbatt [ Mon Dec 19, 2011 12:32 am ]
Post subject: 
Holy Crap that's a huge system I'm impressed.... I can't help you... just impressed. :D
Author:  poflynn [ Mon Dec 19, 2011 11:54 pm ]
Post subject: 
Ok, I got past this by changing the IP addr in the lower "Master Backend" section to be the loopback addr to 127.0.0.1 even though it had defaulted to this initially and didn't work. Now when I run the netstat cmd I see something running on port 6543 where I didn't before. This seems odd to me and a little disconcerting as I won't be able to use the loopback addr when I install a proper frontend but I guess I'll cross that bridge when I come to it

Now the backend is segfaulting which I haven't seen before, no idea why...

As for the 'huge system' compliment; thank you sir! I have no idea what you mean but I'll take any compliment I can get :-)
Author:  stevenj [ Thu Dec 22, 2011 10:52 pm ]
Post subject: 
Just wondering if you've rebooted very many times after you got this working? I ask because my 7.1 box has the same problem about 1/3 to 1/2 of the time I reboot it. I've read on the email list about it being an IPV6 problem but there wasn't a definitive way to fix it. I think it may have been said that the backend is binding to IPV6 or something. I haven't had time to research it further so when it happens I just reboot again and it usually works. Not sure if just disabling IPV6 would fix it or not. I read a little about how to do that but haven't had time to try it. Would like to know if you've rebooted many times without problems. Or if anyone else has a solution (what you did never worked for me consistently). Thanks.
Author:  poflynn [ Thu Dec 22, 2011 11:06 pm ]
Post subject: 
Many reboots, trust me :-( Here's the latest - changing it to the loopback addr didn't fully fix it as I initially thot it did; instead it has now merely become intermittent, like you. I also have a fresh install of 7.1 and that too didn't work at all using the external addr so I switched it to the loopback addr and now it too is intermittently timing out (ie same behavior as my upgraded system). Only difference between the two is the upgraded system has a ton of segfaults in the backend log which the fresh install has none.

I am also getting this MYTH_PROTO_VERSION error which I haven't looked into yet.

This doesn't bode well at all :-(

Quote:
[root@linhes ~]# tail -n 20 /var/log/mythtv/mythfrontend.log
or has deadlocked in due to bugs or hardware failure.
2011-12-21 20:54:06.181 MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1)
2011-12-21 20:54:09.224 MythSocket(9c31bf8:26): readStringList: Connection died (select).
2011-12-21 20:54:09.224 Protocol version check failure.
The response to MYTH_PROTO_VERSION was empty.
This happens when the backend is too busy to respond,
or has deadlocked in due to bugs or hardware failure.
2011-12-21 20:54:14.226 MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1)
2011-12-21 20:54:21.227 MythSocket(9a65470:26): readStringList: Error, timed out after 7000 ms.
2011-12-21 20:54:21.228 Protocol version check failure.
The response to MYTH_PROTO_VERSION was empty.
This happens when the backend is too busy to respond,
or has deadlocked in due to bugs or hardware failure.
2011-12-21 20:54:26.229 MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1)
2011-12-21 20:54:33.232 MythSocket(9bed370:26): readStringList: Error, timed out after 7000 ms.
2011-12-21 20:54:33.233 Protocol version check failure.
The response to MYTH_PROTO_VERSION was empty.
This happens when the backend is too busy to respond,
or has deadlocked in due to bugs or hardware failure.
2011-12-21 20:54:38.233 MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1)
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/