I am not sending WU's!

[Rezman5]

Ever since 2 days ago when my Comcast@home was acting up when (I think) they were switching me to their new service. Anyway, not I can't send any WU's, and when I close program and open it, its says "Attemping to send Results." Then it just starts folding again, but my WU's are not showing up. I have tried reinstalling several times...but still no luck! HELP!!!

[mx]

I had the same problem, I lost over 50 work units before giving up!
If you check your stats page it will say"Active Processors 0".
I turned on the fold monitor and watched it when it turned in my WU'S, but I could'nt get credit for them.
Yes I tried re-installing on both of the machines that I had folding and nothing......not to mention they both have separate connections and eventhough they have separate connections, my credits for WU'S for both machines mysteriously stopped!
I would appreciate it if you let me know if you resolve your problem because you're not alone, I have removed FOLDING@HOME from both of my machines because of this problem........GOOD LUCK :rolleyes:

[mx]

I just checked my stats and it went up one wu for yesterday(the only WU credit I recieved in over a week) but it says two WU'S was my total for the day.....hmm I turned in four yesterday before un-installing and it goes up one and says I turned in two?????:rolleyes:

Also after I re-installed on both machines the last time, I let 24HRS go by and it still said that I had zero active processors.......so finally I got one credit with "active processors 0"
It is very strange that after I un-installed I mysteriously recieved one credit.

[Rezman5]

I got it to work. What OS are u running? If you have XP, go to add/remove programs. Then go to add/remove windows componets, on the left. Then just click continue and go on with the wizard. This solved my problem. I did not get that error tho.

[BBigJ]

I've been having a problem over the last few days also. There was about 24 or 48 hours where the fah website was down, and it looks like the results server was down also. I have six machines now that each have about two workunits in the queue. It looks like the current workunits are being sent ok, but I would like to get credit for 150 or so cpu-hours sitting in the queue. I know there is a command for the console versions to send workunits, but I don't remember it. How do I force the client to send results for 1)linux console, 2)windows console, and 3)windows graphical? Thanks.

SBs

[Kendan]

I got these from the mailing list.
Folding@home Version 2.10
Usage: fah [-mode]

Mode:
-config Configure user information
-queueinfo Get information on queued work units

-delete x Delete item #x from work queue

-send x Send result #x to server. Use x=all to send all
results

-verbosity x Sets the output level, from 1 to 9 (max). The default is 3

-local Use configuration files from local directory

default: Use configuration from Windows registry

[Rav]

I have this same problem. I currently have 5 units backed up in queue, and I can't get them to send! Having this problem previously, they would usually go through eventually, but they seem to be permanently stuck now. I am on dial up 28.8 (both comcast and verizon are incompitent) but it should still send. It transfers data for 10-15 secs before giving me a fail message. Oh and heres something interesting from my router when I try to send units:

Jan 19 10:16:54 - named[173]: sysquery: no addrs found for NS (Argus.stanford.edu)
Jan 19 10:16:54 - named[173]: sysquery: no addrs found for NS (Avallone.stanford.edu)
Jan 19 10:16:54 - named[173]: sysquery: no addrs found for NS (Atalante.stanford.edu)

What's going on?

-Rav

[The Coolest]

I really dunno what's hapening, my secondary rig isn't sending WU's also. when F@H starts, benchmarks, then it writes Trying to send... & after a couple of secs working again! WTF? I dunno if its my connection or the ICS again, I'll have to wait and see if the main rig will send work... That really sux and it ****es me off really bad! :mad:

[KFB]

I am yet another person that is having this problem. I don't know if it is my setup or if it something with Stanford (my guess: its something with ICS, my problem)

[Ploaf]

This problem appears to be a Stanford problem and I'd be willing to bet that it's server 113 that is the problem. I have had this happen on all of my machines. I have used the -send all command and some work was sent in but not all. In the end I erased some of it to keep my work folder clean. If the work is more than 6 days old then throw it out anyway. They won't accept it. Not sure what happened. I just want more of the GNRA hairpins. They are worth 2 points. :)

[KFB]

well it sure does suck. i have 5 or so WU's backed up in the queue. my machine was attempting to connect to .111 and .115 servers on the last attempt, not .113. i hope stanford figures it out before my WUs expire.

[Ploaf]

Originally posted by Kentucky Fried Bird
well it sure does suck. i have 5 or so WU's backed up in the queue. my machine was attempting to connect to .111 and .115 servers on the last attempt, not .113. i hope stanford figures it out before my WUs expire.

That's even worse then. I was having this situation on the same server each time. If it's all of the servers then the problem may be worse than we thought. It's hard to say.

This is why the queue was created, becuse the server problems were responsible for a lot of idle machines and project down time, but I think that it was supposed to work better than this. We should be storing work on occasion. The client was designed that way, but it should eventually be getting sent back.

[KFB]

what's weird is that my machine can get work packets no problem. on the last attempt it got a work unit from server 115.

[Rav]

I have been having problems with both .111 and .113. The .113 is the worst though, it usually fails immediately .111 usually goes through after a couple of tries, but not always.

-Rav

[KFB]

Is there a way to make the client return the WUs to a server that actually works? I agree, 113 totally sux. I'm thinking that the WUs are returned to the server where the client got the WU. Anyone contacted Stanford about this?
Which server(s) is/are actually accepting WUs?

[Ploaf]

