Hello ELECs,
I've encountered a weird problem on raspberry 4, zattoo-pvr and with current libreelec (Git:leia_pi4_18.6-Leia) installed. On raspberry3 (Git:newclock5_18.6-Leia) everything works flawlessly with same settings.
On raspberry4 zattoo-pvr refuses to work (no channels showed up) and the log criticizes name resolution:
2019-04-11 18:28:48.016 T:2794693488 NOTICE: script.tv.show.next.aired: ### TV Show - Next Aired starting background proc (6.0.15)
2019-04-11 18:28:48.020 T:2794693488 NOTICE: script.tv.show.next.aired: ### no prior data found
2019-04-11 18:28:48.303 T:2881561456 NOTICE: AddOnLog: Zattoo PVR Client: Using useragent: Kodi/18.6 pvr.zattoo/18.1.17 (Kodi PVR addon)
2019-04-11 18:28:48.307 T:2881561456 ERROR: CCurlFile::FillBuffer - Failed: Couldn't resolve host name(6)
2019-04-11 18:28:48.307 T:2881561456 ERROR: CCurlFile::Open failed with code 0 for https://zattoo.com/int:
2019-04-11 18:28:48.307 T:2881561456 NOTICE: AddOnLog: Zattoo PVR Client: Could not get app token from page. Try to load from file.
2019-04-11 18:28:48.309 T:2881561456 ERROR: CCurlFile::FillBuffer - Failed: Couldn't resolve host name(6)
2019-04-11 18:28:48.309 T:2881561456 ERROR: CCurlFile::Open failed with code 0 for https://zattoo.com/zapi/session/hello:
2019-04-11 18:28:48.309 T:2881561456 NOTICE: AddOnLog: Zattoo PVR Client: Hello failed.
2019-04-11 18:28:48.310 T:2881561456 ERROR: CCurlFile::FillBuffer - Failed: Couldn't resolve host name(6)
2019-04-11 18:28:48.310 T:2881561456 ERROR: CCurlFile::Open failed with code 0 for https://zattoo.com/zapi/v2/session:
2019-04-11 18:28:48.310 T:2881561456 ERROR: AddOnLog: Zattoo PVR Client: Initialize session failed.
2019-04-11 18:28:48.311 T:2881561456 NOTICE: PVR Manager: Starting
2019-04-11 18:28:48.318 T:2512954224 NOTICE: PVR Manager: Started
2019-04-11 18:28:50.039 T:2794693488 NOTICE: script.tv.show.next.aired: ### starting data update
2019-04-11 18:28:50.039 T:2794693488 NOTICE: script.tv.show.next.aired: ### grabbing a new country mapping listapart fromName resolution
Display More
Apart from this error name resolution works accurately on the system. I can ping zattoo.com without problem.
Has someone made similar experiences or has someone a clue what goes wrong here?
Thanks and regards
Meanwhile I've got similar experience with a current Elec for raspberry 3 but Git:newclock5_18.7.1-Leia. The log says:
2019-04-11 18:28:45.391 T:1799328640 ERROR: CCurlFile::FillBuffer - Failed: Couldn't resolve host name(6)
2019-04-11 18:28:45.391 T:1799328640 ERROR: Previous line repeats 1 times.
2019-04-11 18:28:45.391 T:1799328640 ERROR: CCurlFile::Open failed with code 0 for https://raw.githubusercontent.com/kodi-game/repository.kodi.game/master/release/add
ons.xml.md5:
2019-04-11 18:28:45.391 T:1807721344 ERROR: CCurlFile::Open failed with code 0 for https://addons.libreelec.tv/9.2.0/RPi2/arm/addons.xml.gz.sha256:
2019-04-11 18:28:45.391 T:1799328640 ERROR: Open - failed to open source <https://raw.githubusercontent.com/kodi-game/repository.kodi.game/master/release/addons.xml.m
d5>
2019-04-11 18:28:45.391 T:1807721344 ERROR: Open - failed to open source <https://addons.libreelec.tv/9.2.0/RPi2/arm/addons.xml.gz.sha256>
2019-04-11 18:28:45.392 T:1799328640 ERROR: CRepository: failed read 'https://raw.githubusercontent.com/kodi-game/repository.kodi.game/master/release/addons.xml.md5'
2019-04-11 18:28:45.392 T:1807721344 ERROR: CRepository: failed read 'https://addons.libreelec.tv/9.2.0/RPi2/arm/addons.xml.gz.sha256'
2019-04-11 18:28:45.405 T:1790935936 NOTICE: AddOnLog: Zattoo PVR Client: Using useragent: Kodi/18.6 pvr.zattoo/18.1.17 (Kodi PVR addon)
2019-04-11 18:28:45.437 T:1790935936 ERROR: CCurlFile::FillBuffer - Failed: Couldn't resolve host name(6)
2019-04-11 18:28:45.448 T:1790935936 ERROR: CCurlFile::Open failed with code 0 for https://zattoo.com/zapi/session/hello:
2019-04-11 18:28:45.448 T:1790935936 NOTICE: AddOnLog: Zattoo PVR Client: Hello failed.
2019-04-11 18:28:45.460 T:1790935936 ERROR: CCurlFile::FillBuffer - Failed: Couldn't resolve host name(6)
2019-04-11 18:28:45.460 T:1790935936 ERROR: CCurlFile::Open failed with code 0 for https://zattoo.com/zapi/v2/session:
2019-04-11 18:28:45.461 T:1790935936 ERROR: AddOnLog: Zattoo PVR Client: Initialize session failed.
2019-04-11 18:28:45.461 T:1790935936 NOTICE: PVR Manager: Starting
2019-04-11 18:28:45.690 T:1765757824 NOTICE: Register - new cec device registered on cec->RPI: CEC Adapter (2708:1001)
2019-04-11 18:28:45.772 T:1790935936 ERROR: CCurlFile::FillBuffer - Failed: Couldn't resolve host name(6)
2019-04-11 18:28:45.773 T:1790935936 ERROR: CCurlFile::Open failed with code 0 for http://mirrors.kodi.tv/addons/leia/addons.xml.gz?sha256:
2019-04-11 18:28:45.773 T:1790935936 ERROR: Open - failed to open source <http://mirrors.kodi.tv/addons/leia/addons.xml.gz?sha256>
2019-04-11 18:28:45.773 T:1790935936 ERROR: CRepository: failed read 'http://mirrors.kodi.tv/addons/leia/addons.xml.gz?sha256'
2019-04-11 18:28:47.175 T:1732187008 ERROR: ## LibreELEC Addon ## oe::load_url(http://releases.libreelec.tv/releases.json) ## ERROR: (URLError(gaierror(-3, 'Temporary
failure in name resolution'),))
2019-04-11 18:28:47.175 T:1732187008 ERROR: Traceback (most recent call last):
File "/var/lib/jenkins/LE/build4/workspace/RPi2/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2.3/LibreELEC-settings-42acf261392
7fa93d9d8ec9aa1d3135d101db0e0/.install_pkg/usr/share/kodi/addons/service.libreelec.settings/oe.py", line 362, in load_url
File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen
File "/usr/lib/python2.7/urllib2.py", line 429, in open
File "/usr/lib/python2.7/urllib2.py", line 447, in _open
File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
File "/usr/lib/python2.7/urllib2.py", line 1228, in http_open
File "/usr/lib/python2.7/urllib2.py", line 1198, in do_open
URLError: <urlopen error [Errno -3] Temporary failure in name resolution>
2019-04-11 18:28:47.238 T:1613747072 ERROR: ## LibreELEC Addon ## oe::load_url(https://update.libreelec.tv/updates.php?i=2b82e83c3c6c580b23fd2a5c5caf6b36&d=LibreELEC&
pa=RPi2.arm&v=9.2.3&f=00a02082) ## ERROR: (URLError(gaierror(-3, 'Temporary failure in name resolution'),))
2019-04-11 18:28:47.239 T:1613747072 ERROR: Traceback (most recent call last):
File "/var/lib/jenkins/LE/build4/workspace/RPi2/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2.3/LibreELEC-settings-42acf261392
7fa93d9d8ec9aa1d3135d101db0e0/.install_pkg/usr/share/kodi/addons/service.libreelec.settings/oe.py", line 362, in load_url
File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen
File "/usr/lib/python2.7/urllib2.py", line 429, in open
File "/usr/lib/python2.7/urllib2.py", line 447, in _open
File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
File "/usr/lib/python2.7/urllib2.py", line 1241, in https_open
File "/usr/lib/python2.7/urllib2.py", line 1198, in do_open
URLError: <urlopen error [Errno -3] Temporary failure in name resolution>
2019-04-11 18:28:47.245 T:1613747072 ERROR: ## LibreELEC Addon ## updates::check_updates_v2 ## ERROR: (TypeError('expected string or buffer',))
2019-04-11 18:28:47.250 T:1613747072 ERROR: Traceback (most recent call last):
File "/var/lib/jenkins/LE/build4/workspace/RPi2/LibreELEC.tv/build.LibreELEC-RPi2.arm-9.2.3/LibreELEC-settings-42acf261392
7fa93d9d8ec9aa1d3135d101db0e0/.install_pkg/usr/share/kodi/addons/service.libreelec.settings/resources/lib/modules/updates.py", line 564, in check_updates_v2
File "/usr/lib/python2.7/json/__init__.py", line 339, in loads
File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
TypeError: expected string or buffer
2020-06-17 20:00:52.209 T:1677857664 NOTICE: PVR Manager: Started
2020-06-17 20:00:52.209 T:1799328640 NOTICE: EPG thread started
Display More
I'm not a python expert, but it seems as if network, or at least DNS is not quite ready when services get started. But I'm surprised no one else has reported similar problems in the meantime.
Briefly:
leia_pi4_18.6-Leia does not work
newclock5_18.6-Leia works
newclock5_18.7.1-Leia does not work This was bullshit, technically. In fact that the working newclock5_18.6-device was the only one connected via ethernet and not via wifi, was rather the crucial factor.
June, 19-2020
With setting network configuration from "dhcp" to "manual" it seems as if I've found a workaround for this issue. Maybe someone of the developers will keep an eye on it in the future.
Thanks mates.
June, 20-2020
Meanwhile I installed one of the the primarily flawed devices in another network and there it works flawlessly. Maybe it's because in the network of the first place the gateway ≠ name-server. Or better, wifi + dhcp + name-service was reacting to slow.
Isn't there a parameter where you can adjust waiting time during boot for network services?