Page 1 of 2
Problem connecting to server
Posted: Thu Aug 22, 2013 10:38 pm
by iuchiban
Hi there
I'm not a complete newbie to FaH; I have been working for a while on one PC, but now I'm trying to configure a second one. Unfortunately, I'm getting an error connecting to the remote server. Here's a verbose (logging level 5) log snippet:
Code: Select all
22:34:59:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
22:35:00:2:127.0.0.1 GET /ping?_=1377210900474&callback=jQuery190020738450561479804_1377210900473
22:35:00:WARNING:WU00:FS01:Failed to get ID from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: No connection could be made because the target machine actively refused it.
22:35:00:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
22:35:00:1:127.0.0.1 GET /?nocache=0.4603473277206162
22:35:01:WARNING:WU00:FS01:Failed to get ID from 'assign-GPU.stanford.edu:8080': Failed to connect to assign-GPU.stanford.edu:8080: No connection could be made because the target machine actively refused it.
22:35:01:ERROR:WU00:FS01:Exception: Could not get an assignment ID
22:35:02:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
22:35:02:4:127.0.0.1 GET /js/main.js?nocache=0.411685406528804
22:35:02:4:127.0.0.1:New Web connection
22:35:02:5:127.0.0.1 GET /css/style.css?nocache=0.11597369843166044
22:35:02:WU01:FS00:Connecting to assign-GPU.stanford.edu:80
22:35:03:3:127.0.0.1 GET /api/updates/set?sid=0x8b7af028220c2284b6d30dec3c2f5dde&update_id=0&update_path=/api/basic&update_rate=1
22:35:03:WARNING:WU00:FS01:Failed to get ID from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: No connection could be made because the target machine actively refused it.
22:35:03:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
22:35:03:6:127.0.0.1 GET /api/updates/set?sid=0x8b7af028220c2284b6d30dec3c2f5dde&update_id=1&update_path=/api/slots&update_rate=1
22:35:03:7:127.0.0.1 GET /api/configured?sid=0x8b7af028220c2284b6d30dec3c2f5dde
22:35:03:8:127.0.0.1 GET /api/updates?sid=0x8b7af028220c2284b6d30dec3c2f5dde
22:35:03:WARNING:WU01:FS00:Failed to get ID from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: No connection could be made because the target machine actively refused it.
22:35:03:WU01:FS00:Connecting to assign-GPU.stanford.edu:8080
22:35:03:8:127.0.0.1 GET /api/updates?sid=0x8b7af028220c2284b6d30dec3c2f5dde
22:35:04:WARNING:WU00:FS01:Failed to get ID from 'assign-GPU.stanford.edu:8080': Failed to connect to assign-GPU.stanford.edu:8080: No connection could be made because the target machine actively refused it.
22:35:04:ERROR:WU00:FS01:Exception: Could not get an assignment ID
22:35:04:9:127.0.0.1 GET /api/updates?sid=0x8b7af028220c2284b6d30dec3c2f5dde
22:35:04:WARNING:WU01:FS00:Failed to get ID from 'assign-GPU.stanford.edu:8080': Failed to connect to assign-GPU.stanford.edu:8080: No connection could be made because the target machine actively refused it.
22:35:04:ERROR:WU01:FS00:Exception: Could not get an assignment ID
22:35:04:WU01:FS00:Connecting to assign-GPU.stanford.edu:80
22:35:05:WARNING:WU01:FS00:Failed to get ID from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: No connection could be made because the target machine actively refused it.
22:35:05:WU01:FS00:Connecting to assign-GPU.stanford.edu:8080
22:35:06:8:127.0.0.1 GET /api/updates?sid=0x8b7af028220c2284b6d30dec3c2f5dde
22:35:06:WARNING:WU01:FS00:Failed to get ID from 'assign-GPU.stanford.edu:8080': Failed to connect to assign-GPU.stanford.edu:8080: No connection could be made because the target machine actively refused it.
22:35:06:ERROR:WU01:FS00:Exception: Could not get an assignment ID
22:35:08:8:127.0.0.1 GET /api/updates?sid=0x8b7af028220c2284b6d30dec3c2f5dde
22:35:09:WARNING:Exception: 6:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
22:35:09:WARNING:Exception: 7:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
22:35:10:WARNING:Exception: 9:127.0.0.1: Send error: 10054: An existing connection was forcibly closed by the remote host.
22:35:11:Started thread 8 on PID 7408
22:35:15:WARNING:Exception: 8:127.0.0.1: Send error: 10054: An existing connection was forcibly closed by the remote host.
22:35:16:Started thread 9 on PID 7408
My other PC, on the same local network, is working fine. I have ensured that firewall exceptions exist, as well as opened the specific port, and I have also tried disabling the firewall altogether. So I don't think it is a firewall problem, though I could well be missing something.
Any other suggestions?
Thanks in advance!
Cheers, Don.
Mod Edit: Added Code tags to log
Re: Problem connecting to server
Posted: Thu Aug 22, 2013 10:46 pm
by 7im
Hello iuchiban, welcome to the forum.
Level 3 verbosity is recommended.
Please post the *** System *** section of the log, and the config section. Thanks.
Re: Problem connecting to server
Posted: Thu Aug 22, 2013 10:47 pm
by Joe_H
Welcome to the Folding forum.
Could you post your log from the beginning so that it includes the version and system information. Also, please reset the verbosity level to the default of 3. Higher levels set in the client rarely provide useful additional information and get in the way of troubleshooting a folding setup.
Re: Problem connecting to server
Posted: Thu Aug 22, 2013 10:51 pm
by iuchiban
Hehe, no problem; I wasn't sure if the verbose setting helped or not
Here's a full log, after closing and re-opening the client:
Code: Select all
*********************** Log Started 2013-08-22T22:50:19Z ***********************
22:50:19:************************* Folding@home Client *************************
22:50:19: Website: http://folding.stanford.edu/
22:50:19: Copyright: (c) 2009-2013 Stanford University
22:50:19: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
22:50:19: Args: --open-web-control
22:50:19: Config: C:/Users/Donald.Gardner/AppData/Roaming/FAHClient/config.xml
22:50:19:******************************** Build ********************************
22:50:19: Version: 7.3.6
22:50:19: Date: Feb 18 2013
22:50:19: Time: 15:25:17
22:50:19: SVN Rev: 3923
22:50:19: Branch: fah/trunk/client
22:50:19: Compiler: Intel(R) C++ MSVC 1500 mode 1200
22:50:19: Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
22:50:19: /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
22:50:19: Platform: win32 XP
22:50:19: Bits: 32
22:50:19: Mode: Release
22:50:19:******************************* System ********************************
22:50:19: CPU: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz
22:50:19: CPU ID: GenuineIntel Family 6 Model 58 Stepping 9
22:50:19: CPUs: 4
22:50:19: Memory: 15.94GiB
22:50:19: Free Memory: 13.47GiB
22:50:19: Threads: WINDOWS_THREADS
22:50:19: Has Battery: false
22:50:19: On Battery: false
22:50:19: UTC offset: 12
22:50:19: PID: 5992
22:50:19: CWD: C:/Users/Donald.Gardner/AppData/Roaming/FAHClient
22:50:19: OS: Windows 7 Enterprise
22:50:19: OS Arch: AMD64
22:50:19: GPUs: 1
22:50:19: GPU 0: ATI:4 Cedar PRO [Radeon HD 5450]
22:50:19: CUDA: Not detected
22:50:19:Win32 Service: false
22:50:19:***********************************************************************
22:50:19:<config>
22:50:19: <!-- HTTP Server -->
22:50:19: <allow v='127.0.0.1 0/0'/>
22:50:19: <deny v=''/>
22:50:19:
22:50:19: <!-- Network -->
22:50:19: <proxy v='sts-chc-isa:8080'/>
22:50:19:
22:50:19: <!-- Remote Command Server -->
22:50:19: <command-allow-no-pass v='127.0.0.1 0/0'/>
22:50:19: <command-deny-no-pass v=''/>
22:50:19:
22:50:19: <!-- User Information -->
22:50:19: <passkey v='********************************'/>
22:50:19: <team v='169927'/>
22:50:19: <user v='iuchiban'/>
22:50:19:
22:50:19: <!-- Folding Slots -->
22:50:19: <slot id='0' type='GPU'/>
22:50:19: <slot id='1' type='CPU'/>
22:50:19:</config>
22:50:19:Connecting to assign-GPU.stanford.edu:80
22:50:20:WARNING:Attempting to update GPUs.txt: Failed to connect to assign-GPU.stanford.edu:80: No connection could be made because the target machine actively refused it.
22:50:20:Trying to access database...
22:50:20:Successfully acquired database lock
22:50:20:Enabled folding slot 00: PAUSED gpu:0:Cedar PRO [Radeon HD 5450] (waiting for idle)
22:50:20:Enabled folding slot 01: READY cpu:3
22:50:21:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
22:50:21:WU01:FS00:Connecting to assign-GPU.stanford.edu:80
22:50:22:WARNING:WU00:FS01:Failed to get ID from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: No connection could be made because the target machine actively refused it.
22:50:22:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
22:50:22:WARNING:WU01:FS00:Failed to get ID from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: No connection could be made because the target machine actively refused it.
22:50:22:WU01:FS00:Connecting to assign-GPU.stanford.edu:8080
22:50:23:WARNING:WU00:FS01:Failed to get ID from 'assign-GPU.stanford.edu:8080': Failed to connect to assign-GPU.stanford.edu:8080: No connection could be made because the target machine actively refused it.
22:50:23:ERROR:WU00:FS01:Exception: Could not get an assignment ID
22:50:23:WU00:FS01:Connecting to assign-GPU.stanford.edu:80
22:50:23:WARNING:WU01:FS00:Failed to get ID from 'assign-GPU.stanford.edu:8080': Failed to connect to assign-GPU.stanford.edu:8080: No connection could be made because the target machine actively refused it.
22:50:23:ERROR:WU01:FS00:Exception: Could not get an assignment ID
22:50:23:WU01:FS00:Connecting to assign-GPU.stanford.edu:80
22:50:24:WARNING:WU00:FS01:Failed to get ID from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: No connection could be made because the target machine actively refused it.
22:50:24:WU00:FS01:Connecting to assign-GPU.stanford.edu:8080
22:50:24:WARNING:WU01:FS00:Failed to get ID from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: No connection could be made because the target machine actively refused it.
22:50:24:WU01:FS00:Connecting to assign-GPU.stanford.edu:8080
22:50:25:WARNING:WU00:FS01:Failed to get ID from 'assign-GPU.stanford.edu:8080': Failed to connect to assign-GPU.stanford.edu:8080: No connection could be made because the target machine actively refused it.
22:50:25:ERROR:WU00:FS01:Exception: Could not get an assignment ID
22:50:26:WARNING:WU01:FS00:Failed to get ID from 'assign-GPU.stanford.edu:8080': Failed to connect to assign-GPU.stanford.edu:8080: No connection could be made because the target machine actively refused it.
22:50:26:ERROR:WU01:FS00:Exception: Could not get an assignment ID
22:50:27:3:127.0.0.1:New Web connection
22:50:30:WARNING:Exception: 6:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
22:50:30:WARNING:Exception: 7:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
22:50:30:WARNING:Exception: 8:127.0.0.1: Send error: 10054: An existing connection was forcibly closed by the remote host.
22:50:31:WARNING:Exception: 9:127.0.0.1: Send error: 10054: An existing connection was forcibly closed by the remote host.
Re: Problem connecting to server
Posted: Thu Aug 22, 2013 11:15 pm
by 7im
I see you have configured a proxy server. Is that necessary in this location? If not, try disabling it.
Re: Problem connecting to server
Posted: Thu Aug 22, 2013 11:41 pm
by iuchiban
I tried configuring a proxy server (our old server, now deprecated) to see if it would help. No joy though. It's currently disabled, so it shouldn't be doing anything.
Re: Problem connecting to server
Posted: Fri Aug 23, 2013 12:12 am
by Joe_H
Have you tried entering the IP address of the proxy server instead of the name? You might have to give the full hostname instead of shortened version you have entered.
Re: Problem connecting to server
Posted: Fri Aug 23, 2013 12:52 am
by bruce
iuchiban wrote:I tried configuring a proxy server (our old server, now deprecated) to see if it would help. No joy though. It's currently disabled, so it shouldn't be doing anything.
Do you really NEED a proxy server? In most installations, they're not needed and configuring FAH for one should not be attempted.
Re: Problem connecting to server
Posted: Fri Aug 23, 2013 1:27 am
by iuchiban
bruce wrote:iuchiban wrote:I tried configuring a proxy server (our old server, now deprecated) to see if it would help. No joy though. It's currently disabled, so it shouldn't be doing anything.
Do you really NEED a proxy server? In most installations, they're not needed and configuring FAH for one should not be attempted.
Yeah, I was pretty sure the proxy wouldn't help, but I gave it a try just in case it fixed the problem. No joy though, and as noted above, it's currently disabled.
(I also tried it with IP instead of machine name, as mentioned above; no luck there either).
Re: Problem connecting to server
Posted: Fri Aug 23, 2013 4:06 am
by bruce
Re: Problem connecting to server
Posted: Fri Aug 23, 2013 4:14 am
by iuchiban
Just tried that now; a plain white page with OK in black text. So I guess that means I can see the server then; I wonder why my client can't get a connection?
Re: Problem connecting to server
Posted: Fri Aug 23, 2013 5:58 am
by bruce
If your computer can make the connection from the browser but not from the client, you have one of the more advanced firewalls (sometimes included in an anti-virus suite) which is sometimes called anti-spyware. It blocks ALL outgoing connections that are not specifically authorized. You can confirm this by temporarily shutting down your AV suite or your firewall and confirming FAH can make the necessary connection. Then you have to figure out how to grant an exception to FAHClient.exe, allowing it to make outgoing connections.
Re: Problem connecting to server
Posted: Fri Aug 23, 2013 10:08 am
by bollix47
Another area that may be worth checking:
I realize that you've said you disabled your proxy but please check the config section of your folding log and make sure that
22:50:19: <proxy v='sts-chc-isa:8080'/>
now reads
??:??:??: <proxy v=':8080'/>
and that the box in front of "Enable Proxy Configuration" in the Proxy tab of your Configuration no longer has a check in it. If both those settings are now correct try restarting FAHClient. Sometimes a simple reboot can solve numerous
problems.
Re: Problem connecting to server
Posted: Tue Aug 27, 2013 11:11 pm
by iuchiban
Well, I have already added exceptions to the firewall for the FAHClient, as well as the specific port it is connecting on. I have also completely disabled the firewall. No joy though.
I also double checked my log, and all the proxy settings have been cleared. That hasn't helped either.
Any other suggestions?
Re: Problem connecting to server
Posted: Tue Aug 27, 2013 11:25 pm
by PantherX
Please note that while an exception added to the firewall is fine, F@H uses the web browsing ports, i.e. port 80 and 8080 thus you don't need to open up any other ports. As long as you can access the internet fine from your web browser, F@H should be able to connect to the servers as long as it isn't being blocked by the firewall, Anti-Virus, Anti-Malware applications.
After you restart your system, please post a fresh log section including the initial section so that we can see the current configuration and the error messages. Also, can you open the following pages in your web browser:
http://assign.stanford.edu:8080/
http://assign2.stanford.edu:80/
http://assign-gpu.stanford.edu/
http://assign-gpu.stanford.edu:8080/
Expected response is "OK" in black text on a white page.