Page 1 of 2
Windows 10 w/ two 1080Ti: new clients not working
Posted: Tue Apr 21, 2020 5:05 pm
by Chris_TG
Hi there,
I have a strange problem with one machine that runs Windows 10 Pro with two NVIDIA 1080Ti installed:
The last working FAH-client is version 7.4.x. All newer clients from 7.5.x and 7.6.x do not work properly somehow.
The problem is that it seems to be impossible for the webcontrol and FAHControl to connect to the FAHclient internally.
Something coarse must have changed in the code that performs the network communication or at least how listening sockets are initialized, because the problem is that the FAHclient.exe seems to be unable to open listening TCP-sockets.
The output of "netstat -abn" completely misses entries from FAHclient.
I did not find any deeper informations about how to debug the client, so any help is highly appreciated.
TIA!
Chris
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Tue Apr 21, 2020 6:14 pm
by HaloJones
Very strange. Have you folded on this machine before? I have 7.6.8 working with no issues and no special settings. I would consider if I were you doing a full uninstall, including any data in your %appdata%/roaming/fahclient directory. Then doing a new install with 7.6.8 (not 7.6.9)
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Tue Apr 21, 2020 6:52 pm
by Chris_TG
Folding with client version 7.4.x works without problems, all clients starting with version 7.5.x show the same problem that they seem to be unable to establish TCP sockets on the system.
And yes, I tried every hint I could find here and on the FAQ-page regarding upgrading/reinstall etc.
Even a completely fresh install with manually removing of all traces before does not change a thing.
Strange thing is, that there is absolutely no log-output of the client that could explain this behaviour.
Is any dev of the client here? How can I get decent debugging informations?
TIA
Chris
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Tue Apr 21, 2020 6:54 pm
by HaloJones
There is only one core developer so not sure who could help with this.
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Tue Apr 21, 2020 7:14 pm
by bruce
First, verify that FAHClient is running in the background. If not find the shortcut that was provided with the installation and start it.
If it's still not running, you probably tried to edit config.xml. FAHClient is totally intolerant of minor changes to the xml protocol notation.
if it is running, use the installed shortut to start FAHControl.
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Tue Apr 21, 2020 7:20 pm
by Chris_TG
Hi bruce,
I already tried everything that seemed reasonable to me, including manually starting the client w/ and w/o commandline-params, editing the config.xml, adding firewall-rules and temporarly disabling the firewall.
But still no luck, the client still does not open any listening socket on port 7396 and 33600.
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Tue Apr 21, 2020 7:23 pm
by bruce
The necessary port is 36330 and it can be tested by downloading a telnet client. (It's still an opt-in option in WIn10, I believe, but there are other choice.)
> telnet 127.0.0.1 36330
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Tue Apr 21, 2020 7:28 pm
by Chris_TG
The port is not there, that's the problem (see my first post).
The client process is running but does not open the port(s) for some reason.
Any ideas?
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Tue Apr 21, 2020 8:18 pm
by bruce
Is FAHClinet running?
Is your security software blocking the connection?
Code: Select all
C:\Users\bruce>telnet 127.0.0.1 36330
Welcome to the FAHClient command server.
> q
Connection to host lost.
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Tue Apr 21, 2020 8:39 pm
by Chris_TG
bruce, I really appreciate your attendance to help, but I feel like we're going in circles.
Believe me, the port is not there. It's not that some other software blocks any connection.
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Tue Apr 21, 2020 8:47 pm
by bruce
I don't doubt you can't connect, but you didn't answer my questions. Is FAHClient running?
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Tue Apr 21, 2020 8:51 pm
by Chris_TG
bruce wrote:I don't doubt you can't connect, but you didn't answer my questions. Is FAHClient running?
I did:
Chris_TG wrote:The port is not there, that's the problem (see my first post).
The client process is running but does not open the port(s) for some reason.
Any ideas?
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Tue Apr 21, 2020 10:23 pm
by uyaem
Have you looked at the log files in %APPDATA%\FAHClient\logs?
I once had a windows-related crash which left my config.xml in a rather desolate state, so I manually restored the latest one from %APPDATA%\FAHClient\config.
That said, my "symptoms" were that FAHClient would not even start up, but maybe there's something helpful in the logs for you too.
EDIT: I saw you mentioned logs in the beginning. But still check if your config.xml is valid XML.
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Wed Apr 22, 2020 6:35 am
by PantherX
Welcome to the F@H Forum Chris_TG,
If possible, could you post the log file? Guidance on where to find them on a default installation is available here: viewtopic.php?f=24&t=26036
Re: Windows 10 w/ two 1080Ti: new clients not working
Posted: Thu Apr 23, 2020 9:03 pm
by Chris_TG
Hi,
thanks for your reply.
Here are the requested infos (and some more):
log.txt (with anonymized userdata):
Code: Select all
*********************** Log Started 2020-04-23T20:50:52Z ***********************
20:50:52:****************************** FAHClient ******************************
20:50:52: Version: 7.6.10
20:50:52: Author: Joseph Coffland <[email protected]>
20:50:52: Copyright: 2020 foldingathome.org
20:50:52: Homepage: https://foldingathome.org/
20:50:52: Date: Apr 17 2020
20:50:52: Time: 20:32:19
20:50:52: Revision: 05835e6a32e37abf3c82dbb9d2050d906637a345
20:50:52: Branch: master
20:50:52: Compiler: Visual C++ 2008
20:50:52: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
20:50:52: Platform: win32 10
20:50:52: Bits: 32
20:50:52: Mode: Release
20:50:52: Args: --open-web-control
20:50:52: Config: C:\Users\Render Rechner\AppData\Roaming\FAHClient\config.xml
20:50:52:******************************** CBang ********************************
20:50:52: Date: Apr 17 2020
20:50:52: Time: 11:10:09
20:50:52: Revision: 2fb0be7809c5e45287a122ca5fbc15b5ae859a3b
20:50:52: Branch: master
20:50:52: Compiler: Visual C++ 2008
20:50:52: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
20:50:52: Platform: win32 10
20:50:52: Bits: 32
20:50:52: Mode: Release
20:50:52:******************************* System ********************************
20:50:52: CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
20:50:52: CPU ID: GenuineIntel Family 6 Model 158 Stepping 9
20:50:52: CPUs: 8
20:50:52: Memory: 31.93GiB
20:50:52: Free Memory: 22.60GiB
20:50:52: Threads: WINDOWS_THREADS
20:50:52: OS Version: 6.2
20:50:52: Has Battery: false
20:50:52: On Battery: false
20:50:52: UTC Offset: 2
20:50:52: PID: 35684
20:50:52: CWD: C:\Users\Render Rechner\AppData\Roaming\FAHClient
20:50:52: OS: Windows 10 Enterprise
20:50:52: OS Arch: AMD64
20:50:52: GPUs: 2
20:50:52: GPU 0: Bus:1 Slot:0 Func:0 NVIDIA:8 GP104 [GeForce GTX 1080] 8873
20:50:52: GPU 1: Bus:2 Slot:0 Func:0 NVIDIA:8 GP104 [GeForce GTX 1080] 8873
20:50:52:CUDA Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:6.1 Driver:10.2
20:50:52:CUDA Device 1: Platform:0 Device:1 Bus:2 Slot:0 Compute:6.1 Driver:10.2
20:50:52: OpenCL: Not detected
20:50:52:Win32 Service: false
20:50:52:******************************* libFAH ********************************
20:50:52: Date: Apr 15 2020
20:50:52: Time: 14:53:14
20:50:52: Revision: 216968bc7025029c841ed6e36e81a03a316890d3
20:50:52: Branch: master
20:50:52: Compiler: Visual C++ 2008
20:50:52: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
20:50:52: Platform: win32 10
20:50:52: Bits: 32
20:50:52: Mode: Release
20:50:52:***********************************************************************
20:50:52:<config>
20:50:52: <!-- Network -->
20:50:52: <proxy v=':8080'/>
20:50:52:
20:50:52: <!-- User Information -->
20:50:52: <passkey v='*****'/>
20:50:52: <team v='******'/>
20:50:52: <user v='**********'/>
20:50:52:
20:50:52: <!-- Folding Slots -->
20:50:52: <slot id='0' type='CPU'/>
20:50:52: <slot id='1' type='GPU'/>
20:50:52: <slot id='2' type='GPU'/>
20:50:52:</config>
20:50:52:Trying to access database...
20:50:52:Successfully acquired database lock
20:50:52:Enabled folding slot 00: READY cpu:5
My config.xml (with anonymized userdata):
Code: Select all
<config>
<!-- Network -->
<proxy v=':8080'/>
<!-- User Information -->
<passkey v='**********************'/>
<team v='******'/>
<user v='**********'/>
<!-- Folding Slots -->
<slot id='0' type='CPU'/>
<slot id='1' type='GPU'/>
<slot id='2' type='GPU'/>
</config>
The task of the FAHClient is running:
Code: Select all
C:\Users\user1>tasklist | find "FAHClient"
FAHClient.exe 36640 RDP-Tcp#4 1 20.488 K
C:\Users\user1>
But it does not open any port:
Code: Select all
C:\WINDOWS\system32>netstat -abn | find "FAHClient"
C:\WINDOWS\system32>
Hence a telnet to that port fails:
Code: Select all
C:\WINDOWS\system32>telnet 127.0.0.1 36330
Verbindungsaufbau zu 127.0.0.1...Es konnte keine Verbindung mit dem Host hergestellt werden, auf Port 36330: Verbindungsfehler
C:\WINDOWS\system32>
If you need any other info/file content, please let me know.