I just checked, also on arch-linux, that it specifically was the non-issue discussed here i.e.:
Code: Select all
21:01:00.233 [DEBUG ][deluge.core.alertmanager :130 ] tracker_error_alert: archlinux-2020.05.01-x86_64.iso (udp://tracker.archlinux.org:6969)[127.0.0.1:xxxxx] No route to host "" (1)
The above will display as tracker error in UIs, if coming after the succesfull announce, and if coming before, then will not show error, hence, the errors come and go intermittently, without djlegolas PR, even though no actual error occured, since there is connectivity to tracker fine(no matter if before or after the errored-out announce):
Code: Select all
21:01:00.530 [DEBUG ][deluge.core.alertmanager :130 ] tracker_reply_alert: archlinux-2020.05.01-x86_64.iso (http://tracker.archlinux.org:6969/announce)[192.168.0.2:xxxxx] received peers: 100
So I agree in that you can simply ignore it, like you said, and as I do(I didn't even bother patch locally either, as knew it wasen't an issue, and only did it in unofficial deluge2 installer for windows, to avoid confussion. Also, I use deluge-console myself, which in deluge2 doesn't even show tracker status anymore for some reason).
Deluge
