• 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.

Weird F@H error

T

Tormond

[H]ard|DCer of the Month - June 2007
Joined
May 4, 2003
Messages
1,406
Never seen this one before. I have 3 machines that share a network connection (IE I have to move the cable manually between the 3). They all run 2 instances of the F@H console client (C2D e4300) and I recently got this message. I had about 4 days where I had no connectivity so there is no way these have actually "timed out" since the console client is so much easier on things.. Anyway here is the Snip from the log

15:02:38] + Attempting to send results
[15:03:14] - Server does not have record of this unit. Will try again later.
[15:03:14] Could not transmit unit 02 to Collection server; keeping in queue.

Never seen the no record of this unit. Any ideas?
 
Yeah, that's really weird... Can you post the project info (project # and Run/Clone/Gen). I can ask a mod on the FCF to see what is the status of this one.
 
Getting the same error on both the consoles runnning on this one

1st one is Project: 2921 (Run 3, Clone 11, Gen 8)

2nd one is 2921 (Run 2, Clone 11, Gen 9)

Both under my user name
 
I posted on the FCF and I will report back what the mods find out about those WU. I find this very weird unless someone in the Pande group pulled those 2 for a issue between the time you downloaded and the time you uploaded.
 
This is quite normal and happens a lot. It's the collection server that doesn't have a record of the WU, not the work server that the WU came from. Your client wouldn't be trying to upload to the collection server unless there's an issue with the work server. The way it works is the work server issues WUs then at some point delivers the WU info to the collection server. If the work server issues you a WU, then that work server goes down before it delivers the WU info to the collection server, the collection server has no record of it and won't accept it. In this case you'll just have to wait for the work server to come back online.

ChelseaOilman

 
Cool deal. Just never seen the error before. It isn't a big deal that they sit there for a few days just wanted to make sure I didn't have something in the client that was screwed up
 
Interesting definition indeed, especially with hubs being so cheap these days:p

 
The problem isn't hubs it is that if I put another cable near this stuff then the sheer weight of it all is going to drop it thru the floor :) I am just trying to be as floor concious as I can be :)

Seriously tho this is on my test workbench and I am using this as burn in material and adding another switch into the jumble of wires would make things a bit unbearable. As long as I switch the cables every day or so I have no issues :) All Ihave to do is stop and restart the client and it uploads/downloads immediately so I am all good :)

 
Tormond said:
Seriously tho this is on my test workbench and I am using this as burn in material and adding another switch into the jumble of wires would make things a bit unbearable. As long as I switch the cables every day or so I have no issues :) All Ihave to do is stop and restart the client and it uploads/downloads immediately so I am all good :)
Click to expand...

you are right!

that doesn't sound like much of a hassle!

fold on FTW! ;)
 
How many days should we wait if we continue getting this error? I have been trying to upload an errant WU for the better part of the week to no avail. :(
 
You must log in or register to reply here.
Back
Top