New Client trying to connect to 192.0.2.1 (Test Network)

Moderators: Site Moderators, FAHC Science Team

New Client trying to connect to 192.0.2.1 (Test Network)

Postby lkknapp » Sun Mar 22, 2020 9:47 pm

I just installed the 7.5.1 client on a Mac Pro and am unable to get work units. I noticed that one of the servers it is trying is actually a testing network address (192.0.2.1) I am wondering if the new software still has some test code in it??

Logs:

15:14:55:******************************** Build ********************************
15:14:55: Version: 7.5.1
15:14:55: Date: May 11 2018
15:14:55: Time: 12:57:01
15:14:55: Repository: Git
15:14:55: Revision: 4705bf53c635f88b8fe85af7675557e15d491ff0
15:14:55: Branch: master
15:14:55: Compiler: GNU 4.2.1 Compatible Apple LLVM 7.3.0 (clang-703.0.31)
15:14:55: Options: -std=gnu++98 -O3 -funroll-loops -mmacosx-version-min=10.6
15:14:55: -Wno-unused-local-typedefs
15:14:55: Platform: darwin 15.6.0
15:14:55: Bits: 64
15:14:55: Mode: Release
15:14:55:******************************* System ********************************
<...>
18:33:21:WU00:FS00:Connecting to 65.254.110.245:8080
18:33:22:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
18:33:22:WU00:FS00:Connecting to 18.218.241.186:80
18:33:22:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
18:33:22:ERROR:WU00:FS00:Exception: Could not get an assignment
18:38:44:WU01:FS01:Connecting to 65.254.110.245:8080
18:38:44:WU01:FS01:Assigned to work server 192.0.2.1
18:38:44:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:Tahiti XT [Radeon HD 7970] from 192.0.2.1
18:38:44:WU01:FS01:Connecting to 192.0.2.1:8080
18:39:59:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
18:39:59:WU01:FS01:Connecting to 192.0.2.1:80
18:41:15:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1:80: Operation timed out
lkknapp
 
Posts: 3
Joined: Sun Mar 22, 2020 9:35 pm

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby Joe_H » Sun Mar 22, 2020 10:59 pm

GPU folding is not supported under the macOS. It can work booted into Linux or Windows though. The WU request has been redirected away from the WS pool to keep from adding to the connection load there. Eventually a revised client would include a reason for that.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Joe_H
Site Admin
 
Posts: 6682
Joined: Tue Apr 21, 2009 5:41 pm
Location: W. MA

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby lkknapp » Mon Mar 23, 2020 12:53 am

Ahhhh - I see. I had assumed it would just return an Unsupported message as the other Macs did instead of just keeping on trying to connect.
lkknapp
 
Posts: 3
Joined: Sun Mar 22, 2020 9:35 pm

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby Joe_H » Mon Mar 23, 2020 1:25 am

It is a two pronged issue. In this case you have a supported GPU, the 7970, but the OS is unsupported for this one function and the combination falls into a corner case for messages about Unsupported. Something the developer is aware of, but fixes wait on a new version.
Joe_H
Site Admin
 
Posts: 6682
Joined: Tue Apr 21, 2009 5:41 pm
Location: W. MA

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby DavidCancalon » Tue Mar 24, 2020 11:25 am

Hi all,

I have a similar problem under Windows 10 Pro. Is there a way to kick out this server and reconnect to another one ?...

