Page 1 of 1

Unable to connect to client on Windows 10

Posted: Mon Mar 23, 2020 7:49 pm
by Don_Thate
This is my fourth F@H install this week on my network, and the second on Windows 10; three machines are happily crunching away (when there are WUs, anyway) but the fourth can't connect to the client on itself for some reason. I don't think the client is actually starting. Default install with config set up to use my ID, team, and passkey. It just sits at 'Connecting'.

Log for reference:

Code: Select all

*********************** Log Started 2020-03-23T19:42:38Z ***********************
19:42:38:************************* Folding@home Client *************************
19:42:38:      Website: https://foldingathome.org/
19:42:38:    Copyright: (c) 2009-2018 foldingathome.org
19:42:38:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
19:42:38:         Args: --open-web-control
19:42:38:       Config: C:\Users\****\AppData\Roaming\FAHClient\config.xml
19:42:38:******************************** Build ********************************
19:42:38:      Version: 7.5.1
19:42:38:         Date: May 11 2018
19:42:38:         Time: 13:06:32
19:42:38:   Repository: Git
19:42:38:     Revision: 4705bf53c635f88b8fe85af7675557e15d491ff0
19:42:38:       Branch: master
19:42:38:     Compiler: Visual C++ 2008
19:42:38:      Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
19:42:38:     Platform: win32 10
19:42:38:         Bits: 32
19:42:38:         Mode: Release
19:42:38:******************************* System ********************************
19:42:38:          CPU: AMD Ryzen 3 2200G with Radeon Vega Graphics
19:42:38:       CPU ID: AuthenticAMD Family 23 Model 17 Stepping 0
19:42:38:         CPUs: 4
19:42:38:       Memory: 5.94GiB
19:42:38:  Free Memory: 4.22GiB
19:42:38:      Threads: WINDOWS_THREADS
19:42:38:   OS Version: 6.2
19:42:38:  Has Battery: false
19:42:38:   On Battery: false
19:42:38:   UTC Offset: -4
19:42:38:          PID: 9548
19:42:38:          CWD: C:\Users\****\AppData\Roaming\FAHClient
19:42:38:           OS: Windows 10 Enterprise
19:42:38:      OS Arch: AMD64
19:42:38:         GPUs: 1
19:42:38:        GPU 0: Bus:6 Slot:0 Func:0 AMD:5 Raven [Ryzen vega 8 mobile]
19:42:38:         CUDA: Not detected: Failed to open dynamic library 'nvcuda.dll': The
19:42:38:               specified module could not be found.
19:42:38:
19:42:38:       OpenCL: Not detected: Win32: 0xc0000005: Exception access violation
19:42:38:Win32 Service: false
19:42:38:***********************************************************************
19:42:38:<config>
19:42:38:  <!-- Network -->
19:42:38:  <proxy v=':8080'/>
19:42:38:
19:42:38:  <!-- Slot Control -->
19:42:38:  <power v='FULL'/>
19:42:38:
19:42:38:  <!-- User Information -->
19:42:38:  <passkey v='********************************'/>
19:42:38:  <team v='******'/>
19:42:38:  <user v='******'/>
19:42:38:
19:42:38:  <!-- Folding Slots -->
19:42:38:  <slot id='0' type='CPU'/>
19:42:38:  <slot id='1' type='GPU'/>
19:42:38:</config>
19:42:38:Trying to access database...
19:42:38:Successfully acquired database lock
19:42:38:Enabled folding slot 00: READY cpu:3

Re: Unable to connect to client on Windows 10

Posted: Tue Mar 24, 2020 9:23 pm
by Don_Thate
Bumping for visibility. I've allowed FAHClient and FAHControl through the local Windows 10 firewall and still no dice. It's my only machine not folding!

Re: Unable to connect to client on Windows 10

Posted: Tue Mar 24, 2020 11:32 pm
by Jesse_V
Welcome to the forum and thanks for the bump. There are so many new threads it's hard for all us to keep up!

On the fourth computer, how did you install the software? How are you starting F@h? Is the setup any different from the other Windows machines?

Re: Unable to connect to client on Windows 10

Posted: Wed Mar 25, 2020 12:42 am
by Don_Thate
Thanks, Jesse! I know the team has been swamped with new folders, and I'm no exception. I appreciate the reply.

I installed F@H 7.5.1 with the regular installer, Express mode, and selected to run after closing the installer. I also see FAHClient.exe running at startup, but that's it. The only difference between this and my other machines is that I installed it over Remote Desktop, instead of connected directly. The machine also runs Backblaze for my cloud backup needs.

Hope this helps!

Re: Unable to connect to client on Windows 10

Posted: Wed Mar 25, 2020 12:44 am
by bruce
Find FAH's log and post the first few pages.

