Failed to connect to 171.67.108.200 (or 204)

Moderators: Site Moderators, FAHC Science Team

Post Reply
fltgoon
Posts: 2
Joined: Mon Aug 31, 2015 2:47 am

Failed to connect to 171.67.108.200 (or 204)

Post by fltgoon »

I have more less been unable to fold since the end of June. Basically unable to connect to an assignment server. It's been a while since I have had the time to really focus on this, but I have 1)Verified my firewall is not blocking. 2)Verified my house modem is not blocking. 3) Reinstalled FAHClient.
Here is an edited log of the day it quit:

Code: Select all

******************** Log Started 2015-06-11T04:35:26Z ***********************
04:35:26:************************* Folding@home Client *************************
04:35:26:      Website: http://folding.stanford.edu/
04:35:26:    Copyright: (c) 2009-2014 Stanford University
04:35:26:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
04:35:26:         Args: 
04:35:26:       Config: C:/ProgramData/FAHClient/config.xml
04:35:26:******************************** Build ********************************
04:35:26:      Version: 7.4.4
04:35:26:         Date: Mar 4 2014
04:35:26:         Time: 20:26:54
04:35:26:      SVN Rev: 4130
04:35:26:       Branch: fah/trunk/client
04:35:26:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
04:35:26:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
04:35:26:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
04:35:26:     Platform: win32 XP
04:35:26:         Bits: 32
04:35:26:         Mode: Release
04:35:26:******************************* System ********************************
04:35:26:          CPU: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
04:35:26:       CPU ID: GenuineIntel Family 6 Model 23 Stepping 10
04:35:26:         CPUs: 2
04:35:26:       Memory: 8.00GiB
04:35:26:  Free Memory: 6.44GiB
04:35:26:      Threads: WINDOWS_THREADS
04:35:26:   OS Version: 6.1
04:35:26:  Has Battery: false
04:35:26:   On Battery: false
04:35:26:   UTC Offset: -4
04:35:26:          PID: 4336
04:35:26:          CWD: C:/ProgramData/FAHClient
04:35:26:           OS: Windows 7 Professional
04:35:26:      OS Arch: AMD64
04:35:26:         GPUs: 1
04:35:26:        GPU 0: UNSUPPORTED: RV770 [Radeon HD 4870]
04:35:26:         CUDA: Not detected
04:35:26:Win32 Service: false
04:35:26:***********************************************************************
04:35:26:<config>
04:35:26:  <!-- Folding Core -->
04:35:26:  <cpu-usage v='80'/>
04:35:26:
04:35:26:  <!-- HTTP Server -->
04:35:26:  <allow v='127.0.0.1 192.168.0.0-192.168.0.255'/>
04:35:26:
04:35:26:  <!-- Network -->
04:35:26:  <proxy v=':8080'/>
04:35:26:
04:35:26:  <!-- Remote Command Server -->
04:35:26:  <password v='*********'/>
04:35:26:
04:35:26:  <!-- Slot Control -->
04:35:26:  <power v='MEDIUM'/>
04:35:26:
04:35:26:  <!-- User Information -->
04:35:26:  <passkey v='********************************'/>
04:35:26:  <team v='32'/>
04:35:26:  <user v='fltgoon'/>
04:35:26:
04:35:26:  <!-- Folding Slots -->
04:35:26:  <slot id='0' type='CPU'>
04:35:26:    <paused v='true'/>
04:35:26:  </slot>
04:35:26:</config>
04:35:26:Trying to access database...
04:35:26:Successfully acquired database lock
04:35:26:Enabled folding slot 00: PAUSED cpu:1 (by user)
04:36:12:FS00:Unpaused
04:36:12:WU00:FS00:Starting
04:36:12:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/ProgramData/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 704 -lifeline 4336 -checkpoint 15 -cpu 80
04:36:12:WU00:FS00:Started FahCore on PID 6028
04:36:12:WU00:FS00:Core PID:5752
04:36:12:WU00:FS00:FahCore 0xa4 started
04:36:13:WU00:FS00:0xa4:
04:36:13:WU00:FS00:0xa4:*------------------------------*
04:36:13:WU00:FS00:0xa4:Folding@Home Gromacs GB Core
04:36:13:WU00:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
04:36:13:WU00:FS00:0xa4:
04:36:13:WU00:FS00:0xa4:Preparing to commence simulation
04:36:13:WU00:FS00:0xa4:- Looking at optimizations...
04:36:13:WU00:FS00:0xa4:- Files status OK
04:36:13:WU00:FS00:0xa4:- Expanded 918182 -> 1523092 (decompressed 165.8 percent)
04:36:13:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=918182 data_size=1523092, decompressed_data_size=1523092 diff=0
04:36:13:WU00:FS00:0xa4:- Digital signature verified
04:36:13:WU00:FS00:0xa4:
04:36:13:WU00:FS00:0xa4:Project: 9010 (Run 482, Clone 2, Gen 11)
04:36:13:WU00:FS00:0xa4:
04:36:13:WU00:FS00:0xa4:Assembly optimizations on if available.
04:36:13:WU00:FS00:0xa4:Entering M.D.
04:36:19:WU00:FS00:0xa4:Using Gromacs checkpoints
04:36:19:WU00:FS00:0xa4:Mapping NT from 1 to 1 
04:36:19:WU00:FS00:0xa4:Resuming from checkpoint
04:36:19:WU00:FS00:0xa4:Verified 00/wudata_01.log
04:36:19:WU00:FS00:0xa4:Verified 00/wudata_01.trr
04:36:19:WU00:FS00:0xa4:Verified 00/wudata_01.xtc
04:36:19:WU00:FS00:0xa4:Verified 00/wudata_01.edr
04:36:19:WU00:FS00:0xa4:Completed 87365 out of 250000 steps  (34%)
04:36:27:Removing old file 'configs/config-20150428-000943.xml'
04:36:27:Saving configuration to config.xml
04:36:27:<config>
04:36:27:  <!-- Folding Core -->
04:36:27:  <cpu-usage v='80'/>
04:36:27:
04:36:27:  <!-- HTTP Server -->
04:36:27:  <allow v='127.0.0.1 192.168.0.0-192.168.0.255'/>
04:36:27:
04:36:27:  <!-- Network -->
04:36:27:  <proxy v=':8080'/>
04:36:27:
04:36:27:  <!-- Remote Command Server -->
04:36:27:  <password v='*********'/>
04:36:27:
04:36:27:  <!-- Slot Control -->
04:36:27:  <power v='MEDIUM'/>
04:36:27:
04:36:27:  <!-- User Information -->
04:36:27:  <passkey v='********************************'/>
04:36:27:  <team v='32'/>
04:36:27:  <user v='fltgoon'/>
04:36:27:
04:36:27:  <!-- Folding Slots -->
04:36:27:  <slot id='0' type='CPU'/>
04:36:27:</config>
04:36:57:WU00:FS00:0xa4:Completed 87500 out of 250000 steps  (35%)
04:48:54:WU00:FS00:0xa4:Completed 90000 out of 250000 steps  (36%)
...
52:49:WU00:FS00:0xa4:Completed 242500 out of 250000 steps  (97%)
04:04:18:WU00:FS00:0xa4:Completed 245000 out of 250000 steps  (98%)
04:15:47:WU00:FS00:0xa4:Completed 247500 out of 250000 steps  (99%)
04:15:47:WU01:FS00:Connecting to 171.67.108.200:8080
04:16:08:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:16:08:WU01:FS00:Connecting to 171.67.108.204:80
04:16:29:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:16:29:ERROR:WU01:FS00:Exception: Could not get an assignment
04:16:30:WU01:FS00:Connecting to 171.67.108.200:8080
04:16:51:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:16:51:WU01:FS00:Connecting to 171.67.108.204:80
04:17:12:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:17:12:ERROR:WU01:FS00:Exception: Could not get an assignment
04:17:30:WU01:FS00:Connecting to 171.67.108.200:8080
04:17:51:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:17:51:WU01:FS00:Connecting to 171.67.108.204:80
04:18:12:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:18:12:ERROR:WU01:FS00:Exception: Could not get an assignment
04:19:07:WU01:FS00:Connecting to 171.67.108.200:8080
04:19:28:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:19:28:WU01:FS00:Connecting to 171.67.108.204:80
04:19:49:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:19:49:ERROR:WU01:FS00:Exception: Could not get an assignment
04:21:44:WU01:FS00:Connecting to 171.67.108.200:8080
04:22:05:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:22:05:WU01:FS00:Connecting to 171.67.108.204:80
04:22:26:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:22:26:ERROR:WU01:FS00:Exception: Could not get an assignment
04:25:59:WU01:FS00:Connecting to 171.67.108.200:8080
04:26:20:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:26:20:WU01:FS00:Connecting to 171.67.108.204:80
04:26:41:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:26:41:ERROR:WU01:FS00:Exception: Could not get an assignment
04:27:13:WU00:FS00:0xa4:Completed 250000 out of 250000 steps  (100%)
04:27:13:WU00:FS00:0xa4:DynamicWrapper: Finished Work Unit: sleep=10000
04:27:23:WU00:FS00:0xa4:
04:27:23:WU00:FS00:0xa4:Finished Work Unit:
04:27:23:WU00:FS00:0xa4:- Reading up to 922512 from "00/wudata_01.trr": Read 922512
04:27:23:WU00:FS00:0xa4:trr file hash check passed.
04:27:23:WU00:FS00:0xa4:- Reading up to 848304 from "00/wudata_01.xtc": Read 848304
04:27:23:WU00:FS00:0xa4:xtc file hash check passed.
04:27:23:WU00:FS00:0xa4:edr file hash check passed.
04:27:23:WU00:FS00:0xa4:logfile size: 24941
04:27:23:WU00:FS00:0xa4:Leaving Run
04:27:23:WU00:FS00:0xa4:- Writing 1798245 bytes of core data to disk...
04:27:24:WU00:FS00:0xa4:Done: 1797733 -> 1736042 (compressed to 96.5 percent)
04:27:24:WU00:FS00:0xa4:  ... Done.
04:27:24:WU00:FS00:0xa4:- Shutting down core
04:27:24:WU00:FS00:0xa4:
04:27:24:WU00:FS00:0xa4:Folding@home Core Shutdown: FINISHED_UNIT
04:27:24:WU00:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
04:27:24:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:9013 run:282 clone:4 gen:47 core:0xa4 unit:0x0000003bab40417c554e979859238da7
04:27:24:WU00:FS00:Uploading 1.66MiB to 171.64.65.124
04:27:24:WU00:FS00:Connecting to 171.64.65.124:8080
04:27:26:WU00:FS00:Upload complete
04:27:26:WU00:FS00:Server responded WORK_ACK (400)
04:27:26:WU00:FS00:Final credit estimate, 428.00 points
04:27:26:WU00:FS00:Cleaning up
04:32:50:WU01:FS00:Connecting to 171.67.108.200:8080
04:33:11:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:33:11:WU01:FS00:Connecting to 171.67.108.204:80
04:33:32:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:33:32:ERROR:WU01:FS00:Exception: Could not get an assignment
04:43:56:WU01:FS00:Connecting to 171.67.108.200:8080
04:44:17:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:44:17:WU01:FS00:Connecting to 171.67.108.204:80
04:44:38:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
04:44:38:ERROR:WU01:FS00:Exception: Could not get an assignment
******************************* Date: 2015-06-25 *******************************
05:01:52:WU01:FS00:Connecting to 171.67.108.200:8080
05:02:14:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
05:02:14:WU01:FS00:Connecting to 171.67.108.204:80
05:02:35:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
05:02:35:ERROR:WU01:FS00:Exception: Could not get an assignment
05:30:55:WU01:FS00:Connecting to 171.67.108.200:8080
05:31:16:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
05:31:16:WU01:FS00:Connecting to 171.67.108.204:80
05:31:37:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
05:31:37:ERROR:WU01:FS00:Exception: Could not get an assignment
06:17:54:WU01:FS00:Connecting to 171.67.108.200:8080
06:18:15:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
06:18:15:WU01:FS00:Connecting to 171.67.108.204:80
06:18:36:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
06:18:36:ERROR:WU01:FS00:Exception: Could not get an assignment
07:33:55:WU01:FS00:Connecting to 171.67.108.200:8080
07:34:16:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
07:34:16:WU01:FS00:Connecting to 171.67.108.204:80
07:34:37:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
07:34:37:ERROR:WU01:FS00:Exception: Could not get an assignment
09:36:54:WU01:FS00:Connecting to 171.67.108.200:8080
09:37:15:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
09:37:15:WU01:FS00:Connecting to 171.67.108.204:80
09:37:36:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.204:80': Failed to connect to 171.67.108.204:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
09:37:36:ERROR:WU01:FS00:Exception: Could not get an assignment
******************************* Date: 2015-06-25 *******************************
I was going to just uninstall it and quit, but I decided to look around the site some more, found this topic in the forum and read some similar problems, so I figured I'd see if I could give you enough info to help me...

