Folding Forum

I had quite a few (about 30) of these so far for Projects 1643x on Linux with v7.5.1, on a few different Nvidia video cards (1080, 1080ti, 2080ti) with older drivers v415.27 or v418.56 2020-04-27:22:11:01:WU02:FS00:Server responded WORK_QUIT (404) 2020-04-27:22:11:01:WARNING:WU02:FS00:Server did not...

Thanks for the update. Is a particular 32-bit freetype.dll or freetype6.dll also needed? I used the compiled binary on Win7 64bit, with 32bit FAH client v7.5.1 installed, and the 'freetype6.dll' from FAH v7.4.4. I see everything except the protein atoms. It stays in: 'Connected' | 'Loading' state, a...

For the AMD GPU: Error invoking kernel sortShortList: clEnqueueNDRangeKernel (-5) issue:
viewtopic.php?f=81&t=32771
viewtopic.php?f=74&t=32991 (This one mentions: "Researchers are looking into disabling those projects on AMD GPUs until fix has been found.")

My guess without looking into it much: I think the layout of the atoms is correct, but the colors and the sizes of the purple atoms is not correct (probably due to the format and ?'s in the json above). I'm pretty sure the cube of atoms is a lot of water molecules (like the protein is moving in mois...

There was a workaround mentioned recently: https://github.com/FoldingAtHome/fah-issues/issues/1283 by using the previous viewer executable (and a required dll) file with the current FAH v7.5.1 installation for viewing Core_22 on Windows

The viewer works in Linux (CPU: GRO_A7, and GPU: Core_21 and Core_22 all work on Linux), just not in Windows. Searching the forum or looking at the issues in GitHub, you should be able to find more info on it. Like: https://github.com/FoldingAtHome/fah-is ... pen+viewer https://github.com/FoldingAtH...

If you update to the latest Nvidia driver from the Nvidia website, do you still get the same error?
Old GPU drivers, and GPU overheating/unstable overclocking issues seemed to be the cause of most of the issues the last time Core22 went to advanced.

@vvoelz- I think there's a very easy workaround for this problem (even with 100% assign weights), which is to restart the FAH WS software (or reboot the server if it's a dedicated FAH server) every ~2 days. Setting up a restart/reboot script to run on a schedule should be easy: like a cron job or so...

GPU WU downloads from 155.247.166.219 are slow and failing again (hanging folding slots). It looks like it's time for a server reboot, since it's at 5 days of up time.

Same. I've been getting hung folding slots for the past 4+ hours. Downloads fail from *.219, and just stop like this: 2019-11-06:23:46:53:WU01:FS01:0x21:Completed 25000000 out of 25000000 steps (100%) 2019-11-06:23:46:53:WU01:FS01:0x21:Saving result file logfile_01.txt 2019-11-06:23:46:53:WU01:FS01:...

It looks like all the downloads from 155.247.166.219 are all dying (at 0-5% downloaded) and hanging FahClient folding slots now. Killing FAH and it's processes, and restarting it, all weekend long is going to be a hassle... Time to start running DarthMouse's Reboot FAH script for Linux again: https:...

The WU upload failures and slow-downs are starting to happen again to 155.247.166.219. Both temple servers need to be rebooted since they are past 3 days of uptime.

I did finally find the open ticket for a setting to limit the number of uploads, from 2013: https://github.com/FoldingAtHome/fah-issues/issues/1038 . I'm not the first person with this issue. :) This comment was interesting: https://github.com/FoldingAtHome/fah-issues/issues/983#issuecomment-2942648...

I'll try to look at the PC clocks more when this happens again to look for clock skew on all the PCs. I chose when to run updates on the PCs I have, so that is not a problem. The WU upload backlogs have happened without running a torrent program, and the torrent program has limits set to not exceed ...

I think it's the opposite, and the FAH client is falsely indicating clock drift when the software is too overloaded with failing / slow uploads. I just searched the current logs on all the PCs, and there are no 'Detected clock skew' messages today. I replaced about 50% of the CMOS batteries this yea...