Guide not updating

Channels DVR Server Troubleshooting
#1

I went to set the new show Deputy to record and couldn't find it. I had already thought it was weird that the footballl games today were all wrong in the guide. Didn't take long for me to see that my guide had not behttps://community.getchannels.com/t/update-guide/14056en updated in 13 days. I have no idea why it was not updating.. I clicked the button to do a manual update and it did nothing. It said updating for like 2 seconds and then went back to idle.

So I stopped the docker container and restarted it and the guide update worked. Any idea what might be going on?

This is on docker on Ubuntu 18.10

#2

Sounds like a network issue.

#3

If it happens again it would help to know what the Channels DVR log shows.

#4

Scroll back in the Log and see what error messages are shown for the previous guide download attempts

#5

This looks suspicious

2019/12/29 07:49:13 [SYS] Error checking for update: Get https://channels-dvr.s3.amazonaws.com/latest.json: dial tcp: lookup channels-dvr.s3.amazonaws.com on [::1]:53: read udp [::1]:35882->[::1]:53: read: connection refused
2019/12/29 08:16:11 [NAT] Successfully mapped port 8089 using upnp
2019/12/29 09:01:00 [ERR] No stations available in lineup USA-TN41505-X during guide data download
2019/12/29 09:01:00 [IDX] Pruned 155 expired groups from USA-TN41505-X in 221.139387ms.
2019/12/29 09:01:01 [DVR] Waiting 8h57m58.60823307s until next job 1577642340-8 NFL Football
2019/12/29 09:01:01 [IDX] Pruned 4119 expired airings from USA-TN41505-X in 787.780016ms.
2019/12/29 09:15:58 [ERR] Failed to refresh auth: Post https://community.getchannels.com/dvr/api: dial tcp: lookup community.getchannels.com on [::1]:53: read udp [::1]:34819->[::1]:53: read: connection refused
2019/12/29 09:16:11 [NAT] Successfully mapped port 8089 using upnp

You can see the err line where it says no stations available.

1 Like
#6

This indicates that dns lookups were failing, which also caused failure to load the guide stations and download data.

#7

not sure. A reboot of the docker container got it going. How often does the refresh task run?

#8

Guide data is refreshed every morning at a random time between 9am and 11am.

#9

Daily, around 9:30am. It looks like your Docker container is trying to connect to the localhost via IPv6 for DNS lookups. Perhaps change your Docker container's DNS server to something else, like 1.1.1.1 or 8.8.8.8.

1 Like