Moderators: Site Moderators, PandeGroup
Nert wrote:This whole episode is sad and disrespectful to the people that contribute to this project. Two questions come to mind:
1) Why do the volunteer contributors have a sense of urgency and those responsible for the project do not ?
2) These problems ALWAYS seem to happen over holiday weekends. Is everything so fragile that it fails when no one is there to hand hold the systems and keep them running ?
When I was a graduate student I did NOT get holidays. When I worked at Intel I was on-call 24x7. I bet they could even remedy this remotely. I notified Pande and Chodera and have heard nothingJoe_H wrote:I have heard back that it is being looked into, but nothing further to post. The first reports came in on a Friday evening and reported to PG on Saturday morning. This is a relatively major holiday weekend, so limited staff would be available to work on this.
Adam A. Wanderer wrote:As sad as these developments are, I'll stick with F@H. There's just no other project that does the work F@H does. And, F@H has improved over the years, I hope it'll continue to do so.
Adam A. Wanderer wrote:Nert wrote:Was any form of "hacking" or a virus involved?
Good idea. I'll try it when I get home.boristsybin wrote:Serge_Grenier wrote:Seems <client-type v='beta'/> is working to get WUs since yesterday.
seems it works
SteveWillis wrote:I should mention that my older machine has also not had any problem at all. Only my newer machine had the problem. I mentioned it earlier but didn't bother to include my log.
- Code: Select all
*********************** Log Started 2017-05-29T23:18:46Z ***********************
23:18:46:************************* Folding@home Client *************************
23:18:46: Website: http://folding.stanford.edu/
23:18:46: Copyright: (c) 2009-2014 Stanford University
23:18:46: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
23:18:46: Args: --child --lifeline 1895 /etc/fahclient/config.xml --run-as
23:18:46: fahclient --pid-file=/var/run/fahclient.pid --daemon
23:18:46: Config: /etc/fahclient/config.xml
23:18:46:******************************** Build ********************************
23:18:46: Version: 7.4.4
23:18:46: Date: Mar 4 2014
23:18:46: Time: 12:02:38
23:18:46: SVN Rev: 4130
23:18:46: Branch: fah/trunk/client
23:18:46: Compiler: GNU 4.4.7
23:18:46: Options: -std=gnu++98 -O3 -funroll-loops -mfpmath=sse -ffast-math
23:18:46: -fno-unsafe-math-optimizations -msse2
23:18:46: Platform: linux2 3.2.0-1-amd64
23:18:46: Bits: 64
23:18:46: Mode: Release
23:18:46:******************************* System ********************************
23:18:46: CPU: AMD FX(tm)-8320 Eight-Core Processor
23:18:46: CPU ID: AuthenticAMD Family 21 Model 2 Stepping 0
23:18:46: CPUs: 8
23:18:46: Memory: 31.32GiB
23:18:46:Free Memory: 30.66GiB
23:18:46: Threads: POSIX_THREADS
23:18:46: OS Version: 3.19
23:18:46:Has Battery: false
23:18:46: On Battery: false
23:18:46: UTC Offset: -5
23:18:46: PID: 1897
23:18:46: CWD: /var/lib/fahclient
23:18:46: OS: Linux 3.19.0-32-generic x86_64
23:18:46: OS Arch: AMD64
23:18:46: GPUs: 6
23:18:46: GPU 0: NVIDIA:7 GP104 [GeForce GTX 1080] 8873
23:18:46: GPU 1: UNSUPPORTED: NV3 [PCI]
23:18:46: GPU 2: NVIDIA:7 GP104 [GeForce GTX 1080] 8873
23:18:46: GPU 3: UNSUPPORTED: NV3 [PCI]
23:18:46: GPU 4: NVIDIA:7 GP104 [GeForce GTX 1080] 8873
23:18:46: GPU 5: UNSUPPORTED: NV3 [PCI]
23:18:46: CUDA: 6.1
23:18:46:CUDA Driver: 8000
23:18:46:***********************************************************************
23:18:46:<config>
23:18:46: <!-- Client Control -->
23:18:46: <fold-anon v='true'/>
23:18:46:
23:18:46: <!-- Folding Core -->
23:18:46: <checkpoint v='30'/>
23:18:46:
23:18:46: <!-- Folding Slot Configuration -->
23:18:46: <cause v='HUNTINGTONS'/>
23:18:46:
23:18:46: <!-- Network -->
23:18:46: <proxy v=':8080'/>
23:18:46:
23:18:46: <!-- Slot Control -->
23:18:46: <power v='full'/>
23:18:46:
23:18:46: <!-- User Information -->
23:18:46: <passkey v='********************************'/>
23:18:46: <team v='224497'/>
23:18:46: <user v='DarthMouse_ALL_1GD5nCZbh7gNo1SESPLT24xEd2Jsu4rTP9'/>
23:18:46:
23:18:46: <!-- Work Unit Control -->
23:18:46: <next-unit-percentage v='100'/>
23:18:46:
23:18:46: <!-- Folding Slots -->
23:18:46: <slot id='0' type='GPU'/>
23:18:46: <slot id='1' type='GPU'/>
23:18:46: <slot id='2' type='GPU'/>
23:18:46:</config>
boristsybin wrote:Serge_Grenier wrote:Seems <client-type v='beta'/> is working to get WUs since yesterday.
seems it works
client-type
beta
PS3EdOlkkola wrote:@rwh202 I can confirm that changing the cause preference to Huntington's does avoid the problematic work server/assignment server. All slots are finally operational. Changing this value got 14 slots that were in "ready" mode to get a work unit and start processing. The procedure is to pause the slot that's in "ready" mode, then go to Configure, select tab Advanced, then select the Cause Preference as Huntinton's, click Save then un-pause the slot. The slot should pick up a work unit right away. Thanks rwh202
JimF wrote:PG's usual response is to start a new public relations campaign to make up for the people who leave.
Return to Issues with a specific server
Users browsing this forum: No registered users and 1 guest