Page 1 of 1

Win 10, 7.6.21 timeout issue sending WUs

Posted: Tue Nov 10, 2020 6:46 pm
by MaxTranced
I initially thought it was a server issue and posted here https://foldingforum.org/viewtopic.php?f=18&t=36402 but apparently downgrading the client from 7.6.21 to 7.6.13 solved these timeout issues that were causing quite a lot of Work Units to be queued. The logs were showing this:
15:56:00:WU27:FS02:Connecting to 129.213.40.229:8080
15:56:10:ERROR:WU19:FS02:Exception: 10002: Received short response, expected 512 bytes, got 0
I think the latest Windows client may have a bug around the timeout values or some other networking code. Please look into this and fix, as it's not yet clear if the Work Units make it OK to the servers or are actually queued until abandoned due to expiration. Thank you!

Re: Win 10, 7.6.21 timeout issue sending WUs

Posted: Wed Nov 11, 2020 1:54 am
by bruce
My guesses are different than yours. That message isn't really primarily a timeout issue ... it's a missing response. Why wasn't that response received? I don't know, but it's worth looking into. One possibility is that the server code wasn't running at that time.

Another possibility is that the server was fixed, leading you to assume it was a change you made rather than that a change that was made on the server. Again, I don't know, but it's worth looking into.

Please post a short segment of FAH's log showing a family of failed attempts (typically 2 or 4 attempts ... to a Work Server on port 8080 and on 80 followed by to a Collection Server on both ports.)

Re: Win 10, 7.6.21 timeout issue sending WUs

Posted: Thu Nov 12, 2020 6:35 am
by MaxTranced
Posted on the other thread.