mythinstall fest continued (long ramble)

[Ben Scott]

On 4/7/07, Bruce Labitt <bruce.labitt at verizon.net> wrote:
> Should I log in as user myth?

  At the InstallFest on 31 March, I was having people create a "myth"
user account for regular operations (if they didn't have a user
account of their own created already).  So if you were one of those,
yes, "myth" is the account to use for regular  MythTV purposes.

  Don't confuse that with the "mythtv" account, which is used by the
software to run the backend system.  You shouldn't need to worry about
that one; I mention it only in case you see it in the user list for
your system.

> Run the backend, run mythfilldatabase. Then run the front end?

  As Jarod posted, running "mythfilldatabase" manually should be a
one-time operation.  My understanding is that what you are doing there
is populating the EPG (Electronic Program Guide) before you invoke the
front-end for the first time.  Once the system is up and running, I'm
guessing EPG maintenance happens automatically, at a slow trickle.

> Then when I tried to connect to them, I got a message that they were busy.

  It appears the MythTV front-end gives the message "all tuners are
busy" when it cannot find an available tuner, and even if the reason
it cannot find an available tuner is that no tuners are working at
all.

  A power cycle of the HDHomeRun might be a good thing to try, as
Jarod suggested.  But it might also be that some other part of your
system isn't running.  Make sure the "mysqld", "mythbackend", and
"dhcpd" (for the HDHomeRun) services are running.  You can do so using
the "service" command, e.g.:

	service mythbackend status

  Note that you may need to run "service" as "root" to get accurate results.

  If a service isn't running, you can tell the system to start it
automatically (in the future) with the "chkconfig" command, and then
start it manually.  For example:

	chkconfig dhcpd on
	service dhcpd start

  You can also try pinging the HDHomeRun.  I had configured your DHCP
server to assign it a static address.  As I remember correctly, it was
192.168.254.2.  It was definitely node 2 on whatever subnet we were
using for the HDHR (so if the net was really 192.168.37.0/24, it would
be 192.168.37.2 instead).

> I think one can tell from this long ramble that I'm confused on the
> subject.

  Join the club!  ;-)

-- Ben