Empty work server assignment:

[Joe_H]

No, eventually more WU's will move to the full folding status or will be generated as ones currently out for processing are returned and generate the next WU in the sequence. As for adding the client-type advanced setting, the directions boil down to the following:

Open FAHControl and click on the Configure button

Select the Slots tab, click on the CPU slot and then click the Edit control

A window will pop up labelled Configure folding slot, at the bottom will be Extra slot options with Add and Remove buttons

Click on Add, enter client-type in the option Name field and advanced in the Value field

Then click on OK on that box, OK on the slot configuration window and then Save the settings.

[Macaholic]

Looking at my three Mac Pros, the two 8 thread are getting units with client-type advanced and the one 16 thread with client-type advanced is having the issue. Could be that the core count setting is the problem for the AS.

[AlanH]

I've set up the other two Macs as client-type: advanced and they started folding (a MBP and a retina iMac). I've now reinstalled FaH on my old MacPro, and that seems to be folding again as well.

So I'm not sure what that was about. If client-type: advanced has suddenly become a requirement, I strongly suggest that it is set as a default config. Getting people to type in obscure config additions is not going to help the cause.

[Joe_H]

I don't think this will become a requirement. I suspect that the issue will be just a temporary one linked to the one server going off line and reducing the number of available WU's and projects for full folding release and assignment to OS X systems. If there is an additional problem causing this, hopefully the log information that mpiercy has been able to look at will help identify the cause and make corrections.

[SpockLogic]

Thanks to Joe_H for the client-type advanced setting info. I had an 8 core MacPro and 4 core i7 Hackintosh both dormant for a day or so that are now happily folding again.

[iBozz]

Is it me or is it F@H?

For 14 or more hours my Yosemite Folding v7.44 has remained "Inactive".

I've rebooted but still no work units available - or so it seems.

Here is the log, so can any more IT savvy Folder advise me?

Many thanks in advance.

Code: Select all

*********************** Log Started 2014-12-17T14:44:40Z ***********************
14:44:40:************************* Folding@home Client *************************
14:44:40:    Website: http://folding.stanford.edu/
14:44:40:  Copyright: (c) 2009-2014 Stanford University
14:44:40:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
14:44:40:       Args: --child --lifeline 56 --respawn
14:44:40:     Config: /Library/Application Support/FAHClient/config.xml
14:44:40:******************************** Build ********************************
14:44:40:    Version: 7.4.4
14:44:40:       Date: Mar 4 2014
14:44:40:       Time: 20:27:54
14:44:40:    SVN Rev: 4130
14:44:40:     Branch: fah/trunk/client
14:44:40:   Compiler: GNU 4.2.1 (Apple Inc. build 5666) (dot 3)
14:44:40:    Options: -std=gnu++98 -O3 -funroll-loops -mfpmath=sse -ffast-math
14:44:40:             -fno-unsafe-math-optimizations -msse3 -arch x86_64
14:44:40:             -mmacosx-version-min=10.6
14:44:40:   Platform: darwin 10.8.0
14:44:40:       Bits: 64
14:44:40:       Mode: Release
14:44:40:******************************* System ********************************
14:44:40:        CPU: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz
14:44:40:     CPU ID: GenuineIntel Family 6 Model 30 Stepping 5
14:44:40:       CPUs: 8
14:44:40:     Memory: 16.00GiB
14:44:40:Free Memory: 15.21GiB
14:44:40:    Threads: POSIX_THREADS
14:44:40: OS Version: 10.10
14:44:40:Has Battery: false
14:44:40: On Battery: false
14:44:40: UTC Offset: 0
14:44:40:        PID: 140
14:44:40:        CWD: /Library/Application Support/FAHClient
14:44:40:         OS: Darwin 14.0.0 x86_64
14:44:40:    OS Arch: AMD64
14:44:40:       GPUs: 1
14:44:40:      GPU 0: UNSUPPORTED: M98L [Mobility Radeon HD 4850]
14:44:40:       CUDA: Not detected
14:44:40:***********************************************************************
14:44:40:<config>
14:44:40:  <!-- Network -->
14:44:40:  <proxy v=':8080'/>
14:44:40:
14:44:40:  <!-- Slot Control -->
14:44:40:  <power v='full'/>
14:44:40:
14:44:40:  <!-- User Information -->
14:44:40:  <passkey v='********************************'/>
14:44:40:  <team v='37761'/>
14:44:40:  <user v='iBozz'/>
14:44:40:
14:44:40:  <!-- Folding Slots -->
14:44:40:  <slot id='0' type='CPU'/>
14:44:40:</config>
14:44:40:Trying to access database...
14:44:41:Successfully acquired database lock
14:44:41:Enabled folding slot 00: READY cpu:8
14:44:46:WARNING:WU00:FS00:Exception: Could not get IP address for assign3.stanford.edu: nodename nor servname provided, or not known
14:44:46:ERROR:WU00:FS00:Exception: Could not get an assignment
14:44:46:WARNING:WU00:FS00:Exception: Could not get IP address for assign3.stanford.edu: nodename nor servname provided, or not known
14:44:46:ERROR:WU00:FS00:Exception: Could not get an assignment
14:45:47:WARNING:WU00:FS00:Exception: Could not get IP address for assign3.stanford.edu: nodename nor servname provided, or not known
14:45:47:ERROR:WU00:FS00:Exception: Could not get an assignment
14:47:24:WU00:FS00:Connecting to 171.67.108.200:8080
14:47:26:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
14:47:26:WU00:FS00:Connecting to 171.67.108.204:80
14:47:27:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
14:47:27:ERROR:WU00:FS00:Exception: Could not get an assignment
14:50:01:WU00:FS00:Connecting to 171.67.108.200:8080
14:50:02:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
14:50:02:WU00:FS00:Connecting to 171.67.108.204:80
14:50:02:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
14:50:02:ERROR:WU00:FS00:Exception: Could not get an assignment
14:54:15:WU00:FS00:Connecting to 171.67.108.200:8080
14:54:16:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
14:54:16:WU00:FS00:Connecting to 171.67.108.204:80
14:54:17:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
14:54:17:ERROR:WU00:FS00:Exception: Could not get an assignment
15:01:07:WU00:FS00:Connecting to 171.67.108.200:8080
15:01:07:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
15:01:07:WU00:FS00:Connecting to 171.67.108.204:80
15:01:08:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
15:01:08:ERROR:WU00:FS00:Exception: Could not get an assignment
15:12:12:WU00:FS00:Connecting to 171.67.108.200:8080
15:12:13:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
15:12:13:WU00:FS00:Connecting to 171.67.108.204:80
15:12:15:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
15:12:15:ERROR:WU00:FS00:Exception: Could not get an assignment
15:30:09:WU00:FS00:Connecting to 171.67.108.200:8080
15:30:10:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
15:30:10:WU00:FS00:Connecting to 171.67.108.204:80
15:30:11:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
15:30:11:ERROR:WU00:FS00:Exception: Could not get an assignment
15:59:11:WU00:FS00:Connecting to 171.67.108.200:8080
15:59:15:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
15:59:15:WU00:FS00:Connecting to 171.67.108.204:80
15:59:16:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
15:59:16:ERROR:WU00:FS00:Exception: Could not get an assignment
16:46:10:WU00:FS00:Connecting to 171.67.108.200:8080
16:46:11:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
16:46:11:WU00:FS00:Connecting to 171.67.108.204:80
16:46:12:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
16:46:12:ERROR:WU00:FS00:Exception: Could not get an assignment

