Folding Forum

Community driven support forum for Folding@home
https://foldingforum.org/

[SOLVED] Assigned to work server 192.0.2.1 which can not establish connection.

https://foldingforum.org/viewtopic.php?t=39302

Page 1 of 1

[SOLVED] Assigned to work server 192.0.2.1 which can not establish connection.

Posted: Wed Mar 22, 2023 12:42 pm
by cloud7896
FAH client is assigned to work server 192.0.2.1 which can not establish connection. ( Only CPU folding )

LOG:

Code: Select all

*********************** Log Started 2023-03-22T12:03:34Z ***********************
12:03:34:******************************* libFAH ********************************
12:03:34:         Date: Oct 20 2020
12:03:34:         Time: 13:36:55
12:03:34:     Revision: 5ca109d295a6245e2a2f590b3d0085ad5e567aeb
12:03:34:       Branch: master
12:03:34:     Compiler: Visual C++ 2015
12:03:34:      Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
12:03:34:     Platform: win32 10
12:03:34:         Bits: 32
12:03:34:         Mode: Release
12:03:34:****************************** FAHClient ******************************
12:03:34:      Version: 7.6.21
12:03:34:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
12:03:34:    Copyright: 2020 foldingathome.org
12:03:34:     Homepage: https://foldingathome.org/
12:03:34:         Date: Oct 20 2020
12:03:34:         Time: 13:41:04
12:03:34:     Revision: 6efbf0e138e22d3963e6a291f78dcb9c6422a278
12:03:34:       Branch: master
12:03:34:     Compiler: Visual C++ 2015
12:03:34:      Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
12:03:34:     Platform: win32 10
12:03:34:         Bits: 32
12:03:34:         Mode: Release
12:03:34:       Config: C:\ProgramData\FAHClient\config.xml
12:03:34:******************************** CBang ********************************
12:03:34:         Date: Oct 20 2020
12:03:34:         Time: 11:36:18
12:03:34:     Revision: 7e4ce85225d7eaeb775e87c31740181ca603de60
12:03:34:       Branch: master
12:03:34:     Compiler: Visual C++ 2015
12:03:34:      Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
12:03:34:     Platform: win32 10
12:03:34:         Bits: 32
12:03:34:         Mode: Release
12:03:34:******************************* System ********************************
12:03:34:          CPU: Intel(R) Xeon(R) Platinum 8255C CPU @ 2.50GHz
12:03:34:       CPU ID: GenuineIntel Family 6 Model 85 Stepping 5
12:03:34:         CPUs: 8
12:03:34:       Memory: 16.00GiB
12:03:34:  Free Memory: 14.55GiB
12:03:34:      Threads: WINDOWS_THREADS
12:03:34:   OS Version: 6.2
12:03:34:  Has Battery: false
12:03:34:   On Battery: false
12:03:34:   UTC Offset: 0
12:03:34:          PID: 5588
12:03:34:          CWD: C:\ProgramData\FAHClient
12:03:34:Win32 Service: false
12:03:34:           OS: Windows Server 2022 Datacenter
12:03:34:      OS Arch: AMD64
12:03:34:         GPUs: 0
12:03:34:         CUDA: Not detected: Failed to open dynamic library 'nvcuda.dll': The
12:03:34:               specified module could not be found.
12:03:34:
12:03:34:       OpenCL: Not detected: clGetPlatformIDs() returned -1001
12:03:34:***********************************************************************
12:03:34:<config>
12:03:34:  <!-- Network -->
12:03:34:  <proxy v=':8080'/>
12:03:34:
12:03:34:  <!-- Slot Control -->
12:03:34:  <power v='full'/>
12:03:34:
12:03:34:  <!-- User Information -->
12:03:34:  <team v='268045'/>
12:03:34:  <user v='Cloud'/>
12:03:34:
12:03:34:  <!-- Folding Slots -->
12:03:34:  <slot id='0' type='CPU'>
12:03:34:    <paused v='true'/>
12:03:34:  </slot>
12:03:34:</config>
12:03:34:Trying to access database...
12:03:34:Successfully acquired database lock
12:03:34:FS00:Initialized folding slot 00: cpu:8
12:05:33:FS00:Unpaused
12:05:34:WU00:FS00:Connecting to assign1.foldingathome.org:80
12:05:35:WU00:FS00:Assigned to work server 192.0.2.1
12:05:35:WU00:FS00:Requesting new work unit for slot 00: cpu:8 from 192.0.2.1
12:05:35:WU00:FS00:Connecting to 192.0.2.1:8080
12:05:56:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
12:05:56:WU00:FS00:Connecting to 192.0.2.1:80
12:06:17:ERROR:WU00:FS00: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.
12:06:17:WU00:FS00:Connecting to assign1.foldingathome.org:80
12:06:18:WU00:FS00:Assigned to work server 192.0.2.1
12:06:18:WU00:FS00:Requesting new work unit for slot 00: cpu:8 from 192.0.2.1
12:06:18:WU00:FS00:Connecting to 192.0.2.1:8080
12:06:39:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
12:06:39:WU00:FS00:Connecting to 192.0.2.1:80
12:07:00:ERROR:WU00:FS00: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.
12:07:17:WU00:FS00:Connecting to assign1.foldingathome.org:80
12:07:17:WU00:FS00:Assigned to work server 192.0.2.1
12:07:18:WU00:FS00:Requesting new work unit for slot 00: cpu:8 from 192.0.2.1
12:07:18:WU00:FS00:Connecting to 192.0.2.1:8080
12:07:39:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
12:07:39:WU00:FS00:Connecting to 192.0.2.1:80
12:08:00:ERROR:WU00:FS00: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.
12:08:54:WU00:FS00:Connecting to assign1.foldingathome.org:80
12:08:55:WU00:FS00:Assigned to work server 192.0.2.1
12:08:55:WU00:FS00:Requesting new work unit for slot 00: cpu:8 from 192.0.2.1
12:08:55:WU00:FS00:Connecting to 192.0.2.1:8080
12:09:16:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
12:09:16:WU00:FS00:Connecting to 192.0.2.1:80
12:09:37:ERROR:WU00:FS00: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.
12:11:32:WU00:FS00:Connecting to assign1.foldingathome.org:80
12:11:32:WU00:FS00:Assigned to work server 192.0.2.1
12:11:32:WU00:FS00:Requesting new work unit for slot 00: cpu:8 from 192.0.2.1
12:11:32:WU00:FS00:Connecting to 192.0.2.1:8080
12:11:53:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
12:11:53:WU00:FS00:Connecting to 192.0.2.1:80
12:12:14:ERROR:WU00:FS00: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.

