[mythtv-users] mythfilldatabase

[Michael T. Dean]

On 03/03/2011 01:42 PM, Mike McMullin wrote:
> On Thu, 2011-03-03 at 10:50 -0500, Michael T. Dean wrote:
>> On 03/03/2011 01:49 AM, Mike McMullin wrote:
>>>     Can someone please tell me what I'm seeing in the below output from
>>> mythfilldatabase:
>>>
>>> 1: Data refresh needed because only 0 of 0 channels have at least one
>>> program listed for day @ offset 10 from 8PM - midnight.   Previous day
>>> had had 65 channels with data in that time period
>>>
>>> 2: This DataDirect listing source is shared by 2 MythTV lineups.
>> Sounds like you have 2 MythTV Video Sources using the same DataDirect
>> (Schedules Direct) lineup.  And, it's quite possible that one of those
>> is an accidentally-created Video Source, which doesn't have any channels?
>    I figure that my big problem in the other thread is in the "inputs"
> page of the backend configure, but the pvr-150 is or should be set for
> regular cable and the HDHR for Digital cable.

So you're supposed to have 2 Video Sources and they may well share the 
same Schedules Direct lineup.

>> I'd need full mythfilldatabase log output to really understand what's
>> happening, but I hope this may help you figure it out?
>    I'd lover to but /var/log/mythtv/mythfilldatabase.log was doesn't seem
> to have been updated since July 2010:
>
> mike at P-733-Lin:~$ locate mythfilldatabase.log
> /var/log/mythtv/mythfilldatabase.log
>
> mike at P-733-Lin:/var/log/mythtv$ ls -l
> total 296346
> -rw-r--r-- 1 mythtv mythtv   785616 2011-03-03 13:17 jamu.log
> -rw-r--r-- 1 mike   mythtv      161 2010-05-23 16:03 mtd.log
> -rw-r--r-- 1 root   mythtv   420913 2011-03-03 13:30 mythbackend.log
> -rw-r--r-- 1 root   mythtv 10586185 2011-03-01 07:56 mythbackend.log.1
> -rw-r--r-- 1 root   mythtv 10498153 2011-02-02 04:56 mythbackend.log.2
> -rw-r--r-- 1 root   mythtv 10547414 2011-01-05 09:03 mythbackend.log.3
> -rw-r--r-- 1 root   mythtv 10745070 2010-12-04 10:25 mythbackend.log.4
> -rw-r--r-- 1 root   mythtv 11097436 2010-11-14 09:32 mythbackend.log.5
> -rw-r--r-- 1 root   mythtv 10953629 2010-10-20 04:07 mythbackend.log.6
> -rw-r--r-- 1 root   mythtv 10811057 2010-09-26 09:12 mythbackend.log.7
> -rw-rw-rw- 1 mythtv mythtv  6316123 2011-03-03 08:47 mythexport.log
> -rw-r--r-- 1 mythtv mythtv     8681 2010-07-08 23:25
> mythfilldatabase.log
>
>    Opening the log in gedit show entries from May and July of 2010,
> nothing prior or post that time frame.  I suppose that might have
> something to do with the ownership, I got from root:mythtv to
> mythtv:mythtv, but mythexport.log seems to have updated, and today's
> update is:
>
> March  3 00:54:25 P-733-Lin /usr/bin/mythexport-daemon[1522]: Caught
> SIGTERM:  exiting gracefully
> March  3 00:54:25 P-733-Lin /usr/bin/mythexport-daemon[1522]: Stopping
> Processing:  1299131665
> March  3 00:55:41 P-733-Lin /usr/bin/mythexport-daemon[1572]: Starting
> Processing:  1299131741
> March  3 00:55:42 P-733-Lin /usr/bin/mythexport-daemon[1572]: Can't
> connect to MythTV: Couldn't communicate with 192.168.1.112 on port 6543:
> IO::Socket::INET::MythTV: connect: Connection refused
>   at line 86 in /usr/bin/mythexport-daemon
> March  3 00:55:47 P-733-Lin /usr/bin/mythexport-daemon[1572]: Can't
> connect to MythTV: Couldn't communicate with 192.168.1.112 on port 6543:
> IO::Socket::INET::MythTV: connect: Connection refused
>   at line 86 in /usr/bin/mythexport-daemon
> March  3 00:55:52 P-733-Lin /usr/bin/mythexport-daemon[1572]: Can't
> connect to MythTV: Couldn't communicate with 192.168.1.112 on port 6543:
> IO::Socket::INET::MythTV: connect: Connection refused
>   at line 86 in /usr/bin/mythexport-daemon
> March  3 01:54:43 P-733-Lin /usr/bin/mythexport-daemon[1572]: Caught
> SIGTERM:  exiting gracefully
> March  3 01:54:43 P-733-Lin /usr/bin/mythexport-daemon[1572]: Stopping
> Processing:  1299135283
> March  3 08:46:59 P-733-Lin /usr/bin/mythexport-daemon[1531]: Starting
> Processing:  1299160019
> March  3 08:47:01 P-733-Lin /usr/bin/mythexport-daemon[1531]: Can't
> connect to MythTV: Couldn't communicate with 192.168.1.112 on port 6543:
> IO::Socket::INET::MythTV: connect: Connection refused
>   at line 86 in /usr/bin/mythexport-daemon
> March  3 08:47:06 P-733-Lin /usr/bin/mythexport-daemon[1531]: Can't
> connect to MythTV: Couldn't communicate with 192.168.1.112 on port 6543:
> IO::Socket::INET::MythTV: connect: Connection refused
>   at line 86 in /usr/bin/mythexport-daemon
>
>    Whatever this is, unless it's directly involved with mythfilldatabase,
> it can wait.  I'd rather have my new tuners up and running than tweaking
> things that may not really be required to have the tuners running at
> this point.


Please check the value of "mythfilldatabase log path" in mythtv-setup 
(under General), and verify it's referring to 
/var/log/mythfilldatabase.log .  Also, you may need to change the 
permissions on the file (chmod 775 /var/log/mythfilldatabase.log ).  
And, note that the mythfilldatabase log path is only used if the backend 
runs mythfilldatabase for you.  If you run it at the command line, 
you'll get log output in stdout, by default, or wherever you redirect 
its output.

Mike