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

Blah @ Stanford Servers

T

Tobit

[H]ard|DCer of the Month - March 2010/May 2011
Joined
Dec 12, 2005
Messages
5,145
Ya know, I thought Stanford resolved these types of server problems a long time ago. Just finished my first WU since deciding to return to folding and I'm unable to upload the results.

Reported the problem on FF - Server is showing Full operation status meaning it should be available. However, it is in Reject mode so something is wrong. :rolleyes:

Code: 
[12:59:05] Project: 3861 (Run 199, Clone 12, Gen 19)
[12:59:05] + Attempting to send results [October 15 12:59:05 UTC]
[12:59:06] - Couldn't send HTTP request to server
[12:59:06] + Could not connect to Work Server (results)
[12:59:06]     (128.143.48.226:8080)
[12:59:06] + Retrying using alternative port
[12:59:07] - Couldn't send HTTP request to server
[12:59:07] + Could not connect to Work Server (results)
[12:59:07]     (128.143.48.226:80)
[12:59:07] - Error: Could not transmit unit 01 (completed October 15) to work server.


[12:59:07] + Attempting to send results [October 15 12:59:07 UTC]
[12:59:08] - Server does not have record of this unit. Will try again later.
[12:59:08]   Could not transmit unit 01 to Collection server; keeping in queue.
[12:59:08] - Preparing to get new work unit...
 
It still happens, just less often.

Unless your running the ultra-big work-units that get a bonus for a quick turn around or running close to the final deadline then upload time, within a 3-6 hours window, is not critical.
Your points update just gets delayed.
I see this type of glitch a couple of times a month with the GPU client.

Its when you cannot download any new work.
That glitch is critical as your PpD tanks.
This type of glitch is alot rarer now and tends to be much shorter lived.
Gone are the days when your boxen would sit idle from friday nights to monday morning because a server was down, touches wood.

Luck ............. :D
 
Tigerbiten said:
It still happens, just less often.

Unless your running the ultra-big work-units that get a bonus for a quick turn around or running close to the final deadline then upload time, within a 3-6 hours window, is not critical.
Your points update just gets delayed.
I see this type of glitch a couple of times a month with the GPU client.

Its when you cannot download any new work.
That glitch is critical as your PpD tanks.
This type of glitch is alot rarer now and tends to be much shorter lived.
Gone are the days when your boxen would sit idle from friday nights to monday morning because a server was down, touches wood.

Luck ............. :D
Click to expand...

Which is why IMHO the BOINC client is completely vastly superior because its as stable as the single core console client, it can queue work units, and queue completed units. (up to 10 days worth just in case you lose internet or the projects work server goes down). If Stanford used BOINC i'd be a very, very happy man.
 
Shlomo said:
Which is why IMHO the BOINC client is completely vastly superior because its as stable as the single core console client, it can queue work units, and queue completed units. (up to 10 days worth just in case you lose internet or the projects work server goes down). If Stanford used BOINC i'd be a very, very happy man.
Click to expand...
For some projects in the past Stanford had queued WUs in case of server problems or user-end glitches. IIRC, there is a reason why queuing WUs cannot be done at present. As often as there are server problems, if queuing WUs could be done without compromising the project in some way, I think Stanford would implement it in the current clients.
 
Ive been down all day...... 5 systems and not one of them can connect to the Standford servers to get new WU's or report finished ones, and thats in two entirely different local's.
 
My problems with 128.143.48.226 have apparently been resolved, my first WU in a few months has finally been submitted. Bring on the pernts update!
 
I have a couple single core clients that , of late, have been having a hard time getting new work units .. 17 tries or more .. fortunately , they don't bring in a whole lot of PPD in of themselves, but still ..
 
well, I seem to be back on, all 5 of my ssystems are working on WU's now.
 
ThreeDee said:
I have a couple single core clients that , of late, have been having a hard time getting new work units .. 17 tries or more .. fortunately , they don't bring in a whole lot of PPD in of themselves, but still ..
Click to expand...
I run 'redundant' single-core clients on my machines. Meaning, more than one client per core. That way, I almost never see under 100% CPU utilization because if one client is idle for some reason, there will always be other clients to pick up the slack.
 
You must log in or register to reply here.
Back
Top