For two days server 171.67.108.35 appears to have stopped assigning WUs to 8-core machine. Server Stats http://fah-web.stanford.edu/pybeta/serverstat.html show that server is ok. Clean (re)install of 7.3.6 has the same problem with the same server.
16-core machine on another server is fine, both OSX 10.8.4.
Simple config.xml is unchanged since 7.3.6 came out
*********************** Log Started 2013-06-21T22:45:22Z ***********************
22:45:22:************************* Folding@home Client *************************
22:45:22: Website: http://folding.stanford.edu/
22:45:22: Copyright: (c) 2009-2013 Stanford University
22:45:22: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
22:45:22: Args:
22:45:22: Config: <none>
22:45:22:******************************** Build ********************************
22:45:22: Version: 7.3.6
22:45:22: Date: Feb 18 2013
22:45:22: Time: 15:24:11
22:45:22: SVN Rev: 3923
22:45:22: Branch: fah/trunk/client
22:45:22: Compiler: GNU 4.2.1 (Apple Inc. build 5666) (dot 3)
22:45:22: Options: -std=gnu++98 -O3 -funroll-loops -mfpmath=sse -ffast-math
22:45:22: -fno-unsafe-math-optimizations -msse3 -arch x86_64
22:45:22: -mmacosx-version-min=10.5 -isysroot /Developer/SDKs/MacOSX10.5.sdk
22:45:22: Platform: darwin 10.8.0
22:45:22: Bits: 64
22:45:22: Mode: Release
22:45:22:******************************* System ********************************
22:45:22: CPU: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
22:45:22: CPU ID: GenuineIntel Family 6 Model 42 Stepping 7
22:45:22: CPUs: 8
22:45:22: Memory: 4.00GiB
22:45:22:Free Memory: 1.01GiB
22:45:22: Threads: POSIX_THREADS
22:45:22:Has Battery: false
22:45:22: On Battery: false
22:45:22: UTC offset: -6
22:45:22: PID: 3790
22:45:22: CWD: /Library/Application Support/FAHClient
22:45:22: OS: Darwin 12.4.0 x86_64
22:45:22: OS Arch: AMD64
22:45:22: GPUs: 1
22:45:22: GPU 0: ATI:4 Whistler XT [AMD Radeon HD 6970M]
22:45:22: CUDA: Not detected
22:45:22:***********************************************************************
22:45:22:<config>
22:45:22: <!-- Folding Slots -->
22:45:22:</config>
22:45:22:Trying to access database...
22:45:22:Successfully acquired database lock
22:45:22:Enabled folding slot 00: PAUSED cpu:7 (not configured)
22:45:28:5:127.0.0.1:New Web connection
22:46:44:24:127.0.0.1:New Web connection
22:47:04:Set client configured
22:47:05:WU00:FS00:Connecting to assign3.stanford.edu:8080
22:47:05:WU00:FS00:Connecting to assign3.stanford.edu:8080
22:47:05:WU00:FS00:News: Welcome to Folding@Home
22:47:05:WU00:FS00:Assigned to work server 171.67.108.35
22:47:05:WU00:FS00:Requesting new work unit for slot 00: READY cpu:7 from 171.67.108.35
22:47:05:WU00:FS00:Connecting to 171.67.108.35:8080
22:47:06:ERROR:WU00:FS00:Exception: Server did not assign work unit
22:47:06:WU00:FS00:Connecting to assign3.stanford.edu:8080
22:47:06:WU00:FS00:News: Welcome to Folding@Home
22:47:06:WU00:FS00:Assigned to work server 171.67.108.35
22:47:06:WU00:FS00:Requesting new work unit for slot 00: READY cpu:7 from 171.67.108.35
22:47:06:WU00:FS00:Connecting to 171.67.108.35:8080
22:47:06:ERROR:WU00:FS00:Exception: Server did not assign work unit
22:48:06:WU00:FS00:Connecting to assign3.stanford.edu:8080
22:48:06:WU00:FS00:News: Welcome to Folding@Home
22:48:06:WU00:FS00:Assigned to work server 171.67.108.35
22:48:06:WU00:FS00:Requesting new work unit for slot 00: READY cpu:7 from 171.67.108.35
22:48:06:WU00:FS00:Connecting to 171.67.108.35:8080
22:48:07:ERROR:WU00:FS00:Exception: Server did not assign work unit
22:49:16:Saving configuration to config.xml
22:49:16:<config>
22:49:16: <!-- Folding Slots -->
22:49:16: <slot id='0' type='CPU'/>
22:49:16:</config>
22:49:43:WU00:FS00:Connecting to assign3.stanford.edu:8080
22:49:43:WU00:FS00:News: Welcome to Folding@Home
22:49:43:WU00:FS00:Assigned to work server 171.67.108.35
22:49:43:WU00:FS00:Requesting new work unit for slot 00: READY cpu:7 from 171.67.108.35
22:49:43:WU00:FS00:Connecting to 171.67.108.35:8080
22:49:44:ERROR:WU00:FS00:Exception: Server did not assign work unit
22:52:20:WU00:FS00:Connecting to assign3.stanford.edu:8080
22:52:21:WU00:FS00:News: Welcome to Folding@Home
22:52:21:WU00:FS00:Assigned to work server 171.67.108.35
22:52:21:WU00:FS00:Requesting new work unit for slot 00: READY cpu:7 from 171.67.108.35
22:52:21:WU00:FS00:Connecting to 171.67.108.35:8080
22:52:21:ERROR:WU00:FS00:Exception: Server did not assign work unit
22:56:35:WU00:FS00:Connecting to assign3.stanford.edu:8080
22:56:35:WU00:FS00:News: Welcome to Folding@Home
22:56:35:WU00:FS00:Assigned to work server 171.67.108.35
22:56:35:WU00:FS00:Requesting new work unit for slot 00: READY cpu:7 from 171.67.108.35
22:56:35:WU00:FS00:Connecting to 171.67.108.35:8080
22:56:35:ERROR:WU00:FS00:Exception: Server did not assign work unit
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
Try setting the CPU count to 6 cores, or 8 cores. (I assume since you have an ATI card that the installer did an n-1 setup, reserved a core for the GPU, and this server may not like SMP:7)
Looking at the log page for the WS, it was set to assign only to beta testers up until a few hours ago. Your client is not showing any sign of being configured to run beta WU's. So the Assignment Server should not have been assigning your system to this WS. Did it eventually get reassigned to a different server?
Also, unless you edited your log file, it does not show any sign of being configured at all beyond having a CPU folding slot. Where did you find that config.xml file on your drive?
P.S. The client under OS X does not create a GPU slot, and in my experience normally does not adjust the core count other than the default use of n-1 cores unless the setting is at Full.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Since GPU folding is not supported on OS-X, there will be no slot created for your GPU. With a CPU that supports 8 threads, you can choose between SMP:6 or SMP:8. Normally the Assignment Server will redirect you from a server that has run out of assignments for your system to a server that does have WUs to assign. I'm not sure why that didn't work properly for you, but the SMP:7 setting is a good guess.
Your config also shows no signs of having been configured with your own identity or a passkey. While science does benefit and FAH is perfectly happy to credit points to Anonymous, that may not be what you really wanted.
Thank you for the replies. How it got to a Beta WS I have no idea, but it's going now.
The 4-core 8-thread machine has now been assigned a WU by WS 171.64.65.99 and is folding PRCG 7808 (2, 85, 98). It took off with SMP:7. I used the Web Control interface to switch is back to FULL, 8 threads. The client restarted without losing the WU or the work all ready completed.
Thank you bruce for spotting the anonymous, no team and no passkey. I saved an old copy of the config file on my desktop and just moved it into the directory /Library/Application\ Support/FAHClient/ thinking (hoping) it would be picked up. Edited the config.xml file using FAHControl.app to add user-team-passkey. The config file has been updated and the log file confirms it.
Again the client restarted the WU without any loss of work completed.
ps. All of the GPU log info is auto detect stuff from the installer, fah-installer_7.3.6_x86_64.pkg, same with the 8-core machine
stevew wrote:ps. All of the GPU log info is auto detect stuff from the installer, fah-installer_7.3.6_x86_64.pkg, same with the 8-core machine
Yes, the client will detect your GPU even on OS X. That was part of the design for the client that is common across all platforms - Windows, Linux and OS X. But since there is no GPU folding core available for OS X the install does not create a GPU slot based on that detection. The same currently holds for Linux installs also. If they can work through issues with programming an OpenCL folding core for OS X, there might be GPU folding on OS X at some point in the future. Currently that OpenCL based folding core is in beta test for Windows and Linux, you can read about it in the Beta test forum if you are interested
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Rereading this topic and wanted to add a comment on this part of your post:
stevew wrote:I saved an old copy of the config file on my desktop and just moved it into the directory /Library/Application\ Support/FAHClient/ thinking (hoping) it would be picked up.
Because of the way the FAHClient process is started in the background as a service, just placing the config.xml file in the directory is not enough to get it read. This is an issue for anyone upgrading from an old enough version of V7 or installing on a system that did not already have a prior installation. A system reboot or stopping and restarting the client from the command line would cause the config file to be read. In your case when you edited it from FAHControl did it fill in the entries for user, team and passkey already present in the old file? That would be a third way of initiating a read of the file that I had not used before on new or upgrade installations.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3