System info :
Code: Select all
12:10:32:WU00:FS00:0xa7:************************** Gromacs Folding@home Core ***************************
12:10:32:WU00:FS00:0xa7:       Type: 0xa7
12:10:32:WU00:FS00:0xa7:       Core: Gromacs
12:10:32:WU00:FS00:0xa7:       Args: -dir 00 -suffix 01 -version 705 -lifeline 6612 -checkpoint 15 -np 1
12:10:32:WU00:FS00:0xa7:************************************ CBang *************************************
12:10:32:WU00:FS00:0xa7:       Date: Oct 26 2019
12:10:32:WU00:FS00:0xa7:       Time: 01:38:35
12:10:32:WU00:FS00:0xa7:   Revision: c46a1a011a24143739ac7218c5a435f66777f62f
12:10:32:WU00:FS00:0xa7:     Branch: master
12:10:32:WU00:FS00:0xa7:   Compiler: Visual C++ 2008
12:10:32:WU00:FS00:0xa7:    Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
12:10:32:WU00:FS00:0xa7:   Platform: win32 10
12:10:32:WU00:FS00:0xa7:       Bits: 64
12:10:32:WU00:FS00:0xa7:       Mode: Release
12:10:32:WU00:FS00:0xa7:************************************ System ************************************
12:10:32:WU00:FS00:0xa7:        CPU: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz
12:10:32:WU00:FS00:0xa7:     CPU ID: GenuineIntel Family 6 Model 15 Stepping 6
12:10:32:WU00:FS00:0xa7:       CPUs: 2
12:10:32:WU00:FS00:0xa7:     Memory: 7.94GiB
12:10:32:WU00:FS00:0xa7:Free Memory: 5.46GiB
12:10:32:WU00:FS00:0xa7:    Threads: WINDOWS_THREADS
12:10:32:WU00:FS00:0xa7: OS Version: 6.2
12:10:32:WU00:FS00:0xa7:Has Battery: false
12:10:32:WU00:FS00:0xa7: On Battery: false
12:10:32:WU00:FS00:0xa7: UTC Offset: 1
12:10:32:WU00:FS00:0xa7:        PID: 7956
12:10:32:WU00:FS00:0xa7:        CWD: C:\Users\David\AppData\Roaming\FAHClient\work
12:10:32:WU00:FS00:0xa7:******************************** Build - libFAH ********************************
12:10:32:WU00:FS00:0xa7:    Version: 0.0.18
12:10:32:WU00:FS00:0xa7:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
12:10:32:WU00:FS00:0xa7:  Copyright: 2019 foldingathome.org
12:10:32:WU00:FS00:0xa7:   Homepage: https://foldingathome.org/
12:10:32:WU00:FS00:0xa7:       Date: Oct 26 2019
12:10:32:WU00:FS00:0xa7:       Time: 01:52:44
12:10:32:WU00:FS00:0xa7:   Revision: c1e3513b1bc0c16013668f2173ee969e5995b38e
12:10:32:WU00:FS00:0xa7:     Branch: master
12:10:32:WU00:FS00:0xa7:   Compiler: Visual C++ 2008
12:10:32:WU00:FS00:0xa7:    Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
12:10:32:WU00:FS00:0xa7:   Platform: win32 10
12:10:32:WU00:FS00:0xa7:       Bits: 64
12:10:32:WU00:FS00:0xa7:       Mode: Release
12:10:32:WU00:FS00:0xa7:************************************ Build *************************************
12:10:32:WU00:FS00:0xa7:       SIMD: sse2
12:10:32:WU00:FS00:0xa7:********************************************************************************


Log example :
Code: Select all
01:53:04:WU01:FS01:Assigned to work server 192.0.2.1
01:53:04:WU01:FS01:Requesting new work unit for slot 01: READY gpu:0:GT216 [GeForce GT 220] from 192.0.2.1
01:53:04:WU01:FS01:Connecting to 192.0.2.1:8080
01:53:25:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
01:53:25:WU01:FS01:Connecting to 192.0.2.1:80
01:53:46:ERROR:WU01:FS01:Exception: Failed to connect to 192.0.2.1:80: Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu.
DavidCancalon
 
Posts: 1
Joined: Tue Mar 24, 2020 8:20 am

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby Joe_H » Tue Mar 24, 2020 7:09 pm

Remove the GPU folding slot for the GT 220, it is too old and not supported.
Joe_H
Site Admin
 
Posts: 6682
Joined: Tue Apr 21, 2009 5:41 pm
Location: W. MA

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby owen » Mon Apr 06, 2020 1:38 am

