[mythtv-users] mythfilldatabase false failure

[Bill Meek]

On 11/27/19 9:08 PM, Asher Schaffer wrote:
> On Wed, Nov 27, 2019 at 6:31 PM Bill Meek <keemllib at gmail.com> wrote:
>> mythbackend --setverbose system:debug
>>
>> That will log ALL system calls by the backend. Including start and end
>> logs. You should see a line similar to this:
>>
>>     Managed child (PID: 18730) has exited! command=yourCommandHere, status=256, result=1
>>
>> Note the above is an example of a failure.
>>
>> The code where the failed message is printing hasn't been touched since
>> September of 2018.
>>
>> [ --setverbose system:alert to turn the extra logging off ]
>>
>> mythbackend --version|grep 'MythTV Version' too please (although a full log of
>> a single run of MFDB would be nice to put in a pastebin. With a link to it here.
> 
> Well now I am more confused:
> 
> Nov 27 19:00:51 myth-backend mythbackend: mythbackend[1537]: I
> SystemManager mythsystemunix.cpp:354 (run) Managed child (PID: 6567)
> has exited! command=/usr/bin/mythfilldatabase --dd-grab-all --verbose
> general --loglevel info --quiet --syslog local7, status=0, result=0
> Nov 27 19:00:51 myth-backend mythbackend: mythbackend[1537]: I
> HouseKeeping housekeeper.cpp:160 (Run) HouseKeeperTask 'MythFillDB'
> Finished Successfully.
> 
> but then 15 seconds later it runs it again:
> 
> Nov 27 19:01:06 myth-backend mythbackend: mythbackend[1537]: I
> CoreContext housekeeper.cpp:740 (Run) Queueing HouseKeeperTask
> 'MythFillDB'.
> Nov 27 19:01:06 myth-backend mythbackend: mythbackend[1537]: I
> HouseKeeping housekeeper.cpp:142 (Run) Running HouseKeeperTask
> 'MythFillDB'.
> Nov 27 19:01:06 myth-backend mythbackend: mythbackend[1537]: D
> HouseKeeping mythsystemunix.cpp:784 (Fork) Launching:
> /usr/bin/mythfilldatabase --dd-grab-all --verbose general,system
> --loglevel info --quiet --syslog local7
> Nov 27 19:01:06 myth-backend mythbackend: mythbackend[1537]: I
> HouseKeeping mythsystemunix.cpp:943 (Fork) Managed child (PID: 7148)
> has started! * command=/usr/bin/mythfilldatabase --dd-grab-all
> --verbose general,system --loglevel info --quiet --syslog local7,
> timeout=0
> 
> MythTV Version : v30.0
> pastebin of MFDB: https://pastebin.com/cWJi68fR

What was the return code in the run 15 seconds later?

It used to be if a client accessed SchedulesDirect too frequently,
that client was prevented from grabbing more. Surprised you're
not getting banned for a day 'til it gets reset.

Maybe look at the housekeeping table:

     SELECT * FROM housekeeping ORDER BY tag,hostname;

to see if the timestamps are proper. And thanks for the log
even though I looks good to me too.

Mine looks like this:

    | tag        | hostname  | lastrun             | lastsuccess         |
    | MythFillDB | NULL      | 2019-11-27 19:07:58 | 2019-11-27 19:07:58 |

-- 
Bill