131.239.113.97 : Server responded PLEASE_WAIT (464)

[pyrocyborg]

Hi!

Several of my PCs are stuck at uploading their work for at least a few hours. There seems to be an issue with server 131.239.113.97, and with these work units at least, my client just keeps trying to send to that server for some reason, instead of using a backup one or something. 131.239.113.97 supposedly is in ACCEPT status, yet, it doesn't seem to accept anything.

07:28:54:WU00:FS01:Uploading 34.55MiB to 131.239.113.97
07:28:54:WU00:FS01:Connecting to 131.239.113.97:8080
07:28:58:WU00:FS01:Upload complete
07:28:58:WU00:FS01:Server responded PLEASE_WAIT (464)
07:36:41:WARNING:WU01:FS00:Failed to send results, will try again later

It happens on multiple PCs (6 so far) and it's not my ISP, or my PCs. I don't think that my router is the issue either as I don't recall every having that issue (and well, the server tells PLEASE_WAIT, as if it was overloaded), but I rebooted everything on my end to no avail.

Edit : I just finished a few other work units that got sent to sucessfully to either 129.32.209.206 or 158.130.118.23. Everything went smoothly. The other work units tied to 131.239.113.97 are still stuck.

[bikeaddict]

Have been getting the error for hours on two clients.

Code: Select all

05:02:08:WU01:FS00:Server responded PLEASE_WAIT (464)
05:03:16:WU01:FS00:Server responded PLEASE_WAIT (464)
<snip>
10:04:50:WU01:FS00:Server responded PLEASE_WAIT (464)
11:05:05:WU01:FS00:Server responded PLEASE_WAIT (464)

The server is out of disk space.

https://apps.foldingathome.org/serverstats

There ought to be server monitoring that sends an alert when disk space gets below a certain percentage.

[Joe_H]

A notification has been sent by another about this server being out of space.

There ought to be server monitoring that sends an alert when disk space gets below a certain percentage.

There is monitoring. However it doesn't always work

[pyrocyborg]

I see. I hope it get resolved fast. What a waste of perfectly fine work units and QRB.

[ElectricVehicle]

Same here. WU has failed to upload to 131.239.113.97 for a day now....

[pyrocyborg]

Work units will expire in 5-6 hours. Two of them were sent to 128.174.73.74:8080 instead after 40-42 tries, albeit after the timeout period and with very low credit yield, but the other 4 will most probably expire. A first for me.

Isn't there any way to force my clients to use the 128.174.73.74:8080 collection server instead?

[Joe_H]

The collection server is set as part of the WU downloaded. If the client is not trying another server, about the only suggestion I have that might work is blocking connections to 131.239.113.97 and seeing if the client does fail over to a designated CS. If it doesn't, then the CS wasn't set in the WU parameters properly.

Have not seen any response from either of two persons listed as operating that server. Possibly they are away for some reason.

Edit - found an additional contact email, have sent a message to that just now.

[pyrocyborg]

The collection server is set as part of the WU downloaded. If the client is not trying another server, about the only suggestion I have that might work is blocking connections to 131.239.113.97 and seeing if the client does fail over to a designated CS. If it doesn't, then the CS wasn't set in the WU parameters properly.

Thank you Joe_H! That actually worked. The work units were sent to another CS after blocking connections to 131.239.113.97:80. Too bad I didn't think about that before the timeout, but at least the work units didn't expire.

Thanks again and I'll keep that solution in mind in case something similar ever happens again.

[bikeaddict]

When the upload couldn't connect, it failed over to two different alternate collection servers that both completed.

Code: Select all

18:32:38:WU00:FS01:Sending unit results: id:00 state:SEND error:NO_ERROR project:18725 run:0 clone:1505 gen:935 core:0x22 unit:0xa7030000e10500000000000025490000
18:32:38:WU00:FS01:Uploading 34.54MiB to 131.239.113.97
18:32:38:WU00:FS01:Connecting to 131.239.113.97:8080
18:33:09:WARNING:WU00:FS01:Exception: Failed to send results to work server: Not connected
18:33:09:WU00:FS01:Trying to send results to collection server
18:33:09:WU00:FS01:Uploading 34.54MiB to 129.32.209.207
18:33:09:WU00:FS01:Connecting to 129.32.209.207:8080
18:33:14:3:127.0.0.1:New Web session
18:33:15:WU00:FS01:Upload 12.12%

Code: Select all

18:35:34:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:18725 run:0 clone:1672 gen:954 core:0x22 unit:0xba030000880600000000000025490000
18:35:34:WU01:FS00:Uploading 34.54MiB to 131.239.113.97
18:35:34:WU01:FS00:Connecting to 131.239.113.97:8080
18:35:35:2:127.0.0.1:New Web session
18:36:04:WARNING:WU01:FS00:Exception: Failed to send results to work server: Not connected
18:36:04:WU01:FS00:Trying to send results to collection server
18:36:04:WU01:FS00:Uploading 34.54MiB to 206.223.170.146
18:36:04:WU01:FS00:Connecting to 206.223.170.146:8080
18:36:10:WU01:FS00:Upload 10.49%