Connecting to 155.247.166.219: connection failed

Moderators: Site Moderators, FAHC Science Team

Post Reply
FaaR
Posts: 66
Joined: Tue Aug 19, 2008 1:32 am

Connecting to 155.247.166.219: connection failed

Post by FaaR »

Not getting more than the very occasional work unit. Client always tries to connect to this one specific server and typically gets no work; in a day and a half it has received two work units I think. Client typically stops at the line "HH:MM:SS:WU01:FS00:Connecting to 155.247.166.219:80", and can sit there connecting for hours sometimes without timing out or reporting any updates whatsoever in the log.

Code: Select all

*********************** Log Started 2017-12-12T18:44:33Z ***********************
18:44:33:************************* Folding@home Client *************************
18:44:33:      Website: http://folding.stanford.edu/
18:44:33:    Copyright: (c) 2009-2014 Stanford University
18:44:33:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
18:44:33:         Args: 
18:44:33:       Config: C:/Users/*****/AppData/Roaming/FAHClient/config.xml
18:44:33:******************************** Build ********************************
18:44:33:      Version: 7.4.4
18:44:33:         Date: Mar 4 2014
18:44:33:         Time: 20:26:54
18:44:33:      SVN Rev: 4130
18:44:33:       Branch: fah/trunk/client
18:44:33:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
18:44:33:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
18:44:33:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
18:44:33:     Platform: win32 XP
18:44:33:         Bits: 32
18:44:33:         Mode: Release
18:44:33:******************************* System ********************************
18:44:33:          CPU: Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz
18:44:33:       CPU ID: GenuineIntel Family 6 Model 85 Stepping 4
18:44:33:         CPUs: 20
18:44:33:       Memory: 63.68GiB
18:44:33:  Free Memory: 60.17GiB
18:44:33:      Threads: WINDOWS_THREADS
18:44:33:   OS Version: 6.2
18:44:33:  Has Battery: false
18:44:33:   On Battery: false
18:44:33:   UTC Offset: 1
18:44:33:          PID: 4664
18:44:33:          CWD: C:/Users/*****/AppData/Roaming/FAHClient
18:44:33:           OS: Windows 10 Pro
18:44:33:      OS Arch: AMD64
18:44:33:         GPUs: 1
18:44:33:        GPU 0: ATI:5 Hawaii [Radeon R9 200/300X Series]
18:44:33:         CUDA: Not detected
18:44:33:Win32 Service: false
18:44:33:***********************************************************************
18:44:34:<config>
18:44:34:  <!-- Network -->
18:44:34:  <proxy v=':8080'/>
18:44:34:
18:44:34:  <!-- Slot Control -->
18:44:34:  <power v='full'/>
18:44:34:
18:44:34:  <!-- User Information -->
18:44:34:  <passkey v='********************************'/>
18:44:34:  <team v='37451'/>
18:44:34:  <user v='Kapten_Stofil'/>
18:44:34:
18:44:34:  <!-- Folding Slots -->
18:44:34:  <slot id='0' type='CPU'/>
18:44:34:  <slot id='1' type='GPU'/>
18:44:34:</config>
18:44:34:Trying to access database...
18:44:34:Successfully acquired database lock
18:44:34:Enabled folding slot 00: READY cpu:19
18:44:34:Enabled folding slot 01: READY gpu:0:Hawaii [Radeon R9 200/300X Series]
18:44:34:WU00:FS01:Starting
18:44:34:WU00:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/*****/AppData/Roaming/FAHClient/cores/fahwebx.stanford.edu/cores/Win32/AMD64/ATI/R600/Core_21.fah/FahCore_21.exe -dir 00 -suffix 01 -version 704 -lifeline 4664 -checkpoint 15 -gpu 0 -gpu-vendor ati
18:44:34:WU00:FS01:Started FahCore on PID 6624
18:44:34:WU00:FS01:Core PID:7300
18:44:34:WU00:FS01:FahCore 0x21 started
18:44:34:WU01:FS00:Connecting to 171.67.108.45:8080
18:44:34:WU00:FS01:0x21:*********************** Log Started 2017-12-12T18:44:34Z ***********************
18:44:34:WU00:FS01:0x21:Project: 9431 (Run 458, Clone 2, Gen 78)
18:44:34:WU00:FS01:0x21:Unit: 0x00000062ab436c9d586fdd37171edbf9
18:44:34:WU00:FS01:0x21:CPU: 0x00000000000000000000000000000000
18:44:34:WU00:FS01:0x21:Machine: 1
18:44:34:WU00:FS01:0x21:Digital signatures verified
18:44:34:WU00:FS01:0x21:Folding@home GPU Core21 Folding@home Core
18:44:34:WU00:FS01:0x21:Version 0.0.18
18:44:34:WU00:FS01:0x21:  Found a checkpoint file
18:44:35:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:44:35:WU01:FS00:Connecting to 171.64.65.35:80
18:44:36:WU01:FS00:Assigned to work server 155.247.166.219
18:44:36:WU01:FS00:Requesting new work unit for slot 00: READY cpu:19 from 155.247.166.219
18:44:36:WU01:FS00:Connecting to 155.247.166.219:8080
18:44:38:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
18:44:38:WU01:FS00:Connecting to 155.247.166.219:80
18:44:38:WU00:FS01:0x21:Completed 1150000 out of 6250000 steps (18%)
18:44:38:WU00:FS01:0x21:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
18:44:59:WU01:FS00:Connecting to 171.67.108.45:8080
18:45:00:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
18:45:00:WU01:FS00:Connecting to 171.64.65.35:80
18:45:00:WU01:FS00:Assigned to work server 155.247.166.219
18:45:00:WU01:FS00:Requesting new work unit for slot 00: READY cpu:19 from 155.247.166.219
18:45:00:WU01:FS00:Connecting to 155.247.166.219:8080
18:45:02:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
18:45:02:WU01:FS00:Connecting to 155.247.166.219:80
Joe_H
Site Admin
Posts: 7856
Joined: Tue Apr 21, 2009 4:41 pm
Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2
Location: W. MA

