Page 1 of 1
Woops looks like we may have an empty work server
Posted: Sat Sep 26, 2015 6:22 pm
by Grandpa_01
Code: Select all
17:52:20:WU01:FS02:0xa4:Completed 79200 out of 80000 steps (99%)
17:52:20:WU00:FS02:Connecting to 171.67.108.200:8080
17:52:20:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
17:52:20:WU00:FS02:Connecting to 171.67.108.204:80
17:52:21:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:52:21:ERROR:WU00:FS02:Exception: Could not get an assignment
17:52:21:WU00:FS02:Connecting to 171.67.108.200:8080
17:52:21:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
17:52:21:WU00:FS02:Connecting to 171.67.108.204:80
17:52:22:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:52:22:ERROR:WU00:FS02:Exception: Could not get an assignment
17:52:47:WU01:FS02:0xa4:Completed 80000 out of 80000 steps (100%)
17:52:48:WU01:FS02:0xa4:DynamicWrapper: Finished Work Unit: sleep=10000
17:52:58:WU01:FS02:0xa4:
17:52:58:WU01:FS02:0xa4:Finished Work Unit:
17:52:58:WU01:FS02:0xa4:- Reading up to 4126776 from "01/wudata_01.trr": Read 4126776
17:52:58:WU01:FS02:0xa4:trr file hash check passed.
17:52:58:WU01:FS02:0xa4:- Reading up to 3196876 from "01/wudata_01.xtc": Read 3196876
17:52:58:WU01:FS02:0xa4:xtc file hash check passed.
17:52:58:WU01:FS02:0xa4:edr file hash check passed.
17:52:58:WU01:FS02:0xa4:logfile size: 19867
17:52:58:WU01:FS02:0xa4:Leaving Run
17:52:59:WU01:FS02:0xa4:- Writing 7345911 bytes of core data to disk...
17:53:00:WU01:FS02:0xa4:Done: 7345399 -> 7073408 (compressed to 96.2 percent)
17:53:00:WU01:FS02:0xa4: ... Done.
17:53:06:WU01:FS02:0xa4:- Shutting down core
17:53:06:WU01:FS02:0xa4:
17:53:06:WU01:FS02:0xa4:Folding@home Core Shutdown: FINISHED_UNIT
17:53:07:WU01:FS02:FahCore returned: FINISHED_UNIT (100 = 0x64)
17:53:07:WU01:FS02:Sending unit results: id:01 state:SEND error:NO_ERROR project:9752 run:1792 clone:0 gen:310 core:0xa4 unit:0x00000195ab40416355417404fd0a3525
17:53:07:WU01:FS02:Uploading 6.75MiB to 171.64.65.99
17:53:07:WU01:FS02:Connecting to 171.64.65.99:8080
17:53:13:WU01:FS02:Upload 71.34%
17:53:18:WU01:FS02:Upload complete
17:53:18:WU01:FS02:Server responded WORK_ACK (400)
17:53:18:WU01:FS02:Final credit estimate, 4770.00 points
17:53:18:WU01:FS02:Cleaning up
17:53:21:WU00:FS02:Connecting to 171.67.108.200:8080
17:53:21:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
17:53:21:WU00:FS02:Connecting to 171.67.108.204:80
17:53:22:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:53:22:ERROR:WU00:FS02:Exception: Could not get an assignment
17:54:58:WU00:FS02:Connecting to 171.67.108.200:8080
17:54:59:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
17:54:59:WU00:FS02:Connecting to 171.67.108.204:80
17:54:59:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:54:59:ERROR:WU00:FS02:Exception: Could not get an assignment
17:57:36:WU00:FS02:Connecting to 171.67.108.200:8080
17:57:36:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
17:57:36:WU00:FS02:Connecting to 171.67.108.204:80
17:57:36:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
17:57:36:ERROR:WU00:FS02:Exception: Could not get an assignment
18:01:50:WU00:FS02:Connecting to 171.67.108.200:8080
18:01:50:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
18:01:50:WU00:FS02:Connecting to 171.67.108.204:80
18:01:51:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
18:01:51:ERROR:WU00:FS02:Exception: Could not get an assignment
18:08:41:WU00:FS02:Connecting to 171.67.108.200:8080
18:08:41:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
18:08:41:WU00:FS02:Connecting to 171.67.108.204:80
18:08:42:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
18:08:42:ERROR:WU00:FS02:Exception: Could not get an assignment
18:19:47:WU00:FS02:Connecting to 171.67.108.200:8080
18:19:56:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
18:19:56:WU00:FS02:Connecting to 171.67.108.204:80
18:19:57:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
18:19:57:ERROR:WU00:FS02:Exception: Could not get an assignment
Re: Woops looks like we may have an empty work server
Posted: Sat Sep 26, 2015 6:56 pm
by Joe_H
Without any information as to the configuration of the system requesting work, no way of telling which server(s) are out. The empty WS messages from the assignment servers just means they can not match up your system's request with a WS that has appropriate WU's available. Besides 171.64.65.99 which your system just uploaded a WU to, what other WS addresses have assigned this system work in the recent past?
Re: Woops looks like we may have an empty work server
Posted: Sat Sep 26, 2015 6:58 pm
by Grandpa_01
Yea they got it going again and it only took 46 min. on a Saturday, Good Job
I thought it was supposed to switch automatically if a server was out of work ?
Code: Select all
18:38:30:WARNING:WU00:FS02:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
18:38:30:ERROR:WU00:FS02:Exception: Could not get an assignment
18:45:21:WU00:FS02:Connecting to 171.67.108.200:8080
18:45:21:WU00:FS02:Assigned to work server 171.64.65.99
18:45:21:WU00:FS02:Requesting new work unit for slot 02: READY cpu:31 from 171.64.65.99
18:45:21:WU00:FS02:Connecting to 171.64.65.99:8080
18:45:24:WU00:FS02:Downloading 6.24MiB
18:45:57:WU00:FS02:Download 11.01%
18:46:01:WU00:FS02:Download complete
18:46:01:WU00:FS02:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:9752 run:1682 clone:0 gen:341 core:0xa4 unit:0x000001b2ab404163554173e1a5defcd7
18:46:01:WU00:FS02:Starting
Re: Woops looks like we may have an empty work server
Posted: Sat Sep 26, 2015 7:23 pm
by Grandpa_01
Hmm maybe I spoke too soon it appears to be an intermittent problem and I only see 171.64.65.99:8080 2 more of the Linus SMP rigs have had problems looking back through the logs in the last hour or so.
edit
looking at the server log it looks like it may be having some trouble only 2 lines show up on the report in a couple of instances in the last hour or so. Port 80 appears to be missing in those.
Re: Woops looks like we may have an empty work server
Posted: Sat Sep 26, 2015 7:37 pm
by bruce
[That message does not say there's an "empty work server" but rather that the list of servers to which you can be assigned is empty.
You probably need to remove/relax any settings which would tend to restrict your choices to a limited number of servers.
Re: Woops looks like we may have an empty work server
Posted: Sat Sep 26, 2015 7:49 pm
by Joe_H
There are a limited number of servers with work for larger numbers of CPU cores, and one has been temporarily restricted for assignments due to problems. 171.64.65.99 appears to be processing returned WU's and assigning the resulting next Gen WU's as fast as it is getting them in.
One issue in your configuration, it is requesting for 31 cores. As a large prime, that is always going to get adjusted down to 30 at least. You may get easier assignments if you set it to 30. Also, the last I checked, there are more assignments that top out at 24 cores than for more than that.
Re: Woops looks like we may have an empty work server
Posted: Sat Sep 26, 2015 9:32 pm
by Grandpa_01
I am not running any restrictions at the moment I am guessing it is the server issue. I have not lost a single smp due to the 31 cores which is the default setting. Unfortunately running 1 bigadv or 3 smp slots get less PPD by quite a bit than running 2 on these big boxen and really is not worth the electricity, if the do not have enough to feed them that is fine I have done close to 2000 smp WU's in just under 3 weeks and I am only currently running 3 of the 7 rigs. I also know brilong was bringing some more big rigs online and that has probably put a strain on the system. I can see where that might be a problem since they are making most of the new WU's less friendly to bigger rigs in one way or another whether in points or lack of work. I will try 3 again if my ppd drops like it did before I will just use the bigger rigs for other projects, it is no big deal to me.
Thanks for the explanation it is appreciated.
Re: Woops looks like we may have an empty work server
Posted: Sun Sep 27, 2015 1:28 am
by Grandpa_01
Well it looks like if you are on a bigger boxen it does not matter how many slots you run smp on you still get assigned to the same server. So even if a person wanted to run the 24 core limited WU's it is not going to happen.
Re: Woops looks like we may have an empty work server
Posted: Mon Sep 28, 2015 1:31 am
by Grandpa_01
I did find a cure to the situation, I am now running both v6 and v7 of FAH I am able to run the bigadv or whatever you wish to call them on the H v6 which they run quite a bit faster on this version of v6 than they do on v7, and I run the GPU's on v7. It is a bit of a pain to have to install and run both v6 and v7 on a rig but it makes it worthwhile to run the MP boxen and relieves the pressure on the limited amount of regular smp wu's that will run on these rigs.
Re: Woops looks like we may have an empty work server
Posted: Mon Sep 28, 2015 12:32 pm
by rpmouton
Looking at this sad story that we have to run V6 to get WU´s otherwise nada..
I am just going to remove my CPU clients as they run out of work, so that others that do not GPU fold can process them.
Let us know when we should turn them back on
Re: Woops looks like we may have an empty work server
Posted: Mon Sep 28, 2015 6:21 pm
by toTOW
I had a few Empty work server errors too on machine with odd numbers of cores (SMP 7) ... we might be low on such type of work.
Re: Woops looks like we may have an empty work server
Posted: Mon Sep 28, 2015 8:16 pm
by toTOW
Quick update : I got a confirmation that Pande group is looking at this issue
Re: Woops looks like we may have an empty work server
Posted: Mon Sep 28, 2015 8:36 pm
by toTOW
Issue should be fixed after a reboot of a server hosting some SMP projects.
Please post if you're still having issues.