Page 1 of 2
FahCore_a7 doesn't work on Unsupported Linux distros (CentOS)
Posted: Tue Nov 01, 2016 8:31 pm
by RamonetB
Hello everyone,
I have several CentOS 6.8 boxes up and running utilizing AMD 6100 series processors for a total of 48 cores per system.
Unfortunately with any WU downloaded for the new Core_A7 I am unable to actually fold. The error I receive is:
19:24:53:WU02:FS00:FahCore 0xa7 started
19:24:53:WARNING:WU02:FS00:FahCore returned: FAILED_2 (1 = 0x1)
19:24:53:WARNING:WU02:FS00:Too many errors, failing
19:24:53:WU02:FS00:Sending unit results: id:02 state:SEND error:FAILED
I don't run into this issue while using an A4 core WU's which still run great.
Am I missing a requirement or a piece of software is out of date?
System details:
CentOS 6.8 64-bit
Kernel: 2.6.32-642.6.2.el6.x86_64
Python Version: 2.6.6
FAH version: 7.4.4 (tried 7.4.15 as well).
Memory: 128GB
CPU: 4x AMD 6176
If there are any other details I can provide, please let me know. I'd love to get folding on this new core!
Thanks,
-Kirk
Re: FahCore_a7
Posted: Tue Nov 01, 2016 10:36 pm
by jcoffland
@RamonetB, this sounds like a different issue. Can you post your whole log in a code block?
Re: FahCore_a7
Posted: Tue Nov 01, 2016 10:47 pm
by jcoffland
@RamonetB, since you are running CentOS I'm guessing that the problem is a glibc mismatch in the core. What happens if you try to run the 0xa7 core manually?
Re: FahCore_a7
Posted: Wed Nov 02, 2016 3:29 pm
by RamonetB
jcoffland wrote:@RamonetB, this sounds like a different issue. Can you post your whole log in a code block?
Certainly.
The following is the entirety of the log until the first failure. I've lost the full log due to a restart. If you want, I can post the full log through until it stops trying due to too many errors when it fails it for good once it reaches that point again:
Code: Select all
*********************** Log Started 2016-11-01T20:08:19Z ***********************
20:08:19:************************* Folding@home Client *************************
20:08:19: Website: http://folding.stanford.edu/
20:08:19: Copyright: (c) 2009-2016 Stanford University
20:08:19: Author: Joseph Coffland <[email protected]>
20:08:19: Args: --child --lifeline 35536 /etc/fahclient/config.xml --run-as
20:08:19: fahclient --pid-file=/var/run/fahclient.pid --daemon
20:08:19: Config: /etc/fahclient/config.xml
20:08:19:******************************** Build ********************************
20:08:19: Version: 7.4.15
20:08:19: Date: Aug 17 2016
20:08:19: Time: 04:32:12
20:08:19: Repository: Git
20:08:19: Revision: 4f3e0e25571a9f691719f0c273739294bde517dd
20:08:19: Branch: master
20:08:19: Compiler: GNU 4.4.7 20120313 (Red Hat 4.4.7-17)
20:08:19: Options: -std=gnu++98 -O3 -funroll-loops -ffast-math -mfpmath=sse
20:08:19: -fno-unsafe-math-optimizations -msse2
20:08:19: Platform: linux2 4.6.0-1-amd64
20:08:19: Bits: 64
20:08:19: Mode: Release
20:08:19:******************************* System ********************************
20:08:19: CPU: AMD Opteron(tm) Processor 6176 SE
20:08:19: CPU ID: AuthenticAMD Family 16 Model 9 Stepping 1
20:08:19: CPUs: 48
20:08:19: Memory: 126.03GiB
20:08:19:Free Memory: 123.87GiB
20:08:19: Threads: POSIX_THREADS
20:08:19: OS Version: 2.6
20:08:19:Has Battery: false
20:08:19: On Battery: false
20:08:19: UTC Offset: -4
20:08:19: PID: 35538
20:08:19: CWD: /var/lib/fahclient
20:08:19: OS: Linux 2.6.32-642.6.2.el6.x86_64 x86_64
20:08:19: OS Arch: AMD64
20:08:19: GPUs: 0
20:08:19: CUDA: Not detected
20:08:19: OpenCL: Not detected
20:08:19:***********************************************************************
20:08:19:<config>
20:08:19: <!-- Folding Slot Configuration -->
20:08:19: <gpu v='false'/>
20:08:19:
20:08:19: <!-- Network -->
20:08:19: <proxy v=':8080'/>
20:08:19:
20:08:19: <!-- Slot Control -->
20:08:19: <power v='light'/>
20:08:19:
20:08:19: <!-- User Information -->
20:08:19: <passkey v='********************************'/>
20:08:19: <team v='32'/>
20:08:19: <user v='RamonetB'/>
20:08:19:
20:08:19: <!-- Folding Slots -->
20:08:19: <slot id='0' type='CPU'>
20:08:19: <cpus v='48'/>
20:08:19: </slot>
20:08:19:</config>
20:08:19:Switching to user fahclient
20:08:19:Trying to access database...
20:08:19:Successfully acquired database lock
20:08:19:FS00:Set client configured
20:08:19:Enabled folding slot 00: READY cpu:48
20:08:19:WU00:FS00:Connecting to 171.67.108.45:8080
20:08:20:WU00:FS00:Connecting to 171.67.108.45:8080
20:08:21:WU00:FS00:Assigned to work server 171.64.65.41
20:08:21:WU00:FS00:Requesting new work unit for slot 00: READY cpu:48 from 171.64.65.41
20:08:21:WU00:FS00:Connecting to 171.64.65.41:8080
20:08:22:WU00:FS00:Downloading 21.15MiB
20:08:24:WU00:FS00:Download complete
20:08:24:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:11920 run:4362 clone:1 gen:60 core:0xa7 unit:0x0000004aab40412958098d083b3b4d91
20:08:24:WU00:FS00:Downloading core from http://web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah
20:08:24:WU00:FS00:Connecting to web.stanford.edu:80
20:08:24:WU00:FS00:FahCore a7: Downloading 7.36MiB
20:08:30:WU00:FS00:FahCore a7: 50.92%
20:08:34:WU00:FS00:FahCore a7: Download complete
20:08:35:WU00:FS00:Valid core signature
20:08:35:WU00:FS00:Unpacked 17.60MiB to cores/web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah/FahCore_a7
20:08:35:WU00:FS00:Starting
20:08:35:WU00:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah/FahCore_a7 -dir 00 -suffix 01 -version 704 -lifeline 35538 -checkpoint 15 -np 48
20:08:35:WU00:FS00:Started FahCore on PID 35549
20:08:35:WU00:FS00:Core PID:35553
20:08:35:WU00:FS00:FahCore 0xa7 started
20:08:35:WARNING:WU00:FS00:FahCore returned: FAILED_2 (1 = 0x1)
20:08:35:WU00:FS00:Starting
20:08:35:WU00:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah/FahCore_a7 -dir 00 -suffix 01 -version 704 -lifeline 35538 -checkpoint 15 -np 48
20:08:35:WU00:FS00:Started FahCore on PID 35554
20:08:35:WU00:FS00:Core PID:35558
20:08:35:WU00:FS00:FahCore 0xa7 started
20:08:36:WARNING:WU00:FS00:FahCore returned: FAILED_2 (1 = 0x1)
jcoffland wrote:@RamonetB, since you are running CentOS I'm guessing that the problem is a glibc mismatch in the core. What happens if you try to run the 0xa7 core manually?
For information purposes, the version of glibc that is on the platform is 2.12-1.192.
I'm a little confused by what you mean by running the core manually. If you mean starting the FAHClient binary at the command line rather than through the service or Control Center, then the results are the same. The log file for that is as follows:
Code: Select all
*********************** Log Started 2016-11-02T15:17:56Z ***********************
15:17:56:************************* Folding@home Client *************************
15:17:56: Website: http://folding.stanford.edu/
15:17:56: Copyright: (c) 2009-2016 Stanford University
15:17:56: Author: Joseph Coffland <[email protected]>
15:17:56: Args:
15:17:56: Config: /root/Folding/config.xml
15:17:56:******************************** Build ********************************
15:17:56: Version: 7.4.15
15:17:56: Date: Aug 17 2016
15:17:56: Time: 04:32:12
15:17:56: Repository: Git
15:17:56: Revision: 4f3e0e25571a9f691719f0c273739294bde517dd
15:17:56: Branch: master
15:17:56: Compiler: GNU 4.4.7 20120313 (Red Hat 4.4.7-17)
15:17:56: Options: -std=gnu++98 -O3 -funroll-loops -ffast-math -mfpmath=sse
15:17:56: -fno-unsafe-math-optimizations -msse2
15:17:56: Platform: linux2 4.6.0-1-amd64
15:17:56: Bits: 64
15:17:56: Mode: Release
15:17:56:******************************* System ********************************
15:17:56: CPU: AMD Opteron(tm) Processor 6176 SE
15:17:56: CPU ID: AuthenticAMD Family 16 Model 9 Stepping 1
15:17:56: CPUs: 48
15:17:56: Memory: 126.03GiB
15:17:56:Free Memory: 122.93GiB
15:17:56: Threads: POSIX_THREADS
15:17:56: OS Version: 2.6
15:17:56:Has Battery: false
15:17:56: On Battery: false
15:17:56: UTC Offset: -4
15:17:56: PID: 30618
15:17:56: CWD: /root/Folding
15:17:56: OS: Linux 2.6.32-642.6.2.el6.x86_64 x86_64
15:17:56: OS Arch: AMD64
15:17:56: GPUs: 0
15:17:56: CUDA: Not detected
15:17:56: OpenCL: Not detected
15:17:56:***********************************************************************
15:17:56:<config>
15:17:56: <!-- Folding Slot Configuration -->
15:17:56: <gpu v='false'/>
15:17:56:
15:17:56: <!-- Network -->
15:17:56: <proxy v=':8080'/>
15:17:56:
15:17:56: <!-- Slot Control -->
15:17:56: <power v='light'/>
15:17:56:
15:17:56: <!-- User Information -->
15:17:56: <passkey v='********************************'/>
15:17:56: <team v='32'/>
15:17:56: <user v='RamonetB'/>
15:17:56:
15:17:56: <!-- Folding Slots -->
15:17:56: <slot id='0' type='CPU'>
15:17:56: <cpus v='48'/>
15:17:56: </slot>
15:17:56:</config>
15:17:56:Trying to access database...
15:17:56:Successfully acquired database lock
15:17:56:FS00:Set client configured
15:17:56:Enabled folding slot 00: READY cpu:48
15:17:56:WU00:FS00:Connecting to 171.67.108.45:8080
15:17:57:WU00:FS00:Connecting to 171.67.108.45:8080
15:17:58:WU00:FS00:Assigned to work server 171.64.65.41
15:17:58:WU00:FS00:Requesting new work unit for slot 00: READY cpu:48 from 171.64.65.41
15:17:58:WU00:FS00:Connecting to 171.64.65.41:8080
15:17:58:WU00:FS00:Downloading 21.06MiB
15:18:01:WU00:FS00:Download complete
15:18:01:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:11920 run:1750 clone:0 gen:91 core:0xa7 unit:0x0000007bab40412957bff41b8c9b74d6
15:18:01:WU00:FS00:Downloading core from http://web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah
15:18:01:WU00:FS00:Connecting to web.stanford.edu:80
15:18:01:WU00:FS00:FahCore a7: Downloading 7.36MiB
15:18:07:WU00:FS00:FahCore a7: 41.58%
15:18:13:WU00:FS00:FahCore a7: 95.04%
15:18:13:WU00:FS00:FahCore a7: Download complete
15:18:13:WU00:FS00:Valid core signature
15:18:13:WU00:FS00:Unpacked 17.60MiB to cores/web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah/FahCore_a7
15:18:13:WU00:FS00:Starting
15:18:13:WU00:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /root/Folding/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah/FahCore_a7 -dir 00 -suffix 01 -version 704 -lifeline 30618 -checkpoint 15 -np 48
15:18:13:WU00:FS00:Started FahCore on PID 30627
15:18:13:WU00:FS00:Core PID:30631
15:18:13:WU00:FS00:FahCore 0xa7 started
^[[93m15:18:14:WARNING:WU00:FS00:FahCore returned: FAILED_2 (1 = 0x1)^[[0m
15:18:14:WU00:FS00:Starting
15:18:14:WU00:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /root/Folding/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah/FahCore_a7 -dir 00 -suffix 01 -version 704 -lifeline 30618 -checkpoint 15 -np 48
15:18:14:WU00:FS00:Started FahCore on PID 30632
15:18:14:WU00:FS00:Core PID:30636
15:18:14:WU00:FS00:FahCore 0xa7 started
^[[93m15:18:14:WARNING:WU00:FS00:FahCore returned: FAILED_2 (1 = 0x1)^[[0m
As a side note, and additional info, modifying the environment variable
OMP_NUM_THREADS had no affect, as would be suspected from the lack of the error in the logs. It is included here for completion only.
-Kirk
Re: FahCore_a7
Posted: Fri Nov 04, 2016 12:34 pm
by RamonetB
Are there any other suggestions to help resolve this issue? If it is a glibc problem, what version should be used?
Re: FahCore_a7
Posted: Fri Nov 04, 2016 7:42 pm
by jcoffland
@RamonetB Please try running
Code: Select all
/root/Folding/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah/FahCore_a7
on the command line.
Re: FahCore_a7
Posted: Fri Nov 04, 2016 8:22 pm
by RamonetB
@jcoffland
Oooh. Looks like you're right:
Code: Select all
./FahCore_a7: /lib64/libm.so.6: version `GLIBC_2.15' not found (required by ./FahCore_a7)
./FahCore_a7: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./FahCore_a7)
./FahCore_a7: /lib64/libc.so.6: version `GLIBC_2.17' not found (required by ./FahCore_a7)
./FahCore_a7: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./FahCore_a7)
I suppose I could build a newer glibc and install it in an alternate location and then try to get the program running by pointing to it....
Or is it possible to have the core include support for 2.12? (Yes, I realize I have no idea what this would entail / break for it).
Re: FahCore_a7
Posted: Sun Nov 06, 2016 10:19 pm
by toTOW
I have the same issue on an old Ubuntu 10.04 setup ... I wish I could exclude A7 from assignments on this machine, but it is assigning to everyone
Re: FahCore_a7
Posted: Mon Nov 07, 2016 8:37 pm
by RamonetB
The story so far:
In an attempt to get this running under CentOS 6, I've done the following:
Keep in mind that we are missing versions of glibc, I've gone and downloaded versions 2.14, 2.15, and 2.17, compiled them, and installed them their respective directories in /opt. (Although, only the latest is needed).
For the curious, a handy quick step guide:
Code: Select all
1. wget http://ftp.gnu.org/gnu/glibc/glibc-2.17.tar.gz
2. tar zxvf glibc-2.17.tar.gz
3. cd glibc-2.17
4. mkdir build
5. cd build
6. ../configure --prefix=/opt/glibc-2.17
7. make -j4
8. make install
9. export LD_LIBRARY_PATH=/opt/glibc-2.17/lib
I've then added their library locations to my immediate (non system wide) library path thusly:
Code: Select all
export LD_LIBRARY_PATH=/opt/glibc-2.17/lib
This has resolved the majority of the issues. However, the remaining one, libstdc++.so.6 requiring GLIBCXX_3.4.15 is not so easy to deal with. Downloading the library file itself is all well enough as it also depends on the now installed glibc versions I just mentioned. But actually loading the library so far is proving to be problematic.
Code: Select all
export LD_PRELOAD=/usr/lib64/libstdc++.so.6.0.19
or whatever flavor you prefer of libstdc++ that carries support of GLIBCXX_3.4.15. This results in a segfault.
If one were to be crazy and change the symbolic link of /usr/lib64/libstdc++.so.6 to point directly towards the newer libstdc++.so.6.0.19, you would cripple the system. Linux IS glibc afterall (as the saying goes) and these varying versions get tricky.
I was hoping to find a way to do this without having to compile gcc from scratch and add a whole other build along side, but so far I haven't hit on the right combination.
Ultimately, Core_A7 is built demanding libraries that are newer than CentOS 6 or Ubuntu 10 supplies. I'm curious again to know whether this is strictly necessary and whether or not a version of the core can be released that supports older libraries. CentOS 6.8 isn't THAT old as Enterprise class systems go....
Re: FahCore_a7
Posted: Wed Nov 09, 2016 3:56 pm
by RamonetB
Okay, let's bring things up to speed a little more.
After getting the libstdcc in place correctly and installing glibc-2.17, I did some research and discovered I was running into a problem with running different versions of the loader and libraries (as glibc is more than just libstdc. Who knew? HA! Also,
THIS for more details on this!). So, to correct this, I can call the newer ld-linux-x86-64, provide it with the new library paths, and then indicate, via full path, what command I want to run. For example, to run the FAHClient directly, I would now type this:
Code: Select all
/opt/glibc-2.17/lib/ld-linux-x86-64.so.2 --library-path /opt/glibc-2.17/lib:$LD_LIBRARY_PATH:/usr/lib64/ /usr/bin/FAHClient
where glibc-2.17 is installed in /opt so as not to "corrupt" the current running system and LD_LIBRARY_PATH is:
Code: Select all
export LD_LIBRARY_PATH=/opt/glibc-2.17/lib:/lib:/lib64
When doing this, the FAHClient actually starts! But now I get a new error: "
WARNING:WU00:FS00:FahCore returned: FAILED_3 (255 = 0xff)"
When running the core directly I get this error:
ERROR:Guru Meditation: not checked 'config.xml'
But I've not yet been able to figure this one out. Is there a new flag necessary on the config.xml file for A7 cores? Guru Meditation errors are kind of a broad spectrum when googling....
Although the closest I found was
This Post on these forums but it has no answers. BOO.
Full log for the curious:
Code: Select all
*********************** Log Started 2016-11-09T14:59:01Z ***********************
14:59:01:************************* Folding@home Client *************************
14:59:01: Website: http://folding.stanford.edu/
14:59:01: Copyright: (c) 2009-2016 Stanford University
14:59:01: Author: Joseph Coffland <[email protected]>
14:59:01: Args:
14:59:01: Config: /root/Folding/config.xml
14:59:01:******************************** Build ********************************
14:59:01: Version: 7.4.15
14:59:01: Date: Aug 17 2016
14:59:01: Time: 04:32:12
14:59:01: Repository: Git
14:59:01: Revision: 4f3e0e25571a9f691719f0c273739294bde517dd
14:59:01: Branch: master
14:59:01: Compiler: GNU 4.4.7 20120313 (Red Hat 4.4.7-17)
14:59:01: Options: -std=gnu++98 -O3 -funroll-loops -ffast-math -mfpmath=sse
14:59:01: -fno-unsafe-math-optimizations -msse2
14:59:01: Platform: linux2 4.6.0-1-amd64
14:59:01: Bits: 64
14:59:01: Mode: Release
14:59:01:******************************* System ********************************
14:59:01: CPU: AMD Opteron(tm) Processor 6176 SE
14:59:01: CPU ID: AuthenticAMD Family 16 Model 9 Stepping 1
14:59:01: CPUs: 48
14:59:01: Memory: 126.03GiB
14:59:01:Free Memory: 120.48GiB
14:59:01: Threads: POSIX_THREADS
14:59:01: OS Version: 2.6
14:59:01:Has Battery: false
14:59:01: On Battery: false
14:59:01: UTC Offset: 0
14:59:01: PID: 17058
14:59:01: CWD: /root/Folding
14:59:01: OS: Linux 2.6.32-642.6.2.el6.x86_64 x86_64
14:59:01: OS Arch: AMD64
14:59:01: GPUs: 0
14:59:01: CUDA: Not detected
14:59:01: OpenCL: Not detected
14:59:01:***********************************************************************
14:59:01:<config>
14:59:01: <!-- Folding Slot Configuration -->
14:59:01: <gpu v='false'/>
14:59:01:
14:59:01: <!-- Network -->
14:59:01: <proxy v=':8080'/>
14:59:01:
14:59:01: <!-- Slot Control -->
14:59:01: <power v='light'/>
14:59:01:
14:59:01: <!-- User Information -->
14:59:01: <passkey v='********************************'/>
14:59:01: <team v='32'/>
14:59:01: <user v='RamonetB'/>
14:59:01:
14:59:01: <!-- Folding Slots -->
14:59:01: <slot id='0' type='CPU'>
14:59:01: <cpus v='48'/>
14:59:01: </slot>
14:59:01:</config>
14:59:01:Trying to access database...
14:59:01:Successfully acquired database lock
14:59:01:Enabled folding slot 00: READY cpu:48
^[[93m14:59:01:WARNING:WU00:FS00:Past final deadline 2016-11-03T15:17:58Z, dumping^[[0m
14:59:01:WU00:FS00:Cleaning up
14:59:01:WU00:FS00:Connecting to 171.67.108.45:8080
14:59:02:WU00:FS00:Assigned to work server 171.64.65.41
14:59:02:WU00:FS00:Requesting new work unit for slot 00: READY cpu:48 from 171.64.65.41
14:59:02:WU00:FS00:Connecting to 171.64.65.41:8080
14:59:06:WU00:FS00:Downloading 21.03MiB
14:59:19:WU00:FS00:Download 0.59%
14:59:26:WU00:FS00:Download 1.19%
14:59:36:WU00:FS00:Download 1.78%
14:59:44:WU00:FS00:Download 2.38%
14:59:57:WU00:FS00:Download 2.68%
15:00:09:WU00:FS00:Download 2.97%
15:00:16:WU00:FS00:Download 3.86%
15:00:26:WU00:FS00:Download 5.65%
15:00:34:WU00:FS00:Download 5.95%
15:00:40:WU00:FS00:Download 8.03%
15:00:46:WU00:FS00:Download 9.51%
15:00:59:WU00:FS00:Download 11.00%
15:01:20:WU00:FS00:Download 11.30%
15:01:26:WU00:FS00:Download 13.67%
15:01:32:WU00:FS00:Download 16.35%
15:01:51:WU00:FS00:Download 17.84%
15:02:15:WU00:FS00:Download 18.13%
15:03:04:WU00:FS00:Download 18.43%
15:03:33:WU00:FS00:Download 18.73%
15:03:45:WU00:FS00:Download 19.02%
15:03:52:WU00:FS00:Download 22.89%
15:03:58:WU00:FS00:Download 26.75%
15:04:11:WU00:FS00:Download 27.05%
15:04:21:WU00:FS00:Download 30.62%
15:04:30:WU00:FS00:Download 33.89%
15:04:41:WU00:FS00:Download 35.67%
15:04:51:WU00:FS00:Download 37.45%
15:04:57:WU00:FS00:Download 39.83%
15:05:13:WU00:FS00:Download 44.89%
15:05:19:WU00:FS00:Download 46.37%
15:05:29:WU00:FS00:Download 47.86%
15:05:38:WU00:FS00:Download 52.91%
15:05:56:WU00:FS00:Download 56.48%
15:06:13:WU00:FS00:Download 56.78%
15:06:22:WU00:FS00:Download 57.37%
15:06:28:WU00:FS00:Download 58.56%
15:06:34:WU00:FS00:Download 64.21%
15:06:46:WU00:FS00:Download 70.75%
15:07:00:WU00:FS00:Download 71.04%
15:07:25:WU00:FS00:Download 71.64%
15:07:31:WU00:FS00:Download 72.83%
15:07:37:WU00:FS00:Download 77.88%
15:07:44:WU00:FS00:Download 78.77%
15:07:54:WU00:FS00:Download 80.56%
15:08:05:WU00:FS00:Download 82.64%
15:08:11:WU00:FS00:Download 83.23%
15:08:19:WU00:FS00:Download 87.39%
15:08:31:WU00:FS00:Download 89.47%
15:08:42:WU00:FS00:Download 91.55%
15:08:48:WU00:FS00:Download 95.72%
15:08:52:WU00:FS00:Download complete
15:08:52:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:11920 run:987 clone:0 gen:90 core:0xa7 unit:0x00000087ab40412957bff59ef84afd10
15:08:52:WU00:FS00:Starting
15:08:52:WU00:FS00:Running FahCore: /opt/glibc-2.17/lib/FAHCoreWrapper /root/Folding/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah/FahCore_a7 -dir 00 -suffix 01 -version 704 -lifeline 17058 -checkpoint 15 -np 48
15:08:52:WU00:FS00:Started FahCore on PID 17101
15:08:52:WU00:FS00:FahCore 0xa7 started
^[[93m15:08:52:WARNING:WU00:FS00:FahCore returned: FAILED_3 (255 = 0xff)^[[0m
15:08:53:WU00:FS00:Starting
15:08:53:WU00:FS00:Running FahCore: /opt/glibc-2.17/lib/FAHCoreWrapper /root/Folding/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah/FahCore_a7 -dir 00 -suffix 01 -version 704 -lifeline 17058 -checkpoint 15 -np 48
15:08:53:WU00:FS00:Started FahCore on PID 17103
15:08:53:WU00:FS00:FahCore 0xa7 started
^[[93m15:08:53:WARNING:WU00:FS00:FahCore returned: FAILED_3 (255 = 0xff)^[[0m
15:09:53:WU00:FS00:Starting
15:09:53:WU00:FS00:Running FahCore: /opt/glibc-2.17/lib/FAHCoreWrapper /root/Folding/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah/FahCore_a7 -dir 00 -suffix 01 -version 704 -lifeline 17058 -checkpoint 15 -np 48
15:09:53:WU00:FS00:Started FahCore on PID 17106
15:09:53:WU00:FS00:FahCore 0xa7 started
^[[93m15:09:53:WARNING:WU00:FS00:FahCore returned: FAILED_3 (255 = 0xff)^[[0m
15:10:53:WU00:FS00:Starting
15:10:53:WU00:FS00:Running FahCore: /opt/glibc-2.17/lib/FAHCoreWrapper /root/Folding/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah/FahCore_a7 -dir 00 -suffix 01 -version 704 -lifeline 17058 -checkpoint 15 -np 48
15:10:53:WU00:FS00:Started FahCore on PID 17114
15:10:53:WU00:FS00:FahCore 0xa7 started
^[[93m15:10:53:WARNING:WU00:FS00:FahCore returned: FAILED_3 (255 = 0xff)^[[0m
15:11:53:WU00:FS00:Starting
15:11:53:WU00:FS00:Running FahCore: /opt/glibc-2.17/lib/FAHCoreWrapper /root/Folding/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a7.fah/FahCore_a7 -dir 00 -suffix 01 -version 704 -lifeline 17058 -checkpoint 15 -np 48
15:11:53:WU00:FS00:Started FahCore on PID 17118
15:11:53:WU00:FS00:FahCore 0xa7 started
^[[93m15:11:53:WARNING:WU00:FS00:FahCore returned: FAILED_3 (255 = 0xff)^[[0m
^[[93m15:11:53:WARNING:WU00:FS00:Too many errors, failing^[[0m
15:11:53:WU00:FS00:Sending unit results: id:00 state:SEND error:FAILED project:11920 run:987 clone:0 gen:90 core:0xa7 unit:0x00000087ab40412957bff59ef84afd10
Any additional help on this?
-Kirk
Re: FahCore_a7 doesn't work on Unsupported Linux distros (C
Posted: Mon Nov 14, 2016 8:37 pm
by RamonetB
Is this error now a different issue and I should fork this into a separate thread?
-Kirk
Re: FahCore_a7 doesn't work on Unsupported Linux distros (C
Posted: Mon Nov 14, 2016 9:07 pm
by bruce
At this point, you're still attacking the same problem so I see no need to fork the discussion.
There is no configuration flag for FahCore_a7.
CPU-based projects may be configured by the project owner to run with one of several different FAHCores ... mostly _a4 and _a7. When new features are required, there's always going to be a potential problem with supporting all possible versions of the supported Linux distros and that problem gets worse when you attempt to include all possible other distros.
Linux applications that are generated with a particular compiler on a particular version have always had a potential problem when running on a system created with different libraries. (Windows is no different, in that regard, except that Microsoft takes some responsibility for managing incompatibilities.)
Finding ways to run an application that is based on different libraries than the ones you have is a rather daunting problem, best discussed on the support site (in your case) for CentOS where you''re more likely to find folks who have faced the same issue(s).
Re: FahCore_a7 doesn't work on Unsupported Linux distros (C
Posted: Mon Nov 14, 2016 9:41 pm
by RamonetB
bruce wrote:
Linux applications that are generated with a particular compiler on a particular version have always had a potential problem when running on a system created with different libraries. (Windows is no different, in that regard, except that Microsoft takes some responsibility for managing incompatibilities.)
Finding ways to run an application that is based on different libraries than the ones you have is a rather daunting problem, best discussed on the support site (in your case) for CentOS where you''re more likely to find folks who have faced the same issue(s).
Thanks for the reply, Bruce.
Do you happen to know or be able to point me to what the requirements for A7's are as far as libraries go? (Or what it's being built with?)
I've just installed the latest version of CentOS (7.2) and am running into the same error now.
Thanks,
-Kirk
Re: FahCore_a7 doesn't work on Unsupported Linux distros (C
Posted: Tue Nov 15, 2016 8:03 pm
by jcoffland
ERROR:Guru Meditation: not checked 'config.xml' is caused by running the core in the client's directory. The core sees and reads config.xml from the current directory but that config is for the client not the core. If you run the core manually in a directory that does not contain config.xml this error should go away.
Re: FahCore_a7 doesn't work on Unsupported Linux distros (C
Posted: Tue Nov 15, 2016 8:38 pm
by bruce
Are you using the script "FAHClient"? On my Ubuntu system it's in /etc/init.d. It works to start or stop FAHClient.