Help fight cancer with F@H! join team ECF today!!!!!!

[sashwa]

Gotcha, loft. My iMac is already using smp. So I'm good. I thought you might be talking about another switch.

 

[Wulfe]

Yes what i gave earlier was the basics. If you are more interested in some advanced techniques;

Linux

Documentation:
./FAHClient --help

Configuration using config.xml:
./FAHClient --configure

Configuration with no config file (minimum flags):

./FAHClient --user=Anonymous --team=0 --passkey=1385yourpasskeyhere5924 --gpu=false --smp=true

For Windows just remove the "./"


You may find the command line clients and more information reguarding them from the Stanford Win/Lin Guides respectivly.

Folding@home - WinGuide
Folding@home - LinGuide

I highly recommend using the command line to everyone on Linux OS, and unless your are an advanced/expert user to just stick with the GUI FAHControl on Windows.


I would also like to add that those guides do not afficiate to just the command line options but are also complete guides to both the windows and linux clients. They are very good reading material for anyone who is just starting out on F@H and would like to know everything about there new adventure in F@H.

 

[beebopnjazz]

Not only do I have a WU that can't be sent as the collection server is refusing...my current smp WU is set to be collected by the same server....and that unit is still refusing WUs.

 

[tmcase]

Not only do I have a WU that can't be sent as the collection server is refusing...my current smp WU is set to be collected by the same server....and that unit is still refusing WUs.

How frustrating. Is there somebody at FAH that you can contact to get this resolved?

 

[Wulfe]

Not only do I have a WU that can't be sent as the collection server is refusing...my current smp WU is set to be collected by the same server....and that unit is still refusing WUs.

Collection Server - FaHWiki

For security reasons the Collection Server will only accept results from WUs it knows have been assigned. The Work Servers normally publish lists of their assigned WUs to the Collection Server, but on occasion this does not occur. If in this circumstance the Work Server then becomes unavailable, the Collection server will refuse to accept WUs that were assigned by that Work Server subsequent to the last list being published, because it cannot guarantee that they have been genuinely assigned.

The list for the Collection Server will be updated again when the Work Server is on-line again and then the WU will upload to either one.

I hope this may help your problem. If this does not post logs from your log file so that we may track down the error at hand.

 

[beebopnjazz]

Server load is too high at F@H.......I can't "contact us"........

 

[sashwa]

beeb, that a look at this link for Server Status for FAH:

Server Status for Folding@home

to see if your server is collecting. Sometimes their servers get messed up or get filled up.

 

[beebopnjazz]

21:28:21:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
21:28:23:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
21:28:24:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
21:28:24:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
21:28:26:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
21:28:27:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
21:29:24:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
21:29:26:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
21:29:27:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
21:31:01:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
21:31:03:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
21:31:04:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
21:33:39:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
21:33:40:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
21:33:41:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
21:37:53:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
21:37:54:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
21:37:56:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
21:44:44:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
21:44:46:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
21:44:47:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
21:55:50:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
21:55:51:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
21:55:57:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
22:13:47:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
22:13:48:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
22:13:50:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
22:42:49:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
22:42:51:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
22:42:52:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
23:29:48:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
23:29:49:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
23:30:03:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
00:46:10:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
00:46:31:WARNING:WU02:FS00:Exception: Failed to send results to work server: Failed to connect to 171.67.108.11:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
00:46:52:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
00:46:53:WARNING:WU00:FS00:Failed to get assignment from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
00:47:13:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
00:47:14:WARNING:WU00:FS00:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Failed to connect to assign-GPU.stanford.edu:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
00:47:14:ERROR:WU00:FS00:Exception: Could not get an assignment
00:47:35:WARNING:WU00:FS00:Failed to get assignment from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
02:48:49:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
02:48:50:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
02:48:51:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
******************************** Date: 10/01/13 ********************************
06:07:49:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
06:07:50:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
06:07:51:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
******************************** Date: 10/01/13 ********************************
11:29:48:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
11:29:50:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
11:29:51:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
******************************** Date: 10/01/13 ********************************
17:29:49:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
17:29:50:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
17:29:51:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.
******************************** Date: 10/01/13 ********************************
23:29:49:WARNING:WU02:FS00:Exception: Failed to send results to work server: Transfer failed
23:29:50:WARNING:WU02:FS00:WorkServer connection failed on port 8080 trying 80
23:29:52:ERROR:WU02:FS00:Exception: Failed to connect to 171.67.108.25:80: No connection could be made because the target machine actively refused it.

This is my stalled completed WU - the new one is the same project different run #5765 - all to be collected by 171.67.108.25 -

 

[beebopnjazz]

Both WUs came from the same server too ..... wonder how many uncollected WUs are floating around.

 

[Wulfe]

Yeah that machine is currently in standby mode and not accepting connections. That particular server is a wonky one tbh. I found this post on the F@H forums reguarding the same server.

From what i am gathering the workserver assign-GPU.stanford.edu is down and since its collection server "171.67.108.25" is already wonky, you will just have to wait untill the work server comes back. There really is not anything that can be done about it on your side.

 

[beebopnjazz]

171.67.108.11 is the sending server - it's full but is accepting according to the stats - unfortunately it's sending WUs to be collected by a rejecting unit.

It's gonna start looking like an airport with flights in the air that are unable to land around here.

 

[Wulfe]

I thought that may be the IP of the work server. These things happen. Such is the bane of working with F@H. Its like trying to hit the lottery sometimes. Hang in there it will eventually accept your connections and finish those units out.

 

[loft]

I hate to say it, but if you end up going for days being unable to submit that particular WU, I would abandon it. Especially if the second one you're working on now shows the same pattern.

 

[row6969]

can i join in tean ecf

 

[emonty]

another benefit folding: liquid steeping next to the fan

 

[Mustang73064]

can i join in tean ecf

Just go to the first message in this thread and follow the instructions.

 

[Lbox88]

It can be used for all console clients pre v7 I believe. If you're using the GUI v7 client then it should be on by default (if you used default install options).

Lbox what video card are you using?

 

[loft]

You'll be able to run 12 threads on smp and it should be unaffected by the gpu. Are you using the v7 GUI client?

 

[beebopnjazz]

Here's one for the F@H vets - the same unit is still being rejected - and now it's expired - will it get dumped after next close of the program? AND the unit that was the same last night - and to the bad server - went.....go figure

 

[Lbox88]

Yep. Not using the 560 though, would like to but with the software I have to use at work does not play nice with F@H.

Think those but imagine 800 little boxes running on all that conveyor................. GTX560 not happy lol