Open jawilson opened 3 years ago
Any news? I'm experiencing the same issue in the Prometheus Deluge exporter. https://github.com/tobbez/deluge_exporter/issues/22
The warnings are caused by the version probe. In concrete, the lines 122 and 123. https://github.com/JohnDoee/deluge-client/blob/0c2e5a9a3be903a38b4c957af9de9449f9d60093/deluge_client/client.py#L122 I fixed my issues by patching deluge-client and commenting those lines.
Since Deluge 2.1.1 is the latest version and all users will update eventually, you should consider improving that code to not hit the warnings. For example:
# test the latest version first 2.1
try:
self._send_call(2, 1, 'daemon.info')
# set small socket timeout here
result = self._socket.recv(1)
if ord(result[:1]) == 1:
self.deluge_version = 2
self.deluge_protocol_version = 1
# If we need the specific version of deluge 2, this is it.
daemon_version = self._receive_response(2, 1, partial_data=result)
return
catch:
pass
# test 2.0
# test 1.x
Update 2: I wrote my own Prometheus exporter for Deluge using the Web API. => https://github.com/ngosang/deluge-exporter
Got the same errors in my logs.
I'm running Flexget in a docker container with cpoppema/docker-flexget:latest:
I'm running deluge in a docker container with linuxserver/deluge:latest, currently version 2.0.3-2-201906121747-ubuntu18.04.1 (tested back to the earliest 2.0.0 image they had).
I seem to only see this for some torrents, I think larger ones or ones with more files (others get added perfectly fine), but in flexget I see the following log lines from deluge-client (I manually updated the log level to get the debug info):
In the deluge log, I see:
It seems deluge-client is correctly determining the protocol version, but deluge is still pissed off about it.
Related issues:
27