[mythtv-users] mythfilldatabase false failure

[Bill Meek]

On 11/28/19 10:30 AM, Asher Schaffer wrote:
> On Wed, Nov 27, 2019 at 7:29 PM Bill Meek <keemllib at gmail.com> wrote:
>>
>> What was the return code in the run 15 seconds later?
> 
> It exited cleanly as well:
> Nov 27 19:04:44 myth-backend mythbackend: mythbackend[1537]: I
> SystemManager mythsystemunix.cpp:354 (run) Managed child (PID: 7148)
> has exited! command=/usr/bin/mythfilldatabase --dd-grab-all --verbose
> general,system --loglevel info --quiet --syslog local7, status=0,
> result=0
> Nov 27 19:04:44 myth-backend mythbackend: mythbackend[1537]: I
> HouseKeeping housekeeper.cpp:160 (Run) HouseKeeperTask 'MythFillDB'
> Finished Successfully.
> 
>>
>> 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.
> 
> Me too
> 
>>
>> 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 |
> 
> Mine is a little different in that the last success is prior to the
> last run, but that's probably due to the fact that it keeps running
> new ones:
> 
> | tag                      | hostname | lastrun             |
> lastsuccess         |
> | MythFillDB               | NULL     | 2019-11-28 16:26:06 |
> 2019-11-28 16:22:06 |
> 
> I do find it odd that mythweb shows different data:
> Last mythfilldatabase run started on Fri Jun 28 2019, 1:44 PM and
> ended on Fri Jun 28 2019, 1:46 PM. Successful.
> Suggested next mythfilldatabase run: Sat Jun 29 2019, 3:17 PM.
> 
> Do you know the source of that data? maybe that's where the problem is at.

SELECT * FROM settings WHERE value IN ('mythfilldatabaseLastRunStart', 'mythfilldatabaseLastRunEnd', 'MythFillSuggestedRunTime');

+------------------------------+----------------------+----------+
| value                        | data                 | hostname |
+------------------------------+----------------------+----------+
| mythfilldatabaseLastRunEnd   | 2019-11-28T04:35:07Z | NULL     |
| mythfilldatabaseLastRunStart | 2019-11-28T04:35:03Z | NULL     |
| MythFillSuggestedRunTime     | 2019-11-29T04:35:03Z | NULL     |
+------------------------------+----------------------+----------+

Stop the backend before changing anything, like putting current values
in the above.

-- 
Bill