THGC Needs You -Team 40051

Page 60 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
I have EM-3 to monitor my folding progress on my 7 computer folding farm here at work, I've yet to tinker around with a monitor for folding on my Mandriva box at home.

#118 😀 Expecting a good 1500+ points boost when the 2P server finishes running 4 clients at the same time :lol:

Addictive doesn't describe it 8O Must get other 3 servers runnning F@H... Must find more PC for my farm! MUST FOLD! :mrgreen:
 
I have two instances of FAH running on my Opty 165. I seem to have built up 9 queued WU's ready to go on one instance and 8 on the other.

1st question:
How many will FAH build before it starts throwing them away?

2nd question:
Is there any way to try to force FAH to send them so I can see if my firewall gives me any messages?

I am using Zone Alram and I have granted full privilages to the service's process and to each core.
 
Hey guys, I can't seem to fold my second WU. Here's the logfile:

[05:42:49] + Attempting to send results
[05:42:50] Couldn't send HTTP request to server (wininet)
[05:42:50] + Could not connect to Work Server (results)
[05:42:50] (171.65.103.100:8080)
[05:42:50] Could not transmit unit 02 to Collection server; keeping in queue.
[05:42:50] - Preparing to get new work unit...
[05:42:50] + Attempting to get work packet
[05:42:50] - Connecting to assignment server
[05:42:53] - Successful: assigned to (171.64.122.133).
[05:42:53] + News From Folding@Home: Welcome to Folding@Home
[05:42:53] Loaded queue successfully.
[05:42:55] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[05:43:05] + Attempting to get work packet
[05:43:05] - Connecting to assignment server
[05:43:07] - Successful: assigned to (171.64.122.133).
[05:43:07] + News From Folding@Home: Welcome to Folding@Home
[05:43:07] Loaded queue successfully.
[05:43:08] - Error: Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[05:43:19] + Attempting to get work packet
[05:43:19] - Connecting to assignment server
[05:43:20] - Successful: assigned to (171.64.122.133).
[05:43:20] + News From Folding@Home: Welcome to Folding@Home
[05:43:20] Loaded queue successfully.
[05:43:21] - Error: Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[05:43:55] + Attempting to get work packet
[05:43:55] - Connecting to assignment server
[05:43:55] - Successful: assigned to (171.64.122.133).
[05:43:55] + News From Folding@Home: Welcome to Folding@Home
[05:43:55] Loaded queue successfully.
[05:43:55] - Error: Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[05:44:40] + Attempting to get work packet
[05:44:40] - Connecting to assignment server
[05:44:40] - Successful: assigned to (171.64.122.133).
[05:44:40] + News From Folding@Home: Welcome to Folding@Home
[05:44:40] Loaded queue successfully.
[05:44:40] - Error: Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[05:46:05] + Attempting to get work packet
[05:46:05] - Connecting to assignment server
[05:46:05] - Successful: assigned to (171.64.122.133).
[05:46:05] + News From Folding@Home: Welcome to Folding@Home
[05:46:05] Loaded queue successfully.
[05:46:05] - Error: Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[05:48:52] + Attempting to get work packet
[05:48:52] - Connecting to assignment server
[05:48:52] - Successful: assigned to (171.64.122.133).
[05:48:52] + News From Folding@Home: Welcome to Folding@Home
[05:48:53] Loaded queue successfully.
[05:48:53] - Error: Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[05:54:16] + Attempting to get work packet
[05:54:16] - Connecting to assignment server
[05:54:16] - Successful: assigned to (171.64.122.133).
[05:54:16] + News From Folding@Home: Welcome to Folding@Home
[05:54:16] Loaded queue successfully.
[05:54:16] - Error: Attempt #8 to get work failed, and no other work to do.
Waiting before retry.
[06:05:09] + Attempting to get work packet
[06:05:09] - Connecting to assignment server
[06:05:09] - Successful: assigned to (171.64.122.133).
[06:05:09] + News From Folding@Home: Welcome to Folding@Home
[06:05:09] Loaded queue successfully.
[06:05:09] - Error: Attempt #9 to get work failed, and no other work to do.
Waiting before retry.
[06:26:41] + Attempting to get work packet
[06:26:41] - Connecting to assignment server
[06:26:41] - Successful: assigned to (171.64.122.133).
[06:26:41] + News From Folding@Home: Welcome to Folding@Home
[06:26:41] Loaded queue successfully.
[06:26:41] - Error: Attempt #10 to get work failed, and no other work to do.
Waiting before retry.
[07:09:24] + Attempting to get work packet
[07:09:24] - Connecting to assignment server
[07:09:25] - Successful: assigned to (171.64.122.133).
[07:09:25] + News From Folding@Home: Welcome to Folding@Home
[07:09:25] Loaded queue successfully.
[07:09:25] - Error: Attempt #11 to get work failed, and no other work to do.
Waiting before retry.
[00:18:40] + Attempting to get work packet


