Check your Windozes Boxen.

T

Tigerbiten

[H]ard|DCer of the Month - February 2007/January 2
Joined
Sep 24, 2002
Messages
5,028
A quick heads ups.

Stanford ran out of work units and some Windozes boxen where assigned to a Linux server.
If you box is stuck trying to download FahCore_a0.exe then you in a loop.
Looks like this in the FAHlog file .............

[16:54:56] + Downloading new core: FahCore_a0.exe
[16:54:57] - Error: HTTP GET returned error code 404
[16:54:57] + Error: Could not download core
[16:54:57] + Core download error (#1), waiting before retry...

You need to stop it.
Delete the work unit & part downloaded core.
Restart it and it will then download the correct type work unit.

3 out of 13 of my clients where stuck like this.
So if you see a drop in your PpD check it out.

Luck .............. :D
 
Thanks for the tip, I'll have to check my boxes when I get home..
 
ugh... this might take a while :mad:
 
sobe said:
Thanks for the tip, I'll have to check my boxes when I get home..
Click to expand...

Thanks.

Me too.

You need some help, Flecom? I can come over if you need some help.

It is 24F at 11am. I could use a break from the cold. :D
 
I checked about 20 of mine so far, no problems yet.

edit: ok so i forgot to check my own dual core box. oops.

thanks!
 
Tigerbiten said:
EMIII ............ :p

Works for me.
Click to expand...

He would have to run 7 instances of EMIII to monitor 642 CPUs. ;)
Folding on that many CPUs is hard on bandwidth as it is....then add 7 EMIIIs hammering it every 2 to 5 seconds waiting on 642 responses. Holy crap! :eek:
 
Hmm this ain't good. I won't be able to check any of the computers until mid December. I know people won't agree with me, but this is worse for me then when they assigned big packets to normal computers. Yes this doesn't affect the stability of the comps like the big wu did so that's a good thing, but it does affect my ppd and the # of wus turned in.

 
Yikes I had this on about 8 of our Windows boxes so far. Thank goodness the soekris cluster is running linux heh. I had to nuke everything in the folder except the fold.exe file and the config.cfg file, that was the only way I could get it to download a fresh new WU.
 
Killer[MoB] said:
He would have to run 7 instances of EMIII to monitor 642 CPUs.
Folding on that many CPUs is hard on bandwidth as it is....then add 7 EMIIIs hammering it every 2 to 5 seconds waiting on 642 responses. Holy crap!
Click to expand...

Actually I think it's 50 a instance limit.

Love ya Larry but EM3 takes a shit above ~ 20 or so. Later versions are better I think, I gave up long ago monitoring anything.

This AS issue is total crap. :mad: :( :mad: Tempted to say Stanford breaks'em, Stanford can go fix'em
 
If I was busy and had a huge number of boxen spread around, I'd wait to fix them until their next maintenance/cleaning time. I know that's not cool, but there's a point where one needs to spend time with family or spending time doing other things.

Does this get sorted out with just a restart? It doesn't look like it...

 
I have seven boxen in my garden.

All were fine. Thank goodness!

All okay for now. Hope this problem is sorted out.
 
From the Folding-community forum .............

[02:20:11] + Downloading new core: FahCore_a0.exe
[02:25:11] Couldn't send HTTP request to server (wininet)
[02:25:11] Couldn't download www.stanford.edu
[02:25:11] + Error: Could not download core
[02:25:11] - Giving up on downloading core, trying new work unit instead
[02:25:11] Deleting current work unit & continuing...

So it looks like Stanford may have set up a fix to clear the problem for unmonitored borgs.

Luck ................. :D
 
Tigerbiten said:
From the Folding-community forum .............

[02:20:11] + Downloading new core: FahCore_a0.exe
[02:25:11] Couldn't send HTTP request to server (wininet)
[02:25:11] Couldn't download www.stanford.edu
[02:25:11] + Error: Could not download core
[02:25:11] - Giving up on downloading core, trying new work unit instead
[02:25:11] Deleting current work unit & continuing...

So it looks like Stanford may have set up a fix to clear the problem for unmonitored borgs.

Luck ................. :D
Click to expand...
Good... Now all I've got to do is sit back...
 
Seeing as I turned in ZERO points yesterday..I need to get back to work and see if I got any of these...
 
ya the last few days my stats have been in the trash... i have a feeling this hit me hard... i have no reasonable way of checking my computers without going to each one, and im not manually checking 600 machines... sorry...
 
Some of my borgs are over 1500 miles away, and there's no way I can check them without bothering their owners. I guess Stanford will have to fix the problem on their own somehow...
 
FLECOM said:
ya the last few days my stats have been in the trash... i have a feeling this hit me hard... i have no reasonable way of checking my computers without going to each one, and im not manually checking 600 machines... sorry...
Click to expand...
Slacker
:p ;)
 
FLECOM said:
ya the last few days my stats have been in the trash... i have a feeling this hit me hard... i have no reasonable way of checking my computers without going to each one, and im not manually checking 600 machines... sorry...
Click to expand...

While I don't have as many as you to check, I, like you, am unwilling to take time away from my actual work to investigate all the labs I have F@H running on. A maintenance cycle is coming - if I'm still seeing problems, I'll just have the labs reimaged. :p

 
Tigerbiten said:
So it looks like Stanford may have set up a fix to clear the problem for unmonitored borgs.
Click to expand...

