LinHES Forums :: View topic

Did you do this early enough in the install that it would do it's setup on the newly created /myth volume (before entering the root password for phase 2) or, if you did it after completing the install, did you save the contents of the /myth directory tree and restore them?

Also, what does your partition structure look like?

When you get to the window on the desktop waiting for the root password, switch to an alternate console (Ctrl-Alt-F1) and login as root.

/dev/hda1(4.6 gig)
/dev/vg/myth (332 gig)

Connecting to backend server: 192.168.0.243:6543 (try 1 of 5)

Connection timed out
You probably should notify Master Server
settings in the setup program and set the proper IP address

I think LVM is probably coincidental to your problem. There are a number of threads about how to diagnose issues with the backend not starting, and a TroubleShooting page on the wiki here - http://www.knoppmythwiki.org/index.php?page=MythBackendNotRunning

I suspect this has far more to do with your IP problems here - http://mysettopbox.tv/phpBB2/viewtopic.php?t=11634 Using DHCP for servers is generally asking for trouble unless you've got a really good dynamic name server set up along with it and can use symbolic names everywhere.

When it's finished with the mythfilldatabase, type in: 'mythbackend'. Let it finish doing its thing.

It'd probably pay to hunt through all the settings and make sure that everything agrees on the current IP address(es). In the settings table MasterServerIP and BackendServerIP, it's also stored in a file somewhere...

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
# automatically added when upgrading
auto lo eth0
iface lo inet loopback

iface eth0 inet static
address 192.168.0.115
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.250

2006-09-17 09:22:50.802 Using runtime prefix = /usr
2006-09-17 09:22:50.812 New DB connection, total: 1
2006-09-17 09:22:50.813 Connected to database 'mythconverg' at host: localhost
2006-09-17 09:22:50.816 Current Schema Version: 1123
Starting up as the master server.
2006-09-17 09:22:50.821 New DB connection, total: 2
2006-09-17 09:22:50.822 Connected to database 'mythconverg' at host: localhost
2006-09-17 09:22:50.826 New DB connection, total: 3
2006-09-17 09:22:50.826 Connected to database 'mythconverg' at host: localhost
2006-09-17 09:22:51.001 New DB scheduler connection
2006-09-17 09:22:51.001 Connected to database 'mythconverg' at host: localhost
2006-09-17 09:22:51.005 mythbackend version: 0.19.20060121-2 www.mythtv.org
2006-09-17 09:22:51.006 Enabled verbose msgs: important general
2006-09-17 09:22:51.006 AutoExpire: Found 1 recorders w/max rate of 72 MiB/min
2006-09-17 09:22:51.007 AutoExpire: Required Free Space: 2.1 GB w/freq: 10 min
2006-09-17 09:22:53.006 Reschedule requested for id -1.
2006-09-17 09:22:53.415 Scheduled 0 items in 0.4 = 0.41 match + 0.00 place
2006-09-17 09:22:53.417 Seem to be woken up by USER

Author:	SilverOne [ Sun Jul 30, 2006 4:45 pm ]
Post subject:	R5C7 and LVM
I've installed R5C7 and have tried to add a second drive using LMV documentation on the knoppwiki site. Now there is a could not connect to the master backend server... message. I know that the cache partion is removed from this version but using the create_lvm script doesn't seem to work for me. I will try the manual install again but would appreciate any help. thanks

Author:	tjc [ Sun Jul 30, 2006 5:58 pm ]
Post subject:
Did you do this early enough in the install that it would do it's setup on the newly created /myth volume (before entering the root password for phase 2) or, if you did it after completing the install, did you save the contents of the /myth directory tree and restore them? Also, what does your partition structure look like?