I have tried pings and they don't work. I have tried to bring up each of the servers as a browser page and get a timeout. Finally did a trace route and got this:

Code: Select all

C:\Users\Allen>tracert 171.67.108.200

Tracing route to vsp10v-vz00.stanford.edu [171.67.108.200]
over a maximum of 30 hops:

  1     6 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2    26 ms     8 ms     3 ms  lo0-100.WASHDC-VFTTP-320.verizon-gni.net [108.56.131.1]
  3     8 ms     6 ms     7 ms  T1-2-0-0.WASHDC-LCR-22.verizon-gni.net [100.41.220.12]
  4     *        *        *     Request timed out.
  5    10 ms     8 ms    10 ms  0.ae4.BR1.IAD8.ALTER.NET [140.222.227.9]
  6     7 ms     6 ms    13 ms  10ge13-1.core1.ash1.he.net [216.66.41.173]
  7    73 ms    73 ms    72 ms  10ge9-2.core1.pao1.he.net [184.105.213.177]
  8    75 ms    71 ms    72 ms  stanford-university.10gigabitethernet1-4.core1.pao1.he.net [216.218.209.118]
  9    74 ms    74 ms    69 ms  rtf-rtr-vlan8.SUNet [171.64.255.194]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
C:\Users\Allen>tracert 171.67.108.204

