Trouble getting workunits

[Peter_Hucker]

I've been away for 2.5 weeks. I came back and connected 13 GPUs on 6 machines, and they're all taking quite some time to get a work unit. Is there an overload or technical problem somewhere?

I mentioned it on Github and Joseph Coffland says the error below is indicative of a network problem. I have no problems connecting to anything else here. I'm not using a VPN or proxy. I have a 32 Mbit down 7 Mbit up stable fibre connection which is not under heavy use.

It's the EOF message I get most. (The HTTP_SERVICE_UNAVAILABLE is apparently due to running out of WUs for that project).

Code: Select all

00:06:59:I1::WU124:Requesting WU assignment for user PeterHucker_GRC_53ed9d9b7d568cb7eb1ccc25a7dc4492 team 224497
00:07:00:I1::WU124:Received WU assignment Gf3xRzoSgwuLR_WEWUEpfhAEmm18O2WzaWNXIXcAiQ8
00:07:00:I1::WU124:Downloading WU
00:07:01:E ::WU124:HTTP_SERVICE_UNAVAILABLE: {"error":{"message":"Please wait","code":503}}
00:07:01:I1::WU124:Retry #1 in 2 secs
00:07:03:I1::WU124:Requesting WU assignment for user PeterHucker_GRC_53ed9d9b7d568cb7eb1ccc25a7dc4492 team 224497
00:07:03:I1::WU124:Received WU assignment lQvcEkYaMYN8i38-wwYDp8DdViV53dLZzC3mZwGZJYg
00:07:03:I1::WU124:Downloading WU
00:07:03:E ::WU124:Failed response: EOF
00:07:03:I1::WU124:Retry #2 in 4 secs
00:07:07:I1::WU124:Downloading WU
00:07:08:E ::WU124:Failed response: EOF
00:07:08:I1::WU124:Retry #3 in 8 secs
00:07:16:I1::WU124:Downloading WU
00:07:16:E ::WU124:Failed response: EOF
00:07:16:I1::WU124:Retry #4 in 16 secs
00:07:32:I1::WU124:Downloading WU
00:07:32:E ::WU124:Failed response: EOF
00:07:32:I1::WU124:Retry #5 in 32 secs
00:08:04:I1::WU124:Downloading WU
00:08:04:E ::WU124:Failed response: EOF
00:08:04:I1::WU124:Retry #6 in 1 min 4 secs
00:09:08:I1::WU124:Downloading WU
00:09:08:E ::WU124:Failed response: EOF
00:09:08:I1::WU124:Retry #7 in 2 mins 8 secs
00:11:16:I1::WU124:Downloading WU
00:11:16:E ::WU124:Failed response: EOF
00:11:16:I1::WU124:Retry #8 in 4 mins 16 secs

[bollix47]

FYI, the problems you posted about in this and your other thread might indicate a wrong setting in your router .... I've had similar problems in the past where that turned out to be the situation.

If you can remember any change you might have made to those settings around the time your problems started you might try reversing that change.

Also, I noticed your returns are not receiving a bonus which indicates you're not using a Passkey .... your choice of course but if you wish to earn more then see https://apps.foldingathome.org/getpasskey .

[bollix47]

One more suggestion:

SInce you're using the beta v8 make sure it's the .18 version as earlier versions had some problems including in the comm area.

[Peter_Hucker]

I've not changed anything on the router. I do have several computers running through a bridge on the main computer (which has two network cards), but I've had that a long time and Folding didn't object before. No other programs (including Boinc, web browsers, etc) are having difficulties getting onto the internet. I can't think why I'm repeatedly getting EOF errors. Joseph Coffland only said it means network error, but in my network or yours? Is there any test I can do? Try to download a file from your server through a web browser? That's what we do in Boinc if there's a weird problem getting workunits, try to download a data file manually.

I am using a passkey. The reason I'm not getting a bonus is more likely one of my machines having a dodgy GPU which was consistently failing to start work units. Folding then blindly downloaded another and another ad nauseum and dropped me below the 80% threshold of successfull workunits. I've rebooted the machine and it's now behaving. I've raised this in Github with Joseph Coffland to see if he could impose a limit or warning when a computer is screwing up.

I am using .18 beta.

[toTOW]

I don't understand the error messages from v8 client ... can you try with a v7 one ?

