AS servers - network problem

DocJonz · Post by **DocJonz** » Thu Dec 05, 2013 9:04 pm

Got a weird message this evening on one of my GPU's, see below. Currently it's stuck at 'ready' as a result.
The rest of the Folding Farm seems OK (at present) - even the second GPU in the same machine is still running.
Looks like I've been blacklisted or something ... !?

Code: Select all

20:55:52:******************************** Build ********************************
20:55:52:      Version: 7.3.6
20:55:52:         Date: Feb 18 2013
20:55:52:         Time: 15:25:17
20:55:52:      SVN Rev: 3923
20:55:52:       Branch: fah/trunk/client
20:55:52:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
20:55:52:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
20:55:52:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
20:55:52:     Platform: win32 XP
20:55:52:         Bits: 32
20:55:52:         Mode: Release
20:55:52:******************************* System ********************************
20:55:52:          CPU: Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz
20:55:52:       CPU ID: GenuineIntel Family 6 Model 26 Stepping 5
20:55:52:         CPUs: 8
20:55:52:       Memory: 5.99GiB
20:55:52:  Free Memory: 4.54GiB
20:55:52:      Threads: WINDOWS_THREADS
20:55:52:  Has Battery: false
20:55:52:   On Battery: false
20:55:52:   UTC offset: 0
20:55:52:          PID: 148
20:55:52:          CWD: C:/Users/williams/AppData/Roaming/FAHClient
20:55:52:           OS: Windows 7 Home Premium
20:55:52:      OS Arch: AMD64
20:55:52:         GPUs: 2
20:55:52:        GPU 0: NVIDIA:3 GK110 [GeForce GTX 780]
20:55:52:        GPU 1: NVIDIA:3 GK110 [GeForce GTX 780]
20:55:52:         CUDA: 3.5
20:55:52:  CUDA Driver: 5000
20:55:52:Win32 Service: false
20:55:52:***********************************************************************
20:55:52:<config>
20:55:52:  <!-- Folding Core -->
20:55:52:  <checkpoint v='10'/>
20:55:52:
20:55:52:  <!-- Folding Slot Configuration -->
20:55:52:  <power v='full'/>
20:55:52:
20:55:52:  <!-- HTTP Server -->
20:55:52:  <allow v='127.0.0.1,192.168.1.0/24'/>
20:55:52:
20:55:52:  <!-- Network -->
20:55:52:  <proxy v=':8080'/>
20:55:52:
20:55:52:  <!-- Remote Command Server -->
20:55:52:  <password v='*******'/>
20:55:52:
20:55:52:  <!-- User Information -->
20:55:52:  <passkey v='********************************'/>
20:55:52:  <team v='35947'/>
20:55:52:  <user v='DocJonz'/>
20:55:52:
20:55:52:  <!-- Folding Slots -->
20:55:52:  <slot id='0' type='GPU'>
20:55:52:    <client-type v='beta'/>
20:55:52:  </slot>
20:55:52:  <slot id='1' type='GPU'>
20:55:52:    <client-type v='beta'/>
20:55:52:  </slot>
20:55:52:</config>
20:55:52:Trying to access database...
20:55:52:Successfully acquired database lock
20:55:52:Enabled folding slot 00: READY gpu:0:GK110 [GeForce GTX 780]
20:55:52:Enabled folding slot 01: READY gpu:1:GK110 [GeForce GTX 780]
20:55:53:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
20:55:55:WARNING:WU00:FS00:Failed to get assignment 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.
20:55:55:WU00:FS00:Connecting to assign-GPU.stanford.edu:8080
20:55:57:WARNING:WU00:FS00:Failed to get assignment 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.
20:55:57:ERROR:WU00:FS00:Exception: Could not get an assignment
20:55:57:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
20:55:59:WARNING:WU00:FS00:Failed to get assignment 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.
20:55:59:WU00:FS00:Connecting to assign-GPU.stanford.edu:8080
20:56:00:WARNING:WU00:FS00:Failed to get assignment 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.
20:56:00:ERROR:WU00:FS00:Exception: Could not get an assignment
20:56:06:11:127.0.0.1:New Web connection
20:56:23:WARNING:Exception: 17:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
20:56:23:WARNING:Exception: 15:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
20:56:23:WARNING:Exception: 16:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
20:56:23:WARNING:Exception: 18:127.0.0.1: Send error: 10054: An existing connection was forcibly closed by the remote host.
20:56:24:WARNING:Exception: 22:127.0.0.1: Send error: 10054: An existing connection was forcibly closed by the remote host.
20:56:57:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
20:56:59:WARNING:WU00:FS00:Failed to get assignment 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.
20:56:59:WU00:FS00:Connecting to assign-GPU.stanford.edu:8080
20:57:01:WARNING:WU00:FS00:Failed to get assignment 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.
20:57:01:ERROR:WU00:FS00:Exception: Could not get an assignment
20:58:35:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
20:58:36:WARNING:WU00:FS00:Failed to get assignment 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.
20:58:36:WU00:FS00:Connecting to assign-GPU.stanford.edu:8080
20:58:38:WARNING:WU00:FS00:Failed to get assignment 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.
20:58:38:ERROR:WU00:FS00:Exception: Could not get an assignment

