Page 1 of 1

128.252.203.13 collection server but uploads to work server

Posted: Mon Nov 15, 2021 4:39 pm
by Starman157
I've completed WU 18021, and it will successfully send it to 34.72.228.44, which is the WORK server for this WU. I get the following message:

16:23:41:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:18021 run:42 clone:1 gen:201 core:0x22 unit:0x00000001000000c9000046650000002a
16:23:41:WU01:FS01:Uploading 10.09MiB to 34.72.228.44
16:23:41:WU01:FS01:Connecting to 34.72.228.44:8080
16:23:47:WU01:FS01:Upload 90.45%
16:23:48:WU01:FS01:Upload complete
16:23:48:WU01:FS01:Server responded PLEASE_WAIT (464)

Of course, this completed unit never clears out of my queue as it never receives credit for the work. So it sits there frittering away the WU credit as it constantly retries. I've already lost over 50K credit so far.

11 attempts tried so far. Next attempt delay is already over 35 minutes.

Why didn't this WU go to the collection server on record for this WU, which is 128.252.203.13??

Re: 128.252.203.13 collection server but uploads to work ser

Posted: Mon Nov 15, 2021 4:53 pm
by Joe_H
This is being looked into already. The WS is currently out of space and the connection to the CS is listed as failed.

By default all WUs get uploaded to their WS first, the CS is always a secondary connection. In this case though the WU may have a designated CS, something has occurred to the configuration or connection between the WS and CS so it is not being used as an alternative.

Re: 128.252.203.13 collection server but uploads to work ser

Posted: Tue Nov 23, 2021 11:33 am
by bruce
The WU will only go to the CS after the local client detects an error from the server that was just tried. Inasmuch as the WS indicates that the upload was successful ("Please Wait" isn't recognized as an error so the client doesn't retry the upload). Somebody at Joseph's level needed to rewrite this logic error but it doesn't happen often enough to get their attention.