Re: Connecting to 155.247.166.219: connection failed

Post by Joe_H »

Pause your CPU folding slot and change the request from CPU:19. You will never get a WU with that setting using the 7.4.4 client, it has nothing to do with the 155.247.166.219 server being down. My suggestion would be to use Configure on the slot to set it to either 16 or 18, both are multiples of 2 or 3. Larger prime numbers like 17 or 19 will not work. Once you have saved the changed configuration, resume folding on the CPU slot.

The public beta, 7.4.16, has new code to negotiate with the servers for work that will use as many cores as possible based on the requested maximum. So a future full release for the client will not need changes from the default settings.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
FaaR
Posts: 66
Joined: Tue Aug 19, 2008 1:32 am

Re: Connecting to 155.247.166.219: connection failed

Post by FaaR »

Ok, well, I did regularly get WUs for this setting up until the other day, and then I've had a few more since then as mentioned. So they do exist apparently. But I'll change the setting; only reason it is 19 right now is because one of my GPUs blew its top about a week ago and had to be amputated. Ugh...

Also, more accurate/helpful error messages in the log, perhaps? :)

When is this smarter beta version going live, you think...? Will my client auto-update like cores do, or will I need to reinstall manually?

Thanks! :D
Joe_H
Site Admin
Posts: 7856
Joined: Tue Apr 21, 2009 4:41 pm
Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2
Location: W. MA

Re: Connecting to 155.247.166.219: connection failed

Post by Joe_H »

When you took out the GPU, the default CPU setting changed from 18 to 19.

There might be some WU's from older projects still around that have wrapper code that would fill a request for 19 and then run at 18, that shows up in the logs when they run. But most projects now just will not assign to a CPU:19 request from the 7.4.4 client.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Connecting to 155.247.166.219: connection failed

Post by bruce »

FaaR wrote:...so, more accurate/helpful error messages in the log, perhaps? :)
I'm all in favor of improving error messages, but in this case that's not applicable. The V7.4.4 client doesn't know WHY it's not getting an assignment, only that it needs to retry. The beta version (now ad V7.4.16) already negotiates with the Servers and searches for an assignment that uses less than the maximum you set rather than only the maximum you set so the error is gone.
Joe_H
Site Admin
Posts: 7856
Joined: Tue Apr 21, 2009 4:41 pm
Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2
Location: W. MA

Re: Connecting to 155.247.166.219: connection failed

Post by Joe_H »

FaaR wrote: When is this smarter beta version going live, you think...? Will my client auto-update like cores do, or will I need to reinstall manually?

Thanks! :D
To answer the rest of your questions, no idea when the beta version will become the full release. It has a few bugs that need to be cleared up first. But the developer has been off taking care of updating the Work and Assignment Server code as well as working on the newest CPU core that takes advantage of AVX on CPU's that support it.

One the updated client comes out you will need to do the update. Currently the client does not auto-update itself. You can also try out the public beta, it is available for down load here - https://folding.stanford.edu/beta/. The main bugs are known. First is that there is a memory leak in FAHControl, just not leaving it open all of the time is enough to avoid that. Depending on OS there is a slow memory leak in FAHClient, restarting every 2-3 weeks will avoid problems. And finally the default scheme on Windows is buggy, another needs to be selected during installation.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Post Reply