Originally posted by Kentucky Fried Bird
Is there a way to make the client return the WUs to a server that actually works? I agree, 113 totally sux. I'm thinking that the WUs are returned to the server where the client got the WU. Anyone contacted Stanford about this?
Which server(s) is/are actually accepting WUs?


You can only send them back to the server that they came from. With the old client you could send them to another server, but even then Stanford just threw out the work. The server would accept the transfer and then discard the wu's and you wouldn't receive credit for them. The caching is meant so that in case of a server outage the work would be sent in later. I have manually sent some work back(this morning in fact) using the '-send all' command but not all. :(
Usually it makes it back within a day or so, but it looks like a lot of the previous work is just building up. If I'm not mistaken we have run the course of the villin which may be what those wu's are. The problem appears to be universal in that other teams have had the same problems. It just seems to be a waste of cycles.

[KFB]

Once again, thanks for the info ploaf. I am learning the nuances of Folding as I go along. The people at Stanford have much more work to do than I do, with the thousands of computers across the world that depend on their servers for up/downloading work. So, I shouldn't freak out about a sever being down for a a day or so, even if I don't get "credit" for the WUs or if my rigs end up wasting cycles. Overall, they run a really tight ship over there.

[muddocktor]

Originally posted by Ploaf



I have manually sent some work back(this morning in fact) using the '-send all' command but not all. :(


Ploaf, are you manually sending queued work with the console version or the graphical version of the client? I'm running the graphical version and I have 4 WU in queue on it and would like to get them sent in.

[AMDownz23]

My first post!

Anyway I thought I'd give my experience as a modem user at home and T1 at work.

I've been folding since F@H 1.0 and occasionally I couldn't send work. Till recently I just assumed their servers were down though 113 is clearly messed up right now. After doing a rather serious hardware upgrade a couple weeks ago at home (t-bird 1400@1707, 1333@1466 replaced with what you see in my sig) I had a stretch where I couldn't send my work. Furious, I threw the entire Folding folder onto my usb hard drive and brought it in to work..I ran f@h off that usb drive and what do you know? One by one the results sent like they were supposed to. Do Stanford's servers prefer broadband over 56k? I'd say yes on my end.

I suspect AOL is partly to blame for my continued problems sending work from home. Perhaps if I switched to Earthlink or another ISP my problems would dissappear. Server 115 is still letting me send work but 111 is not yet continues to give me work. We will see what happens tomorrow when I drop a result bomb on them. If a huge number appears under my name in the stats page you'll understand my frustration.

**FYI if you need insight into Stanford's server problems try this link..
http://groups.yahoo.com/group/folding-operations/

Some of the head cronies like Vijay chime in from time to time regarding server complaints

**Also I'm using the 2.17 console version..The main difference over 2.15 I saw was that it shows the time between frame completion. For example I learned one of my dual's will complete 8 bba's in 10 hours. It's probably more efficient running 1 or 2(on dual machines) at a time but I'm forced to run 8 at once since I'm not home all day.
Here's the link for 2.17
http://folding.stanford.edu/beta/

Thanks

[Ploaf]

Click Here (http://www.pickleloaf.com/foldingshortcuts.zip)

I will assume that you let the client install itself in the C:\Program Files\Folding@Home directory. If so then you can unzip this file and place the files in that directory. Use the shortcuts to do what you need. I included a copy of the FAHConsole.exe. If you already have an FAHConsole.exe then do not use that file.

KFB- I think you pretty much got it. As much as I hate to see wasted wu's I think that they may experience some problems when shutting off one of their runs and what we are seeing is that the last proteins to be sent back at the end of the run may never be accepted. It doesn't hurt to try and send them back though. This has always been a problem although it hasn't been as noticeable since we began using the new client.

AMDownz23- Glad to see you post here :D You're doing some serious folding. Thanks for the input. You may be right about the problems with dialup too. It seems that others have had similar problems and have had to manually send in wu's just to get them sent back.

[KFB]

AMDownz, thanks for the info from a veteran folder. You basically confirmed my suspicions that the Stanford servers do not like to wait for my slow-a$$ 28.8 modem upload. Right now the only server that is refusing my WUs is 115. I even wrote a little batch file to repeat the -send all command about 10 times in a row and still no cigar. Also, thanks for the link to the beta client - I'll check it out.
Do you know if it is possible to put the queue data on a floppy and take it to a location with a T1 or similar connection? Or should I put the whole Folding dir on a Zip disk or equivalent? Thanks for the help.

[AMDownz23]

KFB- *Before I continue make sure you've noted the number of each work unit that fails to send..i.e. 01,02, etc.*
I have never tried to just take the queue data with me so I have no idea how that would turn out..I have only tried taking the entire directory with me..If a Zip disk is available go ahead and use that..otherwise I would compress the folder as best you can and email it to the location with broadband and either you or someone there would unzip then run the client to send the wu's..Make sure you stop it before it gets work. When you get home stop f@h and go into the work folder on your machine and just delete the log and result files pertaining to the numbers you took down earlier..i.e 01,02,etc.. when that is done and you restart f@h it will give an error saying it couldn't find some files and then go about it's business. It won't try to upload those anymore. Hope that helps..

[AMDownz23]

Yep! I get to work and all the results sent to server 111...
113 is still down..I might just copy parts of this thread and fire off a complaint to Stanford. Damned sloppy.