<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 19, 2022 at 11:43 AM Stephen Worthington <<a href="mailto:stephen_agent@jsw.gen.nz">stephen_agent@jsw.gen.nz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, 19 Jul 2022 10:16:01 -0400, you wrote:<br>
<br>
>Hi All.<br>
><br>
>For some reason mythfilldatabase just stops automatically starting.<br>
><br>
>Last mythfilldatabase run started on Sat Jul 16 2022, 7:36 PM and ended on<br>
>Sat Jul 16 2022, 7:37 PM. mythfilldatabase ran, but did not insert any new<br>
>data into the Guide for 1 of 1 sources. This can indicate a potential<br>
>grabber failure.<br>
>Suggested next mythfilldatabase run: Sun Jul 17 2022, 7:36 PM.<br>
>There's guide data until 2022-08-03 01:30:00 (15 days).<br>
><br>
>Today is July 19th. So it has not automatically started since then.<br>
>This happens randomly. If i run mythfilldatabase as user mythtv it starts<br>
>working normally again for a week or two. Then it starts failing again.<br>
><br>
>Ubuntu 20.04<br>
><br>
> Candidate: 2:31.0+fixes.202203040618.7e4ce1ba98~ubuntu20.04.1<br>
> Version table:<br>
> 2:31.0+fixes.202203040618.7e4ce1ba98~ubuntu20.04.1 500<br>
> 500 <a href="http://ppa.launchpad.net/mythbuntu/31/ubuntu" rel="noreferrer" target="_blank">http://ppa.launchpad.net/mythbuntu/31/ubuntu</a> focal/main amd64<br>
>Packages<br>
> 2:31.0+fixes.20200323.9579662cdc-0ubuntu1 500<br>
> 500 <a href="http://us.archive.ubuntu.com/ubuntu" rel="noreferrer" target="_blank">http://us.archive.ubuntu.com/ubuntu</a> focal/multiverse amd64<br>
>Packages<br>
><br>
>Log file shows this from last run. Nothing else after this.Jul 16 19:38:52<br>
>hemlock mythfilldatabase: mythfilldatabase[408006]: N CoreContext<br>
>main.cpp:409 (main) Data fetching complete.<br>
>Jul 16 19:38:52 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:417 (main) Adjusting program database end times.<br>
>Jul 16 19:38:52 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:422 (main) 0 replacements made<br>
>Jul 16 19:38:52 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:425 (main) Marking generic episodes.<br>
>Jul 16 19:38:52 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:436 (main) Found 1113<br>
>Jul 16 19:38:52 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:439 (main) Extending non-unique programids with<br>
>multiple parts.<br>
>Jul 16 19:38:53 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:490 (main) Found 0<br>
>Jul 16 19:38:53 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:492 (main) Fixing missing original airdates.<br>
>Jul 16 19:38:53 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:506 (main) Found 510 with programids<br>
>Jul 16 19:38:53 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:528 (main) Found 0 without programids<br>
>Jul 16 19:38:53 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:535 (main) Marking repeats.<br>
>Jul 16 19:38:53 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:548 (main) Found 482<br>
>Jul 16 19:38:53 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:551 (main) Unmarking new episode rebroadcast repeats.<br>
>Jul 16 19:38:54 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:560 (main) Found 744<br>
>Jul 16 19:38:54 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:570 (main) Marking episode first showings.<br>
>Jul 16 19:38:55 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:606 (main) Found 29855<br>
>Jul 16 19:38:55 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:608 (main) Marking episode last showings.<br>
>Jul 16 19:38:56 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:644 (main) Found 29773<br>
>Jul 16 19:38:56 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext main.cpp:660 (main)<br>
>#012===============================================================#012|<br>
>Attempting to contact the master backend for rescheduling. |#012| If the<br>
>master is not running, rescheduling will happen when |#012| the master<br>
>backend is restarted.<br>
> |#012===============================================================<br>
>Jul 16 19:38:56 hemlock mythfilldatabase: mythfilldatabase[408006]: N<br>
>CoreContext main.cpp:674 (main) mythfilldatabase run complete.<br>
>Jul 16 19:38:56 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext platforms/mythpowerdbus.cpp:72 (~MythPowerDBus) PowerDBus:<br>
>Closing interfaces<br>
>Jul 16 19:38:56 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext mythcontext.cpp:1659 (~MythContext) Waiting for threads to exit.<br>
>Jul 16 19:38:56 hemlock mythfilldatabase: mythfilldatabase[408006]: I<br>
>CoreContext mythcontext.cpp:1665 (~MythContext) Exiting<br>
><br>
>I also find the metadata lookup is failing too.<br>
><br>
>Any idea where I should start troubleshooting?<br>
>Thank you<br>
<br>
What does the output of this command show?<br>
<br>
sudo mysql mythconverg -e "select * from settings where value like<br>
'%mythfill%';"<br>
<br>
This is what I get on my system where mythfilldatabase is run<br>
externally via a user cron job:<br>
<br>
+---------------------------------+----------------------+----------+<br>
| value | data | hostname |<br>
+---------------------------------+----------------------+----------+<br>
| mythfilldatabaseLastRunStart | 2022-07-19T03:11:30Z | NULL |<br>
| MythFillSuggestedRunTime | 2022-07-20T03:11:30Z | NULL |<br>
| MythFillGrabberSuggestsTime | 1 | NULL |<br>
| MythFillEnabled | 0 | NULL |<br>
| MythFillDatabasePath | mythfilldatabase | NULL |<br>
| MythFillDatabaseArgs | --only-update-guide | NULL |<br>
| MythFillDatabaseLog | /var/log/mythtv | NULL |<br>
| MythFillPeriod | 1 | NULL |<br>
| MythFillMinHour | | NULL |<br>
| MythFillMaxHour | 23 | NULL |<br>
| MythFillFixProgramIDsHasRunOnce | 1 | mypvr |<br>
| mythfilldatabaseLastRunEnd | 2022-07-19T03:11:32Z | NULL |<br>
| mythfilldatabaseLastRunStatus | Successful. | NULL |<br>
+---------------------------------+----------------------+----------+<br>
<br>
The MythFillSuggestedRunTime, MythFillMinHour and MythFillMaxHour<br>
values normally determine when mythbackend will next run<br>
mythfilldatabase when it is being run that from mythbackend. I am not<br>
sure what happens if mythbackend is shut down when it would normally<br>
run.</blockquote><div> </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">| value | data | hostname |<br>+-------------------------------+----------------------+----------+<br>| mythfilldatabaseLastRunEnd | 2022-07-19T14:17:07Z | NULL |<br>| MythFillEnabled | 1 | NULL |<br>| MythFillDatabasePath | mythfilldatabase | NULL |<br>| MythFillMinHour | 0 | NULL |<br>| MythFillMaxHour | 23 | NULL |<br>| MythFillGrabberSuggestsTime | 1 | NULL |<br>| MythFillSuggestedRunTime | 2022-07-20T14:16:15Z | NULL |<br>| mythfilldatabaseLastRunStart | 2022-07-19T14:16:15Z | NULL |<br>| MythFillDatabaseArgs | | NULL |<br>| mythfilldatabaseLastRunStatus | Successful. | NULL </blockquote><div><br></div><div>What caught my attention in your reply is the comment about the backend being shutdown.</div><div>Now that I think about it, the backend was restarted due to a power outage a few days back. And I think mythfilldatabase has not run since then.</div><div>I have since run mythfilldatabase manually. I will monitor and see if everything is back to normal.</div><div><br></div><div>What would cause this issue after a restart? If that is indeed why this happens. </div><div><br></div><div> </div></div></div>