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.
I seem to have a bunch of computers that have been looking for work. mostly console clients, but even a couple of SMP's have had trouble finding new WU's to process. Is anyone else seeing this as well, or did Evil hack my boxen to keep me from nipping at his heals again?
The SMP client I have on this machine finished a unit roughly 9 hours ago. It took 6 hours to get a new one, and the log appears as if the results for the last one haven't been able to send.
I had one of two regular console clients on my Pentium D at work that took about 6-8 hours to get a work unit yesterday morning. The second client took 12-14 hours to grab a work unit. I would have threatened it with imminent death via ESD but since it's my work system I don't own it and would get in trouble for killing it.
I tried that with several of mine this morning, but its been hit or miss. Only a few of them picked work back up, the rest just kept trying without success.
I had a couple of SMP's as well that couldn't be uploaded and also boxen that couldn't pick up new work. The Fahmon fahinfo indicated the server was ok....
After finally grabbing a couple work units and processing one of them, I have a client on my Pentium D that can't get work again. It keeps getting pointed at 171.64.122.78. Could someone do a check on Stanford's page to see the server status for that server? I can't access Stanford's page from here at work as the webfilter blocks it.
Weekends seem to be notorious for the "looking for work" issue. This was especially true of the single core client. It's an occassional issue with the SMP client.
Hmmm mine have been getting work okay but have been having problems sending work. On the diskless box log it looks like it finally uploaded on the one instance but gave me the below error in red. Does this mean I did not get credit for the work? It also did not give the regular "thank you for your contribution" message.
[01:06:04] - Autosending finished units...
[01:06:04] Trying to send all finished work units
[01:06:04] + Attempting to send results
[01:06:04] - Reading file work/wuresults_02.dat from core
[01:06:04] (Read 1826323 bytes from disk)
[01:06:04] Connecting to http://171.64.65.63:8080/
[01:09:13] - Couldn't send HTTP request to server
[01:09:13] + Could not connect to Work Server (results)
[01:09:13] (171.64.65.63:8080)
[01:09:13] - Error: Could not transmit unit 02 (completed May 20) to work server.
[01:09:13] - 6 failed uploads of this unit.
[01:09:13] + Attempting to send results
[01:09:13] - Reading file work/wuresults_02.dat from core
[01:09:13] (Read 1826323 bytes from disk)
[01:09:13] Connecting to http://171.64.122.76:8080/
[01:09:43] Posted data.
[01:09:43] Initial: 0000; - Uploaded at ~59 kB/s
[01:09:43] - Averaged speed for that direction ~58 kB/s [01:09:43] - Core type used on unit not what server demands.
[01:09:43] Successfully sent unit 02 to Collection server.
[01:09:43] + Sent 1 of 1 completed units to the server
[01:09:43] - Autosend completed
This server was down or not accepting completed WU for a few days. It finally came back up late yesterday. Both my SMPs were pointing to it. I had several WU waiting to be posted, but couldn't till last night.