Tracing route to vsp10v-vz04.stanford.edu [171.67.108.204]
over a maximum of 30 hops:

  1     9 ms     1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     4 ms     3 ms     3 ms  lo0-100.WASHDC-VFTTP-320.verizon-gni.net [108.56.131.1]
  3    12 ms     5 ms     6 ms  T1-2-0-0.WASHDC-LCR-21.verizon-gni.net [100.41.220.10]
  4     *        *        *     Request timed out.
  5     8 ms     8 ms    16 ms  0.ae3.BR1.IAD8.ALTER.NET [140.222.227.7]
  6     5 ms    17 ms     8 ms  10ge13-1.core1.ash1.he.net [216.66.41.173]
  7    80 ms    73 ms    73 ms  10ge9-2.core1.pao1.he.net [184.105.213.177]
  8    72 ms    72 ms    71 ms  stanford-university.10gigabitethernet1-4.core1.pao1.he.net [216.218.209.118]
  9    93 ms    69 ms    71 ms  rtf-rtr-vlan8.SUNet [171.64.255.194]
 10     *        *        *     Request timed out.
Not sure what to do beyond this...

Thanks
Top
davidcoton
Posts: 1094
Joined: Wed Nov 05, 2008 3:19 pm
Location: Cambridge, UK

Re: Failed to connect to 171.67.108.200 (or 204)

Post by davidcoton »

Try rebooting your router. May not help, but AFAICT something is getting misrouted once it reaches Stanford, which could be an outdated cache on your router.