Re: Assigned to work server 192.0.2.1 which can not establish connection.

Posted: Wed Mar 22, 2023 1:28 pm
by Joe_H
Assigned to WS address 192.0.2.1 indicates the client and Assignment Server is not recognizing your CPU type and can not properly set the assignment up for which CPU core to use. 192.0.2.1 is a non-routing address, it keeps the client from repeatedly connecting to Work Servers. This I have mostly seen from clients that have been manually configured with GPU folding slots for unsupported cards, or in the case of Mac's to fold on a GPU which is not supported with macOS.

The only other time I have seen the client and AS not recognize a CPU was a few years ago when someone had a system configured with an engineering sample, not a released version of of a CPU. Is that the case here? A Xeon 8255C is supposed to be showing 24 cores / 48 threads, not the 8 shown in the log. The only other thing I can think of is are you running the client in a VM on a server. There if the VM is not setup correctly the CPU may not be showing the proper capabilities to fold.

Re: Assigned to work server 192.0.2.1 which can not establish connection.

Posted: Wed Mar 22, 2023 4:32 pm
by cloud7896
I was running FAH on an idle cloud server. I did some checking and finally found that it was the team ID 268045 that was causing this problem. After I change the team ID, it works fine. Maybe Assignment Server doesn't support the team ID 268045 anymore ?

Re: Assigned to work server 192.0.2.1 which can not establish connection.

Posted: Wed Mar 22, 2023 5:02 pm
by Joe_H
Theta Edge Computing keeps getting banned for excessive non completion of WUs. I don't know all of the details, but the configurations they initially created had no persistent storage. So WUs would get downloaded, partially processed, ad the instance would be dropped. When restarted it would get a new WU since the previous partially completed one was gone as it was not stored.
All times are UTC
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited