Page 1 of 1

128.252.203.10 server bandwidth exceeded again

Posted: Fri May 29, 2020 2:54 pm
by NRT_AntiKytherA
14:14:02:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 128.252.203.10:80: No connection could be made because the target machine actively refused it.

WU was successfully uploaded to a different server instead. Just posting this here for reference purposes of other folders.

Re: 128.252.203.10 server bandwidth exceeded again

Posted: Sat May 30, 2020 5:46 am
by bruce
WU was successfully uploaded to a different server instead.
Presumably the "different server" was 52.224.109.74 which is the collection server for 128.252.203.10. That's exactly what's supposed to happen.

Re: 128.252.203.10 server bandwidth exceeded again

Posted: Sat May 30, 2020 8:15 am
by NRT_AntiKytherA
I'll double check on the server it did send to but why would the client request a connection to a machine it is not supposed to? Regardless of that strange behaviour, on another subject entirely thanks for the info in the PM about hyper-threading. I won't reply but have taken it onboard ;)

EDIT - The results were sent to 52.224.109.74 instead as you alluded to.

Re: 128.252.203.10 server bandwidth exceeded again

Posted: Sat May 30, 2020 10:13 am
by PantherX
NRT_AntiKytherA wrote:...but why would the client request a connection to a machine it is not supposed to?...
When a WU is downloaded, it can be should be returned to the Work Server (WS). That's the default configuration. However, researchers might configure alternate/backup location(s) called Collection Server(s) so a WU can be either returned to the WS or the CS (there can be multiple CS too, not just one) depending on the situation.