Your current configuration is to fold on a single CPU, and WUs that will run that way are getting scarce. If you can (depending on your other uses of the PC) set the folding power to "Full" and/or force the slot to CPU:2. That will ensure work is available for a bit longer once you can connect.

Alternatively look at running the NaCl client instead of the standard system.
Image
Top
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Failed to connect to 171.67.108.200 (or 204)

Post by bruce »

I'm not sure how it helps, but I can't get to the router that you're having trouble with:


>_>tracert rtf-rtr-vlan8.SUNet
Unable to resolve target system name rtf-rtr-vlan8.SUNet.

>_>tracert vsp10v-vz00.stanford.edu

Tracing route to vsp10v-vz00.stanford.edu [171.67.108.200]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms homeportal [192.168.1.254]
2 22 ms 22 ms 21 ms 108-230-220-2.lightspeed.irvnca.sbcglobal.net [108.230.220.2]
3 23 ms 22 ms 22 ms 75.20.0.240
4 23 ms 23 ms 23 ms 12.83.38.173
5 27 ms 26 ms 27 ms ggr2.la2ca.ip.att.net [12.122.128.97]
6 25 ms 23 ms 24 ms las-bb1-link.telia.net [80.239.193.213]
7 49 ms 49 ms 49 ms palo-b1-link.telia.net [80.91.252.232]
8 41 ms 49 ms 49 ms hurricane-ic-308019-palo-b1.c.telia.net [80.239.167.174]
9 37 ms 52 ms 36 ms stanford-university.10gigabitethernet1-4.core1.pao1.he.net[216.218.209.118]
10 37 ms 37 ms 36 ms rtf-rtr-po8-8.SUNet [171.64.255.194]
11 36 ms 36 ms 36 ms vsp10.stanford.edu [171.67.108.18]
12 37 ms 36 ms 36 ms vsp10v-vz00.stanford.edu [171.67.108.200]

Trace complete.

(That's not surprising. Routers generally do not make themselves known on the internet.)
Do you have a route to vsp10.stanford.edu?
Top
fltgoon
Posts: 2
Joined: Mon Aug 31, 2015 2:47 am

Re: Failed to connect to 171.67.108.200 (or 204)

Post by fltgoon »

I just did a tracert to there and got this:


C:\Users\Allen>tracert vsp10.stanford.edu

Tracing route to vsp10.stanford.edu [171.67.108.18]
over a maximum of 30 hops:

1 122 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 6 ms 8 ms lo0-100.WASHDC-VFTTP-320.verizon-gni.net [108.56.131.1]
3 8 ms 5 ms 11 ms T1-2-0-0.WASHDC-LCR-21.verizon-gni.net [100.41.220.10]
4 * * * Request timed out.
5 8 ms 6 ms 7 ms 0.ae3.BR1.IAD8.ALTER.NET [140.222.227.7]
6 9 ms 10 ms 13 ms 10ge13-1.core1.ash1.he.net [216.66.41.173]
7 79 ms 84 ms 73 ms 10ge9-2.core1.pao1.he.net [184.105.213.177]
8 70 ms 72 ms 71 ms stanford-university.10gigabitethernet1-4.core1.pao1.he.net [216.218.209.118]
9 117 ms 72 ms 70 ms rtf-rtr-vlan8.SUNet [171.64.255.194]
10 * * * Request timed out.
11 * * * Request timed out.

Once I got the double time out I quit. Last time it did that it ran for ten more tries.

Haven't tried rebooting the router. It's been rebooted multiple times since June and I had it replaced last month as well.
Top
toTOW
Site Moderator
Posts: 6394
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France
Contact:
Contact toTOW

Re: Failed to connect to 171.67.108.200 (or 204)

Post by toTOW »

I have the full route here going though rtf-rtr-vlan8.SUNet ...

Code: Select all

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                 LIVEBOX -    0 |   10 |   10 |    0 |    0 |    0 |    0 |
|                           80.10.125.134 -    0 |   10 |   10 |    6 |    6 |    7 |    6 |
|                           10.123.164.10 -    0 |   10 |   10 |    5 |    7 |   10 |    5 |
|ae42-0.nipoi101.Poitiers.francetelecom.net -  0 |   10 |   10 |    8 |    9 |   13 |    9 |
|                          193.252.137.18 -    0 |   10 |   10 |   20 |   24 |   43 |   21 |
|                   mad-b2-link.telia.net -    0 |   10 |   10 |   33 |   36 |   41 |   33 |
|                  prs-bb2-link.telia.net -    0 |   10 |   10 |   53 |   77 |  124 |   77 |
|                  ash-bb4-link.telia.net -    0 |   10 |   10 |  145 |  160 |  198 |  154 |
|                  palo-b1-link.telia.net -    0 |   10 |   10 |  205 |  213 |  222 |  222 |
| hurricane-ic-308019-palo-b1.c.telia.net -    0 |   10 |   10 |  217 |  229 |  239 |  238 |
|stanford-university.10gigabitethernet1-4.core1.pao1.he.net -   17 |    6 |    5 |    0 |  216 |  221 |  221 |
|                     rtf-rtr-vlan8.SUNet -    0 |   10 |   10 |  222 |  230 |  238 |  231 |
|                      vsp10.stanford.edu -    0 |   10 |   10 |  215 |  222 |  230 |  222 |
|                vsp10v-vz00.stanford.edu -    0 |   10 |   10 |  223 |  234 |  243 |  236 |
|________________________________________________|______|______|______|______|______|______|
Note that stanford-university.10gigabitethernet1-4.core1.pao1.he.net is dropping quite a high number of packets (although ICMP packets might have low QoS if the router is heavily loaded).
Image

Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
Top
_r2w_ben
Posts: 285
Joined: Wed Apr 23, 2008 3:11 pm

Re: Failed to connect to 171.67.108.200 (or 204)

Post by _r2w_ben »

Code: Select all

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                   CISCO -    0 |   51 |   51 |    0 |   13 |   16 |   11 |
|                            10.200.108.1 -    0 |   51 |   51 |    9 |   25 |   77 |   10 |
|              192-171-63-10.cpe.pppoe.ca -    0 |   51 |   51 |   14 |   30 |   83 |   16 |
|              192-171-63-12.cpe.pppoe.ca -    0 |   51 |   51 |   13 |   29 |   60 |   30 |
|         ae0_2160-bdr04-tor.teksavvy.com -    0 |   51 |   51 |   15 |   34 |   82 |   28 |
|               10ge2-1.core2.tor1.he.net -    0 |   51 |   51 |   15 |   31 |   83 |   26 |
|              10ge15-1.core1.chi1.he.net -    0 |   51 |   51 |   25 |   46 |  105 |   35 |
|              10ge11-4.core1.pao1.he.net -    0 |   51 |   51 |   79 |   97 |  153 |   90 |
|stanford-university.10gigabitethernet1-4.core1.pao1.he.net -    5 |   43 |   41 |   75 |   80 |  102 |   90 |
|                     rtf-rtr-vlan8.SUNet -    0 |   51 |   51 |   77 |   95 |  146 |   91 |
|                      vsp10.stanford.edu -    0 |   51 |   51 |   77 |   92 |  146 |   89 |
|                vsp10v-vz00.stanford.edu -    0 |   51 |   51 |   79 |   93 |  145 |   79 |
|________________________________________________|______|______|______|______|______|______|

Code: Select all

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                   CISCO -    0 |   54 |   54 |    0 |   11 |   16 |   15 |
|                            10.200.108.1 -    2 |   50 |   49 |    8 |   23 |   37 |   27 |
|              192-171-60-26.cpe.pppoe.ca -    0 |   54 |   54 |   14 |   29 |   51 |   14 |
|              192-171-60-28.cpe.pppoe.ca -    2 |   50 |   49 |   13 |   29 |   42 |   35 |
|         ae0_2160-bdr04-tor.teksavvy.com -    2 |   50 |   49 |   14 |   31 |   67 |   35 |
|               10ge2-1.core2.tor1.he.net -    2 |   50 |   49 |   14 |   30 |   45 |   32 |
|              10ge15-1.core1.chi1.he.net -    2 |   50 |   49 |   24 |   43 |   56 |   45 |
|              10ge11-4.core1.pao1.he.net -    2 |   50 |   49 |   78 |   97 |  121 |   94 |
|stanford-university.10gigabitethernet1-4.core1.pao1.he.net -    5 |   46 |   44 |   76 |   89 |  123 |   78 |
|                     rtf-rtr-vlan8.SUNet -    2 |   50 |   49 |   77 |   92 |  107 |   86 |
|                      vsp10.stanford.edu -    2 |   50 |   49 |   77 |   91 |  106 |   98 |
|                vsp10v-vz04.stanford.edu -    2 |   50 |   49 |   76 |   92 |  105 |   92 |
|________________________________________________|______|______|______|______|______|______|
Has anyone experimented with using Fiddler to diagnose F@H connectivity issues?
Top
ScottK
Posts: 6
Joined: Tue Aug 02, 2011 9:40 pm

Re: Failed to connect to 171.67.108.200 (or 204)

Post by ScottK »

Code: Select all

07:18:03:******************************** Build ********************************
07:18:03:      Version: 7.4.4
07:18:03:         Date: Mar 4 2014
07:18:03:         Time: 20:26:54
07:18:03:      SVN Rev: 4130
07:18:03:       Branch: fah/trunk/client
07:18:03:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
07:18:03:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
07:18:03:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
07:18:03:     Platform: win32 XP
07:18:03:         Bits: 32
07:18:03:         Mode: Release
07:18:03:******************************* System ********************************
07:18:03:          CPU: AMD Phenom(tm) II X4 955 Processor
07:18:03:       CPU ID: AuthenticAMD Family 16 Model 4 Stepping 3
07:18:03:         CPUs: 4
07:18:03:       Memory: 7.96GiB
07:18:03:  Free Memory: 2.99GiB
07:18:03:      Threads: WINDOWS_THREADS
07:18:03:   OS Version: 6.1
07:18:03:  Has Battery: false
07:18:03:   On Battery: false
07:18:03:   UTC Offset: -7
07:18:03:          PID: 13912
07:18:03:          CWD: C:/Users/scottk/AppData/Roaming/FAHClient
07:18:03:           OS: Windows 7 Ultimate
07:18:03:      OS Arch: AMD64
07:18:03:         GPUs: 2
07:18:03:        GPU 0: NVIDIA:1 G92 [GeForce 9800 GT]
07:18:03:        GPU 1: NVIDIA:2 GF116 [GeForce GTS 450]
07:18:03:         CUDA: 1.1
07:18:03:  CUDA Driver: 6000
07:18:03:Win32 Service: false
07:18:03:***********************************************************************
07:18:03:<config>
07:18:03:  <!-- Network -->
07:18:03:  <proxy v=':8080'/>
07:18:03:
07:18:03:  <!-- Slot Control -->
07:18:03:  <power v='full'/>
07:18:03:
07:18:03:  <!-- User Information -->
07:18:03:  <passkey v='********************************'/>
07:18:03:  <team v='67762'/>
07:18:03:  <user v='ScottK'/>
07:18:03:
07:18:03:  <!-- Folding Slots -->
07:18:03:  <slot id='0' type='GPU'/>
07:18:03:</config>
07:18:03:Trying to access database...
07:18:03:Successfully acquired database lock
07:18:03:Enabled folding slot 00: READY gpu:0:G92 [GeForce 9800 GT]
07:18:04:WU00:FS00:Connecting to 171.67.108.200:80
07:18:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:80': Empty work server assignment
07:18:05:WU00:FS00:Connecting to 171.67.108.204:80
07:18:05:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
07:18:05:ERROR:WU00:FS00:Exception: Could not get an assignment
07:18:06:WU00:FS00:Connecting to 171.67.108.200:80
07:18:06:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:80': Empty work server assignment
07:18:06:WU00:FS00:Connecting to 171.67.108.204:80
07:18:07:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
07:18:07:ERROR:WU00:FS00:Exception: Could not get an assignment
Mod edit: Added Code tags to log posting
Top
7im
Posts: 10179
Joined: Thu Nov 29, 2007 4:30 pm
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
Location: Arizona
Contact:
Contact 7im

Re: Failed to connect to 171.67.108.200 (or 204)

Post by 7im »

Hello ScottK, welcome to the Folding Support Forum.

The 9800 GT only supports folding of some older projects. To get those older projects, add the client-type setting of beta, and the max-packet-size setting of small.

See the Configuration Guide for more details.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Top
ScottK
Posts: 6
Joined: Tue Aug 02, 2011 9:40 pm

Re: Failed to connect to 171.67.108.200 (or 204)

Post by ScottK »

Since I haven't had FAClient actively running for a while, is there a manual way to remove any existing / pending / stuck work units sitting on my machine to force new work units to be downloaded? I'm looking at all options to get this going again.

Thanks!
Top
ScottK
Posts: 6
Joined: Tue Aug 02, 2011 9:40 pm

Re: Failed to connect to 171.67.108.200 (or 204)

Post by ScottK »

OK - I re-enabled the main video card on my system, which is identified as GPU:1 (GeForce GTS450) and it currently grinding on Project 10489:

Code: Select all

19:09:12:Adding folding slot 01: READY gpu:1:GF116 [GeForce GTS 450]
19:09:12:Saving configuration to config.xml
19:09:12:<config>
19:09:12:  <!-- Folding Slot Configuration -->
19:09:12:  <cause v='ALZHEIMERS'/>
19:09:12:
19:09:12:  <!-- Logging -->
19:09:12:  <verbosity v='5'/>
19:09:12:
19:09:12:  <!-- Network -->
19:09:12:  <proxy v=':8080'/>
19:09:12:
19:09:12:  <!-- Slot Control -->
19:09:12:  <power v='full'/>
19:09:12:
19:09:12:  <!-- User Information -->
19:09:12:  <passkey v='********************************'/>
19:09:12:  <team v='67762'/>
19:09:12:  <user v='ScottK'/>
19:09:12:
19:09:12:  <!-- Folding Slots -->
19:09:12:  <slot id='0' type='GPU'/>
19:09:12:  <slot id='1' type='GPU'>
19:09:12:    <cuda-index v='1'/>
19:09:12:    <gpu-index v='1'/>
19:09:12:  </slot>
19:09:12:</config>
19:09:12:WU01:FS01:Connecting to 171.67.108.200:80
19:09:13:WU01:FS01:Assigned to work server 140.163.4.234
19:09:13:WU01:FS01:Requesting new work unit for slot 01: READY gpu:1:GF116 [GeForce GTS 450] from 140.163.4.234
19:09:13:WU01:FS01:Connecting to 140.163.4.234:8080
19:09:13:WU01:FS01:Downloading 3.27MiB
19:09:18:WU01:FS01:Download complete
19:09:18:WU01:FS01:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:10489 run:0 clone:89 gen:165 core:0x18 unit:0x000000c5538b3dba551f05b405b0319d
19:09:18:WU01:FS01:Starting
19:09:18:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/scottk/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_18.fah/FahCore_18.exe -dir 01 -suffix 01 -version 704 -lifeline 13912 -checkpoint 15 -gpu 1 -gpu-vendor nvidia
19:09:19:WU01:FS01:Started FahCore on PID 10332
19:09:19:Started thread 15 on PID 13912
19:09:22:WU01:FS01:Core PID:8732
19:09:22:WU01:FS01:FahCore 0x18 started
19:09:23:WU01:FS01:0x18:*********************** Log Started 2015-09-03T19:09:23Z ***********************
19:09:23:WU01:FS01:0x18:Project: 10489 (Run 0, Clone 89, Gen 165)
19:09:23:WU01:FS01:0x18:Unit: 0x000000c5538b3dba551f05b405b0319d
19:09:23:WU01:FS01:0x18:CPU: 0x00000000000000000000000000000000
19:09:23:WU01:FS01:0x18:Machine: 1
19:09:23:WU01:FS01:0x18:Reading tar file state.xml
19:09:24:WU01:FS01:0x18:Reading tar file system.xml
19:09:24:WU01:FS01:0x18:Reading tar file integrator.xml
19:09:24:WU01:FS01:0x18:Reading tar file core.xml
19:09:25:WU01:FS01:0x18:Digital signatures verified
19:09:25:WU01:FS01:0x18:Folding@home GPU core18
19:09:25:WU01:FS01:0x18:Version 0.0.4
19:09:43:Saving configuration to config.xml
19:09:43:<config>
19:09:43:  <!-- Folding Slot Configuration -->
19:09:43:  <cause v='ALZHEIMERS'/>
19:09:43:
19:09:43:  <!-- Logging -->
19:09:43:  <verbosity v='5'/>
19:09:43:
19:09:43:  <!-- Network -->
19:09:43:  <proxy v=':8080'/>
19:09:43:
19:09:43:  <!-- Slot Control -->
19:09:43:  <power v='full'/>
19:09:43:
19:09:43:  <!-- User Information -->
19:09:43:  <passkey v='********************************'/>
19:09:43:  <team v='67762'/>
19:09:43:  <user v='ScottK'/>
19:09:43:
19:09:43:  <!-- Folding Slots -->
19:09:43:  <slot id='0' type='GPU'/>
19:09:43:  <slot id='1' type='GPU'>
19:09:43:    <cuda-index v='1'/>
19:09:43:    <gpu-index v='1'/>
19:09:43:  </slot>
19:09:43:</config>
19:10:20:WU01:FS01:0x18:Completed 0 out of 5000000 steps (0%)
19:10:20:WU01:FS01:0x18:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
However, I'm wanting the GeForce 9800GT - which is, yes, a lesser board but is not driving *any* video and was intended to be used for Folding@Home exclusively.

Looks like I need to move this to a different thread / topic.

Mod edit: Please use Code tags on log listings, available from the Full Editor
Top
ScottK
Posts: 6
Joined: Tue Aug 02, 2011 9:40 pm

Re: Failed to connect to 171.67.108.200 (or 204)

Post by ScottK »

7im wrote:Hello ScottK, welcome to the Folding Support Forum.

The 9800 GT only supports folding of some older projects. To get those older projects, add the client-type setting of beta, and the max-packet-size setting of small.

See the Configuration Guide for more details.
Thanks, I'll look into that, and replacing the 9800 GT with a more capable unit from Fry's or something :wink:

UPDATE: YAY!! Thanks, 7im! working as expected!!
Top
abravo
Posts: 16
Joined: Tue Aug 04, 2015 1:55 pm

Re: Failed to connect to 171.67.108.200 (or 204)

Post by abravo »

A couple of my folding computers with a two core CPU (G3258) are unable to get any more work units from 171.67.108.200 and 204. This started occurring within the last day or so.
Image
Top
Joe_H
Site Admin
Posts: 7989
Joined: Tue Apr 21, 2009 4:41 pm
Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2
Location: W. MA

Re: Failed to connect to 171.67.108.200 (or 204)

Post by Joe_H »

abravo - if you are getting message of "empty work server" from those two Assignment Servers, then you have a different issue than is being discussed in this topic. That message means you have connected to these AS's, but they do not have a Work Server with suitable jobs for your supplied configuration. You would have to supply additional information to determine what servers were down or out of work.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Top
abravo
Posts: 16
Joined: Tue Aug 04, 2015 1:55 pm

Re: Failed to connect to 171.67.108.200 (or 204)

Post by abravo »

I am getting an empty server statement.

Code: Select all

*********************** Log Started 2015-09-27T23:21:21Z ***********************
23:21:21:************************* Folding@home Client *************************
23:21:21:      Website: http://folding.stanford.edu/
23:21:21:    Copyright: (c) 2009-2014 Stanford University
23:21:21:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
23:21:21:         Args: 
23:21:21:       Config: C:/Users/Alexander/AppData/Roaming/FAHClient/config.xml
23:21:21:******************************** Build ********************************
23:21:21:      Version: 7.4.4
23:21:21:         Date: Mar 4 2014
23:21:21:         Time: 20:26:54
23:21:21:      SVN Rev: 4130
23:21:21:       Branch: fah/trunk/client
23:21:21:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
23:21:21:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
23:21:21:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
23:21:21:     Platform: win32 XP
23:21:21:         Bits: 32
23:21:21:         Mode: Release
23:21:21:******************************* System ********************************
23:21:21:          CPU: Intel(R) Pentium(R) CPU G3258 @ 3.20GHz
23:21:21:       CPU ID: GenuineIntel Family 6 Model 60 Stepping 3
23:21:21:         CPUs: 2
23:21:21:       Memory: 15.94GiB
23:21:21:  Free Memory: 14.83GiB
23:21:21:      Threads: WINDOWS_THREADS
23:21:21:   OS Version: 6.1
23:21:21:  Has Battery: false
23:21:21:   On Battery: false
23:21:21:   UTC Offset: -4
23:21:21:          PID: 1828
23:21:21:          CWD: C:/Users/Alexander/AppData/Roaming/FAHClient
23:21:21:           OS: Windows 7 Home Premium
23:21:21:      OS Arch: AMD64
23:21:21:         GPUs: 1
23:21:21:        GPU 0: NVIDIA:5 GM206 [GeForce GTX 960]
23:21:21:         CUDA: 5.2
23:21:21:  CUDA Driver: 7000
23:21:21:Win32 Service: false
23:21:21:***********************************************************************
23:21:21:<config>
23:21:21:  <!-- Network -->
23:21:21:  <proxy v=':8080'/>
23:21:21:
23:21:21:  <!-- Slot Control -->
23:21:21:  <power v='full'/>
23:21:21:
23:21:21:  <!-- User Information -->
23:21:21:  <passkey v='********************************'/>
23:21:21:  <team v='223518'/>
23:21:21:  <user v='AlphaBravo'/>
23:21:21:
23:21:21:  <!-- Folding Slots -->
23:21:21:  <slot id='0' type='CPU'>
23:21:21:    <paused v='true'/>
23:21:21:  </slot>
23:21:21:  <slot id='1' type='GPU'>
23:21:21:    <paused v='true'/>
23:21:21:  </slot>
23:21:21:</config>
23:21:21:Trying to access database...
23:21:21:Successfully acquired database lock
23:21:21:Enabled folding slot 00: PAUSED cpu:1 (by user)
23:21:21:Enabled folding slot 01: PAUSED gpu:0:GM206 [GeForce GTX 960] (by user)
23:21:32:16:127.0.0.1:New Web connection
23:21:51:FS00:Unpaused
23:21:51:FS01:Unpaused
23:21:52:WU01:FS01:Starting
23:21:52:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/Alexander/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_18.fah/FahCore_18.exe -dir 01 -suffix 01 -version 704 -lifeline 1828 -checkpoint 15 -gpu 0 -gpu-vendor nvidia
23:21:52:WU01:FS01:Started FahCore on PID 3080
23:21:52:WU01:FS01:Core PID:3092
23:21:52:WU01:FS01:FahCore 0x18 started
23:21:52:WU00:FS00:Connecting to 171.67.108.200:8080
23:21:52:WU01:FS01:0x18:*********************** Log Started 2015-09-27T23:21:52Z ***********************
23:21:52:WU01:FS01:0x18:Project: 9116 (Run 345, Clone 0, Gen 5)
23:21:52:WU01:FS01:0x18:Unit: 0x000000070a3b1e7854c1718c61ab55a9
23:21:52:WU01:FS01:0x18:CPU: 0x00000000000000000000000000000000
23:21:52:WU01:FS01:0x18:Machine: 1
23:21:52:WU01:FS01:0x18:Digital signatures verified
23:21:52:WU01:FS01:0x18:Folding@home GPU core18
23:21:52:WU01:FS01:0x18:Version 0.0.4
23:21:52:WU01:FS01:0x18:  Found a checkpoint file
23:21:52:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
23:21:52:WU00:FS00:Connecting to 171.67.108.204:80
23:21:53:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
23:21:53:ERROR:WU00:FS00:Exception: Could not get an assignment
23:21:53:WU00:FS00:Connecting to 171.67.108.200:8080
23:21:54:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
23:21:54:WU00:FS00:Connecting to 171.67.108.204:80
23:21:54:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
23:21:54:ERROR:WU00:FS00:Exception: Could not get an assignment
Image
Top
Ricky
Posts: 474
Joined: Sat Aug 01, 2015 1:34 am
Hardware configuration: 1. 2 each E5-2630 V3 processors, 64 GB RAM, GTX980SC GPU, and GTX980 GPU running on windows 8.1 operating system.
2. I7-6950X V3 processor, 32 GB RAM, 1 GTX980tiFTW, and 2 each GTX1080FTW GPUs running on windows 8.1 operating system.
Location: New Mexico

Re: Failed to connect to 171.67.108.200 (or 204)

Post by Ricky »

I have been having problems with these servers for a couple days. I read in this forum that large core count jobs may be limited in number, so I added a second slot for my cpu. I went from 1 cpu:30 to a couple cpu:12 slots. I still have trouble though.

This is the errors from the second cpu:12 slot alone:

Code: Select all

21:17:05:WARNING:WU01:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
******************************* Date: 2015-09-27 *******************************
23:51:47:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
23:51:47:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
23:51:47:ERROR:WU00:FS00:Exception: Could not get an assignment
23:51:48:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
23:51:48:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
23:51:48:ERROR:WU00:FS00:Exception: Could not get an assignment
23:52:48:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
23:52:48:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
23:52:48:ERROR:WU00:FS00:Exception: Could not get an assignment
23:54:25:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
23:54:26:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
23:54:26:ERROR:WU00:FS00:Exception: Could not get an assignment
23:57:02:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Empty work server assignment
23:57:03:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.204:80': Empty work server assignment
23:57:03:ERROR:WU00:FS00:Exception: Could not get an assignment
I get assignments after a number of tries.

I reduced from 2 cpu:15 slots after I noticed that the performance of the GPU slots seemed to improve while waiting for assignments. I must say that it has been interesting to get different projects at cpu:12 than I was getting with the single cpu:30 slot.
Top
Post Reply

Return to “Issues with a specific server”