Adam A. Wanderer wrote:I hope there'll be an announcement.
Maybe there was. viewtopic.php?f=24&t=28878
Nobody (including vvoelz) can tell you if they're they’re dealing with the only server distributing to a particular class of hardware.
Which server(s) were delivering WUs to CPU:7 systems before folks stopped getting them? Nobody knows that unless those of you with some history in your logs gives us a report.
Nobody knows how to predict if a particular project will work reliably on CPU:7 systems. My guess is that there are some projects out there that might work but during beta testing, the project owner made a conservative guess and excluded 7 so it was never tested.
In addition there was this post - viewtopic.php?f=61&t=28860&p=286111#p286111. That group of projects was reported as frequently failing on CPU:14, which usually means they fail often at 7.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
I have had a similar problem for days on one of my systems. X99, 8-core processor. No cpu jobs. The gpus are all getting jobs just fine. But the cpu is sitting idle. There are 3 gpus, so there is no problem with multiples of 7. My cpu is waiting for a job with 13 strings available to work on it.
21:43:20:WU02:FS01:0x21:Completed 192000 out of 1600000 steps (12%)
21:43:30:WU03:FS03:0x21:Completed 775000 out of 2500000 steps (31%)
21:44:00:WU04:FS00:Connecting to 171.67.108.45:8080
21:44:00:WARNING:WU04:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
21:44:00:WU04:FS00:Connecting to 171.64.65.35:80
21:44:01:WU00:FS02:0x21:Completed 4950000 out of 5000000 steps (99%)
21:44:01:WARNING:WU04:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
21:44:01:ERROR:WU04:FS00:Exception: Could not get an assignment
21:44:51:WU02:FS01:0x21:Completed 208000 out of 1600000 steps (13%)
21:45:27:WU03:FS03:0x21:Completed 800000 out of 2500000 steps (32%)
21:46:19:WU02:FS01:0x21:Completed 224000 out of 1600000 steps (14%)
21:46:38:WU04:FS00:Connecting to 171.67.108.45:8080
21:46:38:WARNING:WU04:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
21:46:38:WU04:FS00:Connecting to 171.64.65.35:80
21:46:38:WARNING:WU04:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
21:46:38:ERROR:WU04:FS00:Exception: Could not get an assignment
21:47:25:WU03:FS03:0x21:Completed 825000 out of 2500000 steps (33%)
21:47:46:WU02:FS01:0x21:Completed 240000 out of 1600000 steps (15%)
21:47:48:WU00:FS02:0x21:Completed 5000000 out of 5000000 steps (100%)
21:47:49:WU01:FS02:Connecting to 171.67.108.45:80
21:47:49:WU01:FS02:Assigned to work server 140.163.4.243
21:47:49:WU01:FS02:Requesting new work unit for slot 02: RUNNING gpu:1:GM200 [GeForce GTX 980 Ti] from 140.163.4.243
21:47:49:WU01:FS02:Connecting to 140.163.4.243:8080
21:47:50:WU00:FS02:0x21:Saving result file logfile_01.txt
21:47:50:WU00:FS02:0x21:Saving result file checkpointState.xml
21:47:50:WU01:FS02:Downloading 2.67MiB
21:47:51:WU01:FS02:Download complete
21:47:51:WU01:FS02:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:11707 run:2 clone:6 gen:31 core:0x21 unit:0x000000248ca304f3570bbdaa3d01cf3e
21:47:51:WU00:FS02:0x21:Saving result file checkpt.crc
21:47:51:WU00:FS02:0x21:Saving result file log.txt
21:47:51:WU00:FS02:0x21:Saving result file positions.xtc
21:47:52:WU00:FS02:0x21:Folding@home Core Shutdown: FINISHED_UNIT
21:47:53:WU00:FS02:FahCore returned: FINISHED_UNIT (100 = 0x64)
21:47:53:WU00:FS02:Sending unit results: id:00 state:SEND error:NO_ERROR project:11402 run:2 clone:43 gen:122 core:0x21 unit:0x000000a08ca304f255ed4e5eaaaf773d
21:47:53:WU00:FS02:Uploading 10.82MiB to 140.163.4.242
21:47:53:WU00:FS02:Connecting to 140.163.4.242:8080
21:47:53:WU01:FS02:Starting
21:47:53:WU01:FS02:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/web.stanford.edu/~pande/Linux/AMD64/NVIDIA/Fermi/Core_21.fah/FahCore_21 -dir 01 -suffix 01 -version 704 -lifeline 1457 -checkpoint 30 -gpu 1 -gpu-vendor nvidia
21:47:53:WU01:FS02:Started FahCore on PID 7740
21:47:53:WU01:FS02:Core PID:7744
21:47:53:WU01:FS02:FahCore 0x21 started
21:47:53:WU01:FS02:0x21:*********************** Log Started 2016-06-05T21:47:53Z ***********************
21:47:53:WU01:FS02:0x21:Project: 11707 (Run 2, Clone 6, Gen 31)
21:47:53:WU01:FS02:0x21:Unit: 0x000000248ca304f3570bbdaa3d01cf3e
21:47:53:WU01:FS02:0x21:CPU: 0x00000000000000000000000000000000
21:47:53:WU01:FS02:0x21:Machine: 2
21:47:53:WU01:FS02:0x21:Reading tar file core.xml
21:47:53:WU01:FS02:0x21:Reading tar file system.xml
21:47:53:WU01:FS02:0x21:Reading tar file integrator.xml
21:47:53:WU01:FS02:0x21:Reading tar file state.xml
21:47:53:WU01:FS02:0x21:Digital signatures verified
21:47:53:WU01:FS02:0x21:Folding@home GPU Core21 Folding@home Core
21:47:53:WU01:FS02:0x21:Version 0.0.17
21:47:57:WU01:FS02:0x21:Completed 0 out of 7500000 steps (0%)
21:47:57:WU01:FS02:0x21:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
21:47:59:WU00:FS02:Upload 42.76%
21:48:07:WU00:FS02:Upload 74.55%
21:48:21:WU00:FS02:Upload complete
21:48:21:WU00:FS02:Server responded WORK_ACK (400)
21:48:21:WU00:FS02:Final credit estimate, 83702.00 points
21:48:21:WU00:FS02:Cleaning up
21:49:11:WU02:FS01:0x21:Completed 256000 out of 1600000 steps (16%)
21:49:21:WU03:FS03:0x21:Completed 850000 out of 2500000 steps (34%)
21:50:37:WU02:FS01:0x21:Completed 272000 out of 1600000 steps (17%)
21:50:52:WU04:FS00:Connecting to 171.67.108.45:8080
21:50:52:WARNING:WU04:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
21:50:52:WU04:FS00:Connecting to 171.64.65.35:80
21:50:53:WARNING:WU04:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
21:50:53:ERROR:WU04:FS00:Exception: Could not get an assignment
21:51:20:WU03:FS03:0x21:Completed 875000 out of 2500000 steps (35%)
21:51:47:WU01:FS02:0x21:Completed 75000 out of 7500000 steps (1%)
21:52:05:WU02:FS01:0x21:Completed 288000 out of 1600000 steps (18%)
21:53:16:WU03:FS03:0x21:Completed 900000 out of 2500000 steps (36%)
21:53:30:WU02:FS01:0x21:Completed 304000 out of 1600000 steps (19%)
21:54:54:WU02:FS01:0x21:Completed 320000 out of 1600000 steps (20%)
21:55:13:WU03:FS03:0x21:Completed 925000 out of 2500000 steps (37%)
21:55:36:WU01:FS02:0x21:Completed 150000 out of 7500000 steps (2%)
21:56:18:WU02:FS01:0x21:Completed 336000 out of 1600000 steps (21%)
21:57:09:WU03:FS03:0x21:Completed 950000 out of 2500000 steps (38%)
21:57:44:WU02:FS01:0x21:Completed 352000 out of 1600000 steps (22%)
21:57:48:WU04:FS00:Connecting to 171.67.108.45:8080
21:57:50:WARNING:WU04:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
21:57:50:WU04:FS00:Connecting to 171.64.65.35:80
21:57:51:WARNING:WU04:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
21:57:51:ERROR:WU04:FS00:Exception: Could not get an assignment
21:59:06:WU03:FS03:0x21:Completed 975000 out of 2500000 steps (39%)
21:59:09:WU02:FS01:0x21:Completed 368000 out of 1600000 steps (23%)
21:59:24:WU01:FS02:0x21:Completed 225000 out of 7500000 steps (3%)
22:00:33:WU02:FS01:0x21:Completed 384000 out of 1600000 steps (24%)
22:01:01:WU03:FS03:0x21:Completed 1000000 out of 2500000 steps (40%)
Then set the CPU count to a number other than 13. As mentioned multiple times in a number of threads, that number is not supported and never has been. Depending on the project and WS settings, some WU's may get assigned to requesting systems with CPU:13 set, but they will then map to 12 threads. If you have not been getting assignments, then apparently those projects are not currently available.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
It has been said many times: "Avoid large prime numbers"
Large is subject to definition, though, and have always prohibited 11 and 13. Seven has always been identified as a risk. So far, 5 seems to work.
GROMACS expects to be run on a dedicated real CPUs which generally are built around repeated multiples of 1, 2 or 3. (e.g.- 12 = 2*2*3) Unfortunately when FAH incorporated GROMACS into their CPU core, it was not limited to multiples of 2 or 3.
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).
Adam A. Wanderer wrote:I thought F@H had everything ironed out and we could "launch and forget" the program.
That has never been stated as a fact. A better characterization would be that the goal of the F@H client design with default settings was to be functional on the most common systems after install. So, these large CPU count systems are and always were outside the realm of "common", and have always needed some configuration tweaks to be optimum. What was common then were 2 and 4 core systems, with the high end of common being quad-core i7's as compared to i5's.
An additional item is that projects and processing emphasis have changed in the several years since the current client was created. The client does still work with those projects, but the defaults programmed into it no longer always work as well. Those advanced GPU cores and the AS/WS infrastructure to support them have required a large amount of programming time. Unfortunately, that has not left programming resources available for updating the client. Hopefully that will change sometime, and an updated client released. But until then higher end systems may take tweaking from the defaults to be more optimal, or in some cases to work at all.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
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).
The ability of the FAH client to remain "Set and Forget" over time has always depended on outside 3rd party software, for the cores, drivers, and operating system compatibility.
Set and Forget is still the design goal. But when GROMACs changes, the client will have to change along with it.
FAH has always been on the cutting edge of particularly challenging endeavours and set-and-forget doesn't live nicely in that territory, much as they'd like it to.
Changes to OSs and drivers are to be expected but there's usually an easy way forward.
New projects are generally more challenging than previous ones. They often involve upgraded analysis methods and the proteins being studied keep getting bigger.
If the aim of the research is to process additional data points for a concept that was previously established, then it's minimize changes. If data is being acquired for research of new concepts, you can expect that the unexpected will pop up from time to time.
For many days now (>14) none of the 3 computers, all running debian jessie, have worked on any WU's. They can't seem to connect to any servers. They worked fine since 7.4.4 was loaded more than a year ago and now -- nothing. What gives?
*********************** Log Started 2016-06-09T04:48:36Z ***********************
04:48:36:************************* Folding@home Client *************************
04:48:36: Website: http://folding.stanford.edu/
04:48:36: Copyright: (c) 2009-2014 Stanford University
04:48:36: Author: Joseph Coffland <[email protected]>
04:48:36: Args: --child --lifeline 1022 /etc/fahclient/config.xml --run-as
04:48:36: fahclient --pid-file=/var/run/fahclient.pid --daemon
04:48:36: Config: /etc/fahclient/config.xml
04:48:36:******************************** Build ********************************
04:48:36: Version: 7.4.4
04:48:36: Date: Mar 4 2014
04:48:36: Time: 12:02:38
04:48:36: SVN Rev: 4130
04:48:36: Branch: fah/trunk/client
04:48:36: Compiler: GNU 4.4.7
04:48:36: Options: -std=gnu++98 -O3 -funroll-loops -mfpmath=sse -ffast-math
04:48:36: -fno-unsafe-math-optimizations -msse2
04:48:36: Platform: linux2 3.2.0-1-amd64
04:48:36: Bits: 64
04:48:36: Mode: Release
04:48:36:******************************* System ********************************
04:48:36: CPU: AMD FX(tm)-8350 Eight-Core Processor
04:48:36: CPU ID: AuthenticAMD Family 21 Model 2 Stepping 0
04:48:36: CPUs: 8
04:48:36: Memory: 15.61GiB
04:48:36:Free Memory: 15.35GiB
04:48:36: Threads: POSIX_THREADS
04:48:36: OS Version: 3.16
04:48:36:Has Battery: false
04:48:36: On Battery: false
04:48:36: UTC Offset: -5
04:48:36: PID: 1024
04:48:36: CWD: /var/lib/fahclient
04:48:36: OS: Linux 3.16.0-4-amd64 x86_64
04:48:36: OS Arch: AMD64
04:48:36: GPUs: 0
04:48:36: CUDA: Not detected
04:48:36:***********************************************************************
04:48:36:<config>
04:48:36: <!-- Client Control -->
04:48:36: <fold-anon v='true'/>
04:48:36:
04:48:36: <!-- Folding Slot Configuration -->
04:48:36: <gpu v='false'/>
04:48:36:
04:48:36: <!-- Network -->
04:48:36: <proxy v=':8080'/>
04:48:36:
04:48:36: <!-- User Information -->
04:48:36: <passkey v='********************************'/>
04:48:36: <user v='ainut'/>
04:48:36:
04:48:36: <!-- Folding Slots -->
04:48:36: <slot id='0' type='CPU'/>
04:48:36:</config>
04:48:36:Switching to user fahclient
04:48:36:Trying to access database...
04:48:36:Successfully acquired database lock
04:48:36:Enabled folding slot 00: READY cpu:7
04:48:37:WARNING:WU00:FS00:Exception: Could not get IP address for assign3.stanford.edu: Temporary failure in name resolution
04:48:37:ERROR:WU00:FS00:Exception: Could not get an assignment
04:48:37:WARNING:WU00:FS00:Exception: Could not get IP address for assign3.stanford.edu: Temporary failure in name resolution
04:48:37:ERROR:WU00:FS00:Exception: Could not get an assignment
04:49:37:WU00:FS00:Connecting to 171.67.108.45:8080
04:49:38:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
04:49:38:WU00:FS00:Connecting to 171.64.65.35:80
04:49:38:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
04:49:38:ERROR:WU00:FS00:Exception: Could not get an assignment
04:51:14:WU00:FS00:Connecting to 171.67.108.45:8080
04:51:15:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
04:51:15:WU00:FS00:Connecting to 171.64.65.35:80
04:51:15:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
04:51:15:ERROR:WU00:FS00:Exception: Could not get an assignment
04:53:52:WU00:FS00:Connecting to 171.67.108.45:8080
04:53:52:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
04:53:52:WU00:FS00:Connecting to 171.64.65.35:80
04:53:53:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
04:53:53:ERROR:WU00:FS00:Exception: Could not get an assignment
04:58:06:WU00:FS00:Connecting to 171.67.108.45:8080
04:58:07:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
04:58:07:WU00:FS00:Connecting to 171.64.65.35:80
04:58:07:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
04:58:07:ERROR:WU00:FS00:Exception: Could not get an assignment
05:04:57:WU00:FS00:Connecting to 171.67.108.45:8080
05:04:58:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
05:04:58:WU00:FS00:Connecting to 171.64.65.35:80
05:04:58:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
05:04:58:ERROR:WU00:FS00:Exception: Could not get an assignment
05:16:03:WU00:FS00:Connecting to 171.67.108.45:8080
05:16:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
05:16:04:WU00:FS00:Connecting to 171.64.65.35:80
05:16:04:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
05:16:04:ERROR:WU00:FS00:Exception: Could not get an assignment
05:34:00:WU00:FS00:Connecting to 171.67.108.45:8080
05:34:00:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
05:34:00:WU00:FS00:Connecting to 171.64.65.35:80
05:34:01:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
05:34:01:ERROR:WU00:FS00:Exception: Could not get an assignment
06:03:02:WU00:FS00:Connecting to 171.67.108.45:8080
06:03:03:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
06:03:03:WU00:FS00:Connecting to 171.64.65.35:80
06:03:03:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
06:03:03:ERROR:WU00:FS00:Exception: Could not get an assignment
06:50:01:WU00:FS00:Connecting to 171.67.108.45:8080
06:50:01:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
06:50:01:WU00:FS00:Connecting to 171.64.65.35:80
06:50:02:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
06:50:02:ERROR:WU00:FS00:Exception: Could not get an assignment
08:06:02:WU00:FS00:Connecting to 171.67.108.45:8080
08:06:02:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
08:06:02:WU00:FS00:Connecting to 171.64.65.35:80
08:06:03:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
08:06:03:ERROR:WU00:FS00:Exception: Could not get an assignment
10:09:01:WU00:FS00:Connecting to 171.67.108.45:8080
10:09:02:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
10:09:02:WU00:FS00:Connecting to 171.64.65.35:80
10:09:02:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
10:09:02:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-09 *******************************
13:28:02:WU00:FS00:Connecting to 171.67.108.45:8080
13:28:02:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
13:28:02:WU00:FS00:Connecting to 171.64.65.35:80
13:28:03:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
13:28:03:ERROR:WU00:FS00:Exception: Could not get an assignment
18:50:02:WU00:FS00:Connecting to 171.67.108.45:8080
18:50:03:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:50:03:WU00:FS00:Connecting to 171.64.65.35:80
18:50:03:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
18:50:03:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-10 *******************************
00:50:02:WU00:FS00:Connecting to 171.67.108.45:8080
00:50:03:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:50:03:WU00:FS00:Connecting to 171.64.65.35:80
00:50:03:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:50:03:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-10 *******************************
06:50:02:WU00:FS00:Connecting to 171.67.108.45:8080
06:50:03:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
06:50:03:WU00:FS00:Connecting to 171.64.65.35:80
06:50:03:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
06:50:03:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-10 *******************************
12:50:02:WU00:FS00:Connecting to 171.67.108.45:8080
12:50:03:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
12:50:03:WU00:FS00:Connecting to 171.64.65.35:80
12:50:03:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
12:50:03:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-10 *******************************
18:50:03:WU00:FS00:Connecting to 171.67.108.45:8080
18:50:03:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:50:03:WU00:FS00:Connecting to 171.64.65.35:80
18:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
18:50:04:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-11 *******************************
00:50:03:WU00:FS00:Connecting to 171.67.108.45:8080
00:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:50:04:WU00:FS00:Connecting to 171.64.65.35:80
00:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:50:04:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-11 *******************************
06:50:03:WU00:FS00:Connecting to 171.67.108.45:8080
06:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
06:50:04:WU00:FS00:Connecting to 171.64.65.35:80
06:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
06:50:04:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-11 *******************************
12:50:03:WU00:FS00:Connecting to 171.67.108.45:8080
12:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
12:50:04:WU00:FS00:Connecting to 171.64.65.35:80
12:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
12:50:04:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-11 *******************************
18:50:03:WU00:FS00:Connecting to 171.67.108.45:8080
18:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:50:04:WU00:FS00:Connecting to 171.64.65.35:80
18:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
18:50:04:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-12 *******************************
00:50:03:WU00:FS00:Connecting to 171.67.108.45:8080
00:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:50:04:WU00:FS00:Connecting to 171.64.65.35:80
00:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:50:05:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-12 *******************************
06:50:04:WU00:FS00:Connecting to 171.67.108.45:8080
06:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
06:50:04:WU00:FS00:Connecting to 171.64.65.35:80
06:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
06:50:04:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-12 *******************************
12:50:04:WU00:FS00:Connecting to 171.67.108.45:8080
12:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
12:50:04:WU00:FS00:Connecting to 171.64.65.35:80
12:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
12:50:05:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-12 *******************************
18:50:04:WU00:FS00:Connecting to 171.67.108.45:8080
18:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:50:04:WU00:FS00:Connecting to 171.64.65.35:80
18:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
18:50:05:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-13 *******************************
00:50:04:WU00:FS00:Connecting to 171.67.108.45:8080
00:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:50:05:WU00:FS00:Connecting to 171.64.65.35:80
00:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:50:05:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-13 *******************************
06:50:04:WU00:FS00:Connecting to 171.67.108.45:8080
06:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
06:50:05:WU00:FS00:Connecting to 171.64.65.35:80
06:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
06:50:05:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-13 *******************************
12:50:04:WU00:FS00:Connecting to 171.67.108.45:8080
12:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
12:50:05:WU00:FS00:Connecting to 171.64.65.35:80
12:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
12:50:05:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-13 *******************************
18:50:05:WU00:FS00:Connecting to 171.67.108.45:8080
18:50:07:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:50:07:WU00:FS00:Connecting to 171.64.65.35:80
18:50:08:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
18:50:08:ERROR:WU00:FS00:Exception: Could not get an assignment
00:50:04:WU00:FS00:Connecting to 171.67.108.45:8080
******************************* Date: 2016-06-14 *******************************
00:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:50:05:WU00:FS00:Connecting to 171.64.65.35:80
00:50:06:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:50:06:ERROR:WU00:FS00:Exception: Could not get an assignment
06:50:04:WU00:FS00:Connecting to 171.67.108.45:8080
******************************* Date: 2016-06-14 *******************************
06:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
06:50:05:WU00:FS00:Connecting to 171.64.65.35:80
06:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
06:50:05:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-14 *******************************
12:50:05:WU00:FS00:Connecting to 171.67.108.45:8080
12:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
12:50:05:WU00:FS00:Connecting to 171.64.65.35:80
12:50:06:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
12:50:06:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-14 *******************************
18:50:05:WU00:FS00:Connecting to 171.67.108.45:8080
18:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:50:05:WU00:FS00:Connecting to 171.64.65.35:80
18:50:06:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
18:50:06:ERROR:WU00:FS00:Exception: Could not get an assignment
00:50:04:WU00:FS00:Connecting to 171.67.108.45:8080
******************************* Date: 2016-06-15 *******************************
00:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:50:05:WU00:FS00:Connecting to 171.64.65.35:80
00:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:50:05:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-15 *******************************
06:50:05:WU00:FS00:Connecting to 171.67.108.45:8080
06:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
06:50:05:WU00:FS00:Connecting to 171.64.65.35:80
06:50:06:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
06:50:06:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-15 *******************************
12:50:05:WU00:FS00:Connecting to 171.67.108.45:8080
12:50:06:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
12:50:06:WU00:FS00:Connecting to 171.64.65.35:80
12:50:06:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
12:50:06:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-15 *******************************
18:50:05:WU00:FS00:Connecting to 171.67.108.45:8080
18:50:06:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:50:06:WU00:FS00:Connecting to 171.64.65.35:80
18:50:06:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
18:50:06:ERROR:WU00:FS00:Exception: Could not get an assignment
******************************* Date: 2016-06-16 *******************************
00:50:05:WU00:FS00:Connecting to 171.67.108.45:8080
00:50:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:50:05:WU00:FS00:Connecting to 171.64.65.35:80
00:50:06:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:50:06:ERROR:WU00:FS00:Exception: Could not get an assignment
Well, lessee. There are more than 90 THOUSAND computers spending money on electricity to do this for you guys FOR FREE. You want some THOUSANDS of us who donate compute time and actual dollars to make changes that are not due to our screwups but Pande Group. Sound like a winner? <censored> <censored> <censored>
I have been running FAH for over a decade and you guys always want US to fix your screwups. No more.
And I had to dig out this forum again, ask again, and then SEARCH for my question with zero guidance that it has been moved to some place *I* didn't put it.
Is SETI still running? Are there better places to spend our CPU and electricity dollars than people like this?
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).
This is a change in the 3rd party software GROMACS. This is not a Pande Group screwup that caused this issue. Yes, Pande Group is responsible for staying up to date with their software. And while PG is well known for pioneering new software, they are not well known for maintaining that software.
Unfortunate that you would abandon the decades worth of contributions over one minor problem. Good luck with your new endeavors.
PG definitely changed their server config recently to not send out some primes like 7 and 11. Projects used to be limited if there were errors now its just straight cut off.
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).
mmonnin wrote:PG definitely changed their server config recently to not send out some primes like 7 and 11. Projects used to be limited if there were errors now its just straight cut off.
Or they didn't change any server settings, and the older projects that still used the CPU:7 option have ended. Newer projects were built without that support.
Kind of hard to tell which it was. Someone should ask PG on reddit.