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

Can't send bigadv work unit

DooKey

DooKey

[H]F Junkie
2FA
Joined
Apr 25, 2001
Messages
15,787
I'm pissed. Finished a -bigadv unit and it can't send. Says it can't connect to work server (results). It tried several times then quit and got a new work unit. I'll be really pissed if I don't get my bonus because it won't try again till this new unit is done in 2.4 days. Fracking Stanford.
 
I've noticed the new 6.29 client in windows console tries to auto-send every few hours while it's crunching a WU but always comes up with "no finished WUs to send" and then goes on crunching. Does the Linux client not do that?
 
Not sure. This is the first time my VM wasn't able to send a -bigadv work unit back.
 
That is almost certainly a server problem and at Stanford's end. All you can do is wait.
 
flogge said:
I've noticed the new 6.29 client in windows console tries to auto-send every few hours while it's crunching a WU but always comes up with "no finished WUs to send" and then goes on crunching. Does the Linux client not do that?
Click to expand...

The Linux client does do that. It's actually quite humorous when it does that while in the middle of uploading the work unit the client just finished. I've only seen it happen once and it didn't affect anything luckily.

 
You must log in or register to reply here.
Back
Top