Re: [mythtv-users] Setting up slave backend system
On Tue, 2005-09-20 at 16:04, Bruce Markey wrote: > Scot L. Harris wrote: > > One thing I noticed was that when running mythtv-setup there does not > > appear to be a way to delete/remove individual capture cards. There is > > Press "D" for the delete popup. > Thanks. Will use that next time. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
Scot L. Harris wrote: First I would like to thank everyone that contributed help on this problem. I believe I have success in getting the SBE setup and working. :) At least the tests so far are good. I have found a few things that I need to understand better but I now understand it enough that I believe I can consistently set up a SBE and a MBE. Used FC3 on the MBE and FC4 on the SBE with 0.18.1 mythtv from ATRPMS. 1. a single mysql instance is needed on the MBE, no where else. Correct. I do have multiple databases and each is a different test environments. I can connect frontends and backends to an environment by controlling which mysql.txt file is used. Technically, the mysqld doesn't have to be running on the same host as the master but that is the obvious choice for performance reasons. Wherever the DB is, each process that connects to the same database is part of the same environment. 2. I found three copies of mysql.txt on both the MBE and the SBE. ... I am not clear on why there are three copies of this file scattered on Don't know why there are three on your system but in general, there is one in myth's installed share directory but this will be overwritten with each upgrade. Therefore, it looks to see if there is a file for $HOME/.mythtv/mysql.txt of the userid that is running the program. One thing I noticed was that when running mythtv-setup there does not appear to be a way to delete/remove individual capture cards. There is Press "D" for the delete popup. -- bjm ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
First I would like to thank everyone that contributed help on this problem. I believe I have success in getting the SBE setup and working. :) At least the tests so far are good. I have found a few things that I need to understand better but I now understand it enough that I believe I can consistently set up a SBE and a MBE. Used FC3 on the MBE and FC4 on the SBE with 0.18.1 mythtv from ATRPMS. 1. a single mysql instance is needed on the MBE, no where else. 2. I found three copies of mysql.txt on both the MBE and the SBE. The DBHostName needs to be set to the IP or name (assuming you have /etc/hosts or DNS setup) pointing to the system that has the mysql database, in my case that was the MBE. This I believe was the major problem in getting the SBE setup. I am not clear on why there are three copies of this file scattered on the sytem, I assume it is the result of the guide I used and the ATRPMS packages. Not sure which actually controls this or if all three are needed. I just made sure they were consistent. 3. When setting up the MBE make sure the name or actual IP address is specified for the MBE, do not leave that as 127.0.0.1. I think this was the last part I needed to find to get this all working. It maybe that using ATRPMS and mythtv-suite to install the packages may not be the best way to setup an SBE. Obviously this will install many packages that are not needed on an SBE. At the time this seemed to be the way to do this. One thing I noticed was that when running mythtv-setup there does not appear to be a way to delete/remove individual capture cards. There is an option at startup to clear the capture cards. If the option to clear capture cards is selected when running mythtv-setup on the SBE please note that you need to run mythtv-setup again on the MBE (should actually run this first before running it again on the SBE) since this apparently clears ALL capture cards. This part confused me at first but once I realized what was going on it was easy to resolve. (this did cost me some recordings from last night but they will be on again sometime) I also noticed that via mythweb on the status page that it does list all of the capture cards but does not list the show the card on the SBE is recording like it does for those cards on the MBE. And to wrap this up, I am sorry if my confusion caused problems here on the list. I was just trying to get a better understanding of how mythtv works and is configured, and in the process get an SBE setup. This is one of the more useful applications out there and it works extremely well. Kudos to all the developers and people that answer questions here on the list. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
Isaac Richards wrote: ... Everything's stored in the same central database. Cards don't show up on the master because it requires local access to the card to probe the various available settings & inputs. This is the correct information for this part of the thread but ironically, Scot's problem is that everything was not stored in the same central database. I did a test this morning that may shed some light on why Scot and many before him have gotten into a confusing state. Say there is a host "alpha" (192.168.0.1) running mysqld and MBE and the user starts to set up a slave on "bravo" (192.168.0.2). Either there was a mysqld installed on bravo in his distribution or he thought he was supposed to run a mysqld on the slave. Next he runs mythtv-setup that unwittingly connects to the local host or thought he was supposed to connect to the mysqld on the local machine. Either way, he fills in the IP address for "bravo" as 192.168.0.2 and sets "Master Server IP address:" 192.168.0.1(!). Now when he start mythbackend, it will make a connections to a mythbackend master server on it's port on alpha and report: Running as a slave backend. ... 2005-09-20 11:10:05.795 Connecting to master server: 192.168.0.1:6543 However the mysqld on alpha will know nothing of this slave or any of the configuration that was written to the mysqld on bravo. This also suggests that if a frontend was run on bravo it may be able to find the master and run live TV but the EPG is empty because the program data is in alpha's DB and the frontend is connecting to bravo's DB where the program table is empty. -- bjm ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
Greg Woods wrote: On Tue, 2005-09-20 at 11:04 -0500, Kevin Kuphal wrote: Greg Woods wrote: I expected to see the SBE capture cards defined in the MBE system in the status page or in the setup on the MBE. This means you have to run mythtv-setup on the machine that has the card to set up capture cards. Why is this confusing? I too expected to see all the available capture cards in mythtv-setup no matter which host I ran it on. Now that I understand more about how it works (that is, some things are stored in the central database and some are stored locally), it's not so confusing any more. But when I was first trying to set up an SBE that had previously been a tuner-less front-end-only system, it was confusing. Nothing is stored locally about the cards. The program is showing you only cards that are physically present in the machine that you are configuring. The information about the cards is written to the shared database. Kevin ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On Tuesday 20 September 2005 12:22 pm, Greg Woods wrote: > On Tue, 2005-09-20 at 11:04 -0500, Kevin Kuphal wrote: > > Greg Woods wrote: > > >>I expected to see the SBE capture cards defined in the MBE system in > > >> the status page or in the setup on the MBE. > > > > > >This means you have to run mythtv-setup on the machine that has the card > > >to set up capture cards. > > > > Why is this confusing? > > I too expected to see all the available capture cards in mythtv-setup no > matter which host I ran it on. Now that I understand more about how it > works (that is, some things are stored in the central database and some > are stored locally), it's not so confusing any more. But when I was > first trying to set up an SBE that had previously been a tuner-less > front-end-only system, it was confusing. Everything's stored in the same central database. Cards don't show up on the master because it requires local access to the card to probe the various available settings & inputs. Isaac ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On Tue, 2005-09-20 at 11:04 -0500, Kevin Kuphal wrote: > Greg Woods wrote: > >>I expected to see the SBE capture cards defined in the MBE system in the > >>status page or in the setup on the MBE. > >> > >> > > > >This means you have to run mythtv-setup on the machine that has the card > >to set up capture cards. > Why is this confusing? I too expected to see all the available capture cards in mythtv-setup no matter which host I ran it on. Now that I understand more about how it works (that is, some things are stored in the central database and some are stored locally), it's not so confusing any more. But when I was first trying to set up an SBE that had previously been a tuner-less front-end-only system, it was confusing. --Greg ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
Greg Woods wrote:
On Mon, 2005-09-19 at 20:02 -0400, Scot L. Harris wrote:
I expected to see the SBE capture cards defined in the MBE system in the
status page or in the setup on the MBE.
This means you have to run mythtv-setup on the machine that has the card
to set up capture cards. I found this very confusing too but I finally
figured this out. My slave backend now works fine. mythtv-setup on the
SBE only shows the one card that is on that machine, yet I can use all
three cards including the two in the MBE just fine. Going into MythWeb
will show all three cards, and properly indicate when the SBE is down
("not currently connected"). The reason this is confusing, I think, is
that clearly mythtv-setup is manipulating some information that is
stored only on the local host, and some that is stored in the database,
and nowhere is it documented when this line is crossed, I just had to
figure it out by trial and error. Video sources are defined in the
database, do not try to set those up separately on the SBE. But capture
cards are defined locally, you must set those up with mythtv-setup on
each machine that has one or more cards.
Why is this confusing? You have to define the cards on the machine that
can actually query for the video devices. It spells it out in the docs:
The configuration of a non-master backed is the same as the master
except you skip over the Video sources section. I'm not sure why the
Video sources section has to be skipped because the video sources table
in the DB has no host specific options in it so they should be universal
to whatever backend is doing it, but it maybe simply related to a desire
to keep listing related functions relegated to the master backend only
because it runs mythfilldatabse.
Perhaps it should be considered to grey out or disable Video sources on
non-master backend systems to prevent confusion.
Kevin
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On Mon, 2005-09-19 at 20:02 -0400, Scot L. Harris wrote:
> I expected to see the SBE capture cards defined in the MBE system in the
> status page or in the setup on the MBE.
You don't see them in mythtv-setup, as that only defines
locally-connected capture cards. You SHOULD see them in MythWeb. I found
MythWeb very easy to set up, and it shows you things (like this) that
are difficult or impossible to find any other way. It's worth having.
MythWeb also increases the WAF since she can now schedule recordings
from her Mac.
This means you have to run mythtv-setup on the machine that has the card
to set up capture cards. I found this very confusing too but I finally
figured this out. My slave backend now works fine. mythtv-setup on the
SBE only shows the one card that is on that machine, yet I can use all
three cards including the two in the MBE just fine. Going into MythWeb
will show all three cards, and properly indicate when the SBE is down
("not currently connected"). The reason this is confusing, I think, is
that clearly mythtv-setup is manipulating some information that is
stored only on the local host, and some that is stored in the database,
and nowhere is it documented when this line is crossed, I just had to
figure it out by trial and error. Video sources are defined in the
database, do not try to set those up separately on the SBE. But capture
cards are defined locally, you must set those up with mythtv-setup on
each machine that has one or more cards. If you have a machine that is
ONLY a frontend (no capture cards), then all you really need is the
mysql.txt file so that it can find the MBE, and you may never need to
run mythtv-setup at all (correct or not?).
--Greg
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
Jay Jarvinen wrote: ... Sure, "digital logic" is what the "poor guy" wants to hear about when his SBE isn't working. My reply to him was to point out the cause and solution to the problem he was having. "Digital logic" was in reply to your twisted, paranoid and rambling self-defense in not being able to accept that you didn't know what you were talking about. The "poor guy" wanted a solution to his problem. There is nothing polite about your running him around in circles and there certainly wasn't any intent to be polite in your respnse to my actually helping him. Heaven forbid the answer might be something you didn't understand. How dare I give him the right answer in contradiction to your misguided guesses? You really need to look at yourself. -- bjm ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On Mon, 19 Sep 2005 19:57:05 -0700 Bruce Markey <[EMAIL PROTECTED]> wrote: > Jay Jarvinen wrote: > ... > > Bruce, you magic-hater you, of course there's magic. > > There is no magic. Digital logic is deterministic and there are > specific causes for the events when the code is executing. ... > You screwed up but I have never seen anyone so hyper-sensitive > and ramble on so redundantly with such self-absorbed wussy > defensiveness as this message. What a wimp. Grow up. Pfeh. Whatever, you confuse politeness for wimpyness and come back with this machismo bullshit, being anal about digital logic, woop-dee-doo. Furthermore, I seriously doubt you actually read my post. Sure, "digital logic" is what the "poor guy" wants to hear about when his SBE isn't working. Misinformation? My setup works. Bruce: "BS, 1 + 2 != 3 damnit, but two plus one equals three." Your tough-guy routine needs works, but at least you're convinced. -Jay Jarvinen ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
Jay Jarvinen wrote: ... Bruce, you magic-hater you, of course there's magic. There is no magic. Digital logic is deterministic and there are specific causes for the events when the code is executing. Unfortunately, you had absolutely no clue as to the nature of his problem and were doing him a 'disservice', to use you words, by leading him nowhere. Your statement "The MBE automagically finds available cards on slave backend(s), if/when the SBE mythbackend is running." is in every way false, misleading and a disservice to the poor guy trying to solve his problems. If/when an SBE is running the MBE does not find cards that haven't been entered in the capturecard table and knows nothing about the config for the slave that is connecting to a different database. You screwed up but I have never seen anyone so hyper-sensitive and ramble on so redundantly with such self-absorbed wussy defensiveness as this message. What a wimp. Grow up. As for discouraging clueless wannabe 'expert's who try to dole out misinformation (or however you put it that that you should be revered for being an idiot), Good! Please don't waste the time of others pretending to have these deep insights when you have no idea what you're talking about. Thank you, -- bjm ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
Scot L. Harris wrote: On Mon, 2005-09-19 at 18:12, Bruce Markey wrote: Scot L. Harris wrote: ... Well the magic seems to be missing from my configuration. :) There is no magic. That post was very misleading. Cards must be configured locally. You must add the slave card by running mythtv-setup on the slave host. ... 5. in mythtvsetup on SBE execute steps 1, 2 (note if I try step 4 I don't see any option other than none for the video source) This is a bad sign. If you are connecting to the same ddatabase as your master backend, it will show the same list of video sources as you see from the master. The most common cause of this (and this should have been mentioned in this thread by now) is that you may be connecting to a different mysqld most likely running on the slave host. This won't work. All frontends and backends that need to work together need to connect to the same database. On your slave host, "/etc/init.d/mysqld stop" and/or "killall mysqld" If (when) mythtv-setup fails to connect to any database, get to work on configuring your master's mysqld to allow remote connections and access for a remote "mythtv" user and set the parameters in your mysql.txt file. mysql.txt file on the slave host. Will go through this again. I know it is some simple step that I missed. I have indications that the SBE is able to connect to the MBE but it does not seem to be a full connection. Do I even need to run mysql on the SBE? Absolutely not. Did you read the message? I tried disabling mysqld on the SBE but mythbackend would not startup. Obviously. Now that you've established that, re-read what I wrote. You're slave has been connecting to a different database than your master. The slave needs to connect to the same database as the master. See: http://www.mythtv.org/docs/mythtv-HOWTO-9.html#ss9.3 and http://www.mythtv.org/docs/mythtv-HOWTO-6.html#modify_perm_mysql -- bjm ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
RE: [mythtv-users] Setting up slave backend system
>> Do I even need to run mysql on the SBE? I tried disabling > > No. > >> mysqld on the >> SBE but mythbackend would not startup. If it is not using the local >> copy of mysqld then I would think it would startup. Unless this is an > > True. You don't need MySQL on the slave backend at all. Kill it if > it's running then edit ~/mysql.txt on the slave backend. I think that's > what you're missing here. > You may have a similar problem to what I had - the init script for mythbackend was setting the HOME variable to an odd directory which had its own copy of mysql.txt which was pointing to localhost rather than to the machine that was running the mysql database. In my instance, I could run mythbackend from the command line (where the value of HOME was consistent with the copy of mysql.txt it was getting) but not from the init scripts. Very confusing!! Sounds like you haven't got as far as the automation bit yet though - just thought I'd mention it in case having set mysql.txt correctly it all goes pear shaped later... -- Robin Gilks ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On Mon, 19 Sep 2005 15:12:49 -0700 Bruce Markey <[EMAIL PROTECTED]> wrote: > There is no magic. That post was very misleading. Cards must be > configured locally. You must add the slave card by running > mythtv-setup on the slave host. ... > Once you can connect from your slave host and mythtv-setup sees your > existing video sources, then you can move forward by; checking the > IP addresses in General, adding your local card(s), and associating > your inputs with your existing sources. > > -- bjm Bruce, you magic-hater you, of course there's magic. The master "knows" about cards local to slaves, without user intervention ON the master by way of MBE mythtv-setup, database, or any other means. How? Because mythtv-setup on the slave does the work. Very misleading? Pardon me. From his statement, he was attempting to configure slave* cards on his MBE (assuming using mythtv-setup). To which I replied, "You don't". Him: "Maybe what is confusing me is how to get the capture cards on the SBE configured on the MBE." Me: "You don't. The MBE automagically finds available cards on slave backend(s), if/when the SBE mythbackend is running." Could I have worded it more verbosely as to explicitly point out that "available cards" refers to ones [properly and locally] configured on slave backends that will be utilized IF the slave is available? Perhaps. Was anyone confused that I was suggesting the master server just probes the LAN for 'available cards'? I doubt it. Where did I suggest slave cards be configured anywhere but on slave machines? (Wishlist: braindead SBE starts mythbackend with it's mysql.txt configured, SBE offers local resources (hd space, tuners, etc) to MBE server and prompts user) I fail to see how database records of a properly configured master/slave setup are misleading. However, I feel your characterizing my post in this way, and then later restating what I've already demonstrated in numerous ways, is of disservice. What was the great danger you perceived? That users might _stay away_ from the MBE during slave configuration? That's .. the correct method. Meanwhile, as you were busy setting the record straight with your first reply, my second post hit the list. You then reestablished points already made, only to turn around and re-explain things in even more ambiguous terms. (Examples of this, available upon request) Granted, my statement that "the slave mythtv-setup needs the MBE IP/port configured in order to retrieve available sources", is more correctly stated as "needs the MySQL IP/port configured", which need not necessarily reside on the MBE. But since the MySQL DB _is_ residing on the MBE, in context of this thread, it is therefore moot. Bruce - your long history and contributions to MythTV are much appreciated. But, it doesn't excuse what I would call "pseudo-moderating" perfectly valid attempts to help other users. This only stifles well intentioned posters that would most likely "get by" without your expert attention or criticism. Anyway, despite all our efforts, (according to the latest message), the original poster is still wondering if a MySQL DB is needed on the slave, go figure. Knock yourself out.. -Jay Jarvinen ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
RE: [mythtv-users] Setting up slave backend system
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Scot L. Harris > Sent: Monday, September 19, 2005 8:26 PM > To: Discussion about mythtv > Subject: Re: [mythtv-users] Setting up slave backend system > Do I even need to run mysql on the SBE? I tried disabling No. > mysqld on the > SBE but mythbackend would not startup. If it is not using the local > copy of mysqld then I would think it would startup. Unless this is an True. You don't need MySQL on the slave backend at all. Kill it if it's running then edit ~/mysql.txt on the slave backend. I think that's what you're missing here. -Khanh ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On Mon, 2005-09-19 at 18:12, Bruce Markey wrote: > Scot L. Harris wrote: > ... > > Well the magic seems to be missing from my configuration. :) > > There is no magic. That post was very misleading. Cards must be > configured locally. You must add the slave card by running > mythtv-setup on the slave host. > > ... > > 5. in mythtvsetup on SBE execute steps 1, 2 (note if I try step 4 I > > don't see any option other than none for the video source) > > This is a bad sign. If you are connecting to the same ddatabase > as your master backend, it will show the same list of video sources > as you see from the master. > > The most common cause of this (and this should have been mentioned > in this thread by now) is that you may be connecting to a different > mysqld most likely running on the slave host. This won't work. All > frontends and backends that need to work together need to connect > to the same database. > > On your slave host, "/etc/init.d/mysqld stop" and/or "killall mysqld" > If (when) mythtv-setup fails to connect to any database, get to > work on configuring your master's mysqld to allow remote connections > and access for a remote "mythtv" user and set the parameters in your > mysql.txt file. > Will go through this again. I know it is some simple step that I missed. I have indications that the SBE is able to connect to the MBE but it does not seem to be a full connection. Do I even need to run mysql on the SBE? I tried disabling mysqld on the SBE but mythbackend would not startup. If it is not using the local copy of mysqld then I would think it would startup. Unless this is an indication of the actual problem. Maybe I'm getting close to figuring this out. > Once you can connect from your slave host and mythtv-setup sees your > existing video sources, then you can move forward by; checking the IP > addresses in General, adding your local card(s), and associating your > inputs with your existing sources. > > -- bjm Thanks for helping me try to figure this out. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On Mon, 2005-09-19 at 18:13, Nick wrote: > On 19/09/05, Scot L. Harris <[EMAIL PROTECTED]> wrote: > > On Mon, 2005-09-19 at 16:29, Jay Jarvinen wrote: > > > On Mon, 19 Sep 2005 13:26:00 -0400 > > > "Scot L. Harris" <[EMAIL PROTECTED]> wrote: > > > > > > > Maybe what is confusing me is how to get the capture cards on the > > > > SBE configured on the MBE. > > > > > > You don't. The MBE automagically finds available cards on slave > > > backend(s), if/when the SBE mythbackend is running. > > > > > > Like the docs say, don't set up a new videosource (guide data) on the > > > slave(s). > > > > > > Maybe this will help, from my master backend database (which BTW, is > > > the only* database): > > > > > > > Well the magic seems to be missing from my configuration. :) > > Have you shut down/stopped mythbackend on both machines, brought up > the MBE, and then afterwards, brought up the SBE? Yes, have tried that, but will try it again tomorrow. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On Mon, 2005-09-19 at 18:11, Jay Jarvinen wrote: > On Mon, 19 Sep 2005 17:24:34 -0400 > "Scot L. Harris" <[EMAIL PROTECTED]> wrote: > > > Just to summarize: > > > > 1. load mythtv-suite on SBE > > 2. configure ivtv > > 3. verified that video can be captured on SBE capture cards > > 4. run mythtvsetup on SBE > > 5. in mythtvsetup on SBE execute steps 1, 2 (note if I try step 4 > > I don't see any option other than none for the video source) > > 6. configure mysql on MBE for access by SBE > > 7. start mythbackend on SBE (confirm in log files that it connects > > to MBE) > > 8. run mythtvsetup on MBE > > 9. in mythtvsetup on MBE add new capture cards with video sources > > 10. ??? > > 11. profit! > > > > > > I get to step 9 but am unable to see the capture cards located on > > the SBE. > > Hmm, step 9, the cards .. are configured on the machine where they > physically reside. If a SBE goes down, on the status page, you'll see: > > "Encoder 3 is remote on SLAVE_HOSTNAME (currently not connected)" > .. the MBE continues on it's way, rescheduling where appropriate. > > BTW, can you define "see the capture cards", how? If configured, I expected to see the SBE capture cards defined in the MBE system in the status page or in the setup on the MBE. > http://MBE_hostname_goes_here:6544/ would show Tuner stats. [Likewise > :6544 on SBE shows Tuner* stats, but only for that SBE's card(s)] > On each system (SBE and MBE) I just see the cards in those systems defined. > mythtv-setup on SBE: you should see the videosource from the MBE (menu > option 3), just don't configure a new one. Then, under input > connections (menu option 4) this source should be available to your > SBE card. > > If not, then it sounds like a MySQL issue of some kind. > That is what I don't see. Have verified that the SBE can connect to the MBE. > I'm not sure what the docs recommend, but I'd move your step #6 to #1. > The mythtv-setup program needs the MBE IP/port configured in order to > retrieve available videosources, etc. > > If you're unsure, a quick way to verify mythtv-setup on SBE is > connected, would be to run 'mysqladmin processlist' on the MBE. There > should be 3 threads (I think), with the [EMAIL PROTECTED] you're > expecting. > I see one entry for the SBE. [EMAIL PROTECTED] ~]# mysqladmin -u mythtv processlist +-+++-+-+---+---+--+ | Id | User | Host | db | Command | Time | State | Info | +-+++-+-+---+---+--+ | 50 | mythtv | localhost | mythconverg | Sleep | 12691 | | | | 51 | mythtv | localhost | mythconverg | Sleep | 18 | | | | 52 | mythtv | localhost | mythconverg | Sleep | 291 | | | | 53 | mythtv | localhost | mythconverg | Sleep | 9063 | | | | 55 | mythtv | localhost | mythconverg | Sleep | 18 | | | | 76 | mythtv | localhost | mythconverg | Sleep | 2268 | | | | 77 | mythtv | localhost | mythconverg | Sleep | 2268 | | | | 99 | mythtv | terraslave.slh.lan | mythconverg | Sleep | 8768 | | | | 102 | mythtv | localhost | | Query | 0 | | show processlist | +-+++-+-+---+---+--+ [EMAIL PROTECTED] ~]# > I mean no disrespect, but it should be a straightforward setup - > therefore, instinct tells me it's something simple being overlooked. > Then again, I don't surprise easily .. unless something works on the > first try without reading the docs - then I worry. > None taken. I figure it is something simple that I have missed. A step in the documentation that I skipped or a permission somewhere that is not right. Another question I have: Do I even need to have mysql running on the SBE? > -Jay > > FYI: I just setup my (1st) SBE in the last 48 hours, but it worked out > of the box, first attempt, recordings and scheduling all in order, > playback = good, "failover" to MBE-only = good. Ultimately, this > slave will probably take over BE duties, but I can't miss recordings > in the meantime. ;) Yeah, I'm trying to add some additional encoders to the mix. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
Scot L. Harris wrote: ... Well the magic seems to be missing from my configuration. :) There is no magic. That post was very misleading. Cards must be configured locally. You must add the slave card by running mythtv-setup on the slave host. ... 5. in mythtvsetup on SBE execute steps 1, 2 (note if I try step 4 I don't see any option other than none for the video source) This is a bad sign. If you are connecting to the same ddatabase as your master backend, it will show the same list of video sources as you see from the master. The most common cause of this (and this should have been mentioned in this thread by now) is that you may be connecting to a different mysqld most likely running on the slave host. This won't work. All frontends and backends that need to work together need to connect to the same database. On your slave host, "/etc/init.d/mysqld stop" and/or "killall mysqld" If (when) mythtv-setup fails to connect to any database, get to work on configuring your master's mysqld to allow remote connections and access for a remote "mythtv" user and set the parameters in your mysql.txt file. Once you can connect from your slave host and mythtv-setup sees your existing video sources, then you can move forward by; checking the IP addresses in General, adding your local card(s), and associating your inputs with your existing sources. -- bjm ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On 19/09/05, Scot L. Harris <[EMAIL PROTECTED]> wrote: > On Mon, 2005-09-19 at 16:29, Jay Jarvinen wrote: > > On Mon, 19 Sep 2005 13:26:00 -0400 > > "Scot L. Harris" <[EMAIL PROTECTED]> wrote: > > > > > Maybe what is confusing me is how to get the capture cards on the > > > SBE configured on the MBE. > > > > You don't. The MBE automagically finds available cards on slave > > backend(s), if/when the SBE mythbackend is running. > > > > Like the docs say, don't set up a new videosource (guide data) on the > > slave(s). > > > > Maybe this will help, from my master backend database (which BTW, is > > the only* database): > > > > Well the magic seems to be missing from my configuration. :) Have you shut down/stopped mythbackend on both machines, brought up the MBE, and then afterwards, brought up the SBE? Nick ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On Mon, 19 Sep 2005 17:24:34 -0400 "Scot L. Harris" <[EMAIL PROTECTED]> wrote: > Just to summarize: > > 1. load mythtv-suite on SBE > 2. configure ivtv > 3. verified that video can be captured on SBE capture cards > 4. run mythtvsetup on SBE > 5. in mythtvsetup on SBE execute steps 1, 2 (note if I try step 4 > I don't see any option other than none for the video source) > 6. configure mysql on MBE for access by SBE > 7. start mythbackend on SBE (confirm in log files that it connects > to MBE) > 8. run mythtvsetup on MBE > 9. in mythtvsetup on MBE add new capture cards with video sources > 10. ??? > 11. profit! > > > I get to step 9 but am unable to see the capture cards located on > the SBE. Hmm, step 9, the cards .. are configured on the machine where they physically reside. If a SBE goes down, on the status page, you'll see: "Encoder 3 is remote on SLAVE_HOSTNAME (currently not connected)" .. the MBE continues on it's way, rescheduling where appropriate. BTW, can you define "see the capture cards", how? If configured, http://MBE_hostname_goes_here:6544/ would show Tuner stats. [Likewise :6544 on SBE shows Tuner* stats, but only for that SBE's card(s)] mythtv-setup on SBE: you should see the videosource from the MBE (menu option 3), just don't configure a new one. Then, under input connections (menu option 4) this source should be available to your SBE card. If not, then it sounds like a MySQL issue of some kind. I'm not sure what the docs recommend, but I'd move your step #6 to #1. The mythtv-setup program needs the MBE IP/port configured in order to retrieve available videosources, etc. If you're unsure, a quick way to verify mythtv-setup on SBE is connected, would be to run 'mysqladmin processlist' on the MBE. There should be 3 threads (I think), with the [EMAIL PROTECTED] you're expecting. I mean no disrespect, but it should be a straightforward setup - therefore, instinct tells me it's something simple being overlooked. Then again, I don't surprise easily .. unless something works on the first try without reading the docs - then I worry. -Jay FYI: I just setup my (1st) SBE in the last 48 hours, but it worked out of the box, first attempt, recordings and scheduling all in order, playback = good, "failover" to MBE-only = good. Ultimately, this slave will probably take over BE duties, but I can't miss recordings in the meantime. ;) ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On Mon, 2005-09-19 at 16:29, Jay Jarvinen wrote: > On Mon, 19 Sep 2005 13:26:00 -0400 > "Scot L. Harris" <[EMAIL PROTECTED]> wrote: > > > Maybe what is confusing me is how to get the capture cards on the > > SBE configured on the MBE. > > You don't. The MBE automagically finds available cards on slave > backend(s), if/when the SBE mythbackend is running. > > Like the docs say, don't set up a new videosource (guide data) on the > slave(s). > > Maybe this will help, from my master backend database (which BTW, is > the only* database): > Well the magic seems to be missing from my configuration. :) I checked the tables on the MBE and I can see the existing capture cards on the MBE but nothing from the SBE. So do I need to use a goat or a pig for the sacrifice to get this to work? :) Just to summarize: 1. load mythtv-suite on SBE 2. configure ivtv 3. verified that video can be captured on SBE capture cards 4. run mythtvsetup on SBE 5. in mythtvsetup on SBE execute steps 1, 2 (note if I try step 4 I don't see any option other than none for the video source) 6. configure mysql on MBE for access by SBE 7. start mythbackend on SBE (confirm in log files that it connects to MBE) 8. run mythtvsetup on MBE 9. in mythtvsetup on MBE add new capture cards with video sources 10. ??? 11. profit! I get to step 9 but am unable to see the capture cards located on the SBE. I know I am missing something in the docs or the magic has gone away from here. :) Thanks for taking the time to help. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On Mon, 19 Sep 2005 13:26:00 -0400 "Scot L. Harris" <[EMAIL PROTECTED]> wrote: > Maybe what is confusing me is how to get the capture cards on the > SBE configured on the MBE. You don't. The MBE automagically finds available cards on slave backend(s), if/when the SBE mythbackend is running. Like the docs say, don't set up a new videosource (guide data) on the slave(s). Maybe this will help, from my master backend database (which BTW, is the only* database): (Note: your card #'s may vary (more sequential?)) --- # select cardid, videodevice, defaultinput, hostname FROM capturecard; ++-+--+--+ | cardid | videodevice | defaultinput | hostname | ++-+--+--+ | 1 | /dev/video | Television | lian | | 3 | /dev/video0 | Tuner 0 | duron| ++-+--+--+ 2 rows in set (0.00 sec) # select cardinputid, cardid, sourceid, inputname FROM cardinput; +-++--++ | cardinputid | cardid | sourceid | inputname | +-++--++ | 1 | 1 |1 | Television | | 4 | 3 |1 | Tuner 0| +-++--++ 2 rows in set (0.00 sec) # select sourceid, xmltvgrabber from videosource; +--+--+ | sourceid | xmltvgrabber | +--+--+ |1 | datadirect | +--+--+ 1 row in set (0.00 sec) # select count(*) from videosource; +--+ | count(*) | +--+ |1 | +--+ 1 row in set (0.01 sec) --- Two capture cards, different hosts, same sourceid (videosource). -Jay ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On Mon, 2005-09-19 at 09:40, Nick wrote: > On 19/09/05, Scot L. Harris <[EMAIL PROTECTED]> wrote: > > If this was done on the SBE should this be deleted? On the first couple > > of passes at this I skipped the step of creating video sources but when > > I tried to setup the input connections the only option was none. > > I would think so. You need to make sure you do not have the SBE > connecting to MySQL on the SBE but on the machine where the DB is > (likely the MBE). Can you connect to the database successfully on the > MBE from the command line on the SBE (using the mythtv > login/password)? > > $ mysql -h $DBSERVER -u mythtv -pmythtv mythconverg > > where $DBSERVER is the IP/name of the machine where the mythtv database is. > Confirmed that I was able to connect to the mysql database on the MBE from the SBE system. > Also make sure a firewall is not blocking access to the MBE for MySQL > if the above does not work. Had already made sure of that. In the mythtvsetup on the SBE I specify the MBE IP address. Maybe what is confusing me is how to get the capture cards on the SBE configured on the MBE. I run mythtvsetup on the SBE and can see the cards there. But when I try to assign the video sources on the SBE (in mythtvsetup) there is no choice for my cable listing. I confirmed that the SBE backend connects to the MBE. If I run mythtvsetup on the MBE and try to configure a new capture card it looks like it lists the same cards. Maybe this is what I am getting confused. On both systems there are /dev/video0 and /dev/video1. But in the mythtvsetup there is nothing that I see that indicates that any of these would be on the SBE. Does that make sense? ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On 19/09/05, Scot L. Harris <[EMAIL PROTECTED]> wrote: > On Mon, 2005-09-19 at 07:24, Nick wrote: > > Thank you for the reply. > > > > > *IMPORTANT* - the slave backend (SBE) needs to be configured so that > > it can connect to the master backend (MBE) and database. > > > > I believe I have that working now. From the log file on the slave > backend I get this: > > 2005-09-19 08:31:01.812 Connecting to master server: 192.168.0.3:6543 > 2005-09-19 08:31:01.816 Connected successfully > > I am also getting guide listings now on the slave backend/frontend. > > > You may need to give access to the SBE machine in MySQL (covered in > > the official mythtv docs) if you haven't already, and possibly enable > > networking in /etc/my.cnf (the MySQL config file). On the SBE, the > > ~/.mythtv/mysql.txt file will contain the settings for connecting to > > the database. > > > > Did this. > > > Getting networking sorted is probably the biggest hurdle. Adding the > > extra capture cards on the SBE is pretty easy. > > > > > > 1) Configure the new capture cards on the SBE using mythtvsetup on SBE > > > > Did this. Setup /dev/video0 and /dev/video1 (/dev/video2 is not > working yet, this is a different problem with a PVR-500) > > > 2) You do not create/configure new video sources on the SBE, these are > > only ever configured/created on the MBE. Once you can connect to the > > MBE/DB MythtV will have access to the video sources available on the > > MBE machine. > > > > If this was done on the SBE should this be deleted? On the first couple > of passes at this I skipped the step of creating video sources but when > I tried to setup the input connections the only option was none. I would think so. You need to make sure you do not have the SBE connecting to MySQL on the SBE but on the machine where the DB is (likely the MBE). Can you connect to the database successfully on the MBE from the command line on the SBE (using the mythtv login/password)? $ mysql -h $DBSERVER -u mythtv -pmythtv mythconverg where $DBSERVER is the IP/name of the machine where the mythtv database is. Also make sure a firewall is not blocking access to the MBE for MySQL if the above does not work. Nick ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On Mon, 2005-09-19 at 07:24, Nick wrote: Thank you for the reply. > > *IMPORTANT* - the slave backend (SBE) needs to be configured so that > it can connect to the master backend (MBE) and database. > I believe I have that working now. From the log file on the slave backend I get this: 2005-09-19 08:31:01.812 Connecting to master server: 192.168.0.3:6543 2005-09-19 08:31:01.816 Connected successfully I am also getting guide listings now on the slave backend/frontend. > You may need to give access to the SBE machine in MySQL (covered in > the official mythtv docs) if you haven't already, and possibly enable > networking in /etc/my.cnf (the MySQL config file). On the SBE, the > ~/.mythtv/mysql.txt file will contain the settings for connecting to > the database. > Did this. > Getting networking sorted is probably the biggest hurdle. Adding the > extra capture cards on the SBE is pretty easy. > > > 1) Configure the new capture cards on the SBE using mythtvsetup on SBE > Did this. Setup /dev/video0 and /dev/video1 (/dev/video2 is not working yet, this is a different problem with a PVR-500) > 2) You do not create/configure new video sources on the SBE, these are > only ever configured/created on the MBE. Once you can connect to the > MBE/DB MythtV will have access to the video sources available on the > MBE machine. > If this was done on the SBE should this be deleted? On the first couple of passes at this I skipped the step of creating video sources but when I tried to setup the input connections the only option was none. > 3) Enter Input Connections in mythtvsetup on the SBE machine and > connect the correct video sources to the inputs on the new capture > cards you have just configured. > I believe this was done. > 4) Once this is done (and you've made sure the capture cards are > working normally on the SBE), the newly added SBE capture cards should > be available (whilst the SBE is connected to the MBE) and you should > also be able to view program listings on the SBE. > I can see program listings on the SBE. > 5 You can check the system status in MythTV and using mythweb, and > should report the extra capture cards as available, and the machine > they are on. > I only see the two capture cards that are in the master backend. I have tried restarting both backend systems but no change. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Setting up slave backend system
On 18/09/05, Scot L. Harris <[EMAIL PROTECTED]> wrote: > First I need to thank Jarod yet again. The section of his guide on > upgrading worked just fine on my master backend/frontend system. It was > as simple as running: > > yum install mythtv-suite > > and the system was upgraded from .17 to .18.1 > > > I have a slave backend/front end system that I put together last week. > I held off the final configuration of it until I could get my master > backend system running the same version of mythtv (.18.1). > > For my setup I have nfs mounted the /video/recordings directory from the > master backend system on the slave backend as well as the > /video/pictures directory. > > When I run mythfrontend I am able to watch live TV and play back > existing recordings that reside on the master backend system. This > makes me believe that the two are communicating as expected. > > However, I am unable to get tv listings displayed and it appears that > when playing live tv I am actually using one of the encoders from the > master backend. > > This is reasonable as I only have the two encoders on the master backend > defined. > > What I have not been able to figure out is how to setup the encoders on > the slave backend so they are available for use. Reading the guide it > appears that I should skip step 3 of the mythtvsetup and I should not > run the mythfilldatabase on the slave. > > Can someone point me to the section of documentation that I have skipped > or missed detailing how to get this configured? *IMPORTANT* - the slave backend (SBE) needs to be configured so that it can connect to the master backend (MBE) and database. You may need to give access to the SBE machine in MySQL (covered in the official mythtv docs) if you haven't already, and possibly enable networking in /etc/my.cnf (the MySQL config file). On the SBE, the ~/.mythtv/mysql.txt file will contain the settings for connecting to the database. Getting networking sorted is probably the biggest hurdle. Adding the extra capture cards on the SBE is pretty easy. 1) Configure the new capture cards on the SBE using mythtvsetup on SBE 2) You do not create/configure new video sources on the SBE, these are only ever configured/created on the MBE. Once you can connect to the MBE/DB MythtV will have access to the video sources available on the MBE machine. 3) Enter Input Connections in mythtvsetup on the SBE machine and connect the correct video sources to the inputs on the new capture cards you have just configured. 4) Once this is done (and you've made sure the capture cards are working normally on the SBE), the newly added SBE capture cards should be available (whilst the SBE is connected to the MBE) and you should also be able to view program listings on the SBE. 5 You can check the system status in MythTV and using mythweb, and should report the extra capture cards as available, and the machine they are on. HTH, Nick ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
