• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

wu's not sending/uploading

S

slider11

n00b
Joined
Feb 24, 2012
Messages
53
i recently completed a 6903 wu and it said it failed to connect to the http or whatever to send.

[16:30:14] DynamicWrapper: Finished Work Unit: sleep=10000
[16:30:24]
[16:30:24] Finished Work Unit:
[16:30:24] - Reading up to 121622496 from "work/wudata_01.trr": Read 121622496
[16:30:28] trr file hash check passed.
[16:30:28] - Reading up to 108853476 from "work/wudata_01.xtc": Read 108853476
[16:30:31] xtc file hash check passed.
[16:30:31] edr file hash check passed.
[16:30:31] logfile size: 220043
[16:30:31] Leaving Run
[16:30:32] - Writing 230869007 bytes of core data to disk...
[16:56:37] Done: 230868495 -> 222498324 (compressed to 3.3 percent)
[17:12:09] ... Done.
[17:12:35] - Shutting down core
[17:12:35]
[17:12:35] Folding@home Core Shutdown: FINISHED_UNIT
[17:12:37] CoreStatus = 64 (100)
[17:12:37] Sending work to server
[17:12:37] Project: 6903 (Run 1, Clone 27, Gen 9)


[17:12:37] + Attempting to send results [April 3 17:12:37 UTC]
[19:12:54] - Couldn't send HTTP request to server
[19:12:54] + Could not connect to Work Server (results)
[19:12:54] (130.237.232.237:8080)
[19:12:54] + Retrying using alternative port

i have crappy slow internet where i am but i wouldnt think that would cause it to not send. also i have just downloaded langouste (per the guide) and it still isnt doing anything


also when i have the -bigadv tag on it sits at this and doesnt download a new wu

[23:40:22] Could not open work queue, generating new queue...
[23:40:22] - Preparing to get new work unit...
[23:40:22] Cleaning up work directory
[23:40:22] + Attempting to get work packet
[23:40:22] Passkey found
[23:40:22] - Connecting to assignment server
[23:40:23] - Successful: assigned to (130.237.232.237).
[23:40:23] + News From Folding@Home: Welcome to Folding@Home
[23:40:23] Loaded queue successfully.
 
and again im having the problem with the machine shutting down randomly. its happening about every 5-10 minutes. ive checked all the power options in both ubuntu and windows and everything is set to off or an extremely long amount of time. it freezes for about 3-5 seconds then restarts. it has done it while running fah while not while downloading stuff. it all seems to be random times. a motherboard is about to be used as a Frisbee.
 