I'm getting this message for a Linux system using an ATI Radeon 6450 GPU...
Code: Select all
00:56:32:WU01:FS00:Starting
00:56:32:WU01:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/cores.foldingathome.org/v7/lin/64bit/Core_a7.fah/FahCore_a7 -dir 01 -suffix 01 -version 705 -lifeline 39487 -checkpoint 15 -np 1
00:56:32:WU01:FS00:Started FahCore on PID 105939
00:56:32:WU01:FS00:Core PID:105943
00:56:32:WU01:FS00:FahCore 0xa7 started
00:56:32:WU01:FS00:0xa7:*********************** Log Started 2020-04-06T00:56:32Z ***********************
00:56:32:WU01:FS00:0xa7:************************** Gromacs Folding@home Core ***************************
00:56:32:WU01:FS00:0xa7:       Type: 0xa7
00:56:32:WU01:FS00:0xa7:       Core: Gromacs
00:56:32:WU01:FS00:0xa7:       Args: -dir 01 -suffix 01 -version 705 -lifeline 105939 -checkpoint 15 -np
00:56:32:WU01:FS00:0xa7:             1
00:56:32:WU01:FS00:0xa7:************************************ CBang *************************************
00:56:32:WU01:FS00:0xa7:       Date: Nov 5 2019
00:56:32:WU01:FS00:0xa7:       Time: 05:57:01
00:56:32:WU01:FS00:0xa7:   Revision: 46c96f1aa8419571d83f3e63f9c99a0d602f6da9
00:56:32:WU01:FS00:0xa7:     Branch: master
00:56:32:WU01:FS00:0xa7:   Compiler: GNU 8.3.0
00:56:32:WU01:FS00:0xa7:    Options: -std=c++11 -O3 -funroll-loops -fno-pie -fPIC
00:56:32:WU01:FS00:0xa7:   Platform: linux2 4.19.0-5-amd64
00:56:32:WU01:FS00:0xa7:       Bits: 64
00:56:32:WU01:FS00:0xa7:       Mode: Release
00:56:32:WU01:FS00:0xa7:************************************ System ************************************
00:56:32:WU01:FS00:0xa7:        CPU: AMD Athlon(tm) X2 Dual Core Processor BE-2400
00:56:32:WU01:FS00:0xa7:     CPU ID: AuthenticAMD Family 15 Model 107 Stepping 2
00:56:32:WU01:FS00:0xa7:       CPUs: 2
00:56:32:WU01:FS00:0xa7:     Memory: 3.84GiB
00:56:32:WU01:FS00:0xa7:Free Memory: 2.35GiB
00:56:32:WU01:FS00:0xa7:    Threads: POSIX_THREADS
00:56:32:WU01:FS00:0xa7: OS Version: 5.5
00:56:32:WU01:FS00:0xa7:Has Battery: false
00:56:32:WU01:FS00:0xa7: On Battery: false
00:56:32:WU01:FS00:0xa7: UTC Offset: -7
00:56:32:WU01:FS00:0xa7:        PID: 105943
00:56:32:WU01:FS00:0xa7:        CWD: /var/lib/fahclient/work
00:56:32:WU01:FS00:0xa7:******************************** Build - libFAH ********************************
00:56:32:WU01:FS00:0xa7:    Version: 0.0.18
00:56:32:WU01:FS00:0xa7:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
00:56:32:WU01:FS00:0xa7:  Copyright: 2019 foldingathome.org
00:56:32:WU01:FS00:0xa7:   Homepage: https://foldingathome.org/
00:56:32:WU01:FS00:0xa7:       Date: Nov 5 2019
00:56:32:WU01:FS00:0xa7:       Time: 06:13:26
00:56:32:WU01:FS00:0xa7:   Revision: 490c9aa2957b725af319379424d5c5cb36efb656
00:56:32:WU01:FS00:0xa7:     Branch: master
00:56:32:WU01:FS00:0xa7:   Compiler: GNU 8.3.0
00:56:32:WU01:FS00:0xa7:    Options: -std=c++11 -O3 -funroll-loops -fno-pie
00:56:32:WU01:FS00:0xa7:   Platform: linux2 4.19.0-5-amd64
00:56:32:WU01:FS00:0xa7:       Bits: 64
00:56:32:WU01:FS00:0xa7:       Mode: Release
00:56:32:WU01:FS00:0xa7:************************************ Build *************************************
00:56:32:WU01:FS00:0xa7:       SIMD: sse2
00:56:32:WU01:FS00:0xa7:********************************************************************************
00:56:32:WU01:FS00:0xa7:Project: 13851 (Run 0, Clone 26438, Gen 13)
00:56:32:WU01:FS00:0xa7:Unit: 0x00000017287234c95e788601a8be7ff3
00:56:32:WU01:FS00:0xa7:Digital signatures verified
00:56:32:WU01:FS00:0xa7:Calling: mdrun -s frame13.tpr -o frame13.trr -x frame13.xtc -e frame13.edr -cpi state.cpt -cpt 15 -nt 1
00:56:32:WU01:FS00:0xa7:Steps: first=6500000 total=500000
00:56:34:WU01:FS00:0xa7:Completed 115812 out of 500000 steps (23%)
00:57:04:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
00:57:04:WU00:FS01:Connecting to 192.0.2.1:80
00:59:15:ERROR:WU00:FS01:Exception: Failed to connect to 192.0.2.1:80: Connection timed out
00:59:15:WU00:FS01:Connecting to 65.254.110.245:8080
00:59:15:WU00:FS01:Assigned to work server 192.0.2.1
00:59:15:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:Caicos [AMD RADEON HD 6450] from 192.0.2.1
00:59:15:WU00:FS01:Connecting to 192.0.2.1:8080
01:01:26:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
01:01:26:WU00:FS01:Connecting to 192.0.2.1:80
01:03:37:ERROR:WU00:FS01:Exception: Failed to connect to 192.0.2.1:80: Connection timed out
01:03:37:WU00:FS01:Connecting to 65.254.110.245:8080
01:03:37:WU00:FS01:Assigned to work server 192.0.2.1
01:03:37:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:Caicos [AMD RADEON HD 6450] from 192.0.2.1
01:03:37:WU00:FS01:Connecting to 192.0.2.1:8080
01:05:48:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
01:05:48:WU00:FS01:Connecting to 192.0.2.1:80
01:07:59:ERROR:WU00:FS01:Exception: Failed to connect to 192.0.2.1:80: Connection timed out
01:07:59:WU00:FS01:Connecting to 65.254.110.245:8080
01:08:00:WU00:FS01:Assigned to work server 192.0.2.1
01:08:00:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:Caicos [AMD RADEON HD 6450] from 192.0.2.1
01:08:00:WU00:FS01:Connecting to 192.0.2.1:8080


