Page 1 of 2
Could not authenticate As. Server[Fixed]
Posted: Thu Sep 25, 2014 10:21 am
by artoar_11
I use Client v. 6.41r2 (Core_15) and GTX 460. Several hours I see this:
Code: Select all
[09:49:58] + Attempting to get work packet
[09:49:58] Passkey found
[09:49:58] - Will indicate memory of 8168 MB
[09:49:58] Gpu type=3 species=20.
[09:49:58] - Connecting to assignment server
[09:49:58] Connecting to http://assign-GPU.stanford.edu:8080/
[09:49:59] Posted data.
[09:49:59] Initial: 0000; + Could not authenticate Assignment Server response
[09:49:59] Connecting to http://assign-GPU.stanford.edu:80/
[09:50:00] Posted data.
[09:50:00] Initial: 0000; + Could not authenticate Assignment Server 2 response
[09:50:00] + Couldn't get work instructions.
[09:50:00] - Attempt #13 to get work failed, and no other work to do.
Waiting before retry
Browser shows - OK (
http://assign-GPU.stanford.edu:8080/). Server Status 171.64.65.105 - full / Accepting

Re: Could not authenticate As. Server[171.64.65.105]
Posted: Thu Sep 25, 2014 11:09 am
by bollix47
There have been some reports recently concerning assignment problems ... PG is aware and are looking into these problems. I have notified them of your situation and hopefully it may shed some light. Until they've sorted out what's causing this we will all have to be patient.
Re: Could not authenticate As. Server[171.64.65.105]
Posted: Thu Sep 25, 2014 11:47 am
by artoar_11
Thanks bollix47
Re: Could not authenticate As. Server[171.64.65.105]
Posted: Fri Sep 26, 2014 1:53 am
by jcoffland
@artoar_11, it's very strange that you should see this response. Is this still going on? Do you see this problem with the v7 client? I wonder if anyone else is seeing this.
Re: Could not authenticate As. Server[171.64.65.105]
Posted: Fri Sep 26, 2014 2:05 am
by jcoffland
I am seeing some errors about an invalid version string in the AS logs. I wonder if your version of the client is sending a funny version string. Could you try another client version?
Re: Could not authenticate As. Server[171.64.65.105]
Posted: Fri Sep 26, 2014 6:44 am
by artoar_11
Thanks for the reply jcoffland.
From early spring I use this version. Until yesterday I had no problem.
Around 01:20 h UTC the client received WU
Code: Select all
[00:31:29] + Attempting to get work packet
[00:31:29] Passkey found
[00:31:29] - Will indicate memory of 8168 MB
[00:31:29] Gpu type=3 species=20.
[00:31:29] - Connecting to assignment server
[00:31:29] Connecting to http://assign-GPU.stanford.edu:8080/
[00:31:30] Posted data.
[00:31:30] Initial: 0000; + Could not authenticate Assignment Server response
[00:31:30] Connecting to http://assign-GPU.stanford.edu:80/
[00:31:31] Posted data.
[00:31:31] Initial: 0000; + Could not authenticate Assignment Server 2 response
[00:31:31] + Couldn't get work instructions.
[00:31:31] - Attempt #13 to get work failed, and no other work to do.
Waiting before retry.
[01:19:43] + Attempting to get work packet
[01:19:43] Passkey found
[01:19:43] - Will indicate memory of 8168 MB
[01:19:43] Gpu type=3 species=20.
[01:19:43] - Connecting to assignment server
[01:19:43] Connecting to http://assign-GPU.stanford.edu:8080/
[01:19:44] Posted data.
[01:19:44] Initial: 40AB; - Successful: assigned to (171.64.65.105).
[01:19:44] + News From Folding@Home:
[01:19:44] Loaded queue successfully.
[01:19:44] Gpu type=3 species=20.
[01:19:44] Sent data
[01:19:44] Connecting to http://171.64.65.105:8080/
[01:19:45] Posted data.
[01:19:45] Initial: 0000; - Receiving payload (expected size: 125049)
[01:19:46] - Downloaded at ~122 kB/s
[01:19:46] - Averaged speed for that direction ~122 kB/s
[01:19:46] + Received work.
[01:19:46] + Closed connections
[01:19:46]
[01:19:46] + Processing work unit
[01:19:46] Core required: FahCore_15.exe
[01:19:46] Core found.
[01:19:46] Working on queue slot 01 [September 26 01:19:46 UTC]
[01:19:46] + Working ...
[01:19:46] - Calling '.\FahCore_15.exe -dir work/ -suffix 01 -nice 19 -priority 96 -nocpulock -checkpoint 9 -verbose -lifeline 9256 -version 641'
[01:19:47]
[01:19:47] *------------------------------*
[01:19:47] Folding@Home GPU Core
[01:19:47] Version 2.25 (Wed May 9 17:03:01 EDT 2012)
[01:19:47] Build host AmoebaRemote
[01:19:47] Board Type NVIDIA/CUDA
[01:19:47] Core 15
[01:19:47]
[01:19:47] Window's signal control handler registered.
[01:19:47] Preparing to commence simulation
[01:19:47] - Looking at optimizations...
[01:19:47] DeleteFrameFiles: successfully deleted file=work/wudata_01.ckp
[01:19:47] - Created dyn
[01:19:47] - Files status OK
[01:19:47] sizeof(CORE_PACKET_HDR) = 512 file=<>
[01:19:47] - Expanded 124537 -> 503186 (decompressed 404.0 percent)
[01:19:47] Called DecompressByteArray: compressed_data_size=124537 data_size=503186, decompressed_data_size=503186 diff=0
[01:19:47] - Digital signature verified
[01:19:47]
[01:19:47] Project: 7627 (Run 524, Clone 0, Gen 24)
[01:19:47]
[01:19:47] Assembly optimizations on if available.
[01:19:47] Entering M.D.
[01:19:49] Tpr hash work/wudata_01.tpr: 2495259464 1268715863 3225480518 461630425 319247774
[01:19:49] GPU device id=0
[01:19:49] Working on Protein
[01:19:49] Client config found, loading data.
[01:19:49] Starting GUI Server
[01:20:56] Setting checkpoint frequency: 400000
[01:20:56] Completed 3 out of 40000000 steps (0%).
[01:29:51] Completed 400000 out of 40000000 steps (1%).
[01:38:48] Completed 800000 out of 40000000 steps (2%).
jcoffland wrote:I am seeing some errors about an invalid version string in the AS logs. I wonder if your version of the client is sending a funny version string. Could you try another client version?
I went back to the old client because some new projects with Core_17, GTX 460 completed for 50+ hours.
Re: Could not authenticate As. Server[171.64.65.105]
Posted: Tue Sep 30, 2014 8:09 am
by artoar_11
Today I have the same problem again. I guess it's related to "The new AS is back in action" (my opinion).
Code: Select all
[07:08:29] Completed 39600000 out of 40000000 steps (99%).
[07:17:17] Completed 40000000 out of 40000000 steps (100%).
[07:17:18] Finished fah_main status=0
[07:17:18] Successful run
[07:17:18] DynamicWrapper: Finished Work Unit: sleep=10000
[07:17:28] Reserved 763120 bytes for xtc file; Cosm status=0
[07:17:28] Allocated 763120 bytes for xtc file
[07:17:28] - Reading up to 763120 from "work/wudata_04.xtc": Read 763120
[07:17:28] Read 763120 bytes from xtc file; available packet space=785667344
[07:17:28] xtc file hash check passed.
[07:17:28] Reserved 47688 47688 785667344 bytes for arc file=<work/wudata_04.trr> Cosm status=0
[07:17:28] Allocated 47688 bytes for arc file
[07:17:28] - Reading up to 47688 from "work/wudata_04.trr": Read 47688
[07:17:28] Read 47688 bytes from arc file; available packet space=785619656
[07:17:28] trr file hash check passed.
[07:17:28] Allocated 544 bytes for edr file
[07:17:28] Read bedfile
[07:17:28] edr file hash check passed.
[07:17:28] Allocated 36670 bytes for logfile
[07:17:28] Read logfile
[07:17:28] GuardedRun: success in DynamicWrapper
[07:17:28] GuardedRun: done
[07:17:28] Run: GuardedRun completed.
[07:17:32] + Opened results file
[07:17:32] - Writing 848534 bytes of core data to disk...
[07:17:32] Done: 848022 -> 819851 (compressed to 96.6 percent)
[07:17:32] ... Done.
[07:17:32] DeleteFrameFiles: successfully deleted file=work/wudata_04.ckp
[07:17:33] Shutting down core
[07:17:33]
[07:17:33] Folding@home Core Shutdown: FINISHED_UNIT
[07:17:37] CoreStatus = 64 (100)
[07:17:37] Unit 4 finished with 99 percent of time to deadline remaining.
[07:17:37] Updated performance fraction: 0.978230
[07:17:37] Sending work to server
[07:17:37] Project: 7620 (Run 594, Clone 0, Gen 227)
[07:17:37] + Attempting to send results [September 30 07:17:37 UTC]
[07:17:37] - Reading file work/wuresults_04.dat from core
[07:17:37] (Read 820363 bytes from disk)
[07:17:37] Gpu type=3 species=20.
[07:17:37] Connecting to http://171.64.65.105:8080/
[07:17:39] Posted data.
[07:17:39] Initial: 0000; - Uploaded at ~401 kB/s
[07:17:39] - Averaged speed for that direction ~334 kB/s
[07:17:39] + Results successfully sent
[07:17:39] Thank you for your contribution to Folding@Home.
[07:17:39] + Number of Units Completed: 253
[07:17:44] Trying to send all finished work units
[07:17:44] + No unsent completed units remaining.
[07:17:44] - Preparing to get new work unit...
[07:17:44] Cleaning up work directory
[07:17:44] + Attempting to get work packet
[07:17:44] Passkey found
[07:17:44] - Will indicate memory of 8168 MB
[07:17:44] Gpu type=3 species=20.
[07:17:44] - Connecting to assignment server
[07:17:44] Connecting to http://assign-GPU.stanford.edu:8080/
[07:17:44] Posted data.
[07:17:44] Initial: 0000; + Could not authenticate Assignment Server response
[07:17:44] Connecting to http://assign-GPU.stanford.edu:80/
[07:17:45] Posted data.
[07:17:45] Initial: 0000; + Could not authenticate Assignment Server 2 response
[07:17:45] + Couldn't get work instructions.
[07:17:45] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
Code: Select all
[08:01:51] + Attempting to get work packet
[08:01:51] Passkey found
[08:01:51] - Will indicate memory of 8168 MB
[08:01:51] Gpu type=3 species=20.
[08:01:51] - Connecting to assignment server
[08:01:51] Connecting to http://assign-GPU.stanford.edu:8080/
[08:01:52] Posted data.
[08:01:52] Initial: 0000; + Could not authenticate Assignment Server response
[08:01:52] Connecting to http://assign-GPU.stanford.edu:80/
[08:01:53] Posted data.
[08:01:53] Initial: 0000; + Could not authenticate Assignment Server 2 response
[08:01:53] + Couldn't get work instructions.
[08:01:53] - Attempt #10 to get work failed, and no other work to do.
Waiting before retry.
Re: Could not authenticate As. Server[171.64.65.105]
Posted: Tue Sep 30, 2014 2:59 pm
by bruce
artoar_11 wrote:Today I have the same problem again. I guess it's related to "The new AS is back in action" (my opinion).
Maybe. Maybe not. You were asked to try a newer version of the client and you didn't respond.
Please confirm which version of FAHClient you're running. If the client version that you're running is too old to be supported, you must move to a newer version. If it's a supported version, then the AS will need to be patched to support that version.
Re: Could not authenticate As. Server[171.64.65.105]
Posted: Tue Sep 30, 2014 4:18 pm
by Gary480six
Reporting the same problem as the OP - could not authenticate server. This is the same behavior I saw when the new beta server was online last Thursday.
As you can see, it is the same, older client. Also, it is the same GTX460 video card.
Code: Select all
# Windows GPU Systray Edition #################################################
###############################################################################
Folding@Home Client Version 6.41r2
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: C:\Users\rob\AppData\Roaming\Folding@home-gpu
[15:32:32] - Ask before connecting: No
[15:32:32] - User name: Gary480six (Team 11108)
[15:32:32] - User ID: xxxxxxxxxxx
[15:32:32] - Machine ID: 2
[15:32:32]
[15:32:32] Gpu type=3 species=21.
[15:32:32] Loaded queue successfully.
[15:32:32] Initialization complete
[15:32:32] - Preparing to get new work unit...
[15:32:32] Cleaning up work directory
[15:32:32] + Attempting to get work packet
[15:32:32] Passkey found
[15:32:32] Gpu type=3 species=21.
[15:32:32] - Connecting to assignment server
[15:32:40] + Could not authenticate Assignment Server response
[15:32:40] + Could not authenticate Assignment Server 2 response
[15:32:40] + Couldn't get work instructions.
[15:32:40] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
This PC is at a remote location - so I am not able to try a newer client. When the beta assignment server was shut off Saturday, this PC was able to get work again.
I'm not asking for a 'fix' - just reporting the issue so Stanford has all the information.
Re: Could not authenticate As. Server[171.64.65.105]
Posted: Tue Sep 30, 2014 4:43 pm
by artoar_11
bruce wrote:artoar_11 wrote:Today I have the same problem again. I guess it's related to "The new AS is back in action" (my opinion).
Maybe. Maybe not. You were asked to try a newer version of the client and you didn't respond.
Please confirm which version of FAHClient you're running. If the client version that you're running is too old to be supported, you must move to a newer version. If it's a supported version, then the AS will need to be patched to support that version.
artoar_11 wrote:I use Client v. 6.41r2 (Core_15) and GTX 460.
Today I returned to client v.7.2.9. This works for me. With this client and this video card I have participated in internal tests Core_17. Without any problems.
Code: Select all
*********************** Log Started 2014-09-30T08:37:38Z ***********************
08:37:38:************************* Folding@home Client *************************
08:37:38: Website: http://folding.stanford.edu/
08:37:38: Copyright: (c) 2009-2012 Stanford University
08:37:38: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
08:37:38: Args: --lifeline 6408 --command-port=36330
08:37:38: Config: C:/Users/user/AppData/Roaming/FAHClient/config.xml
08:37:38:******************************** Build ********************************
08:37:38: Version: 7.2.9
08:37:38: Date: Oct 3 2012
08:37:38: Time: 18:05:48
08:37:38: SVN Rev: 3578
08:37:38: Branch: fah/trunk/client
08:37:38: Compiler: Intel(R) C++ MSVC 1500 mode 1200
08:37:38: Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
08:37:38: /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
08:37:38: Platform: win32 XP
08:37:38: Bits: 32
08:37:38: Mode: Release
08:37:38:******************************* System ********************************
08:37:38: CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
08:37:38: CPU ID: GenuineIntel Family 6 Model 42 Stepping 7
08:37:38: CPUs: 4
08:37:38: Memory: 7.98GiB
08:37:38: Free Memory: 5.54GiB
08:37:38: Threads: WINDOWS_THREADS
08:37:38: On Battery: false
08:37:38: UTC offset: 3
08:37:38: PID: 7076
08:37:38: CWD: C:/Users/user/AppData/Roaming/FAHClient
08:37:38: OS: Windows 7 Professional
08:37:38: OS Arch: AMD64
08:37:38: GPUs: 1
08:37:38: GPU 0: NVIDIA:2 GF104 [GeForce GTX 460]
08:37:38: CUDA: 2.1
08:37:38: CUDA Driver: 5000
08:37:38:Win32 Service: false
08:37:38:***********************************************************************
08:37:38:<config>
08:37:38: <!-- FahCore Control -->
08:37:38: <checkpoint v='9'/>
08:37:38:
08:37:38: <!-- Folding Slot Configuration -->
08:37:38: <gpu v='true'/>
08:37:38:
08:37:38: <!-- Network -->
08:37:38: <proxy v=':8080'/>
08:37:38:
08:37:38: <!-- User Information -->
08:37:38: <passkey v='********************************'/>
08:37:38: <team v='224497'/>
08:37:38: <user v='artoar_home'/>
08:37:38:
08:37:38: <!-- Folding Slots -->
08:37:38: <slot id='0' type='GPU'>
08:37:38: <client-type v='beta'/>
08:37:38: <core-priority v='low'/>
08:37:38: <max-packet-size v='normal'/>
08:37:38: <next-unit-percentage v='100'/>
08:37:38: <pause-on-start v='false'/>
08:37:38: </slot>
08:37:38: <slot id='1' type='SMP'>
08:37:38: <client-type v='beta'/>
08:37:38: <core-priority v='low'/>
08:37:38: <cpus v='-1'/>
08:37:38: <max-packet-size v='normal'/>
08:37:38: <next-unit-percentage v='100'/>
08:37:38: <pause-on-start v='true'/>
08:37:38: </slot>
08:37:38:</config>
08:37:38:Trying to access database...
08:37:38:Successfully acquired database lock
08:37:38:Enabled folding slot 00: READY gpu:0:"GF104 [GeForce GTX 460]"
08:37:38:Enabled folding slot 01: PAUSED smp:4
08:37:38:WU00:FS00:Downloading project 7624 description
08:37:38:WU00:FS00:Connecting to fah-web.stanford.edu:80
08:37:41:Server connection id=1 on 0.0.0.0:36330 from 127.0.0.1
08:37:50:WU00:FS00:Project 7624 description downloaded successfully
08:37:50:WU00:FS00:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/beta/Core_15.fah
08:37:50:WU00:FS00:Connecting to web.stanford.edu:80
08:37:50:WU00:FS00:FahCore 15: Downloading 1.88MiB
08:37:56:WU00:FS00:FahCore 15: 76.64%
08:37:57:WU00:FS00:FahCore 15: Download complete
08:37:57:WU00:FS00:Valid core signature
08:37:57:WU00:FS00:Unpacked 7.71MiB to cores/web.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/beta/Core_15.fah/FahCore_15.exe
08:37:57:WU00:FS00:Starting
08:37:57:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/user/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/beta/Core_15.fah/FahCore_15.exe -dir 00 -suffix 01 -version 702 -lifeline 7076 -checkpoint 9 -gpu 0
08:37:57:WU00:FS00:Started FahCore on PID 6984
08:37:57:WU00:FS00:Core PID:3328
08:37:57:WU00:FS00:FahCore 0x15 started
08:37:58:WU00:FS00:0x15:
08:37:58:WU00:FS00:0x15:*------------------------------*
08:37:58:WU00:FS00:0x15:Folding@Home GPU Core
08:37:58:WU00:FS00:0x15:Version 2.25 (Wed May 9 17:03:01 EDT 2012)
08:37:58:WU00:FS00:0x15:Build host AmoebaRemote
08:37:58:WU00:FS00:0x15:Board Type NVIDIA/CUDA
08:37:58:WU00:FS00:0x15:Core 15
08:37:58:WU00:FS00:0x15:
08:37:58:WU00:FS00:0x15:Window's signal control handler registered.
08:37:58:WU00:FS00:0x15:Preparing to commence simulation
08:37:58:WU00:FS00:0x15:- Looking at optimizations...
08:37:58:WU00:FS00:0x15:DeleteFrameFiles: successfully deleted file=00/wudata_01.ckp
08:37:58:WU00:FS00:0x15:- Created dyn
08:37:58:WU00:FS00:0x15:- Files status OK
08:37:58:WU00:FS00:0x15:sizeof(CORE_PACKET_HDR) = 512 file=<>
08:37:58:WU00:FS00:0x15:- Expanded 127227 -> 507182 (decompressed 398.6 percent)
08:37:58:WU00:FS00:0x15:Called DecompressByteArray: compressed_data_size=127227 data_size=507182, decompressed_data_size=507182 diff=0
08:37:58:WU00:FS00:0x15:- Digital signature verified
08:37:58:WU00:FS00:0x15:
08:37:58:WU00:FS00:0x15:Project: 7624 (Run 35, Clone 0, Gen 409)
08:37:58:WU00:FS00:0x15:
08:37:58:WU00:FS00:0x15:Assembly optimizations on if available.
08:37:58:WU00:FS00:0x15:Entering M.D.
08:38:00:WU00:FS00:0x15:Tpr hash 00/wudata_01.tpr: 453264078 3375116050 30715838 2044282433 1516879561
08:38:00:WU00:FS00:0x15:GPU device id=0
08:38:00:WU00:FS00:0x15:Working on Protein
08:38:00:WU00:FS00:0x15:Client config unavailable.
08:38:00:WU00:FS00:0x15:Starting GUI Server
08:39:05:WU00:FS00:0x15:Setting checkpoint frequency: 400000
08:39:05:WU00:FS00:0x15:Completed 3 out of 40000000 steps (0%).
08:48:03:WU00:FS00:0x15:Completed 400000 out of 40000000 steps (1%).
08:57:01:WU00:FS00:0x15:Completed 800000 out of 40000000 steps (2%).
09:05:58:WU00:FS00:0x15:Completed 1200000 out of 40000000 steps (3%).
Re: Could not authenticate As. Server[171.64.65.105]
Posted: Thu Oct 02, 2014 2:55 am
by Gary480six
I'm still finding that my 'located in another state' GTX 460 Folding system is not getting work - and kicking back this error message:
Code: Select all
[00:49:51] + Attempting to get work packet
[00:49:51] Passkey found
[00:49:51] Gpu type=3 species=21.
[00:49:51] - Connecting to assignment server
[00:49:52] + Could not authenticate Assignment Server response
[00:49:52] + Could not authenticate Assignment Server 2 response
[00:49:52] + Couldn't get work instructions.
[00:49:52] - Attempt #32 to get work failed, and no other work to do.
Waiting before retry.
It seems to be because it is using the version 6.41r2 client.
So, I set up a local experiment. I took some old hardware and built a new Folding system.
Intel DP55WB motherboard with an i7-860 CPU
4GB DDR3 memory
Windows 7 32-bit
EVGA GTX 650 video card with cleanly installed 327.23 drivers
I installed the GPU client 6.41r2 directly from the Stanford website....
Same exact error message:
Could not authenticate Assignment Server response
Could not authenticate Assignment Server 2 response
This is not a network problem, an ISP issue or something else you can blame on me.
The fact is that the new Assignment Sever code is blocking access to the work servers from PCs running the last version 6 GPU client.
If the version 6 client is now retired, that's fine - IF YOU ANNOUNCE IT.
If you are still working on getting the Assignment Servers to work with the version 6 client, that's fine - IF YOU ANNOUNCE IT.
Time and time again you leave your hard working VOLUNTEERS in the dark about things that affect us all directly.
I've been cranking out work units for the Folding @ Home program for more than Ten Years.. and frankly, I deserve more RESPECT.
Re: Could not authenticate As. Server[171.64.65.105]
Posted: Thu Oct 02, 2014 6:46 am
by artoar_11
Gary480six wrote:
................
EVGA GTX 650 video card with cleanly installed 327.23 drivers
I installed the GPU client 6.41r2 directly from the Stanford website....
Same exact error message:
Could not authenticate Assignment Server response
Could not authenticate Assignment Server 2 response
.......................
I've been cranking out work units for the Folding @ Home program for more than Ten Years.. and frankly, I deserve more RESPECT.
Fermi graphics cards (400/500 series) can work on the client 6.41r2 and client v.7. Kepler (600 and newer) work on client v.7.
I have a GTX 650Ti. From experience I know that does not work on client 6.41r2.
Have a nice day, and patience
Re: Could not authenticate As. Server[171.64.65.105]
Posted: Thu Oct 02, 2014 7:12 am
by Sn1ken
Gary480six wrote:I'm still finding that my 'located in another state' GTX 460 Folding system is not getting work - and kicking back this error message:
It seems to be because it is using the version 6.41r2 client.
The fact is that the new Assignment Sever code is blocking access to the work servers from PCs running the last version 6 GPU client.
If the version 6 client is now retired, that's fine - IF YOU ANNOUNCE IT.
If you are still working on getting the Assignment Servers to work with the version 6 client, that's fine - IF YOU ANNOUNCE IT.
Time and time again you leave your hard working VOLUNTEERS in the dark about things that affect us all directly.
I've been cranking out work units for the Folding @ Home program for more than Ten Years.. and frankly, I deserve more RESPECT.
Not to be rude, but this problems are related to work on AS server. But they have announced it. viewtopic.php?f=24&t=26794
But they have also clarified the unknown symptoms alongside this work.
In other words, they need our feedback, but it has to be clinical. Show your log, state your hardware and so on. Then it would be easier for everyone who actually wants to help.
Sorry if I am acting rude. I do not mean for it that way. I understand your frustration, but on the other side. I really hope they manage to fix the new AS server for the better for everyone.
Re: Could not authenticate As. Server[171.64.65.105]
Posted: Thu Oct 02, 2014 12:35 pm
by sco01
new AS server for the better for everyone.
all 6 clients no longer get a job, and it's not announced on the forum silence..
7.4.4 clients at NV get 3 day only job 15 core (gtx780 - 31ะบ ppd instead of 180-200k ppd on 17 core) and again silence...
PG just don't care about us now - hence the silence
Re: Could not authenticate As. Server[171.64.65.105]
Posted: Thu Oct 02, 2014 1:03 pm
by jason403
You realize points are worth nothing right? They are just a fun way of keeping score. The goal for us is to complete work units so we contribute to scientific research.