Folding Forum

Confirming that I can't get WU's back to 220 either. I have over 40 SMP systems that have been in production folding for several years. No configuration changes have been made. I don't recall when this first started happening, 2-3 weeks ago?

Bruce, Joe, I'm starting to see the same behavior on other servers as well. So it definitely must be something happening on my side or something in between. Traceroute suggests there is no trouble, though, at least on 171.67.108.101. This particular computer is currently experiencing slow downloads ...

Just to add some more details to this: It is certainly something to do with this server or a connection to it: 171.67.108.101 After clearing out the work folder and restarting the client, the same systems will quickly download a WU from a different one, such as: 155.247.166.219. But after one or two...

I've been seeing an issue over the weekend where the majority of my CPU / SMP WU's using core A7 are downloading extremely slowly. As in, taking almost 2 hours at times for a 3MB - 15MB file. All the ones that are being affected seem to be getting their WU's from 171.67.108.101. Here is a log entry:...

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 er...

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 incompatibil...

Is this error now a different issue and I should fork this into a separate thread?

-Kirk

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! ...

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 ...

@jcoffland Oooh. Looks like you're right: ./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 (r...

Are there any other suggestions to help resolve this issue? If it is a glibc problem, what version should be used?

@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...

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:WARN...