If that's an unsupported config, then so be it, let me know and I"ll take out the GPU configuration.

Otherwise, it seems to me that the AS is handing out a bogus destination address. FWIW, it appears that AS 65.254.110.245 is the one giving me the bogus destination.

Also, if you are going to hand out an invalid address to direct things away from the work server, may I suggest something in the 169.254.0.0/16 (IPv4 Link Local) or IPv6 fe80::/10 (preferably outside of fe80::/16 so as to be extremely unlikely to encounter any actual target).

The advantage to Link Local instead of 192.0.2.0 (Example/Test prefix in IANA reserved range) is that 192.0.2.0 is routable, so it will go to the first default-free router before dying (unless it encounters a bogon filter that happens to include 192.0.2.0/24 first).
OTOH, link local won't make it past the local gateway. Since your goal is to drop the traffic rather than load up your work servers, seems to me dropping it as close to the client as possible is a desirable outcome.
owen
 
Posts: 6
Joined: Tue Mar 24, 2020 10:16 pm

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby Joe_H » Mon Apr 06, 2020 1:46 am

The HD 6450 does not support Double Precision calculations, It was usable until last year when the last GPU projects that did not require mixed precision support, mostly Single Precision with some Double Precision.
Joe_H
Site Admin
 
Posts: 6682
Joined: Tue Apr 21, 2009 5:41 pm
Location: W. MA

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby owen » Mon Apr 06, 2020 2:37 am

owen
 
