Connection problem 128.252.203.2:80 140.163.4.231:80

Moderators: Site Moderators, PandeGroup

Post Reply
kolya.rm
Posts: 4
Joined: Tue Jun 26, 2018 3:02 am

Connection problem 128.252.203.2:80 140.163.4.231:80

Post by kolya.rm » Tue Jun 26, 2018 3:11 am

Win 10, GTX 1070Ti, Nvidia 397.64

Code: Select all

02:53:02:WU01:FS01:Trying to send results to collection server
02:53:02:WU01:FS01:Uploading 11.80MiB to 128.252.203.2
02:53:02:WU01:FS01:Connecting to 128.252.203.2:8080
02:53:23:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
02:53:23:WU01:FS01:Connecting to 128.252.203.2:80
02:53:24:WU01:FS01:Upload 0.53%
02:53:30:ERROR:WU01:FS01:Exception: 10001: Server responded: HTTP_FOUND
02:56:52:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:11713 run:22 clone:97 gen:191 core:0x21 unit:0x000000f98ca304e75a5a522c5cc593f0
02:56:52:WU01:FS01:Uploading 11.80MiB to 140.163.4.231
02:56:52:WU01:FS01:Connecting to 140.163.4.231:8080
02:57:02:WU00:FS01:Connecting to 65.254.110.245:80
02:57:02:WARNING:WU00:FS01:Failed to get assignment from '65.254.110.245:80': 10001: Server responded: HTTP_FOUND
02:57:02:WU00:FS01:Connecting to 18.218.241.186:80
02:57:02:WARNING:WU00:FS01:Failed to get assignment from '18.218.241.186:80': 10001: Server responded: HTTP_FOUND
02:57:02:ERROR:WU00:FS01:Exception: Could not get an assignment
02:57:13:WARNING:WU01:FS01:WorkServer connection failed on port 8080 trying 80
02:57:13:WU01:FS01:Connecting to 140.163.4.231:80
02:57:13:WU01:FS01:Upload 0.53%
02:57:17:WARNING:WU01:FS01:Exception: Failed to send results to work server: 10001: Server responded: HTTP_FOUND
tracert 128.252.203.2

Code: Select all

  2     3 ms     2 ms     4 ms  ykts-bras1.dv.ip.rostelecom.ru [87.226.134.117]
  3     4 ms     3 ms     2 ms  apsb-ykt.ru [80.73.79.130]
  4   117 ms   117 ms   122 ms  ae45.stkm-cr4.intl.ip.rostelecom.ru [87.226.133.133]
  5   145 ms   146 ms   146 ms  hu0-2-0-0.ccr21.sto01.atlas.cogentco.com [149.6.169.145]
  6   143 ms   142 ms   143 ms  be3377.ccr22.sto03.atlas.cogentco.com [154.54.36.89]
  7   151 ms   151 ms   152 ms  be2282.ccr42.ham01.atlas.cogentco.com [154.54.72.105]
  8   148 ms   147 ms   147 ms  be2816.ccr42.ams03.atlas.cogentco.com [154.54.38.209]
  9   257 ms   258 ms   258 ms  be12266.ccr42.par01.atlas.cogentco.com [154.54.56.174]
 10   256 ms   257 ms   255 ms  be12489.ccr42.lon13.atlas.cogentco.com [154.54.57.69]
 11   262 ms   264 ms   262 ms  be2491.ccr22.lpl01.atlas.cogentco.com [154.54.39.117]
 12   256 ms   253 ms   255 ms  be3043.ccr22.ymq01.atlas.cogentco.com [154.54.44.166]
 13   257 ms   257 ms   257 ms  be2104.ccr22.alb02.atlas.cogentco.com [154.54.43.22]
 14   253 ms   253 ms   253 ms  be2879.ccr22.cle04.atlas.cogentco.com [154.54.29.173]
 15   255 ms   258 ms   252 ms  be2718.ccr42.ord01.atlas.cogentco.com [154.54.7.129]
 16   262 ms   261 ms   267 ms  be2388.rcr21.stl03.atlas.cogentco.com [154.54.80.186]
 17   263 ms   264 ms   262 ms  xe-0-0-2-commodity-core.nts.wustl.edu [38.104.162.78]
 18   265 ms   267 ms   264 ms  xe-0-0-6-eps-l29-wu-rt-0.nts.wustl.edu [128.252.100.125]
 19   256 ms   256 ms   258 ms  eth4-17-sgl-core.nts.wustl.edu [128.252.1.45]
 20   257 ms   259 ms   256 ms  te2-7-1-engineering-core.nts.wustl.edu [128.252.1.138]
 21   265 ms   265 ms   267 ms  brodgar.seas.wustl.edu [128.252.203.2]

bruce
Posts: 22470
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Connection problem 128.252.203.2:80 140.163.4.231:80

Post by bruce » Tue Jun 26, 2018 2:39 pm

I think there's something strange happening with brodgar.seas.wustl.edu. I'll check.

BTW, although the tracert shows useful information, in this case I would have just opened http://brodgar.seas.wustl.edu (though neither method can explain why they work and downloading a WU didn't work.

How many times did your client get those errors before it found an alternate path for download or upload?

kolya.rm
Posts: 4
Joined: Tue Jun 26, 2018 3:02 am

Re: Connection problem 128.252.203.2:80 140.163.4.231:80

Post by kolya.rm » Wed Jun 27, 2018 2:31 am

I counted 118 times within 10 hours.

I apply log files with errors. logs

bruce
Posts: 22470
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Connection problem 128.252.203.2:80 140.163.4.231:80

Post by bruce » Wed Jun 27, 2018 3:48 pm

What does Ïîïûòêà óñòàíîâèòü ñîåäèíåíèå áûëà áåçóñïåøíîé, ò.ê. îò äðóãîãî êîìïüþòåðà çà òðåáóåìîå âðåìÿ íå ïîëó÷åí íóæíûé îòêëèê, èëè áûëî ðàçîðâàíî óæå óñòàíîâëåííîå ñîåäèíåíèå èç-çà íåâåðíîãî îòêëèêà óæå ïîäêëþ÷åííîãî êîìïüþòåðà. mean in English?

kolya.rm
Posts: 4
Joined: Tue Jun 26, 2018 3:02 am

Re: Connection problem 128.252.203.2:80 140.163.4.231:80

Post by kolya.rm » Thu Jun 28, 2018 1:14 am

Oh. I'm sorry. If I am not mistaken, it was Windows sockets WSAETIMEDOUT 10060 error message

06:22:36:WARNING:WU03:FS01:Failed to get assignment from '171.67.108.45:80': Failed to connect to 171.67.108.45:80: A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.

bruce
Posts: 22470
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Connection problem 128.252.203.2:80 140.163.4.231:80

Post by bruce » Thu Jun 28, 2018 11:29 pm

Your tracert indicates that your machine can communicate with http://128.252.203.2/ and you can PROBABLY open that URL in your browser -- even though FAHClient cannot connect to that server. That means your firewall is blocking FAHClient from connecting. You'll need to add an exception to that firewall allowing such connections. Since we don't know what security software you're using we can't advise you haw to do that -- and I am not personally familiar with the procedures for many of the firewalls you might have.

FAHClient needs to be allowed to connect to the FAH servers just like your browser does. See Joe_H's answer here

kolya.rm
Posts: 4
Joined: Tue Jun 26, 2018 3:02 am

Re: Connection problem 128.252.203.2:80 140.163.4.231:80

Post by kolya.rm » Fri Jun 29, 2018 12:46 am

Thanks for the clarifications.

I'll try to figure out if this error repeats.

Post Reply

Return to “Issues with a specific server”