[mythtv-users] numerous attempts to find HDHR

Daryl McDonald darylangela at gmail.com
Tue Feb 22 22:58:45 UTC 2022


On Tue, Feb 22, 2022 at 5:36 PM Bill Meek <keemllib at gmail.com> wrote:

> On 2/22/22 16:18, Daryl McDonald wrote:
> > According to the log:
> > cat /var/log/mythtv/hdhr_discovery.log
> > 2022-02-05 08:22:34 INFO Starting HD Homerun discovery
> > 2022-02-05 08:22:35 INFO Found HD Homerun. Seconds=0.429, attempts=1.
> > 2022-02-05 08:24:41 INFO Starting HD Homerun discovery
> > 2022-02-05 08:24:41 INFO Found HD Homerun. Seconds=0.424, attempts=1.
> > 2022-02-05 08:46:38 INFO Starting HD Homerun discovery
> > 2022-02-05 08:46:38 INFO Found HD Homerun. Seconds=0.426, attempts=1.
> > ...
> > 2022-02-18 17:40:32 INFO Starting HD Homerun discovery
> > 2022-02-18 17:40:32 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-18 17:40:34 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-18 17:40:36 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-18 17:40:38 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-18 17:40:40 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-18 17:40:42 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-18 17:40:44 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-18 17:40:46 INFO Found HD Homerun. Seconds=14.485, attempts=8.
> > 2022-02-19 17:41:32 INFO Starting HD Homerun discovery
> > 2022-02-19 17:41:32 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-19 17:41:34 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-19 17:41:36 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-19 17:41:38 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-19 17:41:40 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-19 17:41:42 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-19 17:41:44 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-19 17:41:46 WARNING hdhomerun_config discover failed, return
> code = 1.
> > 2022-02-19 17:41:49 INFO Found HD Homerun. Seconds=16.493, attempts=9.
> > 2022-02-20 09:24:47 INFO Starting HD Homerun discovery
> >
> >  The first attempt to find the HDHR fails, the second is successful.
> Today, however it failed 8 to 14 times before finding the HDHR but the BE
> > would not start because the script exited error code 1.
> > Is there an adjustment I can make to allow more than one failed attempt?
> > For now I've commented out the [Service] and set the scheduler value to
> 0  for the HDHR.
>
> The script makes ATTEMPTS tries (20 if I recall) and tries:
> hdhomerun_config discover
> every DELAY seconds (2).
>
> Run: hdhomerun_config discover from the command line to see what it says.
>
 daryl at trieli:~$ hdhomerun_config discover
hdhomerun device 10426B6B found at 192.168.0.182
>
>
> Then, if the discover works, run the script from the command line.
>
 2022-02-22 17:51:29 INFO Starting HD Homerun discovery
2022-02-22 17:51:29 INFO Found HD Homerun. Seconds=0.424, attempts=1.
>
>
> --
> Bill
>
> According to the log the HDHR was found, but for some reason the BE would
not start citing error code 1. the difference I see is that previously it
was found on the second attempt, but today it took 8 to 14 attempts, so
somewhere between 2 and 8 attempts the error code sticks and prohibits the
BE from starting. My thinking is that an adjustment should be made to allow
for multiple failures, before accepting the exiting error code.
TIA  Daryl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20220222/2249c430/attachment.htm>


More information about the mythtv-users mailing list