Posts: 6
Joined: Tue Mar 24, 2020 10:16 pm

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby owen » Mon Apr 06, 2020 2:40 am

Also, in case you missed it, if you want an invalid IP to direct errant clients at...
I suggest something in the 169.254.0.0/16 (IPv4 Link Local) or IPv6 fe80::/10 (preferably outside of fe80::/16 so as to be extremely unlikely to encounter any actual target).

The advantage to Link Local instead of 192.0.2.0 (Example/Test prefix in IANA reserved range) is that 192.0.2.0 is routable, so it will go to the first default-free router before dying (unless it encounters a bogon filter that happens to include 192.0.2.0/24 first).
OTOH, link local won't make it past the local gateway. Since your goal is to drop the traffic rather than load up your work servers, seems to me dropping it as close to the client as possible is a desirable outcome.
owen
 
Posts: 6
Joined: Tue Mar 24, 2020 10:16 pm

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby Joe_H » Mon Apr 06, 2020 7:52 am

One of your assumptions is wrong, addresses in the 192.0.2.0, and two other blocks of test/documentation IP addresses are Not routable per RFC 5737. Now if some later standard makes them routable, you are welcome to provide a source for that.
Joe_H
Site Admin
 
Posts: 6682
Joined: Tue Apr 21, 2009 5:41 pm
Location: W. MA

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby hammerquill » Fri Apr 10, 2020 2:42 am

Similar issue. My GPU is whitelisted. Running on a PC. The CPUs have work on this PC; a barely better GPU on my other machine has work most of the time. I checked the whitelist before spinning up this computer out of storage.
0x10de:0x05fe:::GT200GL [Quadro FX 4800]


01:35:08:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GT200GL [Quadro FX 4800] from 192.0.2.1
01:35:08:WU00:FS01:Connecting to 192.0.2.1:8080
01:35:30:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
01:35:30:WU00:FS01:Connecting to 192.0.2.1:80
01:35:51:ERROR:WU00:FS01:Exception: Failed to connect to 192.0.2.1:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
hammerquill
 
Posts: 2
Joined: Sat Apr 04, 2020 2:57 am

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby JimboPalmer » Fri Apr 10, 2020 4:43 am

hammerquill wrote:Similar issue. My GPU is whitelisted. Running on a PC. The CPUs have work on this PC; a barely better GPU on my other machine has work most of the time. I checked the whitelist before spinning up this computer out of storage.
0x10de:0x05fe:::GT200GL [Quadro FX 4800]

If the Quadro FX 4800 could fold, then that string of colons would have numbers between them explaining its capabilities. It can't, so that is blank.

https://www.techpowerup.com/gpu-specs/q ... 4800.c1320
No Tesla card can fold, (Core_15 was a good Tesla Core) It does not support OpenCL 1.2. If it could fold, it could not make deadlines. (today's entry level GT 1030 is about twice as fast as 2008's professional card)
Last edited by JimboPalmer on Fri Apr 10, 2020 5:05 am, edited 1 time in total.
Tsar of all the Rushers
I tried to remain childlike, all I achieved was childish.
A friend to those who want no friends
JimboPalmer
 
Posts: 2067
Joined: Mon Feb 16, 2009 5:12 am
Location: Greenwood MS USA

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby Joe_H » Fri Apr 10, 2020 4:50 am

Or as additional explanation, the GPUs.txt file both a whitelist and a blacklist. If there are 0s or no entries in the 3rd and 4th field, that GPU is blacklisted.
Joe_H
Site Admin
 
Posts: 6682
Joined: Tue Apr 21, 2009 5:41 pm
Location: W. MA

Re: New Client trying to connect to 192.0.2.1 (Test Network)

Postby hammerquill » Fri Apr 10, 2020 6:06 am

Okay, I see. Thanks for the explanation. I didn't see anything about that in the other threads where I originally found the link to the GPU list.
hammerquill
 
Posts: 2
Joined: Sat Apr 04, 2020 2:57 am

Next

Return to Issues with a specific server

Who is online

Users browsing this forum: No registered users and 1 guest

cron