Messages

1

Users / Re: Mythfrontend only runs for 30 seconds?

« on: May 29, 2007, 08:56:36 am »

Also (and I'm not sure if it would cause this or what it would do without it) have you changed /etc/mythtv/mysql.txt to point at your existing backend?

UPDATE:  I just looked again at fixMythTvSettings.sh and it does use the db info from mysql.txt, make sure that's correct.  You want it to update the settings on your backend, not the core.

2

Users / Re: Mythfrontend only runs for 30 seconds?

« on: May 29, 2007, 08:43:29 am »

I added routerip="mybackendip"; below the line already there and reran the script.  Sorry that didn't fix your problem, you may want to look at, /var/log/pluto/*MythTV_Player.log on the MD and see if it helps with why the frontend is dying/restarting.  With my networkcontrolport problem I had lots of:

Going to send command jump livetv
Connect() failed, Error Code 111 (Connection refused))

messages.  I would get live tv for about 30 seconds then the player (being unable to connect to the frontend) would kill the process and restart the frontend.

3

Users / Re: Mythfrontend only runs for 30 seconds?

« on: May 27, 2007, 09:30:11 pm »

I have the same setup (using an existing backend) and had the same problem.  Pluto doesn't use the default Myth configuration, this problem is from the NetowkrControlPort setting (default Myth uses 6546, default Pluto is 10001).  Have a look at /usr/pluto/bin/fixMythTvSettings.sh on a MD and you'll find all the settings it changes. I changed routerip= to point to my existing backend and everything works fine.