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

Servers Down?

carlbme

carlbme

[H]ard|Gawd
2FA
Joined
Aug 17, 2001
Messages
1,263
Is anyone else having issues getting new WUs?
I first noticed that my GPUs had stopped folding and am getting errors, and no my CPU has stopped and is getting the same errors when trying to get new work.

Code: 
13:54:29:WARNING:WU00:FS02:Failed to get ID from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: No connection could be made because the target machine actively refused it.
13:54:34:WARNING:WU01:FS00:Failed to get ID from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: No connection could be made because the target machine actively refused it.
13:54:34:WARNING:WU02:FS01:Failed to get ID from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: No connection could be made because the target machine actively refused it.
13:54:50:WARNING:WU00:FS02:Failed to get ID from 'assign-GPU.stanford.edu:8080': Failed to connect to assign-GPU.stanford.edu:8080: No connection could be made because the target machine actively refused it.
13:54:50:ERROR:WU00:FS02:Exception: Could not get an assignment ID
13:54:55:WARNING:WU01:FS00:Failed to get ID from 'assign-GPU.stanford.edu:8080': Failed to connect to assign-GPU.stanford.edu:8080: No connection could be made because the target machine actively refused it.
13:54:55:ERROR:WU01:FS00:Exception: Could not get an assignment ID
13:54:55:WARNING:WU02:FS01:Failed to get ID from 'assign-GPU.stanford.edu:8080': Failed to connect to assign-GPU.stanford.edu:8080: No connection could be made because the target machine actively refused it.
13:54:55:ERROR:WU02:FS01:Exception: Could not get an assignment ID
 
Yes they are, stats and GPU assignment server both. No news on eta for them being back up yet.
 
I had a feeling that something was wrong when I noticed that my computer got quiet.
 
OK, good. Glad it isn't just me then.
I was wearing my headphones and noticed it when I started getting colder.
I have my system running right next to my shoulder and the GTX690 puts out a lot of heat.
 
GPU WU's are back up. Restart your machine to reset that stupid timer that keeps going higher after each failed retry.
 
Liger88 said:
GPU WU's are back up. Restart your machine to reset that stupid timer that keeps going higher after each failed retry.
Click to expand...
I'm at work behind a restrictive firewall so I can't remote home. My rigs are going to be idle for a few more hours
 
jebo_4jc said:
I'm at work behind a restrictive firewall so I can't remote home. My rigs are going to be idle for a few more hours
Click to expand...



That sucks. :(

It's one of the things I don't understand that drives me nuts. It isn't that the servers go down more frequently than they should, or flat out run of WU's because there has only been one main project. It's the fact the timer keeps going up and isn't consistent like 30 minutes. It totally screws up the stability of many peoples systems having to constantly restart every few hours. The programmers need to fix that crap because after 3-4 times going down in the past week I'm personally getting sick of restarting every few hours. Feels like I'm back on Windows 98 for an unnecessary reason.
 
Liger88 said:
That sucks. :(

It's one of the things I don't understand that drives me nuts. It isn't that the servers go down more frequently than they should, or flat out run of WU's because there has only been one main project. It's the fact the timer keeps going up and isn't consistent like 30 minutes. It totally screws up the stability of many peoples systems having to constantly restart every few hours. The programmers need to fix that crap because after 3-4 times going down in the past week I'm personally getting sick of restarting every few hours. Feels like I'm back on Windows 98 for an unnecessary reason.
Click to expand...

For me, at least, pausing and restarting the slots resets the retry timer. I didn't need to reboot the whole machine.

I think the increase of time between requests is in large part to not overload work servers that have just come back online. At first, a lack of response could be a temporary glitch, so it still tries every 15 seconds or so, and hits up other work servers during that time. After a few attempts, however, it's reasonable to assume that the server(s) in question are down, and the longer they're down, the more clients there are waiting for new work. Several thousand slots requesting work within the same minute would probably crash it, so they have the requests spaced out.

Going to 4+ hours between requests seems excessive, though. It seems to me like capping it at half an hour would provide enough breathing room while still checking often enough to not waste too much time after the server's back up.
 
Looks like Stanford is getting ready for the weekend..... again. It blows me away that they can not keep their shit running. A junior level CS student knows how to setup multiple servers for redundancy.
 
Looks like is was deliberate, not a failure.

"We’ve been doing work on the FAH backend servers. We had to take the stats down for a bit longer than we liked. They’re back up now. Sorry for the delay in getting those points recorded."

My guess is all the issues with the servers are related to this
 
You must log in or register to reply here.
Back
Top