Page 1 of 2
WS 171.67.108.31 is in Reject mode
Posted: Sun Mar 23, 2014 8:05 am
by Nicolas_orleans
P9401 work server 171.67.108.31 is in Reject mode, WUs are right now returned to Collection server instead (it works and WUs are credited)
Server status page confirms the Reject mode for 171.67.108.31.
Client log
Code: Select all
18:43:53:WU01:FS02:0x17:Folding@home Core Shutdown: FINISHED_UNIT
18:43:53:WU01:FS02:FahCore returned: FINISHED_UNIT (100 = 0x64)
18:43:53:WU01:FS02:Sending unit results: id:01 state:SEND error:NO_ERROR project:9401 run:951 clone:2 gen:4 core:0x17 unit:0x000000086652edaf53289c2049979f6f
18:43:53:WU01:FS02:Uploading 20.69MiB to 171.67.108.31
18:43:53:WU01:FS02:Connecting to 171.67.108.31:8080
18:43:53:WARNING:WU01:FS02:WorkServer connection failed on port 8080 trying 80
18:43:53:WU01:FS02:Connecting to 171.67.108.31:80
18:43:54:WARNING:WU01:FS02:Exception: Failed to send results to work server: Failed to connect to 171.67.108.31:80: Connection refused
18:43:54:WU01:FS02:Trying to send results to collection server
18:43:54:WU01:FS02:Uploading 20.69MiB to 171.65.103.160
18:43:54:WU01:FS02:Connecting to 171.65.103.160:8080
18:44:00:WU01:FS02:Upload 3.02%
18:44:07:WU01:FS02:Upload 5.74%
18:44:13:WU01:FS02:Upload 8.16%
18:44:19:WU01:FS02:Upload 10.57%
18:44:25:WU01:FS02:Upload 12.99%
18:44:31:WU01:FS02:Upload 15.41%
18:44:38:WU01:FS02:Upload 17.52%
18:44:45:WU01:FS02:Upload 20.54%
18:44:51:WU01:FS02:Upload 22.96%
18:44:57:WU01:FS02:Upload 25.38%
18:45:03:WU01:FS02:Upload 27.79%
18:45:09:WU01:FS02:Upload 29.91%
18:45:16:WU01:FS02:Upload 32.33%
18:45:22:WU01:FS02:Upload 34.74%
18:45:28:WU01:FS02:Upload 37.16%
18:45:34:WU01:FS02:Upload 39.58%
18:45:40:WU01:FS02:Upload 41.99%
18:45:47:WU01:FS02:Upload 44.11%
18:45:54:WU01:FS02:Upload 47.43%
18:46:01:WU01:FS02:Upload 49.85%
18:46:08:WU01:FS02:Upload 52.87%
18:46:14:WU01:FS02:Upload 54.99%
18:46:20:WU01:FS02:Upload 57.40%
18:46:26:WU01:FS02:Upload 59.82%
18:46:33:WU01:FS02:Upload 62.24%
18:46:40:WU01:FS02:Upload 65.26%
18:46:46:WU01:FS02:Upload 67.37%
18:46:53:WU01:FS02:Upload 70.09%
18:46:59:WU01:FS02:Upload 72.51%
18:47:05:WU01:FS02:Upload 74.93%
18:47:11:WU01:FS02:Upload 77.04%
18:47:17:WU01:FS02:Upload 79.46%
18:47:23:WU01:FS02:Upload 81.87%
18:47:29:WU01:FS02:Upload 84.29%
18:47:35:WU01:FS02:Upload 86.41%
18:47:41:WU01:FS02:Upload 88.82%
18:47:47:WU01:FS02:Upload 91.24%
18:47:53:WU01:FS02:Upload 93.66%
18:48:00:WU01:FS02:Upload 96.07%
18:48:06:WU01:FS02:Upload 98.49%
18:48:13:WU01:FS02:Upload complete
18:48:13:WU01:FS02:Server responded WORK_ACK (400)
18:48:13:WU01:FS02:Final credit estimate, 54853.00 points
18:48:13:WU01:FS02:Cleaning up
client headers
Code: Select all
*********************** Log Started 2014-03-22T10:19:21Z ***********************
10:19:21:************************* Folding@home Client *************************
10:19:21: Website: http://folding.stanford.edu/
10:19:21: Copyright: (c) 2009-2013 Stanford University
10:19:21: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
10:19:21: Args: --child --lifeline 964 /etc/fahclient/config.xml --run-as fahclient
10:19:21: --pid-file=/var/run/fahclient.pid --daemon
10:19:21: Config: /etc/fahclient/config.xml
10:19:21:******************************** Build ********************************
10:19:21: Version: 7.3.6
10:19:21: Date: Feb 18 2013
10:19:21: Time: 07:24:08
10:19:21: SVN Rev: 3923
10:19:21: Branch: fah/trunk/client
10:19:21: Compiler: GNU 4.4.7
10:19:21: Options: -std=gnu++98 -O3 -funroll-loops -mfpmath=sse -ffast-math
10:19:21: -fno-unsafe-math-optimizations -msse2
10:19:21: Platform: linux2 3.2.0-1-amd64
10:19:21: Bits: 64
10:19:21: Mode: Release
10:19:21:******************************* System ********************************
10:19:21: CPU: Intel(R) Celeron(R) CPU G1610 @ 2.60GHz
10:19:21: CPU ID: GenuineIntel Family 6 Model 58 Stepping 9
10:19:21: CPUs: 2
10:19:21: Memory: 3.81GiB
10:19:21:Free Memory: 3.39GiB
10:19:21: Threads: POSIX_THREADS
10:19:21:Has Battery: false
10:19:21: On Battery: false
10:19:21: UTC offset: 1
10:19:21: PID: 1023
10:19:21: CWD: /var/lib/fahclient
10:19:21: OS: Linux 3.8.0-27-generic x86_64
10:19:21: OS Arch: AMD64
10:19:21: GPUs: 2
10:19:21: GPU 0: NVIDIA:3 GK104 [GeForce GTX 770]
10:19:21: GPU 1: NVIDIA:3 GK104 [GeForce GTX 770]
10:19:21: CUDA: 3.0
10:19:21:CUDA Driver: 5050
10:19:21:***********************************************************************
10:19:21:<config>
10:19:21: <!-- Client Control -->
10:19:21: <fold-anon v='true'/>
10:19:21:
10:19:21: <!-- Folding Slot Configuration -->
10:19:21: <power v='full'/>
10:19:21:
10:19:21: <!-- HTTP Server -->
10:19:21: <allow v='127.0.0.1,192.168.1.32'/>
10:19:21:
10:19:21: <!-- Network -->
10:19:21: <proxy v=':8080'/>
10:19:21:
10:19:21: <!-- Remote Command Server -->
10:19:21: <password v='******'/>
10:19:21:
10:19:21: <!-- User Information -->
10:19:21: <passkey v='********************************'/>
10:19:21: <team v='33'/>
10:19:21: <user v='Nicolas_orleans'/>
10:19:21:
10:19:21: <!-- Folding Slots -->
10:19:21: <slot id='1' type='GPU'>
10:19:21: <client-type v='advanced'/>
10:19:21: <gpu-index v='0'/>
10:19:21: <next-unit-percentage v='100'/>
10:19:21: </slot>
10:19:21: <slot id='2' type='GPU'>
10:19:21: <client-type v='advanced'/>
10:19:21: <gpu-index v='1'/>
10:19:21: <next-unit-percentage v='100'/>
10:19:21: </slot>
10:19:21:</config>
Re: WS 171.67.108.31 is in Reject mode
Posted: Sun Mar 23, 2014 8:23 am
by billford
I started to report that too, but it's been noticed:
viewtopic.php?f=18&t=26064&p=261248&hilit=108.31#p261248
Re: WS 171.67.108.31 is in Reject mode
Posted: Sun Mar 23, 2014 8:36 pm
by Nicolas_orleans
Thanks billford, I did not realize that.
Since projects 8900 and 9401 are now down / rejecting, 140.163.4.231 (P13000/13001) is now the only WS providing Zeta WUs. And by the way it is now below 1500 available WU, it will be interesting to see whether 171.67.108.31 is fixed on time... or if there will be a new Core 17 shortage in coming days.
Re: WS 171.67.108.31 is in Reject mode
Posted: Sun Mar 23, 2014 9:55 pm
by billford
Nicolas_orleans wrote:or if there will be a new Core 17 shortage in coming days.
I hope not
Re: WS 171.67.108.31 is in Reject mode
Posted: Sun Mar 23, 2014 11:40 pm
by bison88
Nicolas_orleans wrote:Thanks billford, I did not realize that.
Since projects 8900 and 9401 are now down / rejecting, 140.163.4.231 (P13000/13001) is now the only WS providing Zeta WUs. And by the way it is now below 1500 available WU, it will be interesting to see whether 171.67.108.31 is fixed on time... or if there will be a new Core 17 shortage in coming days.
At least it's bouncing some of you to other available Core 17 projects (well the only one up apparently P13000/01), most of us are getting bounced back to that godawful Core 15.
Re: WS 171.67.108.31 is in Reject mode
Posted: Mon Mar 24, 2014 6:47 am
by billford
My gpu runs under Linux so (afaik) I get i7's or nothing... even an i5 is preferable to nothing, surely?
Re: WS 171.67.108.31 is in Reject mode
Posted: Mon Mar 24, 2014 7:09 am
by ChristianVirtual
That was a good one: i7 vs 17 vs i5 vs 15
But yeah, mainly 0x17 under Linux, but on both i7 and i5
Re: WS 171.67.108.31 is in Reject mode
Posted: Mon Mar 24, 2014 6:33 pm
by rwh202
billford wrote:My gpu runs under Linux so (afaik) I get i7's or nothing... even an i5 is preferable to nothing, surely?
That's debatable - from a project perspective, then of course core_15's need doing. Entirely altruistic donors probably feel the same way, but when the same watts / $$$ get 1/3 to 1/4 the points (scientific value?) on core_15, some would prefer to save effort for different uses.
Fortunately my AMD cards are still getting core_17 (core_16 seemed to dry up sometime in January) but the windows nVIDIA cards are still on a diet or core_15 from 171.67.108.142.
Re: WS 171.67.108.31 is in Reject mode
Posted: Mon Mar 24, 2014 6:42 pm
by billford
rwh202 wrote:
That's debatable - from a project perspective, then of course core_15's need doing. Entirely altruistic donors probably feel the same way, but when the same watts / $$$ get 1/3 to 1/4 the points (scientific value?) on core_15, some would prefer to save effort for different uses.
Acknowledged, that's a fair point.
Re: WS 171.67.108.31 is in Reject mode
Posted: Mon Mar 24, 2014 8:04 pm
by davidcoton
This is a case where points do not reflect the relative scientific value of projects on different cores. The latest thinking at PG is that a quick return enhances scientific value (because the whole project goes faster). Hence the latest GPU core (17) has a Quick Return Bonus that greatly increases the points value on a fast GPU -- the faster the better. But Core_15 never had the QRB -- and AFAIK never will, because it's on the way out. It does raise questions about the value (in at least two senses) of points, because the only useful comparison between Core_15 and Core_17 is the base points (without QRB). And even though I don't fold for points, I'm not about to remove my passkey just to get a points value that is comparable across all cores.
David
Re: WS 171.67.108.31 is in Reject mode
Posted: Mon Mar 24, 2014 11:09 pm
by 7im
billford wrote:rwh202 wrote:
That's debatable - from a project perspective, then of course core_15's need doing. Entirely altruistic donors probably feel the same way, but when the same watts / $$$ get 1/3 to 1/4 the points (scientific value?) on core_15, some would prefer to save effort for different uses.
Acknowledged, that's a fair point.
With that kind of logic, you should stop folding for the next 2 years, and wait for an even more efficient core_18, and an even more efficient GPU model to come out.
And we'll just ask everyone to not die from Cancer or Alzheimers for another 2 years.
Except for the last 10 years of folding that I've done (along with 10s of thousands of others) with cores that did much less science/watt that helped you all get to this point where you can enjoy the points from core 17. Everyone has to pay their dues by folding the current mix of work units. Fold or don't. Help contribute to saving the 2 out of 5 people in your family that will die from cancer or don't. The rest of us will still be here.
Re: WS 171.67.108.31 is in Reject mode
Posted: Tue Mar 25, 2014 7:15 am
by rwh202
7im wrote:Fold or don't.
I appreciate the smiley, but I'm not sure this is something that should be said, even in jest. I' don't think you should risk serious folders take offence to something - that's perhaps 1% total output gone.
For me, switching off a few computers when production is low is a valid option - it's quieter, cooler, cheaper and a good opportunity for dusting. As it happens, I've got more hardware than I can run 24/7 anyway, so I've just swapped out a few nVIDIA for AMD to optimise ppd/w.
Points inflation is related, but can probably be separated from the short term issues of WU assignment. I've only been folding for 8 years, but even back in my day, it took 2 years for my laptop to do what core_17 does in 2 hours on my GPUs.
Anyway, back on topic, is there a diagnosis or ETA on 171.67.108.31?
Re: WS 171.67.108.31 is in Reject mode
Posted: Tue Mar 25, 2014 7:19 am
by Nicolas_orleans
171.67.108.31 is still in reject mode, but good news is that P13000/P13001 WS now has more than 6000 available Core 17 units, this should at least help linux users to keep a steady Core 17 production.
As rwh202 pointed out it would be great to have P8900/9401 project managers stopping by and giving news about ongoing server operations (or the new PR person doing donor relations
)
Re: WS 171.67.108.31 is in Reject mode
Posted: Tue Apr 01, 2014 6:49 pm
by PantherX
I have informed the appropriate PG Member about the Server being in Reject Mode.
Re: WS 171.67.108.31 is in Reject mode
Posted: Tue Apr 01, 2014 7:37 pm
by billford
PantherX wrote:I have informed the appropriate PG Member about the Server being in Reject Mode.
As of a few moments ago, along with over 20 others… that's too many.