You already posted your logs on the other thread and figured out your issue, no? The server is coming up without network access so it cannot find your hdhomerun.
Seems to be working. Just wanted to add To the thread I had the same problem with the same version. Never had the problem with previous versions.
Thanks
2017/02/04 11:26:42 [SYS] Starting Channels DVR v2017.02.03.0335 (linux-x86_64) in /home/nokomis/channels-dvr/data
2017/02/04 11:26:43 [HDR] Found 0 devices
2017/02/04 11:26:43 [SYS] Bonjour service running for dvr-nokomis.local. []
2017/02/04 11:26:43 [ERR] Failed to refresh auth: Post https://community.getchannels.com/dvr/api: dial tcp: lookup community.getchannels.com on [::1]:53: read udp [::1]:44877->[::1]:53: read: connection refused
2017/02/04 11:26:43 [SYS] Started HTTP Server
2017/02/04 11:26:43 [DVR] Recording engine started in /media/dvr/Recorded TV
2017/02/04 11:26:43 [NAT] Failed to discover gateway: no gateway found
2017/02/04 11:26:43 [NAT] Failed to discover upnp: write udp4 0.0.0.0:57950->239.255.255.250:1900: sendto: network is unreachable
2017/02/04 11:26:43 [NAT] Failed to discover router using natpmp and upnp.
2017/02/04 11:26:43 [DVR] Error during search: cannot perform operation on empty alias
2017/02/04 11:26:43 [DVR] Error during search: cannot perform operation on empty alias
2017/02/04 11:26:43 [DVR] Error during search: cannot perform operation on empty alias
2017/02/04 11:26:43 [DVR] Error during search: cannot perform operation on empty alias
2017/02/04 11:26:43 [DVR] Error during search: cannot perform operation on empty alias
2017/02/04 11:26:43 [DVR] Error during search: cannot perform operation on empty alias
2017/02/04 11:26:43 [DVR] Error during search: cannot perform operation on empty alias
2017/02/04 11:26:43 [DVR] Error during search: cannot perform operation on empty alias
2017/02/04 11:26:43 [DVR] Error during search: cannot perform operation on empty alias
2017/02/04 11:26:43 [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]:60020->[::1]:53: read: connection refused
2017/02/04 11:26:43 [SYS] Created database snapshot: backup-20170204.112643
2017/02/04 11:26:43 [SYS] Removing old backup backup-20170129.213036
Looks like the same issue. The software is starting before the network is available. What distro and version of Linux was this?
Mine occurred on Mac OS X 10.12.3.
linux ubuntu
16.04 (kernel: 4.4.0-62-generic)
I think you are right. When I kill the DVR process, it restarts itself and then works flawlessly – including Bonjour.
It’s possible your ubuntu is not configured to bring up networking correctly. See the discussion in Wait for networking on reboot (ubuntu network-online.target)
No issues with ubuntu here. The DVR is automatically updating and running great. Linux Ubuntu 16.04 (kernel: 4.4.0-59-generic)
1 Like
Yes, that was the problem. Somehow my eth0 is now eno1 – so had to make an edit to the /etc/network/interfaces file. Not sure how or when that happened.
All working now. Resolved.
1 Like
Or not. That was resolved for one or two reboots. Now, though I have no network issues (boot log shows clean boot with no errors) it also shows Channels is loading before the network. Any idea how to change that to wait?
Maybe @karlmitchell has some ideas too
Try running “sudo systemctl list-dependencies network-online.target” to see if the DVR is listed
it is not.
Check to see if network-online.target is listed in /etc/systemd/system/channels-dvr.service
[Unit]
Description=Channels DVR
Wants=network-online.target
After=network-online.target
No, only has:
[Unit]
Description=Channels DVR
Adding that to channels-dvr.service fixes the problem.
Not sure why that wasn’t there to start…
1 Like
Great. Sounds like you might have installed before I added that.
Yeah, I was one of your early payment system beta testers.
1 Like
If I recall, the issue occurred on my system because the time was set incorrectly. This was a result of my firewall blocking NTP, made worse by the lack of a hardware clock. I’d start there. If you’re still struggling tomorrow I’ll look into it some more.
Thabks. The edit to channels-dvr.service fixed it.