Author |
Message |
daskrabs
|
Posted: Sat Jan 20, 2007 9:05 am |
|
Joined: Mon Jan 15, 2007 3:45 pm
Posts: 1
|
Firstly, I'm a n00b. Secondly, I did try searching for the answer, so forgive me if the solution is trivial. I have a new install of R5E50. Backend and frontend are the same machine. I get the error:
"Could not connect to the master backend server..."
for just about everything I try to do. My front and back IP's are both 127.0.0.1 (default). Does one of them have to change? Thanks.
Also, how do I change the Time Zone?
|
|
Top |
|
|
thornsoft
|
Posted: Sat Jan 20, 2007 9:13 am |
|
Joined: Fri Nov 18, 2005 9:22 am
Posts: 777
Location:
spencerport, ny (USA)
|
Re-start the backend by pressing Alt+3 on the keyboard.
If it's chronic, consider my babysit_backend.sh script.
Code: http://mysettopbox.tv/phpBB2/viewtopic.php?t=13613
|
|
Top |
|
|
tjc
|
Posted: Sat Jan 20, 2007 10:14 am |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
It's a known bug. Restart the server as described. To cure it permanently edit /etc/init.d/mythtv-backend (you must become root to do this) and make the section under the start) case look like this:
Code: start) echo -n "Starting $DESC: $NAME" start-stop-daemon --start --pidfile $RUNDIR/$NAME.pid \ --chuid $USER --nicelevel $NICE --exec $DAEMON -- $ARGS echo "." ;;
This should mostly involve deleting the extraneous and buggy if wrapped around the call to start-stop-daemon. Remember that Linux is case sensitive and make sure that there's no whitespace following the \ on the third line.
|
|
Top |
|
|
whoa
|
Posted: Wed Jan 24, 2007 8:00 am |
|
Joined: Fri Oct 07, 2005 7:18 am
Posts: 77
Location:
Dallas, TX
|
TJC - that does not fix my backend not starting. I have to do /etc/init.d/mythtv-backend restart everytime I reboot. Anymore ideas?
|
|
Top |
|
|
thornsoft
|
Posted: Wed Jan 24, 2007 9:13 am |
|
Joined: Fri Nov 18, 2005 9:22 am
Posts: 777
Location:
spencerport, ny (USA)
|
whoa wrote: TJC - that does not fix my backend not starting. I have to do /etc/init.d/mythtv-backend restart everytime I reboot. Anymore ideas?
Try my script (above).
Edit: Obviously only useful if the backend CAN start, but doesn't always come up after reboot. If mythbackend is already running, then your problems lie elsewhere.
Last edited by thornsoft on Wed Jan 24, 2007 9:41 am, edited 1 time in total.
|
|
Top |
|
|
Dak48
|
Posted: Wed Jan 24, 2007 9:35 am |
|
Joined: Mon May 29, 2006 2:16 pm
Posts: 52
Location:
Lincoln, Nebraska
|
I noticed you said your frontend and backend are both using the loopback address of 127.0.0.1. To answer your question, yes your backend and frontend need separate and unique IP addresses in order to function properly. There are a few good howto's on the KnoppMyth wiki that cover this. You may want to consider referring to the howto's for Slave backend and nfs, as these both helped me get my system functioning.
_________________ Wouldn't it be really cool if Harley-Davidson made computers too?
|
|
Top |
|
|
whoa
|
Posted: Wed Jan 24, 2007 10:22 am |
|
Joined: Fri Oct 07, 2005 7:18 am
Posts: 77
Location:
Dallas, TX
|
thornsoft - I should have been more clear - I have tried your script and tjc's - neither work. I should also add that after I initially did my install of r5e50 it did work - but I had other issues going on at the time all of which are working or I have work arounds (much like this - the work around is - i restart the backend script) and now it does not work properly.
|
|
Top |
|
|
whoa
|
Posted: Wed Jan 24, 2007 7:02 pm |
|
Joined: Fri Oct 07, 2005 7:18 am
Posts: 77
Location:
Dallas, TX
|
Well - no one has suggested anything - what logs should I take a look at or where should I go so someone can help me?
Thanks for any help anyone can throw my way.
|
|
Top |
|
|
thornsoft
|
Posted: Wed Jan 24, 2007 7:04 pm |
|
Joined: Fri Nov 18, 2005 9:22 am
Posts: 777
Location:
spencerport, ny (USA)
|
whoa wrote: Well - no one has suggested anything - what logs should I take a look at or where should I go so someone can help me?
Thanks for any help anyone can throw my way.
Since it WAS working before, I'd try a re-install.
Then put things back in smaller increments, so you know where it fouled up.
|
|
Top |
|
|
tjc
|
Posted: Wed Jan 24, 2007 11:57 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
http://www.knoppmythwiki.org/index.php?page=CheckingLogFiles
BTW - Use pgrep to find out if the backend is running at all. It may just have the wrong connection info if the configuration got screwed up. This can happen for instance if you picked a different hostname during the upgrade, or get a different IP address via DHCP, or...
|
|
Top |
|
|
Steve Hosgood
|
Posted: Mon Feb 19, 2007 8:05 am |
|
Joined: Wed Oct 04, 2006 8:44 am
Posts: 17
Location:
Swansea, UK
|
My machine fails to start up every time. However, it's not down to the backend not running - the backend *is* running, it just doesn't seem to be able to do anything, and the frontend doesn't seem to be able to talk to it.
( This is a frontend + backend on the same machine BTW, I've not tried a separate frontend on it as yet. )
A known fix is to stop the frontend (frontend takes about 30 sec before pointing out that it can't talk to the backend before allowing the "do you really want to quit the frontend" box to appear). After this, I run bash in an xterm (right click on the destktop and select the correct option). I type "/etc/init.d/mythtv-backend stop" followed by "/etc/init.d/mythtv-backend start" followed by "mythfrontend". All is fine from then on, but it's a right PITA. It certainly kills any chance of a BIOS-rtc restart to record a programme for you at some point in the future after a powerdown.
So I wondered why the initial backend running on the machine was useless. I wondered if it had managed to come up too soon after the start of the "mysql" daemon, and that the mysql server wasn't running properly yet (notice that the processor is "only" 533MHz). So I added a "sleep 10" as the first command in the "start" case in the "mythtv-backend" script in /etc/init.d to see if that helped. It didn't.
So what on earth *is* wrong with that initial backend? It *is* an unusable backend BTW: if I just stop the frontend and restart it, that's not enough to fix anything, I do have to restart the backend itself.
Things I don't know: if I schedule a programme to record, and restart the machine to get into this "faulty backend" mode, does the programme record? I can try that tonight possibly. I also don't know if "/etc/init.d/mythtv-backend restart" is good enough to fix the situation, I've always used "stop" followed by "start" so far..
_________________ ChainTech 6ATA2 MoBo (533MHz PentiumIII Katmai, Via VT82C693A/686A chipset)
20Gb UDMA33 disk.
R5E50 plus keyboard fixes for UK.
1x Hauppauge Nova-T DVB-T card.
1x Bt848 Analog capture card.
SIS 6326 AGP2x Video card (too slow for watching TV).
|
|
Top |
|
|
bube
|
Posted: Fri Mar 09, 2007 7:39 pm |
|
Joined: Wed Apr 20, 2005 7:50 pm
Posts: 35
Location:
Germany
|
Hi,
I think this thread can be interesting for you.
Check if the socket of mythbackend is open.
Code: netstat -lnp | grep myth
good luck
bube
|
|
Top |
|
|
bjl
|
Posted: Mon Mar 12, 2007 11:53 am |
|
Joined: Tue Aug 29, 2006 1:47 pm
Posts: 3
|
I believe that I am having the same problem. I should note that it's possible that it's somehow related to running LCDd or that I had fixed the "C7 respawning" problem described in other threads. Here's my output:
Code: root@HTPC:/home/mythtv# /etc/init.d/mythtv-backend restart Restarting MythTV server: mythbackend. . root@HTPC:/home/mythtv# ps ax | grep myth 2959 ? Ss 0:00 /usr/bin/openvt -fwc 6 -- /bin/su - mythtv -c /usr/bin/startx 2972 ? Ss 0:00 /usr/bin/openvt -fwc 6 -- /bin/su - mythtv -c /usr/bin/startx 2973 ? S 0:00 /bin/su - mythtv -c /usr/bin/startx 2990 ? S 0:00 xinit /etc/X11/xinit/xinitrc -- /etc/X11/xinit/xserverrc -auth /home/mythtv/.serverauth.2974 3051 ? Ssl 0:19 mythfrontend 3072 ? Sl 0:00 /usr/bin/mythlcdserver -v none 3953 ? Ss 0:00 sshd: mythtv [priv] 3955 ? S 0:00 sshd: mythtv@ttyp1 3975 ? Ssl 0:00 /usr/bin/mythbackend --daemon --logfile /var/log/mythtv/mythbackend.log --pidfile /var/run/mythtv/mythbackend.pid root@HTPC:/home/mythtv# ps ax | grep mysql 2652 ? S 0:00 /bin/sh /usr/bin/mysqld_safe 2692 ? Sl 0:00 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-external-locking --port=3306 --socket=/var/run/mysqld/mysqld.sock 2693 ? S 0:00 logger -p daemon.err -t mysqld_safe -i -t mysqld root@HTPC:/home/mythtv# netstat -lnp | grep myth tcp 0 0 0.0.0.0:6545 0.0.0.0:* LISTEN 3072/mythlcdserver udp 0 0 0.0.0.0:32768 0.0.0.0:* 3072/mythlcdserver udp 0 0 192.168.0.30:5060 0.0.0.0:* 3051/mythfrontend unix 2 [ ACC ] STREAM LISTENING 12532 3062/gconfd-2 /tmp/orbit-mythtv/linc-bf6-0-3a9ec8d198a95 unix 2 [ ACC ] STREAM LISTENING 12540 3063/gnome-volume-m /tmp/orbit-mythtv/linc-bed-0-359c6795d38af root@HTPC:/home/mythtv# netstat -lnp | grep mysql tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 2692/mysqld unix 2 [ ACC ] STREAM LISTENING 9382 2692/mysqld /var/run/mysqld/mysqld.sock root@HTPC:/home/mythtv# tail -35 /var/log/mythtv/mythbackend.log 2007-03-12 12:58:11.238 Connected to database 'mythconverg' at host: localhost 2007-03-12 12:58:11.250 EITHelper: localtime offset -4:00:00 2007-03-12 12:58:37.515 Using runtime prefix = /usr 2007-03-12 12:58:37.540 New DB connection, total: 1 2007-03-12 12:58:37.545 Connected to database 'mythconverg' at host: localhost 2007-03-12 12:58:37.549 Current Schema Version: 1160 Starting up as the master server. 2007-03-12 12:58:37.555 New DB connection, total: 2 2007-03-12 12:58:37.557 Connected to database 'mythconverg' at host: localhost 2007-03-12 12:58:37.559 EITHelper: localtime offset -4:00:00 2007-03-12 12:58:37.563 New DB connection, total: 3 2007-03-12 12:58:37.564 Connected to database 'mythconverg' at host: localhost 2007-03-12 12:58:37.574 EITHelper: localtime offset -4:00:00 2007-03-12 13:00:08.193 Using runtime prefix = /usr 2007-03-12 13:00:08.219 New DB connection, total: 1 2007-03-12 13:00:08.224 Connected to database 'mythconverg' at host: localhost 2007-03-12 13:00:08.228 Current Schema Version: 1160 Starting up as the master server. 2007-03-12 13:00:08.234 New DB connection, total: 2 2007-03-12 13:00:08.236 Connected to database 'mythconverg' at host: localhost 2007-03-12 13:00:08.238 EITHelper: localtime offset -4:00:00 2007-03-12 13:00:08.241 New DB connection, total: 3 2007-03-12 13:00:08.242 Connected to database 'mythconverg' at host: localhost 2007-03-12 13:00:08.253 EITHelper: localtime offset -4:00:00 2007-03-12 13:50:27.405 Using runtime prefix = /usr 2007-03-12 13:50:27.430 New DB connection, total: 1 2007-03-12 13:50:27.435 Connected to database 'mythconverg' at host: localhost 2007-03-12 13:50:27.439 Current Schema Version: 1160 Starting up as the master server. 2007-03-12 13:50:27.445 New DB connection, total: 2 2007-03-12 13:50:27.447 Connected to database 'mythconverg' at host: localhost 2007-03-12 13:50:27.449 EITHelper: localtime offset -4:00:00 2007-03-12 13:50:27.452 New DB connection, total: 3 2007-03-12 13:50:27.453 Connected to database 'mythconverg' at host: localhost 2007-03-12 13:50:27.464 EITHelper: localtime offset -4:00:00
|
|
Top |
|
|
mjl
|
Posted: Mon Mar 12, 2007 3:27 pm |
|
Joined: Sun Jun 12, 2005 10:55 pm
Posts: 3161
Location:
Warwick, RI
|
HI,
Not sure who was on first however appears to be simular issues for all 3 or 4 posts. I was trying to pick out if these were installs, upgrades or broke it trying to "enhance" the KM. One was an R5E50, unk for the others
One thing that is a requirement for the backend to run is the hostname must stay the same as the original install. Yes, it is changeable but refer to mythtv.org for guidence. Edit the /etc/hostname to be what it was, reboot.
Also, if the paths to the proper storage areas are not correct this will cause the no backend. ie, /myth/tv /myth/video /myth/music and the rest. Simply go through all the setup screens to review.
Maybe that will help
Mike
|
|
Top |
|
|
bjl
|
Posted: Mon Mar 12, 2007 3:41 pm |
|
Joined: Tue Aug 29, 2006 1:47 pm
Posts: 3
|
I'm on a clean installation of R5E50 (Rob Levin). I've completely reinstalled (auto) once in order to get rid of this problem--it looks like I'm going to try again. Previously, I installed a frontend/backend auto-install in a similar system that didn't run into either of this problems (C7 respawning or backend not opening ports).
Thanks for the input about the storage locations, I've only been dealing with tv recordings, no videos, music, or pictures, but it's worth a shot.
In response to trying to "'enhance' the KM"-- on the broken system, I definately am doing something different than the norm (for me) by setting up the lcd server.
|
|
Top |
|
|