Short Response Error - Unable to download any work units

[Kitchi]

Hi,

I've been getting the following errors since I installed the FAHClient a few days ago. I initially thought it could be a server error, since a few forum posts had the same problem and were resolved when the server came back up. However I am able to ping the IP address and access it through a browser. So the server seems to be up, and the connection isn't blocked.

I'm running a CentOS 7 X64 box, and installed FAH through the RPMs provided on the install page. Do let me know if I need to provide any more info! I've pasted the error message, ping and traceroute to the server below.

Error message

Code: Select all

06:32:14:WU00:FS00:Connecting to 171.67.108.200:8080
^[[93m06:32:14:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': 10002: Received short response, expected 272 bytes, got 0^[[0m
06:32:14:WU00:FS00:Connecting to 171.67.108.204:80
06:32:15:WU00:FS00:Assigned to work server 171.64.65.99
06:32:15:WU00:FS00:Requesting new work unit for slot 00: READY cpu:4 from 171.64.65.99
06:32:15:WU00:FS00:Connecting to 171.64.65.99:8080
^[[91m06:32:16:ERROR:WU00:FS00:Exception: 10002: Received short response, expected 512 bytes, got 0^[[0m
06:34:51:WU00:FS00:Connecting to 171.67.108.200:8080
^[[93m06:34:52:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': 10002: Received short response, expected 272 bytes, got 0^[[0m
06:34:52:WU00:FS00:Connecting to 171.67.108.204:80
06:34:53:WU00:FS00:Assigned to work server 171.64.65.124
06:34:53:WU00:FS00:Requesting new work unit for slot 00: READY cpu:4 from 171.64.65.124
06:34:53:WU00:FS00:Connecting to 171.64.65.124:8080
^[[91m06:34:53:ERROR:WU00:FS00:Exception: 10002: Received short response, expected 512 bytes, got 0

Ping results

Code: Select all

PING 171.64.65.124 (171.64.65.124) 56(84) bytes of data.
64 bytes from 171.64.65.124: icmp_seq=1 ttl=51 time=256 ms
64 bytes from 171.64.65.124: icmp_seq=2 ttl=51 time=260 ms
64 bytes from 171.64.65.124: icmp_seq=3 ttl=51 time=260 ms
64 bytes from 171.64.65.124: icmp_seq=4 ttl=51 time=257 ms
64 bytes from 171.64.65.124: icmp_seq=5 ttl=51 time=257 ms
^C
--- 171.64.65.124 ping statistics ---
6 packets transmitted, 5 received, 16% packet loss, time 5005ms
rtt min/avg/max/mdev = 256.175/258.194/260.238/1.732 ms

Traceroute

Code: Select all

traceroute to 171.64.65.124 (171.64.65.124), 30 hops max, 60 byte packets
 1  192.168.8.1 (192.168.8.1)  0.487 ms  0.981 ms  1.213 ms
 2  192.168.1.3 (192.168.1.3)  0.184 ms  0.177 ms  0.186 ms
 3  210.212.192.129 (210.212.192.129)  0.947 ms  0.927 ms  1.021 ms
 4  172.24.194.30 (172.24.194.30)  3.874 ms  3.790 ms  4.670 ms
 5  218.248.235.158 (218.248.235.158)  8.185 ms  8.142 ms  8.120 ms
 6  115.114.89.29.static-Mumbai.vsnl.net.in (115.114.89.29)  41.657 ms 115.114.131.141.static-mumbai.vsnl.net.in (115.114.131.141)  39.430 ms 115.114.89.29.static-mumbai.vsnl.net.in (115.114.89.29)  40.018 ms
 7  172.29.251.33 (172.29.251.33)  39.995 ms  39.345 ms  39.622 ms
 8  ix-7-1331.tcore1.HK2-Hong-Kong.as6453.net (116.0.67.121)  260.229 ms  259.180 ms  258.133 ms
 9  hurricaneelectric3-10G.hkix.net (123.255.91.158)  344.497 ms  344.476 ms  342.941 ms
10  10ge1-1.core1.lax2.he.net (184.105.223.169)  295.612 ms  295.604 ms  296.067 ms
11  10ge1-13.core1.lax2.he.net (184.105.223.105)  252.408 ms  271.105 ms  271.080 ms
12  100ge2-1.core1.lax1.he.net (72.52.92.121)  240.572 ms  241.383 ms 10ge5-2.core1.pao1.he.net (72.52.92.69)  253.784 ms
13  100ge15-1.core1.sjc2.he.net (184.105.223.249)  255.916 ms  251.298 ms stanford-university.10gigabitethernet1-4.core1.pao1.he.net (216.218.209.118)  256.848 ms
14  csmx-west-rtr.SUNet (171.64.255.214)  258.364 ms  265.178 ms 10ge5-2.core1.pao1.he.net (72.52.92.69)  264.596 ms
15  vspg14e.stanford.edu (171.64.65.124)  255.212 ms !X stanford-university.10gigabitethernet1-4.core1.pao1.he.net (216.218.209.118)  253.511 ms vspg14e.stanford.edu (171.64.65.124)  255.625 ms !X

[Joe_H]

Welcome to the folding support forum.

Generally this message is caused by a firewall or anti-malware setting blocking transfer of data. The FAHClient process needs the same access to transfer over ports 80 and 8080 as a browser such as Firefox. The fact that you can access the Assignment Server's address through a web browser is a good indication your are not blocked in general.

Additional useful information for troubleshooting a problem is contained in the first 100 or so lines of your log file. That shows which client you are using, system info about your configuration including OS such as 32 bit vs. 64 bit, and the configuration settings used for the client.

[Kitchi]

Thanks for the really quick response!

I've pasted the beginning of the log file below.

Code: Select all

*********************** Log Started 2015-07-03T06:25:48Z ***********************
06:25:48:************************* Folding@home Client *************************
06:25:48:    Website: http://folding.stanford.edu/
06:25:48:  Copyright: (c) 2009-2014 Stanford University
06:25:48:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
06:25:48:       Args: --child --lifeline 28579 /etc/fahclient/config.xml --run-as
06:25:48:             fahclient --pid-file=/var/run/fahclient.pid --daemon
06:25:48:     Config: /etc/fahclient/config.xml
06:25:48:******************************** Build ********************************
06:25:48:    Version: 7.4.4
06:25:48:       Date: Mar 4 2014
06:25:48:       Time: 12:01:17
06:25:48:    SVN Rev: 4130
06:25:48:     Branch: fah/trunk/client
06:25:48:   Compiler: GNU 4.1.2 20080704 (Red Hat 4.1.2-46)
06:25:48:    Options: -std=gnu++98 -O3 -funroll-loops -mfpmath=sse -ffast-math
06:25:48:             -fno-unsafe-math-optimizations -msse2
06:25:48:   Platform: linux2 2.6.18-164.11.1.el5
06:25:48:       Bits: 64
06:25:48:       Mode: Release
06:25:48:******************************* System ********************************
06:25:48:        CPU: Intel(R) Core(TM)2 Quad CPU Q9650 @ 3.00GHz
06:25:48:     CPU ID: GenuineIntel Family 6 Model 23 Stepping 10
06:25:48:       CPUs: 4
06:25:48:     Memory: 3.73GiB
06:25:48:Free Memory: 115.60MiB
06:25:48:    Threads: POSIX_THREADS
06:25:48: OS Version: 3.10
06:25:48:Has Battery: false
06:25:48: On Battery: false
06:25:48: UTC Offset: 5
06:25:48:        PID: 28581
06:25:48:        CWD: /var/lib/fahclient
06:25:48:         OS: Linux 3.10.0-229.4.2.el7.x86_64 x86_64
06:25:48:    OS Arch: AMD64
06:25:48:       GPUs: 1
06:25:48:      GPU 0: NVIDIA:1 G86 [Quadro NVS 290]
06:25:48:       CUDA: Not detected
06:25:48:***********************************************************************
06:25:48:<config>
06:25:48:  <!-- Folding Slot Configuration -->
06:25:48:  <gpu v='false'/>
06:25:48:
06:25:48:  <!-- Slot Control -->
06:25:48:  <power v='FULL'/>
06:25:48:
06:25:48:  <!-- User Information -->
06:25:48:  <team v='45032'/>
06:25:48:  <user v='Kitchi'/>
06:25:48:
06:25:48:  <!-- Folding Slots -->
06:25:48:  <slot id='0' type='CPU'/>
06:25:48:</config>
06:25:48:Switching to user fahclient
06:25:48:Trying to access database...
06:25:48:Successfully acquired database lock
06:25:48:Enabled folding slot 00: READY cpu:4
06:25:50:WU00:FS00:Connecting to 171.67.108.200:8080
^[[93m06:25:51:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': 10002: Received short response, expected 272 bytes, got 0^[[0m
06:25:51:WU00:FS00:Connecting to 171.67.108.204:80
06:25:52:WU00:FS00:Assigned to work server 171.64.65.124
06:25:52:WU00:FS00:Requesting new work unit for slot 00: READY cpu:4 from 171.64.65.124
06:25:52:WU00:FS00:Connecting to 171.64.65.124:8080
^[[91m06:25:53:ERROR:WU00:FS00:Exception: 10002: Received short response, expected 512 bytes, got 0^[[0m

I'll also have a look at the firewall settings on the OS to see if there's any way to allow FAH through.

[7im]

Please also consider adding a Passkey number to enable bonus points.

[Kitchi]

I haven't taken a look at the firewall yet. But meanwhile I downloaded the NaCl client for the Chrome browser, which is also complaining that it cannot download FAH onto the browser.

Since the NaCl client runs in-browser, I expected it to work without any issues. Or does it not access the FAH servers via HTTP?

I'm at a university where we have mostly unrestricted access to the internet, except a few websites deemed "harmful". And since I can ping the FAH servers, clearly they aren't blocked. I'm really confused about why the FAH client is unable to connect to the server when other methods of trying to contact the servers seem to work fine.

[bruce]

I agree with Joe_H.

What security software is running on your computer? It's not uncommon for a good firewall and/or anti-spyware software will automatically block any site that's not on that company's White List -- treating FAHClient as unknown software trying to contact an unknown site. Temporarily disable that software to confirm it's the culprit. Then find a way to create an exception allowing the connection to go through.

[Kitchi]

Since I'm running CentOS, I had to disable the iptables process. So now I have completely turned off the firwall, but I'm still getting the same "short response" errors.

Does the FAH Client need to connect through *both* port 80 and port 8080, or is only one enough? Maybe my university has blocked port 8080, I'll need to check with IT about that.

Meanwhile, below are my iptables rules (everything is set to accept)

Code: Select all

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination      

and the same error message as last time

Code: Select all

11:07:13:WU00:FS00:Requesting new work unit for slot 00: READY cpu:4 from 171.64
.65.124
11:07:13:WU00:FS00:Connecting to 171.64.65.124:8080
^[91m11:07:13:ERROR:WU00:FS00:Exception: 10002: Received short response, expecte
d 512 bytes, got 0^[0m
11:09:48:WU00:FS00:Connecting to 171.67.108.200:8080
^[93m11:09:49:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:80
80': 10002: Received short response, expected 272 bytes, got 0^[0m
11:09:49:WU00:FS00:Connecting to 171.67.108.204:80
11:09:50:WU00:FS00:Assigned to work server 171.64.65.99
11:09:50:WU00:FS00:Requesting new work unit for slot 00: READY cpu:4 from 171.64
.65.99
11:09:50:WU00:FS00:Connecting to 171.64.65.99:8080
^[91m11:09:51:ERROR:WU00:FS00:Exception: 10002: Received short response, expecte
d 512 bytes, got 0^[0m

This is getting stranger and stranger. Any ideas?

Thanks for all the help so far!

[ChristianVirtual]

Can you try you use the addresses above in a browser ? You should get a browser response (like simple an OK or even a nice logo)

[Kitchi]

@ChristianVirtual - Yup, I can access the addresses just fine in a browser. I get the FAH logo, and the work server version etc.

I can also ping the servers with no issues. The only problem seems to be that the FAH client is unable to reach the server (even with my firewall turned off!). The NaCl client on Chrome also faced the same issue, complaining that it could not access the internet.

I'm really very confused about what the issue is!

[bruce]

The browser will use port 80 by default, and that should be sufficient for FAH. Port 8080 is probably blocked by the university. You can test that by opening http://171.64.65.124:8080 in your browser.

I would call the commuter support line and ask them about whether the university has a proxy on port 8080 and if so, how to connect to it correctly. FAH has a tab under Configure called Proxy that may need to be configured.

[Kitchi]

So I can confirm that both port 80 and port 8080 are open. I'm running through a transparent proxy, so I don't have to set anything up on my computer to access the internet.

I've completly turned off the firewall, so it cannot be the firewall that is blocking the connection. My guess is that there is something causing the client to *not* use either port 80 or 8080 to connect to the server, because I even tried routing the NaCl chrome client through the Tor network (which should allow me to access sites blocked by the University) but that didn't work either.

Does the client "tunnel" through another port to access 80/8080? I'm running everything through the command line, since the GUI requires library versions older than what my distro supplies.

Thanks so much for the help so far guys! I really appreciate it.

[bruce]

If I remember correctly, all FAH servers associated with WUs prefer port 8080. Communications received/sent on port 80 are redirected by iptables at the server, itself.

[Joe_H]

You probably will need to talk with your computer support people to see how their "transparent proxy" is set up. Ordinarily you should not have to do any additional setup, but the folding client may need additional settings to point to the proxy server. Since you are running through the command line, I am not certain of the format to add that information as it is usually configured through the FAHControl GUI.

[Kitchi]

So that's not a problem at my end then. Looks like I'll have to dig still deeper to see what the problem is!

Thanks for your help! I'll post back if I have any updates, or if anyone needs more info.

EDIT: @Joe_H - As far as I know, the GUI just adds to the config.xml file, so if I do that by hand it should have the same effect. So I'll have to fiddle around with this and see what I can find. It's a real shame that it isn't running straight out of the box, because there are several (~ 50) computers here that sit idle most of the time that could do some folding in their spare time!

[Joe_H]

That is true, but you need to be careful editing the config.xml file by hand. It can easily be made unusable, and cause the client to be inaccessible. Normally we only recommend making changes to the config.xml client through the control interfaces as sanity checks are made in the process. Better would be to see if you can create a setup on a system with the GUI and copy that config.xml file over with a minimum of changes made.