[00:18:40] + Attempting to send results
[00:18:41] - Connecting to assignment server
[00:18:45] Couldn't send HTTP request to server (wininet)
[00:18:45] + Could not connect to Assignment Server
[00:18:45] Couldn't send HTTP request to server (wininet)
[00:18:45] + Could not connect to Assignment Server 2
[00:18:45] + Couldn't get work instructions.
[00:18:45] - Error: Attempt #12 to get work failed, and no other work to do.
Waiting before retry.
[00:18:53] Couldn't send HTTP request to server (wininet)
[00:18:53] + Could not connect to Work Server (results)
[00:18:53] (171.65.103.160:8080)
[00:18:53] - Error: Could not transmit unit 02 (completed December 14) to work server.


[00:18:53] + Attempting to send results
[00:18:54] Couldn't send HTTP request to server (wininet)
[00:18:54] + Could not connect to Work Server (results)
[00:18:54] (171.65.103.100:8080)
[00:18:54] Could not transmit unit 02 to Collection server; keeping in queue.

Please help me!
 
djplanet,
It is telling you that it can't establish a network connection to send the results or to get new work. 🙁

If that is the machine you posted your message with then Stanford is probably having some problems. Just be patient. 8)

If it is a different machine then be sure to double check your network. Try to ping yahoo, or somebody like that, from that machine. 8)

e-mail or IM me for more detailed help if you need it after checking your network. :wink:

Bill
 
@Aragorn:
1) i think it would probably keep up to 9, however, i am uncertain about this, but when you look at your queue, you will find that there are 9 spaces, look at the example below on how i would view my queue

[code:1:3c97551524]cd\
cd/FAH1
fah504-console.exe -queueinfo[/code:1:3c97551524]

*note that you have to cd out of the default directory and into the FAH directory*

finding the directory and then putting the -queueinfo command after the exe file's name

2) to force an instance of F@H to send, you have to go to the directory of that instance and then, after viewing your queue and finding a valid sending number, do:

[code:1:3c97551524]cd\
cd/FAH1
fah504-console.exe -send XX[/code:1:3c97551524]

where xx is the queue number previously chosen

note that this is an example of how i have my directories set up (using C:\FAH1 and C:\FAH2 and your directories may be different, but you get the point.

if you want to see more details, like the upload details of a specific WU, while you are giving the -send xx command, also give the -verbosity 9 command.

Ara

PM me if you have any other questions...
 
@Ara
Thanks for the advice.

@All
It looks like all lthe finished WU's are supposed to go to machines that are full. Is there anything I can do to get credit for these? Can they go to a different server?
 
djplanet,

Hay there pardner :)
You got that connection going yet so you can continue folding? :)
If you are still having trouble I've got a fix for you. 8)

One of my machines hung this morning trying to download a work packet and I had to make a config change to get it to continue on. :x

If you are still having trouble please post the client type, graphical or console, and I'll let you know how to fix it. 8)

Of course, if all is working OK, never mind 😀

Bill
 
mpilchfamily,

No problem, you're good :)
See the wiki explaining some of this at the following link:
http://fahwiki.net/index.php/WorkUnits

The most common WUs right now seem to be from the p2124 and the p2125 projects 8)
The above link explaines how this works pretty well and why you may get 2, or more, from the same project. They arn't the same, just from the same projest :)

Points are awarded based on a benchmark system that is a 2.8 Ghz P4 running Linux. 8) 110 points is awarded for each 24 hours the run takes. I.E. 2 days is worth 220 points, etc. :)
You can turn that around and figure a 400 pointer running on a 2.8 Ghz P4 takes almost 4 days 8) How does your computer compare to a 2.8 Ghz P4. Faster will get done sooner, slower will take longer :)
This is explained in more detail in the above link as well :)

The link should explain most of the basics well enough and there are links on the page taking you to about anything else you may want to know, all the way to information overload 8)

If you have any more questions, don't hesitate to ask 😀

Bill
 