[Peter_Hucker]

Tried with v7 and it downloaded immediately without problems.
Reinstalled v8 and it also didn't have problems.
Typical, things never go wrong when you test them, although I was sure I got the error every single time and several attempts were needed.

[Peter_Hucker]

Still getting problems. Are you short of work on some servers? I'm not sure how the system works, does a central server tell my computer to go ask server x for work, by which time server x has run out? Or is server x overloaded? The below log is weird. Firstly it seems to be told to contact temple.edu, which says please wait, but my computer than goes off to Berlin, which gives the weird EOF message many times.

This cycle usually repeats for about 10-20 minutes until a task is finally received.

16:53:11:I1::Added new work unit: cpus:0 gpus:gpu:39:00:00
16:53:11:I1::WU415:Requesting WU assignment for user PeterHucker_GRC_53ed9d9b7d568cb7eb1ccc25a7dc4492 team 224497
16:53:11:I1:OUT108:> POST https://assign2.foldingathome.org/api/assign HTTP/1.1
16:53:11:I3:Connecting to assign2.foldingathome.org:443
16:53:11:I1:OUT108:< assign2.foldingathome.org:443 HTTP/1.1 200 HTTP_OK
16:53:11:I1::WU415:Received WU assignment 3dSPWWRJ6GfuX9T7ak1W3G2sudK5rLyUacCd18W2MFo
16:53:11:I1::WU415:Downloading WU
16:53:12:I1:OUT109:> POST https://vav17.fah.temple.edu/api/assign HTTP/1.1
16:53:12:I3:Connecting to vav17.fah.temple.edu:443
16:53:12:I1:OUT109:< vav17.fah.temple.edu:443 HTTP/1.1 503 HTTP_SERVICE_UNAVAILABLE
16:53:12:E ::WU415:HTTP_SERVICE_UNAVAILABLE: {"error":{"message":"Please wait","code":503}}
16:53:12:I1::WU415:Retry #1 in 2 secs
16:53:14:I1::WU415:Requesting WU assignment for user PeterHucker_GRC_53ed9d9b7d568cb7eb1ccc25a7dc4492 team 224497
16:53:14:I1:OUT110:> POST https://assign3.foldingathome.org/api/assign HTTP/1.1
16:53:14:I3:Connecting to assign3.foldingathome.org:443
16:53:15:I1:OUT110:< assign3.foldingathome.org:443 HTTP/1.1 200 HTTP_OK
16:53:15:I1::WU415:Received WU assignment _QrtWzwt7-5YI30QoDGXYjeXHmQzHCCRvQavCVw8plg
16:53:15:I1::WU415:Downloading WU
16:53:15:I1:OUT111:> POST https://fah01.physik.fu-berlin.de/api/assign HTTP/1.1
16:53:15:I3:Connecting to fah01.physik.fu-berlin.de:443
16:53:15:E ::WU415:Failed response: EOF
16:53:15:I1::WU415:Retry #2 in 4 secs
16:53:19:I1::WU415:Downloading WU
16:53:19:I1:OUT112:> POST https://fah01.physik.fu-berlin.de/api/assign HTTP/1.1
16:53:19:I3:Connecting to fah01.physik.fu-berlin.de:443
16:53:19:E ::WU415:Failed response: EOF
16:53:19:I1::WU415:Retry #3 in 8 secs
16:53:27:I1::WU415:Downloading WU
16:53:27:I1:OUT113:> POST https://fah01.physik.fu-berlin.de/api/assign HTTP/1.1
16:53:27:I3:Connecting to fah01.physik.fu-berlin.de:443
16:53:27:E ::WU415:Failed response: EOF
16:53:27:I1::WU415:Retry #4 in 16 secs

[Joe_H]

Yes, your client's WU request first goes to an Assignment Server (AS) which transfers the request to a Work Server (WS) that should have WUs available for your configuration. The WU availability of any give server is updated periodically to the AS. At the moment there are 2 AS in operation, a primary one that handles most requests and a backup AS. You can check the server stats here - https://apps.foldingathome.org/serverstats.

[Peter_Hucker]

Thanks, I like that page, very useful.

It seems the servers my computer was asked to go to were low on work, one only shows 2 tasks available (I'm assuming that's what the public jobs column means).

Is it me having old cards causing there to be a small choice of things to do?