Author:	Dr. Hood [ Fri Sep 15, 2006 7:04 am ]
Post subject:
tjc wrote: Did you do this early enough in the install that it would do it's setup on the newly created /myth volume (before entering the root password for phase 2) or, if you did it after completing the install, did you save the contents of the /myth directory tree and restore them? Also, what does your partition structure look like? tjc, I am also having this exact same problem. I restored the LVM using the instructions found in the KnoppMyth wiki... Quote: When you get to the window on the desktop waiting for the root password, switch to an alternate console (Ctrl-Alt-F1) and login as root. Did not save the contents of the /myth directory. The restore LVM script worked great and I can see the contents /myth. The partition structure is pretty simple... Quote: /dev/hda1(4.6 gig) /dev/vg/myth (332 gig) /dev/vg/myth is a combination of two partitions (hda2 and hdb1) When I start the frontend with 'myth' and logged in as root, I get the message.... Quote: Connecting to backend server: 192.168.0.243:6543 (try 1 of 5) Connection timed out You probably should notify Master Server settings in the setup program and set the proper IP address However, I have verified that the IP address in the backend is the same as ifconfig for eth0. I checked the inod space with 'df -i' command it reports that /dev/hda1 is 24% used and /dev/vg/myth is 2% used. Any suggestions? Dr. Hood

Author:	tjc [ Fri Sep 15, 2006 7:17 am ]
Post subject:
I think LVM is probably coincidental to your problem. There are a number of threads about how to diagnose issues with the backend not starting, and a TroubleShooting page on the wiki here - http://www.knoppmythwiki.org/index.php?page=MythBackendNotRunning I suspect this has far more to do with your IP problems here - http://mysettopbox.tv/phpBB2/viewtopic.php?t=11634 Using DHCP for servers is generally asking for trouble unless you've got a really good dynamic name server set up along with it and can use symbolic names everywhere.

Author:	Dr. Hood [ Fri Sep 15, 2006 8:48 am ]
Post subject:
tjc wrote: I think LVM is probably coincidental to your problem. There are a number of threads about how to diagnose issues with the backend not starting, and a TroubleShooting page on the wiki here - http://www.knoppmythwiki.org/index.php?page=MythBackendNotRunning I suspect this has far more to do with your IP problems here - http://mysettopbox.tv/phpBB2/viewtopic.php?t=11634 Using DHCP for servers is generally asking for trouble unless you've got a really good dynamic name server set up along with it and can use symbolic names everywhere. Thanks for the quick reply. I can start the mythtv-backend manually with /etc/init.d/mythtv-backend start', but the 'cannot connect to master server' still appears and no ability to watch livetv. Your suggestion prompted to me reconfigure the network interface with 'netcardconfig' and set an IP address manually. The only thing I changed was the IP address from 192.168.0.243 to 192.168.0.115 and the gateway ip address. Everything else I left at the defaults. I then updated the mythtv backend to use this static ip address. Unfortunately, using the static IP address didn't solve the problem. I still get the 'cannot connect' error message. I will give the link you suggestion to the KnoppMyth Wiki a closer read and see if there is anything that I missed. Any other suggestion will be greatly appreciated. Dr. Hood

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

R5C7 and LVM http://forum.linhes.org/viewtopic.php?f=6&t=11015	Page 1 of 1

Author:	Dr. Hood [ Fri Sep 15, 2006 9:03 am ]
Post subject:
I am suspecting that the backend server is crashing when I start the frontend. This is because I start the backend manually (as root in a terminal), then start the front end (by using 'Restart'), exit out of the frontend, and the backend is no longer running. I am in the process of searching the forum, but haven't found a relevant thread. If anyone knows of a solution or a thread with a fix, please post. Dr. Hood

Author:	Dr. Hood [ Fri Sep 15, 2006 9:23 am ]
Post subject:
Solved by doing as tjc suggested and followed the instructions at MythBackendNotRunning The specific step that solved is was... Quote: When it's finished with the mythfilldatabase, type in: 'mythbackend'. Let it finish doing its thing. When I ran the 'mythbackend' command a bunch of messages appeared and it never returned to a prompt. I just closed the terminal window and went back into the frontend and the message was gone....I was then able to watch TV and view the Program Guide with no message popping up. Thanks tjc for pointing me in the right direction. Your help is very, very appreciated. Dr. Hood

Author:	tjc [ Fri Sep 15, 2006 5:35 pm ]
Post subject:
It'd probably pay to hunt through all the settings and make sure that everything agrees on the current IP address(es). In the settings table MasterServerIP and BackendServerIP, it's also stored in a file somewhere... /etc/network/interfaces /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/hosts ...