Servers have WU return deadline of 2 hours, regardless of connection activity...:(
 
slider11 said:
also when i have the -bigadv tag on it sits at this and doesnt download a new wu

[23:40:22] Could not open work queue, generating new queue...
[23:40:22] - Preparing to get new work unit...
[23:40:22] Cleaning up work directory
[23:40:22] + Attempting to get work packet
[23:40:22] Passkey found
[23:40:22] - Connecting to assignment server
[23:40:23] - Successful: assigned to (130.237.232.237).
[23:40:23] + News From Folding@Home: Welcome to Folding@Home
[23:40:23] Loaded queue successfully.
Click to expand...

Even with a high speed cable modem, my rigs will sit at this point in the process for varying amounts of time. Minutes even. If you have a crappy connection, how long have you waited at this point before hitting CTRL-C?
 
Takes me a bit under an hour to upload a 6904
 
ok ill just let it sit longer. now about the upload of the finished wu. any ideas why that isnt connecting? also the powering off. it doesnt happen when im in windows only in ubuntu. i can nearly guarantee its not temperatures because i havent seen it go over mid low 30's at load in windows running fah
 
Post a pic of CPUID and CoreTemp while folding in windows.
 
i can tomorrow. it wont be completely accurate though since windows only shows one of my cpu's, i have ubuntu running fah right now seeing if it will stay on and download/send a wu. i havent heard my mobo do it's start up beeps yet but it is 2 rooms away
 
im running the g34 version of the noctua cooler with the higher rpm fans sitting next to a cracked window with outside air temperature of roughly 35-55F depending on what time of day it is so it stays pretty cold in that room plus i have a fan blowing air from the window sill to the computer. in windows idle was 20-22c
 
If you don't give us data we can't make suggestions/help.
 
i understand that and ill be more than happy to get it for yall tomorrow morning. right now its after 4 am though and im ready to put todays computer isues to rest or the mobo might go flying through the air. i dont believe its a hardware issue though either since it hasnt once reset itself or shut down in windows. but ive seen answers all over the place by just googling ubuntu 10.10 randomly shuts down so who knows at this point.
 
Core32 said:
Even with a high speed cable modem, my rigs will sit at this point in the process for varying amounts of time. Minutes even. If you have a crappy connection, how long have you waited at this point before hitting CTRL-C?
Click to expand...

Core32, I'm assuming (a) you're running a linux box and (b) the filesystem is formatted as Ext4. This is a known issue due to additional "safety" features in ext4 and the bizarre way PG chose to wipe files. Either reformat the partition as ext3, or disable "barriers" on your ext4 partition.

H.
 
Haitch said:
Core32, I'm assuming (a) you're running a linux box and (b) the filesystem is formatted as Ext4. This is a known issue due to additional "safety" features in ext4 and the bizarre way PG chose to wipe files. Either reformat the partition as ext3, or disable "barriers" on your ext4 partition.

H.
Click to expand...

No, I definitely believe I'm running ext3, formatted as in the guide.
Just in case however, what's the simplest way to verify that? Do an fdisk -l ?
 
Core32,

Looked at your original post again - you're getting delays downloading not uploading ?

My linux knowledge is stale - but from memory you want to do "cat /etc/fstab"

H.
 
Ok after about 35 minutes a 6903 downloaded and is running. Aswell as the comp is still on. I'm sure once I wake up it will be restarted but as long as I've got the wu downloaded I'm fine with it right now. The wu I've already finished are those points more less gone to the wind since it hasn't sent yet? That I know of atleast
 
Haitch said:
Core32,
Looked at your original post again - you're getting delays downloading not uploading ?
My linux knowledge is stale - but from memory you want to do "cat /etc/fstab"
H.
Click to expand...

The delay I spoke of, related to slider11's delay, is for DL.
With my cable modem it takes about 12 minutes to UL a 6903. I don't think that's too bad.
I'll double check the format type this evening.

 
slider11 said:
so basically if it doesnt send 2 hours after its finished it doesnt count?
Click to expand...
Client will still keep it in the queue and will try to return the WU again but if your connection
can't satisfy "complete-upload-in-2-h-or-less" the return will never succeed...
 
ok thank you for clearing that up. i have to have it uploaded within 2 hours not if it isnt uploaded within 2 hours of completion its useless. that is atleast relieving now if i could get it to stay on long enough to do a fold id be happy
 
slider11 said:
ok thank you for clearing that up. i have to have it uploaded within 2 hours not if it isnt uploaded within 2 hours of completion its useless. that is atleast relieving now if i could get it to stay on long enough to do a fold id be happy
Click to expand...

Nvm, missed tear's post with the same answer
 
ok one last question. when will it try to resend the finished wu? will it be at a random time cause i know ive seen it on my 2700k at random times it will say attempting to send finished wu's no wu's to send or something to that effect or will it try to send both once my current wu is finished

also i believe the shutting down issue is resolved. i had the ecc scrubbing set to good or every 8 hours and since turning that off it hasnt shut down on me or freeze yet... knock on wood
 
Normally the cleint retries every 6-12 hours, if you want to force the issue just shut down teh client and restart it, it will usually wait a couple of minutes to start processing the current WU and the it will try to upload any outstanding units. If that fails shutdown the client again and restart it with the -sendall switch
 
slider11 said:
(...) at random times it will say attempting to send finished wu's no wu's to send or something to that effect or will it try to send both once my current wu is finished
Click to expand...
It's actually both:
(1) autosend gets kicked off every 6 hours and
(2) client additionally tries to return all unsent units at unit completion
 
ok i tryed the send command and it didnt work so i checked the que log and it only had the one i was working on so i think i may have killed it myself when i was killing a non bigadv wu. my loss but who cares at this point. i thought i had fixed the issue with it turning off but aparently i havent so i am gonna download a full blown (larger than 700mb) version of ubuntu and see if that works better. also im gonna do a solo boot so win7 isnt on there possibly hindering or messing with settings
 
This problem seemed to match up with this thread:

I had two 6903s, one on each 4P rig, finish around the same time.
I wasn't in the vacinity but when I looked later I noticed they were both stuck for over an hour in Sending mode.
I shut down both systems, restarted one at a time. The first, when I restarted fah, stated it was trying to send the WU and began to DL and run a 6901 WU.
After a few minutes it gave me the notice the WU had been successfully sent and continued to run the 6901.
Followed the same process with the second rig but get:
+ Attempting to send results...
- Couldn't send HTTP request to server
+ Could not connect to Work Server (results)
(130.237.232.237:8080)
+ Retrying using alternative port
- Couldn't send HTTP request to server
- Could not connect to Work Server (results)
(130.237.232.237:80)
- Error: Could not transmit unit 06 (completed .....) to work server.
Keeping unit 06 in queue.
- Failed to send all units to server
Click to expand...
I get the same stuff if I use the -send all flag as well.
I also tried pinging 130.237.232.237 from this rig and it responds fine.
Any ideas?

Edit: It finally went through after another hour of sweating it out.
I believe there was something up with Stanford at the time.
 
Last edited:
You must log in or register to reply here.
Back
Top