Hey bholland2, I'm running the graphical client. It's a 50,000 frame GROMACS core WU. Three days later, still hasn't sent the job.

Some more logfile-age!


[04:55:05] + Attempting to send results
[04:55:10] - Connecting to assignment server
[04:55:12] Couldn't send HTTP request to server (wininet)
[04:55:12] + Could not connect to Assignment Server
[04:55:14] Couldn't send HTTP request to server (wininet)
[04:55:14] + Could not connect to Assignment Server 2
[04:55:14] + Couldn't get work instructions.
[04:55:14] - Error: Attempt #30 to get work failed, and no other work to do.
Waiting before retry.
[04:55:50] Couldn't send HTTP request to server (wininet)
[04:55:50] + Could not connect to Work Server (results)
[04:55:50] (171.65.103.160:8080)
[04:55:50] - Error: Could not transmit unit 02 (completed December 14) to work server.


[04:55:50] + Attempting to send results
[04:55:51] Couldn't send HTTP request to server (wininet)
[04:55:51] + Could not connect to Work Server (results)
[04:55:51] (171.65.103.100:8080)
[04:55:51] Could not transmit unit 02 to Collection server; keeping in queue.
[05:43:25] + Attempting to get work packet
[05:43:25] - Connecting to assignment server
[05:43:25] - Successful: assigned to (171.64.122.133).
[05:43:25] + News From Folding@Home: Welcome to Folding@Home
[05:43:25] Loaded queue successfully.
[05:43:25] - Error: Attempt #31 to get work failed, and no other work to do.
Waiting before retry.

Could Stanford be having problems for three days straight? Maybe they have something againt me, I did apply to Cal :lol: .
 
djplanet,

Could Stanford be having problems for three days straight? Maybe they have something againt me, I did apply to Cal.

That's probably it... They heard about you :lol:

Seriously though, the graphical client is the easy one. :)

Be sure to read all of this before starting :)

This won't help in sending your results. As a point of interest, I had one try for almost 2 weeks once before it finally went. I've not been able to find any solution to an upload problem other than patience. :?
The server stats says all is well with the server you are trying to send to:
http://fah-web.stanford.edu/serverstat.html
(as a point of interest, that is the same server I had trouble with)

As for getting work, well that is a bit easier to fix.

Here is what worked for me:
Right click on the folding (little red gear) icon in the system tray
select "Configure..."
in the config menu select the "Advanced" tab
down near the bottom in the "Deadlines" section select the "standard" option (NOTE - select "Standard" if you have "No Preference". If you already have "Standard" then make it "No Prefenence". Never select "Deadlineless", there is hardley ever any work there anymore).
after changing your preferences click OK

Now you have to kill the client and restart it. You have changed the configuration but it doesn't know about it yet:
The easiest way to do that is to Re-Boot windows :roll:

You can do it this way too:
right click on the FAH gear icon again
this time select "quit" (OK... now you have killed it)

Now start it again from the screen icon or from the "startup" sub menu.

It should now connect, get a job and start it. Give it a couple of minutes to get started then check your log.

Like I said, this won't help with uploading, but it should get you back to work while you are waiting.

If you have any problems or questions, just let me know.

Bill
 
djplanet, if I'd want to help you, I'd need more information on your connection..
like:
are you in a company-LAN?
does your normal (ie IE) internet-connection use a PROXY server?
did you choose "use IE-connection settings" in your FAH-client configuration?

if all of the above is true, it might be the configuration of the proxy server in your LAN environment. --> talk to your admin!
 
Thanks for the help. I did have it set to deadlineless work because I was afraid my laptop wasn't powerful enough to get WUs done on time. Does a Pentium M 760 sound sufficient?

In other news, when open the client window, it shows I only have one WU completed. But on the stats webpage, it says I have two, go figure :roll: . As long as the online one is right.

At stefan: no proxy server, my home connection and computer. Thanks for the help though.
 
djplanet,

Yah, the M760 sounds fine. :)
I actually have 3 machines a lot slower than that running. How about 3 Celeron 466 machines overclocked to 525 :lol: These bad boys do about 100 points a week each (the old celerons don't have the SSE extensions so they are really slow). It isn't much, but there are 3 of tham. :) It adds up.

More importantly to this conversation, I have a PIII 733 running that produces about 35 points per day, that's about 245 points per week, and that is just fine. It always turns in work before the preferd deadline. 8) The M760 should be in that neighborhood, perhaps a bit faster. 8)

Bill
 

TRENDING THREADS