Let's hope so, as this is kinda up there with the QMD to all fiasco last year. :(
 
Tigerbiten said:
A quick heads ups.

Stanford ran out of work units and some Windozes boxen where assigned to a Linux server.
If you box is stuck trying to download FahCore_a0.exe then you in a loop.
Looks like this in the FAHlog file .............

[16:54:56] + Downloading new core: FahCore_a0.exe
[16:54:57] - Error: HTTP GET returned error code 404
[16:54:57] + Error: Could not download core
[16:54:57] + Core download error (#1), waiting before retry...

You need to stop it.
Delete the work unit & part downloaded core.
Restart it and it will then download the correct type work unit.

3 out of 13 of my clients where stuck like this.
So if you see a drop in your PpD check it out.

Luck .............. :D
Click to expand...

Yup, I had the same thing happen, just deleted it and reinstalled F@Home.
 
deleting all but the exe and cfg files didn't see to fix the problem -nor did deleting all of it and reinstalling the client. is there any harm in manually downloading the core?
 
jmroberts70 said:
deleting all but the exe and cfg files didn't see to fix the problem -nor did deleting all of it and reinstalling the client. is there any harm in manually downloading the core?
Click to expand...

You cannot manully down load the core.
Even if you could it would do you no good and it a Linux core not a Windozes one.

You need to delete the Queue.dat file and then either the whole work folder or just the Current.xyz file in it.

That will clear the problem.

Luck .............. :D
 
Nevermind, I think I'm going to go to the console client anyways since I'm running on a core2 system and want to take advantage of multiple CPU's. I bet that will solve the problem anyways.

**edit**

Alright this is getting silly. Am I missing something terribly obvious? I uninstalled, deleted the directory, installed the console client, and this is what I still get in the log:

[06:00:09] + Processing work unit
[06:00:09] Core required: FahCore_78.exe
[06:00:09] Core not found.
[06:00:09] - Core is not present or corrupted.
[06:00:09] - Attempting to download new core...
[06:00:09] + Downloading new core: FahCore_78.exe
[06:00:09] - Error: HTTP GET returned error code 0
[06:00:09] + Error: Could not download core
[06:00:09] + Core download error (#2), waiting before retry...

Help me out here guys!
 
The core it's downloading is a normal core--not the Linux one that's causing problems. I've heard that Stanford is having problems with their assignment servers (besides assigning Linux WUs to Windows boxen). You're set up fine. Just let it run until Stanford fixes their servers.
 
The bad core is the FahCore_a0.exe
Yours is a standard FahCore_78.exe

Do you have any other boxen folding.
If so just copy the "FahCore_78.exe" from one to other.
Then you should be good to go.

Luck ............ :D
 
its happened again.

[17:04:31] - Preparing to get new work unit...
[17:04:31] + Attempting to get work packet
[17:04:31] - Connecting to assignment server
[17:04:31] - Successful: assigned to (171.65.103.68). <- Linux only server.
[17:04:31] + News From Folding@Home: Welcome to Folding@Home
[17:04:32] Loaded queue successfully.
[17:04:32] - Couldn't send HTTP request to server
[17:04:32] (Got status 503)
[17:04:32] + Could not connect to Work Server
[17:04:32] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
--------- Snip ------------------------
[17:05:16] - Error: Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[17:05:57] + Attempting to get work packet
[17:05:57] - Connecting to assignment server
[17:05:57] - Successful: assigned to (171.65.103.68).
[17:05:57] + News From Folding@Home: Welcome to Folding@Home
[17:05:58] Loaded queue successfully.
[17:07:51] + Closed connections
[17:07:51]
[17:07:51] + Processing work unit
[17:07:51] Core required: FahCore_a0.exe <- Linux core on Windoze boxen wont work.
[17:07:51] Core not found.
[17:07:51] - Core is not present or corrupted.
[17:07:51] - Attempting to download new core...
[17:07:51] + Downloading new core: FahCore_a0.exe
[17:07:51] - Error: HTTP GET returned error code 404
[17:07:51] + Error: Could not download core
[17:07:51] + Core download error (#2), waiting before retry...

[17:08:08] + Downloading new core: FahCore_a0.exe
[17:08:09] - Error: HTTP GET returned error code 404
[17:08:09] + Error: Could not download core
[17:08:09] + Core download error (#3), waiting before retry...
---------- Etc, etc ---------------------------------------------

Going to the suport forums to report this.

Luck ............... :D
 
JUst happend to me not more than a hour ago, the machine is about 5 feet from me (fax server) so its really no big deal. I am going to reinstall. Time to update anyway.

 
Actually, I'm still having the same problem with the machine I mentioned earlier. It looks like it's never been able to download the core -no matter what I've tried. 2 weeks seems like a long time for Stanford to not have their servers running properly to me.
 
I must have been lucky.

This never happened to any of my boxen. Have 7 running full time.
 
2 of mine were stuck in the loop... Stopped the client, deleted the work folder and the queue.dat file and the 0 byte linux core file fixed it right up.
 
Oh well.... I spoke too soon.


One of my boxen had this problem. Deleted some stuff and started over. Working fine now.

How come this error is still in the wild?
 
I started up a new install (only temporary) on a P4D and both cores kept trying to download the linux core 8(

 
You must log in or register to reply here.
Back
Top