| Author |
Message |
|
ceenvee703
|
 Posted: Thu Oct 27, 2005 10:10 am |
|
|
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location:
Virginia, USA
|
Quote: P.S. Here are the two mysql.txt files I found in the filesystem of my current FE, which is booted off the CD (no hard drive connected) in its FE-only mode. I haven't edited either one of them, but they're quite different
That makes sense to me: one's the version off of the CD (unmodified) and one's the modified version sitting on a RAM disk or whatever that's being used to boot from (since you can't change the settings on a CD).
Instead, change either /etc/mythtv/mysql.txt or /usr/share/mythtv/mysql.txt on a hard disk install. You'll find changing one changes the other (at least it does for me), because there's only one file.
|
|
| Top |
|
 |
|
greenstalk
|
Posted: Thu Oct 27, 2005 10:17 am |
|
|
Joined: Wed Mar 30, 2005 3:47 am
Posts: 56
|
|
Okay, I'll try that; I'm in the middle of the MBE reinstall, so it'll be a while.
It could be that -that's- where I recalled seeing a symlink (I kept forgetting to look in /usr/share); in that case, if the copy in /home/mythtv/.mythtv/mysql.txt isn't used, then the LINHES instructions definitely do point to the wrong file. But I can't confirm that until my reinstall completes (at least :)
Thanks!
|
|
| Top |
|
|
|
greenstalk
|
Posted: Thu Oct 27, 2005 11:57 am |
|
|
Joined: Wed Mar 30, 2005 3:47 am
Posts: 56
|
Okay, I'm pretty convinced that there's a big fat bug here, and I'd be very interested indeed if someone can replicate my installation and -not- get the errors I'm seeing, or can find some hole in what I'm doing. My entire log of what I did is reproduced below, plus some discussion at the end, followed by a couple of logs of output from running mythfrontend.
Unless someone can figure out the bug or figure out what I'm doing wrong, I think my only alternative is going to be to try installing A16 instead and see if I still see the behavior there. That'll take a couple of hours at least, and I'll hold off for a few hours while I do other things.
Thanks!
Code: full auto install to MBE machine (192.168.0.20):
picked menu option "2. Auto Install"
preferred hostname: myth-master-backend [no FQDN anywhere!]
unsupported HSync/VSync X mode upon reboot, hence:
[aargh! no net yet! so -this- didn't work... :) ] C-A-F1, aptitude, "u", "/emacs", "g g"; fix /etc/X11/XF86Config-4; /etc/init.d/gdm restart
[okay, edit it in nano] fix /etc/X11/XF86Config-4; /etc/init.d/gdm restart
now i'm sitting at the "please provide root Password: " prompt
no to DHCP broadcast, and now i'm in the blank-as-cursor regime
entered a pw for MythWeb that was -not- "mythtv" (picked same as my root, for now)
yes to bootsplash (somewhere in here)
picked i686 modules
i -think- it said something about "answer no to the following two questions", but it scrolled off the screen!
answered YES anyway, just in case, to the bash-your-cards & bash-your-channels questions at the start of mythtv-setup
changed IP address for myth-master-backend from 127.0.0.1 to 192.168.0.20
changed IP address for "Master Server" from 127.0.0.1 to 192.168.0.20
adjusted Live TV buffer down to 12GB (could this still be slightly too high? 12601724 blocks free; 12GB = (* 12 1024 1024) = 12582912; very close...
configured capture cards
configured video sources & retrieved lineups
got "ch3 does not exist" errors; did "No, I know what I'm doing"
got "if this is MBE, please run mythfilldatabase"; hit okay, whereupon it asked for my zipcode for MythWeather
then it went ahead & ran mythfilldatabase for me
asked for my zipcode again, after "tweaks based on our SQL settings"
spit out a bunch o' errors i couldn't read in time
Watch TV works
backend shut down for CD move.
backend back up; Watch TV still works
edited /etc/lilo.conf to change vga=488 to vga=normal & ran lilo -v
rebooted; Watch TV still works
[note that I have -not- edited /etc/hosts yet! I'll hold off for now...]
ssh'ed in. /usr/share/mythtv/mysql.txt is a symlink to /etc/mythtv/mysql.txt
there is -no- /home/mythtv/.mythtv/mysql.txt! that dir contains only: (dirs MythPhone, channels, themecache), (file lircrc)
left the MBE up & started in on the FE
CD-FE-only install on FE machine (192.168.0.21):
picked menu option "1. Frontend"
current configuration is:
DBHostName=localhost
DBUserName=mythtv
DBPassowrd=mythtv
DBName=mythconverg
LocalHostName=mythfe1
is this what you want? answered NO
IP address of backend server: 192.168.0.20
username for database: mythtv
password for database: mythtv
name for database: mythconverg
unique hostname of this machine: myth-frontend [no FQDN!]
current configuration is:
DBHostName=192.168.0.20
DBUserName=mythtv
DBPassowrd=mythtv
DBName=mythconverg
LocalHostName=myth-frontend
is this what you want? answered YES
use DHCP broadcast? answered NO
IP address for eth0: 192.168.0.21
netmask 255.255.255.0
broadcast 192.168.0.255
gatewawy 192.168.0.1
nameservers [a nameserver out on the net I use for all my machines here]
KnoppMyth X background comes up
Select your preferred language: English
"Myth could not connect to the database. Please verify your settings below."
(and now I'm in the "Database Configuration 1/2" screen)
the "host name" it's showing is 192.168.0.20, which is the IP address of the MBE.
Database Configuration 2/2 has "use custom identifier for frontend
preferences" auto-checked, and the identifier is "myth-frontend"
interestingly, -BEFORE- I reinstalled the MBE, the CD-FE got farther
before complaining that it couldn't talk to the database (e.g., all
the way to letting me hit Watch TV before complaining). Now, it
complained and didn't even put up the frontend scrren; I've got just
the X background sitting on the LCD.
ran mythfrontend in a script window. saw lots of errors of the form
"Can't connect to MySQL server on '192.168.0.20'"
Edited /etc/mysql/my.cnf on MBE and commented-out "skip-networking".
Rebooted MBE.
on FE, reran mythfrontend, to a different script file. this time it
got through initialization and showed me a GANT-theme homepage.
BUT TRYING "WATCH TV" -STILL- SAYS "Could not connect to the master
backend server -- is it running? Is the IP address set for it in the
setup program correct?"
THERE IS DEFINITELY A BUG HERE!
The two script files are appended below. It's pretty damned clear to
me that SOMETHING is buggy, because the FE manages to connect to the
MBE database enough to bring up the homepage, but THEN starts trying
to connect to localhost instead when I try "Watch TV"!
Second try with FE: rebooted from CD, now using this as my configuration:
DBHostName=192.168.0.20
DBUserName=mythtv
DBPassowrd=mythtv
DBName=mythconverg
LocalHostName=mythtv
(same as above EXCEPT that I'm trying LocalHostName of mythtv and
-not- either myth-frontend -or- the default mythfe1; I'm doing this
only because the very start of this thread claimed that this was the
only thing that made -their- FE's work...)
No change in behavior: still claims it can't talk to the database
if I try Watch TV.
If I look at /ramdisk/home/knoppix/.mythtv/mysql.txt, it's got my
settings: it believes the DBHostName is 192.168.0.20, and the
localname is mythtv
If I tail /var/log/mysql/mysql.log on the MBE, and then start up
mythfrontend on the FE, the logfile instantly spits out a huge number
of queries which all have a hostname of "mythtv" in them.
My guess? Something, somewhere, has a hardcoded hostname in it when
it -should- be taking the hostname from the configuration. And it's
probably only in one spot---hence things -almost- start up, but some
actions fail.
So what do I do now? I'm thinking, "throw in the towel on A22 and
install fromk A16 and see if this behavior happens there." It'll
take me another couple of hours to try reproducing this there, but
I don't have any other options unless someone can figure out what's
going on here.
Starting up mythfrontend on the FE machine -after- editing my.cnf on the SBE to comment-out "skip-networking": Code: Script started on Thu Oct 27 13:23:18 2005
knoppix@ttyp1[knoppix]$ mythfrontend
2005-10-27 13:23:22.411 Using runtime prefix = /usr
2005-10-27 13:23:22.450 New DB connection, total: 1
2005-10-27 13:23:25.237 Total desktop dim: 1024x768, with 1 screen[s].
2005-10-27 13:23:25.263 Using screen 0, 1024x768 at 0,0
2005-10-27 13:23:25.272 mythfrontend version: 0.19.20050712-1 www.mythtv.org
2005-10-27 13:23:25.272 Enabled verbose msgs : important general
2005-10-27 13:23:26.105 Total desktop dim: 1024x768, with 1 screen[s].
2005-10-27 13:23:26.127 Using screen 0, 1024x768 at 0,0
2005-10-27 13:23:26.135 Switching to square mode (G.A.N.T.)
mythtv: could not connect to socket
mythtv: Connection refused
lirc_init failed for mythtv, see preceding messages
2005-10-27 13:23:26.667 Joystick disabled.
2005-10-27 13:23:30.252 Registering Internal as a media playback plugin.
2005-10-27 13:23:30.696 Inserting MythDVD initial database information.
2005-10-27 13:23:30.706 New DB connection, total: 2
2005-10-27 13:23:30.708 Upgrading to MythDVD schema version 1001
2005-10-27 13:23:30.725 Registering MythDVD DVD Media Handler as a media handler
2005-10-27 13:23:30.726 Registering MythDVD VCD Media Handler as a media handler
2005-10-27 13:23:30.904 Inserting MythGallery initial database information.
2005-10-27 13:23:30.905 Upgrading to MythGallery schema version 1000
2005-10-27 13:23:33.537 Inserting MythMusic initial database information.
2005-10-27 13:23:33.537 Upgrading to MythMusic schema version 1000
2005-10-27 13:23:33.540 Upgrading to MythMusic schema version 1001
2005-10-27 13:23:33.541 New DB connection, total: 3
2005-10-27 13:23:33.542 Upgrading to MythMusic schema version 1002
2005-10-27 13:23:33.558 Updating music metadata to be UTF-8 in the database
2005-10-27 13:23:33.559 Done updating music metadata to UTF-8
2005-10-27 13:23:33.559 Upgrading to MythMusic schema version 1003
2005-10-27 13:23:33.560 Upgrading to MythMusic schema version 1004
2005-10-27 13:23:33.597 Upgrading to MythMusic schema version 1005
2005-10-27 13:23:34.850 Registering MythMusic Media Handler as a media handler
2005-10-27 13:23:35.256 Inserting MythPhone initial database information.
2005-10-27 13:23:35.257 Upgrading to MythPhone schema version 1000
2005-10-27 13:23:35.259 Upgrading to MythPhone schema version 1001
SIP: Creating autogen directory entry for this host
2005-10-27 13:23:35.507 Inserting MythVideo initial database information.
2005-10-27 13:23:35.507 Upgrading to MythVideo schema version 1000
SIP listening on IP Address 192.168.0.21:5060 NAT address 192.168.0.21
2005-10-27 13:23:35.512 Upgrading to MythVideo schema version 1001
SIP: Cannot register; proxy, username or password not set
2005-10-27 13:23:35.532 Upgrading to MythVideo schema version 1002
2005-10-27 13:23:35.544 Upgrading to MythVideo schema version 1003
2005-10-27 13:23:35.557 Upgrading to MythVideo schema version 1004
2005-10-27 13:23:35.558 Upgrading to MythVideo schema version 1005
2005-10-27 13:24:14.939 Connecting to backend server: localhost:6543 (try 1 of 5)
2005-10-27 13:24:14.939 Connection timed out.
You probably should modify the Master Server
settings in the setup program and set the
proper IP address.
2005-10-27 13:24:16.872 Attempting to change from None to None
2005-10-27 13:24:30.155 Connecting to backend server: localhost:6543 (try 1 of 5)
2005-10-27 13:24:30.155 Connection timed out.
You probably should modify the Master Server
settings in the setup program and set the
proper IP address.
2005-10-27 13:24:59.144 Attempting to change from None to None
2005-10-27 13:25:03.203 Connecting to backend server: localhost:6543 (try 1 of 5)
2005-10-27 13:25:03.203 Connection timed out.
You probably should modify the Master Server
settings in the setup program and set the
proper IP address.
Destroying SipFsm object
knoppix@ttyp1[knoppix]$ exit
Script done on Thu Oct 27 13:25:15 2005
Starting up mythfrontend -before- editing my.cnf. This probably isn't so useful, but whatever... Code: File Edit Options Buffers Tools Help
Script started on Thu Oct 27 13:19:27 2005
knoppix@ttyp1[knoppix]$ mythfrontend
2005-10-27 13:19:30.812 Using runtime prefix = /usr
2005-10-27 13:19:30.851 New DB connection, total: 1
2005-10-27 13:19:30.877 Unable to connect to database!
2005-10-27 13:19:30.902 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
2005-10-27 13:19:31.024 Unable to connect to database!
2005-10-27 13:19:31.049 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
2005-10-27 13:19:31.171 Database not open while trying to load setting: GuiVidModeResolution
2005-10-27 13:19:31.196 Unable to connect to database!
2005-10-27 13:19:31.220 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
2005-10-27 13:19:31.342 Database not open while trying to load setting: GuiVidModeWidth
2005-10-27 13:19:31.367 Unable to connect to database!
2005-10-27 13:19:31.391 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
2005-10-27 13:19:31.513 Database not open while trying to load setting: GuiVidModeHeight
2005-10-27 13:19:31.538 Unable to connect to database!
2005-10-27 13:19:31.563 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
2005-10-27 13:19:31.685 Database not open while trying to load setting: DisplaySizeResolution
2005-10-27 13:19:31.710 Unable to connect to database!
2005-10-27 13:19:31.734 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
2005-10-27 13:19:31.856 Database not open while trying to load setting: DisplaySizeWidth
2005-10-27 13:19:31.881 Unable to connect to database!
2005-10-27 13:19:31.905 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
2005-10-27 13:19:32.027 Database not open while trying to load setting: DisplaySizeHeight
2005-10-27 13:19:32.052 Unable to connect to database!
2005-10-27 13:19:32.076 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
2005-10-27 13:19:32.198 Database not open while trying to load setting: TVVidModeResolution
2005-10-27 13:19:32.223 Unable to connect to database!
2005-10-27 13:19:32.247 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
[ . . . lots moe like this deleted . . . ]
2005-10-27 13:19:33.532 Database not open while trying to load setting: Language
2005-10-27 13:19:34.802 Unable to connect to database!
2005-10-27 13:19:34.802 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
2005-10-27 13:19:34.802 Database not open while trying to save setting: Language
2005-10-27 13:19:34.815 Unable to connect to database!
2005-10-27 13:19:34.815 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
2005-10-27 13:19:34.815 Database not open while trying to load setting: Language
2005-10-27 13:19:34.816 Unable to connect to database!
2005-10-27 13:19:34.816 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
2005-10-27 13:19:34.816 Database not open while trying to save setting: Language
2005-10-27 13:19:34.817 Unable to connect to database!
2005-10-27 13:19:34.817 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
2005-10-27 13:19:36.366 Unable to connect to database!
2005-10-27 13:19:36.366 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.0.20' (111)
2005-10-27 13:19:36.366 Failed to init MythContext, exiting.
knoppix@ttyp1[knoppix]$ exit
Script done on Thu Oct 27 13:19:40 2005
|
|
| Top |
|
|
|
cesman
|
Posted: Thu Oct 27, 2005 12:43 pm |
|
|
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location:
Fontana, Ca
|
I tested using the CD as a frontend (again) and it just works (given a properly configured backend). Did you review the logs you posted?
cough cough
Code: 2005-10-27 13:25:03.203 Connection timed out.
You probably should modify the Master Server
settings in the setup program and set the
proper IP address.
_________________
cesman
When the source is open, the possibilities are endless!
|
|
| Top |
|
|
|
ceenvee703
|
Posted: Thu Oct 27, 2005 1:03 pm |
|
|
Joined: Fri Apr 02, 2004 10:08 am
Posts: 1637
Location:
Virginia, USA
|
greenstalk wrote: changed IP address for myth-master-backend from 127.0.0.1 to 192.168.0.20
changed IP address for "Master Server" from 127.0.0.1 to 192.168.0.20
I would double-check that these settings actually got set on your master backend by re-running mythtv-setup. One thing about MythTV config screens is that you seem to have to get all the way through all config screens and use the "finish" button at the end in order to have the changes actually be set. If you just enter the numbers and somehow exit the screen, the changes won't be made.
Also, I'm not sure why you would wait to do the steps required on your master backend specified here:
http://www.knoppmythwiki.org/?id=KnoppM ... l#frontend
I would do those steps from the outset before you tried to run your remote frontend. From what you described, that was not the case.
|
|
| Top |
|
|
|
greenstalk
|
Posted: Thu Oct 27, 2005 1:06 pm |
|
|
Joined: Wed Mar 30, 2005 3:47 am
Posts: 56
|
|
But I -DID- modify them!
Look, it's definitely making a connection to the database. You see that, right? The MBE database logs hundreds of queries every time I do anything on the FE.
If I now start mythtv-setup on the FE, it claims "IP address for mythtv" is 127.0.0.1 (which is NOT how I configured it!), so something's changing it behind my back. It -does- claim "Master Server IP address" is -still- 192.168.0.20, which is the MBE's IP.
So I've just changed the 127.0.0.1 back to 192.168.0.21. I also noticed that mythtv-setup has magically changed the directories to which to save video to /var/lib/mythtv/ and /var/cache/mythtv, and it's warning me about them on exit. I'm leaving them pointing to /var at the moment and exiting mythtv-setup.
And now I'm starting mythfrontend again, and whattya know, it -still- complains that it can't talk to the backend when I try Watch TV.
Is there some -other- place I should be changing? If so, -where-???
Note that I'm still running the FE booted off the CD (no hard disk plugged into the FE right now), and the MBE configuration is still identical; I hadn't touched any configuration between sending my last post and reading yours.
|
|
| Top |
|
|
|
greenstalk
|
Posted: Thu Oct 27, 2005 1:16 pm |
|
|
Joined: Wed Mar 30, 2005 3:47 am
Posts: 56
|
ceenvee703 wrote: greenstalk wrote: changed IP address for myth-master-backend from 127.0.0.1 to 192.168.0.20
changed IP address for "Master Server" from 127.0.0.1 to 192.168.0.20 I would double-check that these settings actually got set on your master backend by re-running mythtv-setup. One thing about MythTV config screens is that you seem to have to get all the way through all config screens and use the "finish" button at the end in order to have the changes actually be set. If you just enter the numbers and somehow exit the screen, the changes won't be made. I've been going all the way through to "finish". In any event, I just exited mythfrontend on the MBE and started mythtv-setup on it. The "Host Address Backend Setup" scren is claiming that both IP's are 192.168.0.20, which are the correct IP's for the MBE. Is there somewhere else I should be looking? Quote: Also, I'm not sure why you would wait to do the steps required on your master backend specified here: http://www.knoppmythwiki.org/?id=KnoppM ... l#frontendI would do those steps from the outset before you tried to run your remote frontend. From what you described, that was not the case. I think you've misread something. I -did- forget to comment-out skip-networking the first time, but I fixed that and rebooted the MBE (that was my "first" long log at the end of my post, the "second" one was -before- I remembered to do that, so they're reversed chronologically, and I probably should have just omitted the second one entirely to avoid confusion).
I've also run mythtv-setup on the MBE (right now I'm actually looking at it), and both IP's are set to the MBE's IP address.
I don't -see- anything -else- I should be doing in those instructions that I have not done. I've tried booting the FE from CD, twice, once with its local hostname called "myth-frontend" and once called "mythtv". I have -not- tried booting that CD and letting it default to "mythfe1" because the very first posters in this thread claimed that didn't work, but I can try that if you think it matters.
Am I missing something here?
|
|
| Top |
|
|
|
jakep_82
|
Posted: Thu Oct 27, 2005 1:27 pm |
|
|
Joined: Thu Oct 13, 2005 9:18 am
Posts: 91
Location:
Washington
|
|
cesman,
Would it be possible for you to post the contents of your mysql.txt files from your backend as well as your frontend? This would help clarify what settings go where (since your setup works correctly).
|
|
| Top |
|
|
|
greenstalk
|
Posted: Thu Oct 27, 2005 1:27 pm |
|
|
Joined: Wed Mar 30, 2005 3:47 am
Posts: 56
|
cesman wrote: I tested using the CD as a frontend (again) and it just works (given a properly configured backend). Did you review the logs you posted? Of course. That's why I posted them. Quote: cough coughCode: 2005-10-27 13:25:03.203 Connection timed out.
You probably should modify the Master Server
settings in the setup program and set the
proper IP address.
Look, I'm really not sure how I can be clearer here. I am seeing the FE make hundreds of queries to the MBE on certain operations, like starting up mythfrontend. And -yet- it complains, for SOME of its UI operations, that it can't talk to the backend (e.g,. Watch TV). All of the relevant IP settings seem to be correct (and if they weren't, wouldn't it make sense that ZERO queries to the SQL database on the MBE would arrive?)
It's really looking to me like certain parts of the frontend are failing to use the configured IP address and are falling back to the loopback address instead. I have no idea how to effectively debug this. (Where's the source to A22, for starters? Not that it makes loads of sense for me to dive in having never seen them before, but maybe it would help...)
I am curious to know whether anyone, anyone at all, has actually started from a virgin machine, allowed A22 to completely partition (not upgrade), installed and tested an MBE, and then booted the A22 CD as a frontend on a second machine and successfully gotten "Watch TV" to not return an error. If someone has done that entire sequence, I would be very, very interested in seeing every config file they can throw at me, so I can compare them to mine. But I'm still not sure if anyone has actually done this.
|
|
| Top |
|
|
|
cesman
|
Posted: Thu Oct 27, 2005 1:41 pm |
|
|
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location:
Fontana, Ca
|
|
I'm simply (re)posting what I saw in your log. It doesn't matter if one does an install or an upgrade. In either case, / is wiped clean. If you have an SBE or FE only, one still has to modify my.cnf and restart MySQL. The only difference is the IP entry is the database as this is restored. I've already posted my mysql.txt in the LinHES doc.
_________________
cesman
When the source is open, the possibilities are endless!
|
|
| Top |
|
|
|
jakep_82
|
Posted: Thu Oct 27, 2005 1:45 pm |
|
|
Joined: Thu Oct 13, 2005 9:18 am
Posts: 91
Location:
Washington
|
Quote: But I'm still not sure if anyone has actually done this
I did. Watch TV worked fine. I was not able to watch recorded programs though, and it only worked if the LocalHostName on the FE was set to mythtv (my BE's hostname is mythtv also). When I tried to watch a recorded program on the FE it tried to connect to localhost:6543.
|
|
| Top |
|
|
|
greenstalk
|
Posted: Thu Oct 27, 2005 2:04 pm |
|
|
Joined: Wed Mar 30, 2005 3:47 am
Posts: 56
|
cesman wrote: I'm simply (re)posting what I saw in your log. It doesn't matter if one does an install or an upgrade. In either case, / is wiped clean. If you have an SBE or FE only, one still has to modify my.cnf and restart MySQL. The only difference is the IP entry is the database as this is restored. I've already posted my mysql.txt in the LinHES doc.
In my current debugging, where I've got an installed MBE and am running the FE from CD, do I need to have modified any mysql.txt files? If so, on which hosts? The one on my MBE (in /etc/mythtv/mysql.txt) used to say DBHostName=localhost; I just changed it to be DBHostName=192.168.0.20 and rebooted the MBE; no change in behavior on the FE.
Does the -FE- need any changes to its local mysql.txt files, -even if it's theoretically been configured to look at the MBE by mythtv-setup-? Note that I'm not (currently) trying to get the FE to be an SBE; I'm just trying to get it to be an FE at the moment.
You've posted the contents of your SBE's mysql.txt at linhes.html; I don't see that you've made any modifications to the MBE's mysql.txt file (so perhaps my experimental mod to mine was pointless; it sure seems to have done nothing to change any behavior). Must I modify the mysql.txt on my FE just to make it a frontend? Even though I answered its config questions? [I should point out that my CD-booted FE's copy of /ramdisk/home/knoppix/.mythtv/mysql.txt is currently saying that the DBHostName=192.168.0.20, which is correct, and that its LocalHostName is mythtv, which is how I've most-recently configured it. Is that the right copy of the file to be looking at?]
One thing I'd be curious about would be an installation on -your- machines using other names, e.g., not "mbe" or "sbe" but perhaps "moe" and "curly", just in case something's using something hardwired instead of the configuration variables. I'm worried that it works for you because you always choose the same names, and anyone who's chosen different names might be getting screwed by a missing variable somewhere.
|
|
| Top |
|
|
|
greenstalk
|
Posted: Thu Oct 27, 2005 2:23 pm |
|
|
Joined: Wed Mar 30, 2005 3:47 am
Posts: 56
|
jakep_82 wrote: Quote: But I'm still not sure if anyone has actually done this I did. Watch TV worked fine. I was not able to watch recorded programs though, and it only worked if the LocalHostName on the FE was set to mythtv (my BE's hostname is mythtv also). When I tried to watch a recorded program on the FE it tried to connect to localhost:6543. That's interesting. So you started from a blank machine, did an Auto Install to get an MBE, then booted the CD for a FrontEndOnly install on a different machine? Using A22 in both cases? Can you post /etc/mythtv/mysql.txt from the front- and backend machines, and also /etc/mysql/my.cnf from the backend? (And anything else anyone can think of, really...) Also, can you verify that /usr/share/mythtv/mysql.txt is indeed a symlink to /etc/mythtv/mysql.txt?
I'm wondering if the reason "Watch TV" is working for you is precisely because the FE and BE are both claiming to have the same hostname. This would be consistent with some sort of localhost-sometimes bug. And I'm wondering having those names be the same might be causing the FE to conclude that, since they match, recordings must be on the "same" host, rewriting that to localhost, and then failing.
(This is all without benefit of seeing the source, of course, since I'm not sure where the source -is- for A22's version of everything.)
Also: When "Watch TV" works for you, it's using a tuner on the BACK-end machine, right? You either have no tuners on your FE, or at least you're using a BE tuner, right?
|
|
| Top |
|
|
|
bjenx
|
Posted: Thu Oct 27, 2005 4:27 pm |
|
|
Joined: Tue Oct 25, 2005 3:22 pm
Posts: 7
Location:
Utah
|
I have not been able to connect yet either, so before doing a reinstall, I have been trying to verify that my settings are being updated in the mysql database. I have also been checking a friends settings to see where mine might be different.
I looked at the setting for the BE database and this is what I have for the Master and Backend Server IP
mysql> Select * from settings where data = "192.168.1.5";
+--------------------+---------------+------------+
| value | data | hostname |
+--------------------+---------------+------------+
| MasterServerIP | 192.168.1.5 | mythtv |
| BackendServerIP | 192.168.1.5 | mythtv |
+--------------------+---------------+-----------+
Now I conpaired this to a friends settings, he is running MythTV 0.17 on Suse, but this is what we saw mysql> Select * from settings where data = "192.168.100.6";
+--------------------+---------------+------------+
| value | data | hostname |
+--------------------+---------------+------------+
| MasterServerIP | 192.168.1.5 | mythtv |
| BackendServerIP | 192.168.1.5 | null |
+--------------------+---------------+------------+
His host name for the backend server is null. I am wondering if it is only using the BackendServerIP for a hostname of mthytv, and this is why it will connect on the FE when the hostname mythtv is used. I would try this, but I am at work right now, and not able to see what happens.
|
|
| Top |
|
|
|
greenstalk
|
Posted: Thu Oct 27, 2005 5:48 pm |
|
|
Joined: Wed Mar 30, 2005 3:47 am
Posts: 56
|
More data points:
On my MBE, here's what I get if I do the same SQL query:
Code: # mysql
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 13 to server version: 4.0.22-log
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> use mythconverg
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> select * from settings where data = "192.168.0.20";
+-----------------+--------------+---------------------+
| value | data | hostname |
+-----------------+--------------+---------------------+
| MasterServerIP | 192.168.0.20 | myth-master-backend |
| BackendServerIP | 192.168.0.20 | myth-master-backend |
+-----------------+--------------+---------------------+
2 rows in set (0.00 sec)
mysql> If I try it on the FE (still sitting there running off the CD, as before), I get: Code: # mysql
ERROR 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
#
However, I have no idea if just trying to invoke mysql this way on a FE is supposed to work in the first place. And since I can see hundreds of queries being logged in the MBE's SQL log whenever I try starting up mythfrontend on the FE machine, my conclusion is that mythfrontend, at least, -does- know how to talk to the MBE's SQL database, even if I don't know how from the command line.
Dunno if this will be helpful at all, but there it is.
|
|
| Top |
|
|
View unanswered posts
View active topics
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register
