Closed marcosfrm closed 3 months ago
I'm not seeing this error. It looks like you may have a networking error. Send error: 101: Network is unreachable
means address 1.1.1.1
is unreachable. Is it possible your /etc/resolv.conf
contains other server addresses? Can you ping 1.1.1.1
?
Indeed, this exception is due to a lack of connectivity, likely caused by having debugging enabled. Without debugging and with Cloudflare's DNS, name resolution is working fine. With my ISP's servers, it fails consistently, recovering after a few attempts. I suspect they have subpar servers.
With my ISP's servers:
18:09:46:D5:DNS: response TIMEOUT to a:assign1.foldingathome.org with 1 waiting requests, 1 attempts
18:09:51:D5:DNS: response TIMEOUT to a:assign1.foldingathome.org with 1 waiting requests, 2 attempts
18:09:56:D5:DNS: response TIMEOUT to a:assign1.foldingathome.org with 1 waiting requests, 3 attempts
18:09:56:W :CON2:DNS lookup failed for assign1.foldingathome.org
18:09:56:D3:CON2:Connection failed
18:09:56:E :OUT2:Failed response: CONNECT
...until it succeeds...
This is strange behavior. Debugging shouldn't have a significant impact on DNS lookups. I also don't see this issue with debugging enabled. Are you having other networking problems?
I didn't see the problem again today. Looks like it was something specific to this VM. I'm going to close this bug. If it happens on other machines, I'll open a new one. Sorry for the trouble.
The Client is experiencing recurring DNS resolution failures when downloading work units and submitting results. It typically takes 3-6 tries for the DNS to resolve with my ISP servers.
After changing the DNS server to Cloudflare, I encountered the following exception:
On the next attempt, it worked. The network was up when this exception occurred.
AlmaLinux 8 cbang git bb6841b234fcbbad74272d081b31eb3bb78bdde1 fah-client git 88692f3db014831bb4d226b4fc2efa8066b5118d