I have two Linux machines that are running GPU's (GTX 780's) which are both sitting at the 'Ready' stage indicating the above message in the log (also see end of log attached below) - has the Core 17 work temporarily run dry for Linux GPU's?
03:02:59:WU01:FS01:0x17:Completed 4750000 out of 5000000 steps (95%)
03:09:38:WU01:FS01:0x17:Completed 4800000 out of 5000000 steps (96%)
03:16:09:WU01:FS01:0x17:Completed 4850000 out of 5000000 steps (97%)
03:22:47:WU01:FS01:0x17:Completed 4900000 out of 5000000 steps (98%)
03:29:16:WU01:FS01:0x17:Completed 4950000 out of 5000000 steps (99%)
03:35:45:WU01:FS01:0x17:Completed 5000000 out of 5000000 steps (100%)
03:35:46:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
03:35:47:WU00:FS01:News:
03:35:47:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:80': Empty work server assignment
03:35:47:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
03:35:48:WU00:FS01:News:
03:35:48:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Empty work server assignment
03:35:48:ERROR:WU00:FS01:Exception: Could not get an assignment
03:35:48:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
03:35:49:WU00:FS01:News:
03:35:49:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:80': Empty work server assignment
03:35:49:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
03:35:49:WU00:FS01:News:
03:35:49:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Empty work server assignment
03:35:49:ERROR:WU00:FS01:Exception: Could not get an assignment
03:35:53:WU01:FS01:0x17:Saving result file logfile_01.txt
03:35:53:WU01:FS01:0x17:Saving result file checkpointState.xml
03:35:55:WU01:FS01:0x17:Saving result file checkpt.crc
03:35:55:WU01:FS01:0x17:Saving result file log.txt
03:35:55:WU01:FS01:0x17:Saving result file positions.xtc
03:35:57:WU01:FS01:0x17:Folding@home Core Shutdown: FINISHED_UNIT
03:35:57:WU01:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
03:35:57:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:13001 run:54 clone:0 gen:81 core:0x17 unit:0x0000008c538b3db753285ef94b762bc3
03:35:58:WU01:FS01:Uploading 12.83MiB to 140.163.4.231
03:35:58:WU01:FS01:Connecting to 140.163.4.231:8080
03:36:04:WU01:FS01:Upload 63.35%
03:36:17:WU01:FS01:Upload complete
03:36:17:WU01:FS01:Server responded WORK_ACK (400)
03:36:17:WU01:FS01:Final credit estimate, 79677.00 points
03:36:17:WU01:FS01:Cleaning up
03:36:48:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
03:36:49:WU00:FS01:News:
03:36:49:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:80': Empty work server assignment
03:36:49:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
03:36:49:WU00:FS01:News:
03:36:49:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Empty work server assignment
03:36:49:ERROR:WU00:FS01:Exception: Could not get an assignment
03:38:25:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
03:38:26:WU00:FS01:News:
03:38:26:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:80': Empty work server assignment
03:38:26:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
03:38:27:WU00:FS01:News:
03:38:27:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Empty work server assignment
03:38:27:ERROR:WU00:FS01:Exception: Could not get an assignment
03:41:02:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
03:41:03:WU00:FS01:News:
03:41:03:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:80': Empty work server assignment
03:41:03:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
03:41:04:WU00:FS01:News:
03:41:04:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Empty work server assignment
03:41:04:ERROR:WU00:FS01:Exception: Could not get an assignment
03:45:17:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
03:45:17:WU00:FS01:News:
03:45:17:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:80': Empty work server assignment
03:45:17:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
03:45:18:WU00:FS01:News:
03:45:18:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Empty work server assignment
03:45:18:ERROR:WU00:FS01:Exception: Could not get an assignment
03:52:08:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
03:52:09:WU00:FS01:News:
03:52:09:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:80': Empty work server assignment
03:52:09:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
03:52:10:WU00:FS01:News:
03:52:10:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Empty work server assignment
03:52:10:ERROR:WU00:FS01:Exception: Could not get an assignment
04:03:14:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
04:03:15:WU00:FS01:News:
04:03:15:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:80': Empty work server assignment
04:03:15:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
04:03:15:WU00:FS01:News:
04:03:15:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Empty work server assignment
04:03:15:ERROR:WU00:FS01:Exception: Could not get an assignment
04:21:11:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
04:21:12:WU00:FS01:News:
04:21:12:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:80': Empty work server assignment
04:21:12:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
04:21:12:WU00:FS01:News:
04:21:12:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Empty work server assignment
04:21:12:ERROR:WU00:FS01:Exception: Could not get an assignment
04:50:13:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
04:50:14:WU00:FS01:News:
04:50:14:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:80': Empty work server assignment
04:50:14:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
04:50:15:WU00:FS01:News:
04:50:15:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Empty work server assignment
04:50:15:ERROR:WU00:FS01:Exception: Could not get an assignment
05:37:12:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
05:37:21:WU00:FS01:News:
05:37:21:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:80': Empty work server assignment
05:37:21:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
05:37:22:WU00:FS01:News:
05:37:22:WARNING:WU00:FS01:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Empty work server assignment
05:37:22:ERROR:WU00:FS01:Exception: Could not get an assignment
I've been getting that message too, but on cpu clients not gpu, oddly enough. All on either Linux or OS X, which is Unix underneath of course so maybe that's the common factor?
I suspect it's more related to the AS problems than a shortage of work.
How the supply of available WUs is assigned does depend on rather complex logic in the AS. We've been getting reports of shortages for somewhat more than 24 hours so it's certainly possible that there's an AS problem. As you've already said, Linux vs. Windows matters. It should also be noted that DocJonz is asking about a GTX 780 which is a Kepler and there are at least four types of NV GPUs as well as a couple of ATI types, and the mapping of specific projects also may be limited based on the type of GPU.
Bilford's report doesn't specify which GPU is being reported nor does it specify the IP address of the AS and whether you're running client-type=advanced or not.
bruce wrote:
Bilford's report doesn't specify which GPU is being reported.
Sorry, it's early in the morning here
2 GPUs- a 780Ti and a 650Ti, both Linux.
The 780Ti was on Windows until yesterday but then it started getting Core15's, so it seemed a good time to get an item off the "to do" list and change the machine to Linux (Ubuntu if it matters, the 650Ti is Mint).
06:36:11:WU01:FS00:0xa4:DynamicWrapper: Finished Work Unit: sleep=10000
06:36:12:WU00:FS00:Connecting to 171.67.108.200:8080
06:36:13:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
06:36:13:WU00:FS00:Connecting to 171.64.65.121:80
06:36:13:WU00:FS00:Assigned to work server 155.247.166.220
06:36:13:WU00:FS00:Requesting new work unit for slot 00: RUNNING cpu:4 from 155.247.166.220
06:36:13:WU00:FS00:Connecting to 155.247.166.220:8080
06:36:14:WU00:FS00:Downloading 197.59KiB
06:36:14:WU00:FS00:Download complete
06:36:14:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:6383 run:8 clone:0 gen:2 core:0xa4 unit:0x000000020002894c54173866b849ad96
That was an OS X machine, the only upset on the gpu's was getting Core15's on the Windows machine, since I switched to Linux both have been getting Core17's with no problems.
Just noticed something else which may simply be coincidence or may be of significance- one smp machine hasn't (yet) had any empty WS assignments, and it's the only one (out of 6) which I haven't yet got around to updating to 7.4.4 from 7.3.6.
On all my systems, only SMP rigs are getting work units, absolutely nothing for GPUs including all AMD and Nvidia on Windows 7 x64. All are sitting idle right now.
In Texas, it's starting to get cool in the mornings. I'd rather turn on the heat by folding, not with HVAC
I've been getting the same message as the OP all morning. This on a Win 7 Amd GPU box. I just upgraded from V.7.3.6 to V.7.4.4, and I'm receiving work again.
13:17:00:WU02:FS01:0x17:Completed 5000000 out of 5000000 steps (100%)
13:17:01:WU01:FS01:Connecting to 171.67.108.201:80
13:17:02:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
13:17:02:WU01:FS01:Connecting to 171.64.65.160:80
13:17:03:WU01:FS01:Assigned to work server 171.67.108.52
13:17:03:WU01:FS01:Requesting new work unit for slot 01: RUNNING gpu:0:GK110 [GeForce GTX 780 Ti] from 171.67.108.52
13:17:03:WU01:FS01:Connecting to 171.67.108.52:8080
13:17:04:WU01:FS01:Downloading 1.52MiB
13:17:05:WU02:FS01:0x17:Saving result file logfile_01.txt
13:17:05:WU02:FS01:0x17:Saving result file checkpointState.xml
13:17:06:WU01:FS01:Download complete
13:17:06:WU01:FS01:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:9201 run:124 clone:0 gen:203 core:0x17 unit:0x0000010b6652edc45399dae261446fb6
v7.4.4, Linux, client-type is empty. So it's giving Core_17's to some people
Upgraded all my V.7.3.6 to V.7.4.4 and now they are folding.
I am using windows. All Nvidia cards get core 15, but all AMD gets core 17.
Funny thing, my machine folding on V.7.4.4 did not work until I downloaded V.7.4.4 and re-installed it. Restart of client or computer did not work. Strange.
Sn1ken wrote:Upgraded all my V.7.3.6 to V.7.4.4 and now they are folding.
I am using windows. All Nvidia cards get core 15, but all AMD gets core 17.
Funny thing, my machine folding on V.7.4.4 did not work until I downloaded V.7.4.4 and re-installed it. Restart of client or computer did not work. Strange.
I was having the same problem as the original poster. No WU for over 12 hours.
Windows 7x64 pro with AMD Tahiti XT graphics card.
I upgraded to v7.4.4 and immediately got a WU for my AMD
