Folding Forum

I guess that's what I'll do - thanks - didn't realize I was posting in the wrong forum for help on it.

I have the same issue and posted in the GPU forums about it, but it's waiting moderation approval..

Same here and no BETA but advanced

WChilla wrote:Same here and no BETA but advanced

Code: Select all

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: CORE_OUTDATED (110 = 0x6e)
01:54:59:WARNING:WU00:FS01:FahCore has not changed since last download, aborting core update
01:54:59:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e)
01:57:30:WARNING:WU00:FS01:FahCore has not changed since last download, aborting core update
01:57:30:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e)
02:01:43:WARNING:WU00:FS01:FahCore has not changed since last download, aborting core update
02:01:44:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e)

WChilla, what I had to do was pause all of my jobs, then stop the folding at home client completely. Then delete the entire folder matching up to the offending work unit #. Once that folder is gone, then I restarted the client and restarted my jobs (a couple of times because I kept getting garbage from that one server).

That should be a more succinct explanation of how to follow JohnChodera's directions.

JohnChodera wrote:Thanks for the update. I'll pause that server (aws3.foldingathome.org) from ADVANCED until we can figure out what is going on.

Can you try removing your cores/ directory and see if it correctly auto-downloads core22 0.0.5?

OK. New information:

I believe this has now been fixed.

JimboPalmer wrote:To the best of my knowledge, 0.0.2 is the latest production version.

You aren't playing with Beta flags without being on the Beta team are you?

Nope no beta just advanced - first WU I've had to dump but that's the nature of things sometimes. All 5 slots now folding again.

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.

Lol I was just startled and didn't want to dump a good unit - I'm just glad it's resolved and I look forward to crunching a ton tonight.

tbonse wrote:

WChilla wrote:Same here and no BETA but advanced

Code: Select all

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: CORE_OUTDATED (110 = 0x6e)
01:54:59:WARNING:WU00:FS01:FahCore has not changed since last download, aborting core update
01:54:59:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e)
01:57:30:WARNING:WU00:FS01:FahCore has not changed since last download, aborting core update
01:57:30:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e)
02:01:43:WARNING:WU00:FS01:FahCore has not changed since last download, aborting core update
02:01:44:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e)

WChilla, what I had to do was pause all of my jobs, then stop the folding at home client completely. Then delete the entire folder matching up to the offending work unit #. Once that folder is gone, then I restarted the client and restarted my jobs (a couple of times because I kept getting garbage from that one server).

That should be a more succinct explanation of how to follow JohnChodera's directions.

JohnChodera wrote:Thanks for the update. I'll pause that server (aws3.foldingathome.org) from ADVANCED until we can figure out what is going on.

Can you try removing your cores/ directory and see if it correctly auto-downloads core22 0.0.5?

Thank you… I'll try…

02:48:34:WU00:FS01:0x22:ERROR:110: Need version 0.0.5
02:48:34:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e)
02:49:33:WARNING:WU00:FS01:FahCore has not changed since last download, aborting core update
02:49:34:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e)

no luck

JohnChodera wrote: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 chunky 205k pts. Still better to work on something that will fold and not have a slot sitting idle for a day and a half in the off chance something will fix itself.

schapman1978 wrote:Lol I was just startled and didn't want to dump a good unit - I'm just glad it's resolved and I look forward to crunching a ton tonight.

Same here schapman1978. I've got all of my currently assembled machines operating in "heater" mode. Fortunately it's been cool enough out that I haven't reached the point of needing to turn on the AC.

WChilla wrote:

tbonse wrote:

WChilla wrote:Same here and no BETA but advanced

Code: Select all

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: CORE_OUTDATED (110 = 0x6e)
01:54:59:WARNING:WU00:FS01:FahCore has not changed since last download, aborting core update
01:54:59:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e)
01:57:30:WARNING:WU00:FS01:FahCore has not changed since last download, aborting core update
01:57:30:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e)
02:01:43:WARNING:WU00:FS01:FahCore has not changed since last download, aborting core update
02:01:44:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e)

WChilla, what I had to do was pause all of my jobs, then stop the folding at home client completely. Then delete the entire folder matching up to the offending work unit #. Once that folder is gone, then I restarted the client and restarted my jobs (a couple of times because I kept getting garbage from that one server).

That should be a more succinct explanation of how to follow JohnChodera's directions.

JohnChodera wrote:Thanks for the update. I'll pause that server (aws3.foldingathome.org) from ADVANCED until we can figure out what is going on.

Can you try removing your cores/ directory and see if it correctly auto-downloads core22 0.0.5?

Thank you… I'll try…

02:48:34:WU00:FS01:0x22:ERROR:110: Need version 0.0.5
02:48:34:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e)
02:49:33:WARNING:WU00:FS01:FahCore has not changed since last download, aborting core update
02:49:34:WARNING:WU00:FS01:FahCore returned: CORE_OUTDATED (110 = 0x6e)

no luck

Ah, the key is to delete the unit from the "Work" folder, not the cores folder. That fixed it for me..

Merci

> And again with another bad core for project 13400 served by 18.188.125.154.

@tbonse: Our apologies! I set the WS to INTERNAL-only as soon as we realized what was going on, when I posted immediately before you---you must have got some of the tail end of the WUs that require 0.0.5.

We're just waiting for it to be rolled out to ADVANCED.

> Ah, the key is to delete the unit from the "Work" folder, not the cores folder. That fixed it for me..

@alien88: Thanks for this solution! You're right---I had previously thought the issue was that the core22 0.0.5 release was available for ADVANCED downloads, but the real issue was that the WU you got from the WS (which is now safely back in INTERNAL mode) was intended only for core22 0.0.5, which hasn't yet made it to ADVANCED. We're working to get that deployed to ADVANCED ASAP.

Again, my apologies! This was my fault---we're documenting this so it doesn't happen again!

JohnChodera wrote:> Ah, the key is to delete the unit from the "Work" folder, not the cores folder. That fixed it for me..

@alien88: Thanks for this solution! You're right---I had previously thought the issue was that the core22 0.0.5 release was available for ADVANCED downloads, but the real issue was that the WU you got from the WS (which is now safely back in INTERNAL mode) was intended only for core22 0.0.5, which hasn't yet made it to ADVANCED. We're working to get that deployed to ADVANCED ASAP.

Again, my apologies! This was my fault---we're documenting this so it doesn't happen again!

No problem John! Mistakes happen and I get what the issue is now haha.. I appreciate the work everyone is doing with the explosive growth of F@H