155.247.166.219 & 155.247.166.220 are now hosed [Not Now]

Moderators: Site Moderators, PandeGroup

Re: 155.247.166.219 & 155.247.166.220 are now hosed [Not Now

Postby Joe_H » Thu Apr 05, 2018 8:42 pm

An additional thing to keep in mind is that your WU is among thousands returned each hour. The first of those servers is currently handling about 3000 returns an hour, the second about half that many. AT the same time that means they are also sending out about the same number of WU's.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Joe_H
Site Admin
 
Posts: 4124
Joined: Tue Apr 21, 2009 4:41 pm
Location: W. MA

Re: 155.247.166.219 & 155.247.166.220 are now hosed [Not Now

Postby e3072743 » Mon Apr 16, 2018 5:43 am

Is it possible to "blacklist" these servers somehow because they just don't seem to work for me... I tried disabling all my firewalls (hw & sw) but still no connection (not even with browser, neither :80 or :8080) other than PING which works fine. So I think this leaves pretty much either my ISP or server (geo?)block to blame?

CPU uses other servers and works fine all the time but for the GPU, once again, over the weekend my log looks like this :(

Code: Select all
12:56:03:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
12:56:03:WU00:FS01:Connecting to 155.247.166.219:8080
12:56:24:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
12:56:24:WU00:FS01:Connecting to 155.247.166.219:80
13:02:51:WU00:FS01:Connecting to 171.67.108.45:80
13:02:52:WU00:FS01:Assigned to work server 155.247.166.219
13:02:54:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
13:02:54:WU00:FS01:Connecting to 155.247.166.219:8080
13:03:15:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
13:03:15:WU00:FS01:Connecting to 155.247.166.219:80
13:13:57:WU00:FS01:Connecting to 171.67.108.45:80
13:13:57:WU00:FS01:Assigned to work server 155.247.166.219
13:14:00:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
13:14:00:WU00:FS01:Connecting to 155.247.166.219:8080
13:14:21:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
13:14:21:WU00:FS01:Connecting to 155.247.166.219:80
13:31:55:WU00:FS01:Connecting to 171.67.108.45:80
13:31:56:WU00:FS01:Assigned to work server 155.247.166.219
13:31:56:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
13:31:56:WU00:FS01:Connecting to 155.247.166.219:8080
13:32:18:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
13:32:18:WU00:FS01:Connecting to 155.247.166.219:80
14:00:56:WU00:FS01:Connecting to 171.67.108.45:80
14:00:56:WU00:FS01:Assigned to work server 155.247.166.219
14:00:59:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
14:00:59:WU00:FS01:Connecting to 155.247.166.219:8080
14:01:20:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
14:01:20:WU00:FS01:Connecting to 155.247.166.219:80
14:47:55:WU00:FS01:Connecting to 171.67.108.45:80
14:47:55:WU00:FS01:Assigned to work server 155.247.166.219
14:47:57:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
14:47:57:WU00:FS01:Connecting to 155.247.166.219:8080
14:48:18:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
14:48:18:WU00:FS01:Connecting to 155.247.166.219:80
******************************* Date: 2018-04-13 *******************************
16:03:57:WU00:FS01:Connecting to 171.67.108.45:80
16:03:58:WU00:FS01:Assigned to work server 155.247.166.219
16:03:58:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
16:03:58:WU00:FS01:Connecting to 155.247.166.219:8080
16:04:19:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
16:04:19:WU00:FS01:Connecting to 155.247.166.219:80
18:06:56:WU00:FS01:Connecting to 171.67.108.45:80
18:06:57:WU00:FS01:Assigned to work server 155.247.166.219
18:06:58:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
18:06:58:WU00:FS01:Connecting to 155.247.166.219:8080
18:07:19:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
18:07:19:WU00:FS01:Connecting to 155.247.166.219:80
21:25:57:WU00:FS01:Connecting to 171.67.108.45:80
21:25:58:WU00:FS01:Assigned to work server 155.247.166.219
21:25:58:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
21:25:58:WU00:FS01:Connecting to 155.247.166.219:8080
21:26:19:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
21:26:19:WU00:FS01:Connecting to 155.247.166.219:80
******************************* Date: 2018-04-13 *******************************
02:47:56:WU00:FS01:Connecting to 171.67.108.45:80
02:47:56:WU00:FS01:Assigned to work server 155.247.166.219
02:47:58:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
02:47:58:WU00:FS01:Connecting to 155.247.166.219:8080
02:48:19:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
02:48:19:WU00:FS01:Connecting to 155.247.166.219:80
******************************* Date: 2018-04-14 *******************************
08:47:57:WU00:FS01:Connecting to 171.67.108.45:80
08:47:58:WU00:FS01:Assigned to work server 155.247.166.219
08:47:58:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
08:47:58:WU00:FS01:Connecting to 155.247.166.219:8080
08:48:19:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
08:48:19:WU00:FS01:Connecting to 155.247.166.219:80
******************************* Date: 2018-04-14 *******************************
14:47:57:WU00:FS01:Connecting to 171.67.108.45:80
14:47:58:WU00:FS01:Assigned to work server 155.247.166.219
14:47:58:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
14:47:58:WU00:FS01:Connecting to 155.247.166.219:8080
14:48:19:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
14:48:19:WU00:FS01:Connecting to 155.247.166.219:80
******************************* Date: 2018-04-14 *******************************
20:47:57:WU00:FS01:Connecting to 171.67.108.45:80
20:47:57:WU00:FS01:Assigned to work server 155.247.166.219
20:47:59:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
20:47:59:WU00:FS01:Connecting to 155.247.166.219:8080
20:48:20:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
20:48:20:WU00:FS01:Connecting to 155.247.166.219:80
******************************* Date: 2018-04-14 *******************************
02:47:57:WU00:FS01:Connecting to 171.67.108.45:80
02:47:58:WU00:FS01:Assigned to work server 155.247.166.219
02:47:59:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
02:47:59:WU00:FS01:Connecting to 155.247.166.219:8080
02:48:20:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
02:48:20:WU00:FS01:Connecting to 155.247.166.219:80
******************************* Date: 2018-04-15 *******************************
08:47:57:WU00:FS01:Connecting to 171.67.108.45:80
08:47:58:WU00:FS01:Assigned to work server 155.247.166.219
08:47:59:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
08:47:59:WU00:FS01:Connecting to 155.247.166.219:8080
08:48:20:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
08:48:20:WU00:FS01:Connecting to 155.247.166.219:80
******************************* Date: 2018-04-15 *******************************
14:47:57:WU00:FS01:Connecting to 171.67.108.45:80
14:47:58:WU00:FS01:Assigned to work server 155.247.166.219
14:47:59:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
14:47:59:WU00:FS01:Connecting to 155.247.166.219:8080
14:48:20:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
14:48:20:WU00:FS01:Connecting to 155.247.166.219:80
******************************* Date: 2018-04-15 *******************************
20:47:57:WU00:FS01:Connecting to 171.67.108.45:80
20:47:58:WU00:FS01:Assigned to work server 155.247.166.219
20:47:59:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 155.247.166.219
20:47:59:WU00:FS01:Connecting to 155.247.166.219:8080
20:48:20:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
20:48:20:WU00:FS01:Connecting to 155.247.166.219:80
******************************* Date: 2018-04-15 *******************************
02:47:57:WU00:FS01:Connecting to 171.67.108.45:80
02:47:58:WU00:FS01:Assigned to work server 140.163.4.231
02:47:59:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GP104GL [xxx] from 140.163.4.231
02:47:59:WU00:FS01:Connecting to 140.163.4.231:8080
02:48:20:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
02:48:20:WU00:FS01:Connecting to 140.163.4.231:80
02:48:27:WU00:FS01:Downloading 16.52MiB
02:48:33:WU00:FS01:Download 81.34%
02:48:34:WU00:FS01:Download complete
e3072743
 
Posts: 5
Joined: Thu Mar 29, 2018 5:12 am

Re: 155.247.166.219 & 155.247.166.220 are now hosed [Not Now

Postby bruce » Mon Apr 16, 2018 7:44 pm

What does your browser say when you open http://155.247.166.219:8080/ or http://155.247.166.220:8080/

Blacklisting those servers (even if it's possible) would gain nothing. The Assignment Server is designed to direct your cli

Which version of FAHClient are you running?
bruce
 
Posts: 21403
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 155.247.166.219 & 155.247.166.220 are now hosed [Not Now

Postby e3072743 » Tue Apr 17, 2018 5:26 am

bruce wrote:What does your browser say when you open http://155.247.166.219:8080/ or http://155.247.166.220:8080/


In Chrome I get "ERR_CONNECTION_TIMED_OUT", same with :80. I'm using client v7.4.4.
e3072743
 
Posts: 5
Joined: Thu Mar 29, 2018 5:12 am

Re: 155.247.166.219 & 155.247.166.220 are now hosed [Not Now

Postby bruce » Tue Apr 17, 2018 3:22 pm

There are several factors in ivolved that can cause your FAHClient to fail to connect to those two (actually 4) URLs. Some problems can be resolved on your end and others require actions at the server.

First, let's talk about ports. At the server level, FAH actually uses port 8080. The servers are supposed to be configured to redirect port 80 to port 8080, but that doesn't always happen (especially on those two servers) and somebody has to re-enable that port redirection. On your end, if you connect through a proxy server, port 8080 may not work and only port 80 will work for you. Can you connect to port 8080 on ANY of FAH's servers? If that's a problem, you're probably using your employer's internet connection and how they handle their security is up to them.

Right now, I'm getting through to either server on port 8080 and both are timing out on port 80. I've notified the appropriate folks, so the first issue will probably be resolved shortly at the servers.

Next (3rd & 4th), it's possible that the security software on your computer is blocking all access to those servers or the servers, themselves, can be off-line. You can test that possibity by temporarily disabling your security software.

5th, the server may not have any more WUs that fit your configuration. The primary job of the Assignment Server is to find an active work server that DOES have WUs that fit your configuration. Ordinarily there are several valid choices it can make.

6th, if you have an unusual configuration (say your client is seeking an assignment for 7 CPUs, a combination which is not valid) there may not be any work for you.

As you can see, it's rather complicatged. When we're asked to fix "the problem" we have to gather enough information to figure out which issue is causing the problem. I can test 1, 2, and 4 from here. With a few questions, I can often get you to resolve 3 and maybe 6 on your end. Each possibility is generally quite rare.
bruce
 
Posts: 21403
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 155.247.166.219 & 155.247.166.220 are now hosed [Not Now

Postby e3072743 » Wed Apr 18, 2018 5:57 am

Thanks Bruce! I did some testing with the server list on http://fah-web.stanford.edu/pybeta/serverstat.html and it seems I'm unable to connect to ANY server with my browser using the port 8080. Port 80 does work with ALL available servers, except these two. Disabling my software firewall doesn't change anything so it must be some issue with my router/ISP blocking 8080. I don't have any proxies configured anywhere but maybe finding a good free one and setting it just for the FAHClient would be useful to try and avoid this issue. Hopefully fixing the port 80 on the server side will also help.
e3072743
 
Posts: 5
Joined: Thu Mar 29, 2018 5:12 am

Re: 155.247.166.219 & 155.247.166.220 are now hosed [Not Now

Postby stealthswifttlk » Thu Apr 19, 2018 7:17 pm

Is anyone else having slow upload to these servers again? I'm on a 80Mbit down/20Mbit up VDSL2+ in the UK and usually don't have any issues with F@h speeds, but it's just taken me nearly 15 minutes to upload a 1.77Megabyte WU return which I thought was being a bit too slow. I'd expect it to go up in under 5 minutes max, and that's with heavy contention due to time of day etc!

Code: Select all
18:45:54:WU02:FS01:0xa7:Folding@home Core Shutdown: FINISHED_UNIT
18:45:55:WU02:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
18:45:55:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13743 run:183 clone:3 gen:52 core:0xa7 unit:0x000000370002894b59d595e3eebd0e57
18:45:55:WU02:FS01:Uploading 1.77MiB to 155.247.166.219
18:45:55:WU02:FS01:Connecting to 155.247.166.219:8080
18:46:09:WU02:FS01:Upload 7.05%
18:46:17:WU02:FS01:Upload 10.57%
18:46:24:WU02:FS01:Upload 14.10%
18:46:39:WU02:FS01:Upload 17.62%
18:47:06:WU02:FS01:Upload 21.15%
18:47:26:WU02:FS01:Upload 24.67%
18:48:02:WU02:FS01:Upload 31.72%
18:48:22:WU02:FS01:Upload 35.25%
18:48:59:WU02:FS01:Upload 38.77%
18:49:28:WU02:FS01:Upload 42.30%
18:49:40:WU02:FS01:Upload 45.82%
18:49:52:WU02:FS01:Upload 49.35%
18:50:34:WU02:FS01:Upload 52.87%
18:51:28:WU02:FS01:Upload 56.40%
18:52:02:WU02:FS01:Upload 59.92%
18:53:06:WU02:FS01:Upload 63.45%
18:53:58:WU02:FS01:Upload 66.97%
18:54:07:WU02:FS01:Upload 70.49%
18:54:23:WU02:FS01:Upload 74.02%
18:54:42:WU02:FS01:Upload 77.54%
18:55:33:WU02:FS01:Upload 81.07%
18:55:41:WU02:FS01:Upload 84.59%
18:55:49:WU02:FS01:Upload 88.12%
18:56:15:WU02:FS01:Upload 91.64%
18:56:29:WU02:FS01:Upload 95.17%
18:56:43:WU02:FS01:Upload 98.69%
18:56:59:WU02:FS01:Upload 100.00%
18:58:05:WU02:FS01:Upload complete
18:58:05:WU02:FS01:Server responded WORK_ACK (400)


The server URL in chrome returns a "Work Server Version 9.2.5" page for me at present, the server is up and responding normally but being quite slow, at least from this end.

Code: Select all
C:\Windows\system32>tracert 155.247.166.219

Tracing route to vav3.ocis.temple.edu [155.247.166.219]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    12 ms    13 ms    12 ms  be436.pr2.enlba.isp.sky.com [89.200.131.252]
  4    15 ms    12 ms    11 ms  ae3.cr11-lon1.ip4.gtt.net [77.67.74.93]
  5    11 ms    11 ms    11 ms  be3008.ccr21.lon01.atlas.cogentco.com [130.117.15.21]
  6    11 ms    11 ms    11 ms  be2871.ccr42.lon13.atlas.cogentco.com [154.54.58.185]
  7    81 ms    81 ms    81 ms  be2490.ccr42.jfk02.atlas.cogentco.com [154.54.42.85]
  8    84 ms    84 ms    85 ms  be2333.rcr22.phl01.atlas.cogentco.com [154.54.5.2]
  9    84 ms    85 ms    89 ms  be3164.rcr21.phl03.atlas.cogentco.com [154.54.25.142]
 10    84 ms    84 ms    84 ms  38.140.148.74
 11     *        *        *     Request timed out.
 12    86 ms    86 ms    86 ms  vav3.ocis.temple.edu [155.247.166.219]

Trace complete.


*additional in edit* To put this into further context, a few minutes earlier from the same machine a GPU WU uploaded to a different server from the same desktop:

Code: Select all
18:36:52:WU00:FS00:0x21:Folding@home Core Shutdown: FINISHED_UNIT
18:36:52:WU00:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
18:36:52:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:11713 run:0 clone:83 gen:139 core:0x21 unit:0x0000009c8ca304e75a5a521b3b09e416
18:36:52:WU00:FS00:Uploading 11.82MiB to 140.163.4.231
18:36:52:WU00:FS00:Connecting to 140.163.4.231:8080
18:36:58:WU00:FS00:Upload 5.81%
18:37:04:WU00:FS00:Upload 12.16%
18:37:10:WU00:FS00:Upload 17.97%
18:37:16:WU00:FS00:Upload 24.32%
18:37:22:WU00:FS00:Upload 30.66%
18:37:28:WU00:FS00:Upload 37.00%
18:37:34:WU00:FS00:Upload 43.35%
18:37:40:WU00:FS00:Upload 49.69%
18:37:46:WU00:FS00:Upload 56.03%
18:37:52:WU00:FS00:Upload 62.37%
18:37:58:WU00:FS00:Upload 68.72%
18:38:04:WU00:FS00:Upload 75.06%
18:38:10:WU00:FS00:Upload 81.40%
18:38:16:WU00:FS00:Upload 87.22%
18:38:22:WU00:FS00:Upload 93.56%
18:38:28:WU00:FS00:Upload 99.91%
18:38:28:WU00:FS00:Upload complete
18:38:28:WU00:FS00:Server responded WORK_ACK (400)

So I surmised that my connection and settings this side are working fine...
stealthswifttlk
 
Posts: 14
Joined: Fri Aug 29, 2008 9:01 pm
Location: Sheffield, UK

Re: 155.247.166.219 & 155.247.166.220 are now hosed [Not Now

Postby stealthswifttlk » Sat Apr 21, 2018 8:07 pm

A little over 24 hours later and someone must have kicked it in to touch a little, as this is more in line with what I would usually be expecting! Similar filesize upload to the same server just now from the same desktop on the same connection.

Code: Select all
20:00:39:WU02:FS01:0xa7:Folding@home Core Shutdown: FINISHED_UNIT
20:00:39:WU02:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
20:00:39:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:13738 run:195 clone:2 gen:92 core:0xa7 unit:0x000000650002894b59d54600fb37b71b
20:00:39:WU02:FS01:Uploading 1.76MiB to 155.247.166.219
20:00:39:WU02:FS01:Connecting to 155.247.166.219:8080
20:00:45:WU02:FS01:Upload 35.44%
20:00:51:WU02:FS01:Upload 77.96%
20:00:55:WU02:FS01:Upload complete
20:00:55:WU02:FS01:Server responded WORK_ACK (400)
20:00:55:WU02:FS01:Final credit estimate, 1573.00 points
20:00:55:WU02:FS01:Cleaning up


Looking a lot better now, so currently back to normal I guess. The fact that other people are suggesting that there's something wrong with it though may warrant people at least keeping an eye out for a while at least. Anyone know if anything was done and if so, what was the problem just out of interest?
stealthswifttlk
 
Posts: 14
Joined: Fri Aug 29, 2008 9:01 pm
Location: Sheffield, UK

Re: 155.247.166.219 & 155.247.166.220 are now hosed [Not Now

Postby bruce » Sat Apr 21, 2018 9:29 pm

When FAH sets up a server, they're at the mercy of the network services firewall's rules. Some ports required by FAH's servers have been blocked.
I have been assuming that server port 80 was blocked by something that could be fixed on the servers, themselves, but it turns out it's the campus firewall.

I still can't get through on http://155.247.166.219:80/ or http://155.247.166.220:80/ Fortunately that it only affects a limited number of clients.
Other ports used by FAH servers have also been having troubles.

There have been ongoing discussions for several weeks.
bruce
 
Posts: 21403
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Previous

Return to Issues with a specific server

Who is online

Users browsing this forum: Google [Bot] and 1 guest

cron