Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

When is the master BE not the master BE?

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


bfoddy at visi

Oct 19, 2007, 7:01 PM

Post #1 of 4 (624 views)
Permalink
When is the master BE not the master BE?

A month ago, I swapped out my master BE machine with another,
doing so changed the machine name and IP address.

To do the conversion, I dumped the database to a file and
globally changed every occurrence of the old machine and
ip address with the new values, copied it over and reloaded
the database. Then I double checked the values in
mythtv-setup and everything seems fine.

The system also has a slave BE machine that doubles
as a FE machine, which hasn't changed names/ip.

The system is working fine except for two funny
problems.
1. It refuses to run mythfilldatabase automatically as the
old master used to do. Manually running it works fine.
2. The system is not logging any events in the database log.

Beyond that, it schedules programs, plays, etc just like it's
supposed to. The slave machine also works like it should.

I'm running 0.20.1 on a Mandriva 2007 Spring machine.

Must be some setting I've missed in the conversion, but
can't find it. Any clues?

Brian
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


drescherjm at gmail

Oct 19, 2007, 7:24 PM

Post #2 of 4 (572 views)
Permalink
Re: When is the master BE not the master BE? [In reply to]

On 10/19/07, Brian Foddy <bfoddy [at] visi> wrote:
> A month ago, I swapped out my master BE machine with another,
> doing so changed the machine name and IP address.
>
> To do the conversion, I dumped the database to a file and
> globally changed every occurrence of the old machine and
> ip address with the new values, copied it over and reloaded
> the database. Then I double checked the values in
> mythtv-setup and everything seems fine.
>
> The system also has a slave BE machine that doubles
> as a FE machine, which hasn't changed names/ip.
>
> The system is working fine except for two funny
> problems.
> 1. It refuses to run mythfilldatabase automatically as the
> old master used to do. Manually running it works fine.
> 2. The system is not logging any events in the database log.
>
Not that this helps but I have the exact same two problems. The last
thing I got in the database log was from the old master (several
months ago). And I have had to schedule mythfilldatabase via a cron
job because it was never running. Other than that all is well. I am
using a svn version of mythtv-0.21 under 64 bit gentoo.

John
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


bfoddy at visi

Oct 21, 2007, 12:21 PM

Post #3 of 4 (551 views)
Permalink
Re: When is the master BE not the master BE? [In reply to]

On Friday 19 October 2007, John Drescher wrote:
> On 10/19/07, Brian Foddy <bfoddy [at] visi> wrote:
> > A month ago, I swapped out my master BE machine with another,
> > doing so changed the machine name and IP address.
> >
> > To do the conversion, I dumped the database to a file and
> > globally changed every occurrence of the old machine and
> > ip address with the new values, copied it over and reloaded
> > the database. Then I double checked the values in
> > mythtv-setup and everything seems fine.
> >
> > The system also has a slave BE machine that doubles
> > as a FE machine, which hasn't changed names/ip.
> >
> > The system is working fine except for two funny
> > problems.
> > 1. It refuses to run mythfilldatabase automatically as the
> > old master used to do. Manually running it works fine.
> > 2. The system is not logging any events in the database log.
>
> Not that this helps but I have the exact same two problems. The last
> thing I got in the database log was from the old master (several
> months ago). And I have had to schedule mythfilldatabase via a cron
> job because it was never running. Other than that all is well. I am
> using a svn version of mythtv-0.21 under 64 bit gentoo.
>
> John
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Digging around a little, I notice the housekeeping table:

mysql> select * from housekeeping;
+-------------------------------------+---------------------+
| tag | lastrun |
+-------------------------------------+---------------------+
| LogClean | 2007-09-23 13:03:17 |
| MythFillDB | 2007-09-22 12:02:44 |
| JobQueueCleanup | 2007-01-28 08:20:13 |
| JobQueueRecover-mammouth.foddy.home | 2007-09-22 15:27:45 |
| JobQueueRecover-fodvo.foddy.home | 2007-10-21 09:17:02 |
| InUseProgramsCleanup | 2007-01-28 08:20:13 |
| JobQueueRecover-starfire.foddy.home | 2007-05-27 23:48:36 |
| DailyCleanup | 2007-10-21 09:12:52 |
| JobQueueRecover-pvrfe | 2007-04-04 23:00:40 |
| JobQueueRecover-mammouth | 2007-10-20 15:47:49 |
+-------------------------------------+---------------------+
10 rows in set (0.00 sec)


The master is hostname is "mammouth", fodvo is a FE slave BE.
Its possible early in the setup it might have been
called "mammouth.foddy.home", fully qualified.
Notice the duplicate entry of "JobQueueRecover" parameter.
It also so happens that 9/22/2007 was the last time mythfilldatabase ran.

Anyone have any thoughts on this? Should I alter database records to remove
the fully qualified names, or alter the hostname to be fully qualified?
Or am I totally off-base.

Brian

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


drescherjm at gmail

Oct 21, 2007, 4:32 PM

Post #4 of 4 (562 views)
Permalink
Re: When is the master BE not the master BE? [In reply to]

> Digging around a little, I notice the housekeeping table:
>
> mysql> select * from housekeeping;
> +-------------------------------------+---------------------+
> | tag | lastrun |
> +-------------------------------------+---------------------+
> | LogClean | 2007-09-23 13:03:17 |
> | MythFillDB | 2007-09-22 12:02:44 |
> | JobQueueCleanup | 2007-01-28 08:20:13 |
> | JobQueueRecover-mammouth.foddy.home | 2007-09-22 15:27:45 |
> | JobQueueRecover-fodvo.foddy.home | 2007-10-21 09:17:02 |
> | InUseProgramsCleanup | 2007-01-28 08:20:13 |
> | JobQueueRecover-starfire.foddy.home | 2007-05-27 23:48:36 |
> | DailyCleanup | 2007-10-21 09:12:52 |
> | JobQueueRecover-pvrfe | 2007-04-04 23:00:40 |
> | JobQueueRecover-mammouth | 2007-10-20 15:47:49 |
> +-------------------------------------+---------------------+
> 10 rows in set (0.00 sec)
>
>
> The master is hostname is "mammouth", fodvo is a FE slave BE.
> Its possible early in the setup it might have been
> called "mammouth.foddy.home", fully qualified.
> Notice the duplicate entry of "JobQueueRecover" parameter.
> It also so happens that 9/22/2007 was the last time mythfilldatabase ran.
>

Here is what I have on this:

mysql> select * from housekeeping;
+----------------------+---------------------+
| tag | lastrun |
+----------------------+---------------------+
| MythFillDB | 2007-05-17 08:55:22 |
| LogClean | 2007-05-07 16:20:10 |
| JobQueueCleanup | 2006-12-03 16:30:56 |
| JobQueueRecover-jmd0 | 2007-05-17 20:31:00 |
| InUseProgramsCleanup | 2006-12-03 16:30:56 |
| JobQueueRecover-jmd1 | 2007-10-21 18:43:54 |
| DailyCleanup | 2007-10-21 05:04:54 |
+----------------------+---------------------+
7 rows in set (0.01 sec)

jmd0 was the old retired master backend while the new machine is jmd1.
I believe my database
log ended on 5-17 as well as I only have entries for jmd0.

John
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.