Folding Forum

I'm not able to reach 171.64.65.124 from here nor does it appear on https://apps.foldingathome.org/serverstats I'm not sure what's going on. Could you have possibly restored an old FAHClient directory, or installed the FoldingAtHome software that referenced an old FAHClient directory, and found a n...

bruce wrote:I'm not able to reach 171.64.65.124 from here nor does it appear on https://apps.foldingathome.org/serverstats I'm not sure what's going on.

Why is a 4-1/2 year old thread being revived?

Right after I sent that update about it taking an hour, the server did finally respond (at a cost of over 30000 points lost due to server delays). Not that the points are worth more than just bragging rights, but the cost for earning the points is more for me (and other contributors) to have the hig...

Still a problem with uploads failing to 128.252.203.10. 16:44:00:WU03:FS02:Sending unit results: id:03 state:SEND error:NO_ERROR project:11762 run:0 clone:1308 gen:50 core:0x22 unit:0x0000006280fccb0a5e6d80d6991aa7fe 16:44:00:WU03:FS02:Uploading 33.02MiB to 128.252.203.10 16:44:00:WU03:FS02:Connecti...

16:38:19:WU03:FS02:0x22:Completed 1000000 out of 1000000 steps (100%) 16:38:24:WU03:FS02:0x22:Saving result file ..\logfile_01.txt 16:38:24:WU03:FS02:0x22:Saving result file checkpointState.xml 16:38:24:WU03:FS02:0x22:Saving result file checkpt.crc 16:38:24:WU03:FS02:0x22:Saving result file positio...

Joe_H wrote:No posts have been deleted, the search function turns up quite a few, including your own. There is a "View your own posts" option as well.

I did review my own posts, and 2 of them were gone, related to this specific server.

Multiple prior posts about this server were deleted by someone. The 3.133.76.19 server keeps having issues with not responding. 00:24:20:WU03:FS02:Assigned to work server 3.133.76.19 00:24:20:WU03:FS02:Requesting new work unit for slot 02: READY gpu:1:TU102 [GeForce RTX 2080 Ti] M 13448 from 3.133.7...

This server's uptime is less than 40 minutes and is already having problems again. 3.133.76.19 aws1.foldingathome.org WS 9.6.8 joseph 10,764.00/hr 0 0 Yes Assign 18,116 7,896 OPENMM_22, GRO_A7 6.72TiB 37 minutes 2020-05-03T04:09:54Z 04:07:02:WU01:FS01:Uploading 78.05MiB to 3.133.76.19 04:07:02:WU01:...

Update: 3.133.76.19:80 did finally start responding. I believe the assessment from a prior thread about these cloud servers being poorly suited to the task of supporting the FAH work was very apt. It seems that just about every time there is a server malfunctioning, it is either an Azure or AWS serv...

Both of these servers (3.133.76.19 and 3.21.157.11 show an uptime of 1 hour, but are not accepting communication to upload completed jobs. ******************************* Date: 2020-05-01 ******************************* 00:32:33:WU01:FS02:0x22:Completed 7840000 out of 8000000 steps (98%) 00:33:35:WU...

slowbook wrote:Is there some way to configure one power (CPU/GPU) level for non-idle usage and another power level for idle operations (on the same installation)? I poked around in FAHControl but I didn't see an obvious way to do that?

Thanks!

Long answer: not really

Short answer: no

This was my fault! I missed a step in the core release process and neglected to roll it out to ADVANCED as well. I've halted 13400 and 13401, and am working to get 0.0.5 deployed to ADVANCED. Thanks JohnChodera. I was a bit upset about not getting to fold that WU since it was estimated for a nice c...

Same here and no BETA but advanced 01:52:22:WU00:FS01:0x22:ERROR:110: Need version 0.0.5 01:52:22:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e) 01:53:15:WARNING:WU00:FS01:FahCore has not changed since last download, aborting core update 01:53:15:WARNING:WU00:FS01:FahCore returned: ...

This was an issue for those participating in internal testing of an unreleased FAHCore. I'm sorry, but support in this forum is for WUs and FAHCores that have been released to the public (including beta testing, provided you apply for beta test registration) Discard that project. Topic closed. Bruc...

So from the limited sample size, I'd say that there are still a few kinks to work out with Core22 0.0.5. Just in case it's not captured, I had already updated the client to the Windows version 7.6.9 of the F@H client. Similar version upgrades to 7.6.9 were also completed on 2 out of 3 of my Linux se...