Author:	Dr. Hood [ Sun Sep 17, 2006 5:46 am ]
Post subject:
tjc wrote: It'd probably pay to hunt through all the settings and make sure that everything agrees on the current IP address(es). In the settings table MasterServerIP and BackendServerIP, it's also stored in a file somewhere... /etc/network/interfaces /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/hosts ... I have a partial fix...... Executing 'mythbackend' does restore the connection between the frontend and the backend, but it the connection is lost on a reboot. So, 'mythbackend' has to be executed again when rebooted. I took a look at the files interfaces, ifcfg-eth0 and hosts, and this is the output. /etc/network/interfaces Quote: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface # automatically added when upgrading auto lo eth0 iface lo inet loopback iface eth0 inet static address 192.168.0.115 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 gateway 192.168.0.250 /etc/sysconfig/network-scripts/ifcfg-eth0 Quote: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface # automatically added when upgrading auto lo eth0 iface lo inet loopback iface eth0 inet static address 192.168.0.115 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 gateway 192.168.0.250 /etc/hosts Quote: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface # automatically added when upgrading auto lo eth0 iface lo inet loopback iface eth0 inet static address 192.168.0.115 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 gateway 192.168.0.250 To me, this looks okay. How do I find the other file mentioned in your post? Dr. Hood

Author:	Dr. Hood [ Sun Sep 17, 2006 7:27 am ]
Post subject:
Here is more information when I execute 'mythbackend' as root. Quote: 2006-09-17 09:22:50.802 Using runtime prefix = /usr 2006-09-17 09:22:50.812 New DB connection, total: 1 2006-09-17 09:22:50.813 Connected to database 'mythconverg' at host: localhost 2006-09-17 09:22:50.816 Current Schema Version: 1123 Starting up as the master server. 2006-09-17 09:22:50.821 New DB connection, total: 2 2006-09-17 09:22:50.822 Connected to database 'mythconverg' at host: localhost 2006-09-17 09:22:50.826 New DB connection, total: 3 2006-09-17 09:22:50.826 Connected to database 'mythconverg' at host: localhost 2006-09-17 09:22:51.001 New DB scheduler connection 2006-09-17 09:22:51.001 Connected to database 'mythconverg' at host: localhost 2006-09-17 09:22:51.005 mythbackend version: 0.19.20060121-2 www.mythtv.org 2006-09-17 09:22:51.006 Enabled verbose msgs: important general 2006-09-17 09:22:51.006 AutoExpire: Found 1 recorders w/max rate of 72 MiB/min 2006-09-17 09:22:51.007 AutoExpire: Required Free Space: 2.1 GB w/freq: 10 min 2006-09-17 09:22:53.006 Reschedule requested for id -1. 2006-09-17 09:22:53.415 Scheduled 0 items in 0.4 = 0.41 match + 0.00 place 2006-09-17 09:22:53.417 Seem to be woken up by USER It stops with a blinking cursor and I just close the terminal. Maybe I should be executing this command as mythtv user and not as root. I am hopeful that the above will give a clue as to establishing a permament connection between the master backend server and the frontend. Any help will be greatly appreciated. Dr. Hood

Author:	Dr. Hood [ Sun Sep 17, 2006 9:21 am ]
Post subject:
SOLVED!!!! The trouble I was having was that after doing an upgrade from R5B7 to R5C7, the frontend was unable to connect to the master backend server evidenced by a 'cannot connect to master server...Is it running?' message appearing when attempting to watch LiveTV or view the Program Guide. The problem was the result of the /myth directory not having the right ownership, which was root access only. Changing the ownership of /myth to the user myth fixed the problem. These are the steps I used...At a command prompt, execute the following.... 1. ls -al / This command lists the permissions in the root directory. Verify that /myth only has root access. 2. chown mythtv:mytht /myth This command changes the user and group of /myth directory to 'mythtv'. That's it!!! Hope this helps others. Dr. Hood

Page 1 of 1	All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/