harlam357 / hfm-net

Client Monitoring Application for Folding@Home
34 stars 6 forks source link

HFM 9.28.1718 timeout on some client #355

Closed Adanorm closed 7 months ago

Adanorm commented 2 years ago

Hello Harlam, I just updated my HFM.net to 9.28.1718 (and installed new .net Framework).

2 of my 6 clients now reports "timeouts".

Just before the update all was OK. [15/01/2022-19:46:18] X (Serveur 4) Connection attempt has timed out. [15/01/2022-19:46:18] X System.TimeoutException: Connection attempt has timed out. at HFM.Client.Sockets.TcpClientConnection.ConnectAsync(String host, Int32 port, Int32 timeout) at HFM.Client.FahClientConnection.OpenAsync() at HFM.Core.Client.FahClient.CreateAndOpenConnection() at HFM.Core.Client.FahClient.OnConnect() at HFM.Core.Client.Client.Connect() at HFM.Core.Client.Client.Retrieve() [15/01/2022-19:46:18] X (Poste 11) Connection attempt has timed out. [15/01/2022-19:46:18] X System.TimeoutException: Connection attempt has timed out. at HFM.Client.Sockets.TcpClientConnection.ConnectAsync(String host, Int32 port, Int32 timeout) at HFM.Client.FahClientConnection.OpenAsync() at HFM.Core.Client.FahClient.CreateAndOpenConnection() at HFM.Core.Client.FahClient.OnConnect() at HFM.Core.Client.Client.Connect() at HFM.Core.Client.Client.Retrieve()

Serveur 4 is a PC running Ubuntu 20.04 and Fah 7.6.21. Poste 11 is a PC running Windows 10 and Fah 7.6.21.

HFM is installed on a Windows 11 PC.

Thank you in advance

Adanorm commented 2 years ago

The rollback to the previous version fixes temporarily the issue

Adanorm commented 2 years ago

Confirmed local DNS lookup has error when using IPv4/IPv6

harlam357 commented 7 months ago

Closing. Issue not related to HFM.