[iBozz]

Apologies, I forgot to update my signature which should correctly now read:

27" i7 quad-core iMac running under MacOSX.10.10.1 Build 14B25 Yosemite, 1TB HD, 16GB RAM

[RobertVan]

Joe_H thanks. That got my 4 computers back up and folding. been not folding for at least 2 days with my macs.

[mpiercy]

Hi,

Looks like its running again, I fixed some simple errors,

Thanks,

Mark

[bruce]

So I'm not sure what that was about. If client-type: advanced has suddenly become a requirement, I strongly suggest that it is set as a default config. Getting people to type in obscure config additions is not going to help the cause.

I don't think this will become a requirement. I suspect that the issue will be just a temporary one linked to the one ...

This will most definitely not become a requirement, but it will continue to be an option that you can choose. Every new project is tested and goes through a series of progressively relaxed restrictions. Beta is reserved for projects with a high degree of risk of failures. Once that is completed, there's still some risk, so the project is moved to Advanced. After a suitable time lapse, if no problems remain, the project is moved to full FAH.

In this case, all of the risk-free projects happened to be on a server which was temporarily off-line. The only projects that were available were advanced so those with the default settings had to wait until they could be assigned projects which had been assigned to the lowest risk category.

[MacRat]

Looks like its running again, I fixed some simple errors,

Confirming that my 8 Macs are doing work again.

[AlanH]

This will most definitely not become a requirement, but it will continue to be an option that you can choose. Every new project is tested and goes through a series of progressively relaxed restrictions. Beta is reserved for projects with a high degree of risk of failures. Once that is completed, there's still some risk, so the project is moved to Advanced. After a suitable time lapse, if no problems remain, the project is moved to full FAH.

In this case, all of the risk-free projects happened to be on a server which was temporarily off-line. The only projects that were available were advanced so those with the default settings had to wait until they could be assigned projects which had been assigned to the lowest risk category.

So should I remove the advanced setting now?

[bruce]

So should I remove the advanced setting now?

That's up to you. You can remove it or you can leave it, based on your tolerance for an occasional WU being dumped vs. your willingness to remain idle if that server is ever down again. You can revisit that decision at any time, too. No matter which setting you choose, if you notice any problems, please report them here in the forum.

FACT: Advanced projects eventually get released to full FAH so there aren't always any such projects but it doesn't hurt to show your willingness to process them if that fits your style. On the other hand, new projects can appear in Advanced at any time. If none are available, you'll get regular released projects.

[pompeyrodney]

Hi
I seem to have the same issue running 7.4.4 on Windows 8 32 bit. Here are my errors

Code: Select all

21:56:10:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.200:80': Empty work server assignment
21:56:11:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
21:56:11:ERROR:WU01:FS01:Exception: Could not get an assignment

I should point out that my SMP client appears fine but it is the GPU client with this issue. Help please?

[davidcoton]

@pompeyrodney
Please post the full log, so we can see your hardware and configuration. See viewtopic.php?f=24&t=26036 for instructions on posting logs and other "getting help" tips.