7im · Post by **7im** » Thu Dec 05, 2013 9:19 pm

There are no beta core_17 work units, and we can't discuss beta settings in the public section of the forum. Post in the beta section, or remove those settings and try the client again, posting a new log. Thanks

DocJonz · Post by **DocJonz** » Thu Dec 05, 2013 9:27 pm

I'd forgotten to take the flags off. Now done. Same error message still present.

Code: Select all

21:25:44:******************************** Build ********************************
21:25:44:      Version: 7.3.6
21:25:44:         Date: Feb 18 2013
21:25:44:         Time: 15:25:17
21:25:44:      SVN Rev: 3923
21:25:44:       Branch: fah/trunk/client
21:25:44:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
21:25:44:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
21:25:44:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
21:25:44:     Platform: win32 XP
21:25:44:         Bits: 32
21:25:44:         Mode: Release
21:25:44:******************************* System ********************************
21:25:44:          CPU: Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz
21:25:44:       CPU ID: GenuineIntel Family 6 Model 26 Stepping 5
21:25:44:         CPUs: 8
21:25:44:       Memory: 5.99GiB
21:25:44:  Free Memory: 4.86GiB
21:25:44:      Threads: WINDOWS_THREADS
21:25:44:  Has Battery: false
21:25:44:   On Battery: false
21:25:44:   UTC offset: 0
21:25:44:          PID: 5076
21:25:44:          CWD: C:/Users/williams/AppData/Roaming/FAHClient
21:25:44:           OS: Windows 7 Home Premium
21:25:44:      OS Arch: AMD64
21:25:44:         GPUs: 2
21:25:44:        GPU 0: NVIDIA:3 GK110 [GeForce GTX 780]
21:25:44:        GPU 1: NVIDIA:3 GK110 [GeForce GTX 780]
21:25:44:         CUDA: 3.5
21:25:44:  CUDA Driver: 5000
21:25:44:Win32 Service: false
21:25:44:***********************************************************************
21:25:44:<config>
21:25:44:  <!-- Folding Core -->
21:25:44:  <checkpoint v='10'/>
21:25:44:
21:25:44:  <!-- Folding Slot Configuration -->
21:25:44:  <power v='full'/>
21:25:44:
21:25:44:  <!-- HTTP Server -->
21:25:44:  <allow v='127.0.0.1,192.168.1.0/24'/>
21:25:44:
21:25:44:  <!-- Network -->
21:25:44:  <proxy v=':8080'/>
21:25:44:
21:25:44:  <!-- Remote Command Server -->
21:25:44:  <password v='*******'/>
21:25:44:
21:25:44:  <!-- User Information -->
21:25:44:  <passkey v='********************************'/>
21:25:44:  <team v='35947'/>
21:25:44:  <user v='DocJonz'/>
21:25:44:
21:25:44:  <!-- Folding Slots -->
21:25:44:  <slot id='0' type='GPU'/>
21:25:44:  <slot id='1' type='GPU'/>
21:25:44:</config>
21:25:44:Trying to access database...
21:25:44:Successfully acquired database lock
21:25:44:Enabled folding slot 00: READY gpu:0:GK110 [GeForce GTX 780]
21:25:44:Enabled folding slot 01: READY gpu:1:GK110 [GeForce GTX 780]
21:25:45:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
21:25:46:5:127.0.0.1:New Web connection
21:25:47:WARNING:WU00:FS00:Failed to get assignment 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.
21:25:47:WU00:FS00:Connecting to assign-GPU.stanford.edu:8080
21:25:48:WARNING:WU00:FS00:Failed to get assignment 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.
21:25:48:ERROR:WU00:FS00:Exception: Could not get an assignment
21:25:48:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
21:25:50:WARNING:WU00:FS00:Failed to get assignment 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.
21:25:50:WU00:FS00:Connecting to assign-GPU.stanford.edu:8080
21:25:51:WARNING:WU00:FS00:Failed to get assignment 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.
21:25:51:ERROR:WU00:FS00:Exception: Could not get an assignment
21:25:56:WARNING:Exception: 2:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
21:25:56:WARNING:Exception: 6:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
21:25:56:WARNING:Exception: 7:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
21:25:56:WARNING:Exception: 8:127.0.0.1: Receive error: 10054: An existing connection was forcibly closed by the remote host.
21:25:56:WARNING:Exception: 9:127.0.0.1: Send error: 10054: An existing connection was forcibly closed by the remote host.
21:26:48:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
21:26:50:WARNING:WU00:FS00:Failed to get assignment 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.
21:26:50:WU00:FS00:Connecting to assign-GPU.stanford.edu:8080
21:26:51:WARNING:WU00:FS00:Failed to get assignment 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.
21:26:51:ERROR:WU00:FS00:Exception: Could not get an assignment