Is the security software blocking internet connections?

Re: Unable to connect to client on Windows 10

Posted: Wed Mar 25, 2020 2:31 am
by Don_Thate
Sure thing! Below are the contents of the log.txt file in my FAHClient folder in AppData, and a warning I found in Event Viewer. It doesn't look like it's even having an issue connecting to the internet, but that the client is never starting on port 36330 locally (or any port, when I search by PID using the output of netstat -ano).

Also worth noting there's no more or less security software on this desktop than any of the other four, and they're all on the same LAN.

Code: Select all

*********************** Log Started 2020-03-25T00:34:18Z ***********************
00:34:18:************************* Folding@home Client *************************
00:34:18:      Website: https://foldingathome.org/
00:34:18:    Copyright: (c) 2009-2018 foldingathome.org
00:34:18:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
00:34:18:         Args: --open-web-control
00:34:18:       Config: <none>
00:34:18:******************************** Build ********************************
00:34:18:      Version: 7.5.1
00:34:18:         Date: May 11 2018
00:34:18:         Time: 13:06:32
00:34:18:   Repository: Git
00:34:18:     Revision: 4705bf53c635f88b8fe85af7675557e15d491ff0
00:34:18:       Branch: master
00:34:18:     Compiler: Visual C++ 2008
00:34:18:      Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
00:34:18:     Platform: win32 10
00:34:18:         Bits: 32
00:34:18:         Mode: Release
00:34:18:******************************* System ********************************
00:34:18:          CPU: AMD Ryzen 3 2200G with Radeon Vega Graphics
00:34:18:       CPU ID: AuthenticAMD Family 23 Model 17 Stepping 0
00:34:18:         CPUs: 4
00:34:18:       Memory: 5.94GiB
00:34:18:  Free Memory: 3.88GiB
00:34:18:      Threads: WINDOWS_THREADS
00:34:18:   OS Version: 6.2
00:34:18:  Has Battery: false
00:34:18:   On Battery: false
00:34:18:   UTC Offset: -4
00:34:18:          PID: 8760
00:34:18:          CWD: C:\Users\Dana\AppData\Roaming\FAHClient
00:34:18:           OS: Windows 10 Enterprise
00:34:18:      OS Arch: AMD64
00:34:18:         GPUs: 0
00:34:18:         CUDA: Not detected: Failed to open dynamic library 'nvcuda.dll': The
00:34:18:               specified module could not be found.
00:34:18:
00:34:18:       OpenCL: Not detected: Win32: 0xc0000005: Exception access violation
00:34:18:Win32 Service: false
00:34:18:***********************************************************************
00:34:18:<config>
00:34:18:  <!-- Folding Slots -->
00:34:18:</config>
00:34:18:Connecting to assign1.foldingathome.org:8080
00:34:18:Updated GPUs.txt
00:34:18:Read GPUs.txt
00:34:18:Trying to access database...
00:34:18:Successfully acquired database lock
00:34:18:Enabled folding slot 00: PAUSED cpu:2 (not configured)

Code: Select all

C:\Program Files (x86)\FAHClient\FAHClient.exe
Exception: Failed to connect to 127.0.0.1:36330: No connection could be made because the target machine actively refused it.

Re: Unable to connect to client on Windows 10

Posted: Sat Mar 28, 2020 2:36 pm
by Don_Thate
Another bump in an attempt to fix this, though I understand how quickly these get lost!

Re: Unable to connect to client on Windows 10

Posted: Sat Mar 28, 2020 2:48 pm
by kostuek

Code: Select all

00:34:18:       OpenCL: Not detected: Win32: 0xc0000005: Exception access violation
From this my wild guess is, that the FAHClient is missing some local rights on that machine.

Re: Unable to connect to client on Windows 10

Posted: Sat Mar 28, 2020 2:51 pm
by ajm
I know how it's going to sound, but have you tried to reboot the machine?
The "not configured" issue already has been solved this way, here: viewtopic.php?f=61&t=33181&hilit=not+configured

EDIT: I read further that this error message can indicate out of date drivers. It should not happen in win10, but the automatic update is maybe deactivated?

Re: Unable to connect to client on Windows 10

Posted: Sat Mar 28, 2020 3:03 pm
by Don_Thate
Automatic updates are enabled and the machine is rebooted nightly, but I'll check for UEFI updates and new driver versions manually!

Re: Unable to connect to client on Windows 10

Posted: Sat Mar 28, 2020 7:21 pm
by Joe_H
Also, if you have automatic update on the video drivers you may want to turn it off while folding. The updates provided by MS through Windows Update usually do not include the OpenCL support, and may remove it when they install.

One way to keep ahead of MS and this is to have recent enough drivers installed from AMD or nVidia that Windows Update doesn't see them as needing any update.