Page 1 of 2
FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 4:28 pm
by eagles_fly
I've been folding for over 18 months now with minimal problems.
Running 6.34 SMP on an Pentium Dual Core T4300 @ 2.10GHz.
Went to check on progress as I normally do and noticed that it's stuck on trying to download FahCore.17.exe.
Code: Select all
[16:19:17]
[16:19:18] Loaded queue successfully.
[16:19:18]
[16:19:18] + Processing work unit
[16:19:18] Core required: FahCore_17.exe
[16:19:18] Core not found.
[16:19:18] - Core is not present or corrupted.
[16:19:18] - Attempting to download new core...
[16:19:18] + Downloading new core: FahCore_17.exe
[16:19:18] - Error: HTTP GET returned error code 404
[16:19:18] + Error: Could not download core
[16:19:18] + Core download error (#2), waiting before retry...
[16:19:24] + Downloading new core: FahCore_17.exe
[16:19:27] - Error: HTTP GET returned error code 404
[16:19:27] + Error: Could not download core
[16:19:27] + Core download error (#3), waiting before retry...
This is running as a service. I've stopped it in the services module, removed program from firewall (to get new prompts to allow access) and restarted the service with the same results as seen above.
Because I haven't been actively tweaking my FAH lately, I don't know which way to go with this.
Any thoughts or solutions appreciated.
Thanks!
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 4:39 pm
by bollix47
Welcome to the folding@home support forum eagles_fly.
What is the model of your GPU?
IIRC the minimum client version for core_17 work is version 7 so I'm not sure how you got that assignment. You might want to upgrade your client or make sure there's no reference to beta in your v6 configuration(if you have a -beta reference change it to -advmethods).
Also, if you're using Windows Vista or later you cannot run a GPU slot as a service.
If you could add more of the log showing the part where the work unit was downloaded and your config arguments it may help.
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 5:08 pm
by eagles_fly
Running on:
Dell Inspirion 1545 Laptop
Pentium Dual-Core T4300 @ 2.10Ghz
8GB DDR2 Memory
256GB Samsung 840 SSD
onboard video: Mobile Intel 4 Series Express Chipset
Windows 7 64-bit, Home Premium
v6.34 SMP, running at 100%
cpu only, no gpu processing
Code: Select all
[02:23:26] Completed 242500 out of 250000 steps (97%)
[02:38:30] Completed 245000 out of 250000 steps (98%)
[02:53:32] Completed 247500 out of 250000 steps (99%)
[03:11:44] Completed 250000 out of 250000 steps (100%)
[03:11:47] DynamicWrapper: Finished Work Unit: sleep=10000
[03:11:57]
[03:11:57] Finished Work Unit:
[03:11:57] - Reading up to 1567212 from "work/wudata_06.trr": Read 1567212
[03:11:57] trr file hash check passed.
[03:11:57] - Reading up to 1758352 from "work/wudata_06.xtc": Read 1758352
[03:11:57] xtc file hash check passed.
[03:11:57] edr file hash check passed.
[03:11:57] logfile size: 56823
[03:11:57] Leaving Run
[03:12:01] - Writing 3391815 bytes of core data to disk...
[03:12:03] Done: 3391303 -> 3247242 (compressed to 95.7 percent)
[03:12:03] ... Done.
[03:12:03] - Shutting down core
[03:12:03]
[03:12:03] Folding@home Core Shutdown: FINISHED_UNIT
[03:12:07] CoreStatus = 64 (100)
[03:12:07] Sending work to server
[03:12:07] Project: 8702 (Run 48, Clone 5, Gen 48)
[03:12:07] + Attempting to send results [July 28 03:12:07 UTC]
[03:13:06] + Results successfully sent
[03:13:06] Thank you for your contribution to Folding@Home.
[03:13:06] + Number of Units Completed: 272
[03:13:11] - Preparing to get new work unit...
[03:13:11] Cleaning up work directory
[03:13:11] + Attempting to get work packet
[03:13:11] Passkey found
[03:13:11] - Connecting to assignment server
[03:13:11] - Successful: assigned to (143.89.28.72).
[03:13:11] + News From Folding@Home: Welcome to Folding@Home
[03:13:12] Loaded queue successfully.
[03:13:12] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[03:13:23] + Attempting to get work packet
[03:13:23] Passkey found
[03:13:23] - Connecting to assignment server
[03:13:24] - Successful: assigned to (143.89.28.72).
[03:13:24] + News From Folding@Home: Welcome to Folding@Home
[03:13:24] Loaded queue successfully.
[03:13:25] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
~~Multiple attempts (18 total) at getting work then:
[10:16:51] - Attempt #18 to get work failed, and no other work to do.
Waiting before retry.
[11:05:02] + Attempting to get work packet
[11:05:02] Passkey found
[11:05:02] - Connecting to assignment server
[11:05:23] - Couldn't send HTTP request to server
[11:05:23] + Could not connect to Assignment Server
[11:05:24] - Successful: assigned to (171.64.65.98).
[11:05:24] + News From Folding@Home: Welcome to Folding@Home
[11:05:24] Loaded queue successfully.
[11:05:28] + Closed connections
[11:05:28]
[11:05:28] + Processing work unit
[11:05:28] Core required: FahCore_17.exe
[11:05:28] Core not found.
[11:05:28] - Core is not present or corrupted.
[11:05:28] - Attempting to download new core...
[11:05:28] + Downloading new core: FahCore_17.exe
[11:05:31] - Error: HTTP GET returned error code 404
[11:05:31] + Error: Could not download core
[11:05:31] + Core download error (#2), waiting before retry...
[11:05:49] + Downloading new core: FahCore_17.exe
[11:05:49] - Error: HTTP GET returned error code 404
[11:05:49] + Error: Could not download core
[11:05:49] + Core download error (#3), waiting before retry...
Checked config, adv and big are not enabled.
Let me know if you need more info.
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 5:18 pm
by bollix47
Okay, so you should not have received that assignment. I suggest you stop the client and delete the work folder as well as queue.dat and unitinfo.txt. You should also change the machine id in your configuration so you don't get the same work unit.
I'll ask PG to look into this as core_17 should not be assigned to a CPU client or to version 6 at this time.
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 5:30 pm
by eagles_fly
OK, did what you said (deleted work folder, queue.dat and unitinfo.dat) and changed id to 2. Now no work?
Code: Select all
[17:26:38] - Ask before connecting: No
[17:26:38] - User name: Eagles_Fly (Team 40051)
[17:26:38] - User ID: *******************
[17:26:38] - Machine ID: 2
[17:26:38]
[17:26:38] Work directory not found. Creating...
[17:26:38] Could not open work queue, generating new queue...
[17:26:38] - Preparing to get new work unit...
[17:26:38] Cleaning up work directory
[17:26:38] + Attempting to get work packet
[17:26:38] Passkey found
[17:26:38] - Connecting to assignment server
[17:26:41] - Successful: assigned to (143.89.28.72).
[17:26:41] + News From Folding@Home: Welcome to Folding@Home
[17:26:41] Loaded queue successfully.
[17:26:42] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
So I just let it keep checking for work?
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 5:35 pm
by bollix47
The server 143.89.28.72 appears to be working properly and does have work.
Can you please post the first 10 or 15 lines of FAHlog.txt where it shows the version and the arguments?
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 5:38 pm
by bollix47
Also, run the client with -configonly and change the packet size to big.
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 5:42 pm
by eagles_fly
Code: Select all
--- Opening Log file [July 27 11:28:18 UTC]
# Windows CPU Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.34
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Users\****\FAH
Service: C:\Users\****\FAH\FAH6.34-win32-SMP.exe
Arguments: -svcstart -d C:\Users\****\FAH -forceasm
Launched as a service.
Entered C:\Users\****\FAH to do work.
Warning:
By using the -forceasm flag, you are overriding
safeguards in the program. If you did not intend to
do this, please restart the program without -forceasm.
If work units are not completing fully (and particularly
if your machine is overclocked), then please discontinue
use of the flag.
[11:28:18] - Ask before connecting: No
[11:28:18] - User name: Eagles_Fly (Team 40051)
[11:28:18] - User ID: ***********************
[11:28:18] - Machine ID: 1
[11:28:18]
[11:28:18] Loaded queue successfully.
[11:28:18]
[11:28:18] + Processing work unit
[11:28:18] Core required: FahCore_a4.exe
[11:28:18] Core found.
[11:28:18] Working on queue slot 06 [July 27 11:28:18 UTC]
[11:28:18] + Working ...
[11:28:32]
[11:28:32] *------------------------------*
[11:28:32] Folding@Home Gromacs GB Core
[11:28:32] Version 2.27 (Dec. 15, 2010)
[11:28:32]
[11:28:32] Preparing to commence simulation
[11:28:32] - Assembly optimizations manually forced on.
[11:28:32] - Not checking prior termination.
[11:28:34] - Expanded 1024716 -> 2544640 (decompressed 248.3 percent)
[11:28:34] Called DecompressByteArray: compressed_data_size=1024716 data_size=2544640, decompressed_data_size=2544640 diff=0
[11:28:34] - Digital signature verified
[11:28:34]
[11:28:34] Project: 8702 (Run 48, Clone 5, Gen 48)
[11:28:34]
[11:28:36] Assembly optimizations on if available.
[11:28:36] Entering M.D.
[11:28:41] Using Gromacs checkpoints
[11:28:42] Mapping NT from 1 to 1
[11:28:43] Resuming from checkpoint
[11:28:43] Verified work/wudata_06.log
[11:28:43] Verified work/wudata_06.trr
[11:28:43] Verified work/wudata_06.xtc
[11:28:43] Verified work/wudata_06.edr
[11:28:44] Completed 96360 out of 250000 steps (38%)
[11:36:24] Completed 97500 out of 250000 steps (39%)
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 5:47 pm
by eagles_fly
changed to big and same results.
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 5:49 pm
by bollix47
That looks okay so after you change the packet size to big please open a command prompt in your fah directory and enter the following:
Paste the output here. You can x out your passkey and other personal info.
It may be that the server is simply out of work for your configuration.
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 6:01 pm
by eagles_fly
Code: Select all
C:\Users\****\FAH>type client.cfg
[settings]
username=Eagles_Fly
team=40051
passkey=*************************
asknet=no
machineid=2
bigpackets=big
extra_parms=-forceasm
local=272
[http]
active=no
host=localhost
port=8080
usereg=no
[core]
cpuusage=100
checkpoint=3
priority=96
addr=
[power]
battery=no
[clienttype]
memory=8152
type=0
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 6:10 pm
by bollix47
I can't see anything that looks like it would cause your problem other than there may not be any work for your configuration at this time.
One suggestion would be that you uninstall v6 and install v7. This will open up other projects that are currently v7 only and should give you work.
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 6:17 pm
by eagles_fly
Ok, thanks for all of the help.
At least we took care of the core 17 issue.
I tried v7 last year and it appeared to consume more resources than v6.34.
I've just upgraded memory and SSD recently so prob give it another shot.
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 6:24 pm
by bollix47
The latest edition of version 7 (7.3.6) does make an attempt to not be too intrusive. It should start off at a setting of Medium which should use one less than your total number of cores ... i.e. it should use only 1 of your cores just like your v6 setup is currently doing. Whether you decide to try v7 or simply wait for work is, of course, entirely your decision.
Good luck either way and don't hesitate to ask for help.
Re: FahCore_17.exe returned error 404
Posted: Sun Jul 28, 2013 6:58 pm
by eagles_fly
Well actually, v6 is set at 100% but using 50% of each core, which is why I liked this setup.
Last time I tried v7 I didn't have this functionality available. Like for 2 cores, if at 50%, it would max out one and leave the other idle.