billford · Post by **billford** » Thu Dec 05, 2013 9:34 pm

Don't know if it's connected, but I've had several of these tonight, on two machines (the other two haven't tried to connect):

Code: Select all

21:26:57:WU00:FS00:Connecting to assign3.stanford.edu:8080
21:26:57:WARNING:WU00:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': Failed to connect to assign3.stanford.edu:8080: Connection refused
21:26:57:WU00:FS00:Connecting to assign4.stanford.edu:80
21:26:58:WU00:FS00:News: Welcome to Folding@Home
21:26:58:WU00:FS00:Assigned to work server 171.64.65.99
21:26:58:WU00:FS00:Requesting new work unit for slot 00: READY cpu:4 from 171.64.65.99
21:26:58:WU00:FS00:Connecting to 171.64.65.99:8080
21:27:00:WU00:FS00:Downloading 1.98MiB
21:27:03:WU00:FS00:Download complete

and

Code: Select all

20:22:46:WU00:FS00:Connecting to assign3.stanford.edu:8080
20:22:47:WARNING:WU00:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': 10001: Server responded: HTTP_SERVICE_UNAVAILABLE
20:22:47:WU00:FS00:Connecting to assign4.stanford.edu:80
20:22:47:WU00:FS00:News: Welcome to Folding@Home
20:22:47:WU00:FS00:Assigned to work server 171.64.65.99
20:22:47:WU00:FS00:Requesting new work unit for slot 00: RUNNING cpu:2 from 171.64.65.99
20:22:47:WU00:FS00:Connecting to 171.64.65.99:8080
20:22:49:WU00:FS00:Downloading 1.96MiB
20:22:52:WU00:FS00:Download complete

And the stats don't seem to be updating as far as I can tell.

DocJonz · Post by **DocJonz** » Thu Dec 05, 2013 9:36 pm

I have another GPU WU finished on another machine and it is saying "connection refused" as well - so maybe there is an issue Stanford end?

bollix47 · Post by **bollix47** » Thu Dec 05, 2013 9:37 pm

Thanks for the reports ... PG notified.

Post by **schwancr** » Thu Dec 05, 2013 9:51 pm

There is a network issue that affects assign and assign-gpu. We're working to resolve this.

uncle fuzzy · Post by **uncle fuzzy** » Thu Dec 05, 2013 10:03 pm

Came home to several idle GPUs. Team mates also have some.

Code: Select all

21:46:08:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
21:46:10:WARNING:WU00:FS00:Failed to get assignment 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.

Just had a third box with the same issue.
W7 64- GTX 780 Ti
W7 64- GTX 660 Ti
XP- GTX 660 Ti

Several more WUs finishing in the next hour.

bollix47 · Post by **bollix47** » Thu Dec 05, 2013 11:18 pm

Assignments have resumed ... thank you schwancr for your speedy response.

Folding Forum

AS servers - network problem

AS servers - network problem

Re: "Target machine refused connection"

Re: "Target machine refused connection"

Re: "Target machine refused connection"

Re: "Target machine refused connection"

Re: "Target machine refused connection"

Re: "Target machine refused connection"

GPU AS down?

Re: AS servers - network problem