Problem returning WUs to 171.64.65.56 - Resolved

Moderators: Site Moderators, FAHC Science Team

Post Reply
mfrisbyuk
Posts: 9
Joined: Mon Oct 17, 2011 12:30 pm

Problem returning WUs to 171.64.65.56 - Resolved

Post by mfrisbyuk »

Hi
I started this project last night, but now its stuck on send. I guess there is an issue with the server not sure what I need to do to complete this ?

http://fah-web.stanford.edu/logs/171.67.108.26.log.html
as the log page states
Sat Oct 22 05:00:10 PDT 2011 171.67.108.26 CS 6 vsp09a - standby Not Accept

I'm keep getting:
12:33:12:ERROR: Exception: Failed to connect to 171.67.108.26:80: No connection could be made because the target machine actively refused it.

Work Unit
PRCG 11294 (10, 359, 30)
Project 11294
Work Server 171.64.65.56
Collection Server 171.67.108.26

Code: Select all

*********************** Log Started 2011-10-22T12:00:56 ************************
12:00:56:************************* Folding@home Client *************************
12:00:56:      Website: http://folding.stanford.edu/
12:00:56:    Copyright: (c) 2009-2011 Stanford University
12:00:56:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
12:00:56:         Args: --lifeline 6548 --command-port=36330
12:00:56:       Config: C:/Users/Mark/AppData/Roaming/FAHClient/config.xml
12:00:56:******************************** Build ********************************
12:00:56:      Version: 7.1.38
12:00:56:         Date: Oct 6 2011
12:00:56:         Time: 19:57:04
12:00:56:      SVN Rev: 3080
12:00:56:       Branch: fah/trunk/client
12:00:56:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
12:00:56:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
12:00:56:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT
12:00:56:     Platform: win32 XP
12:00:56:         Bits: 32
12:00:56:         Mode: Release
12:00:56:******************************* System ********************************
12:00:56:          CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
12:00:56:       CPU ID: AuthenticAMD Family 15 Model 107 Stepping 2
12:00:56:         CPUs: 2
12:00:56:       Memory: 4.00GiB
12:00:56:  Free Memory: 2.34GiB
12:00:56:      Threads: WINDOWS_THREADS
12:00:56:   On Battery: false
12:00:56:   UTC offset: 1
12:00:56:          PID: 3076
12:00:56:          CWD: C:/Users/Mark/AppData/Roaming/FAHClient
12:00:56:           OS: Microsoft Windows XP Service Pack 3
12:00:56:      OS Arch: AMD64
12:00:56:         GPUs: 1
12:00:56:        GPU 0: ATI:4 Redwood [Radeon HD 5670]
12:00:56:         CUDA: Not detected
12:00:56:Win32 Service: false
12:00:56:***********************************************************************
12:00:57:<config>
12:00:57:  <!-- FahCore Control -->
12:00:57:  <checkpoint v='10'/>
12:00:57:  <core-priority v='low'/>
12:00:57:
12:00:57:  <!-- Folding Slot Configuration -->
12:00:57:  <gpu v='true'/>
12:00:57:  <smp v='false'/>
12:00:57:
12:00:57:  <!-- Network -->
12:00:57:  <proxy v=':8080'/>
12:00:57:
12:00:57:  <!-- User Information -->
12:00:57:  <team v='78731'/>
12:00:57:  <user v='cnutard'/>
12:00:57:
12:00:57:  <!-- Folding Slots -->
12:00:57:  <slot id='0' type='GPU'>
12:00:57:    <client-type v='advanced'/>
12:00:57:  </slot>
12:00:57:  <slot id='1' type='UNIPROCESSOR'/>
12:00:57:</config>
12:00:57:Trying to access database...
12:00:57:Successfully acquired database lock
12:00:57:Enabled folding slot 00: READY gpu:0:"Redwood [Radeon HD 5670]"
12:00:57:Enabled folding slot 01: READY uniprocessor
12:00:57:Downloading project 11293 description
12:00:57:Connecting to fah-web.stanford.edu:80
12:00:57:Sending unit results: id:01 state:SEND error:OK project:11294 run:10 clone:359 gen:30 core:0x16 unit:0x0000001e0a3b1e5c4d9a1d888f9d8464
12:00:57:Unit 01: Uploading 2.37MiB to 171.64.65.56
12:00:57:Starting Unit 00
12:00:57:Connecting to 171.64.65.56:8080
12:00:57:Running core: C:/Users/Mark/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_16.fah/FahCore_16.exe -dir 00 -suffix 01 -lifeline 3076 -version 701 -checkpoint 10 -gpu 0
12:00:57:Started core on PID 5580
12:00:57:FahCore 0x16 started
12:00:57:Starting Unit 02
12:00:57:Running core: C:/Users/Mark/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 02 -suffix 01 -lifeline 3076 -version 701 -checkpoint 10
12:00:57:Started core on PID 3696
12:00:57:FahCore 0xa4 started
12:00:57:Unit 00:
12:00:57:Unit 00:*------------------------------*
12:00:57:Unit 00:Folding@Home GPU Core
12:00:57:Unit 00:Version 2.11 (Thu Dec 9 15:00:14 PST 2010)
12:00:57:Unit 00:
12:00:57:Unit 00:Compiler  : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86 
12:00:57:Unit 00:Build host: user-f6d030f24f
12:00:57:Unit 00:Board Type: AMD/OpenCL
12:00:57:Unit 00:Core      : x=16
12:00:57:Unit 00: Window's signal control handler registered.
12:00:57:Unit 00:Preparing to commence simulation
12:00:57:Unit 00:- Ensuring status. Please wait.
12:00:57:Unit 02:
12:00:57:Unit 02:*------------------------------*
12:00:57:Unit 02:Folding@Home Gromacs GB Core
12:00:57:Unit 02:Version 2.27 (Dec. 15, 2010)
12:00:57:Unit 02:
12:00:57:Unit 02:Preparing to commence simulation
12:00:57:Unit 02:- Ensuring status. Please wait.
12:00:58:Server connection id=1 on 0.0.0.0:36330 from 127.0.0.1
12:00:58:WARNING: Exception: Failed to connect to fah-web.stanford.edu:80: No connection could be made because the target machine actively refused it.
12:00:58:Downloading project 11293 description
12:00:58:Connecting to fah-web.stanford.edu:80
12:01:07:Unit 00:- Looking at optimizations...
12:01:07:Unit 00:- Working with standard loops on this execution.
12:01:07:Unit 00:- Previous termination of core was improper.
12:01:07:Unit 00:- Files status OK
12:01:07:Unit 00:sizeof(CORE_PACKET_HDR) = 512 file=<>
12:01:07:Unit 00:- Expanded 42528 -> 171163 (decompressed 402.4 percent)
12:01:07:Unit 00:Called DecompressByteArray: compressed_data_size=42528 data_size=171163, decompressed_data_size=171163 diff=0
12:01:07:Unit 00:- Digital signature verified
12:01:07:Unit 00:
12:01:07:Unit 00:Project: 11293 (Run 2, Clone 164, Gen 0)
12:01:07:Unit 00:
12:01:07:Unit 00:Entering M.D.
12:01:07:Unit 02:- Looking at optimizations...
12:01:07:Unit 02:- Working with standard loops on this execution.
12:01:07:Unit 02:- Previous termination of core was improper.
12:01:07:Unit 02:- Going to use standard loops.
12:01:07:Unit 02:- Files status OK
12:01:07:Unit 02:- Expanded 1701141 -> 3718204 (decompressed 218.5 percent)
12:01:07:Unit 02:Called DecompressByteArray: compressed_data_size=1701141 data_size=3718204, decompressed_data_size=3718204 diff=0
12:01:07:Unit 02:- Digital signature verified
12:01:07:Unit 02:
12:01:07:Unit 02:Project: 7708 (Run 6, Clone 10, Gen 5)
12:01:07:Unit 02:
12:01:07:Unit 02:Entering M.D.
12:01:09:Unit 00:Will resume from checkpoint file 00/wudata_01.ckp
12:01:09:Unit 00:Tpr hash 00/wudata_01.tpr:  2932735169 1049138205 187498599 3625615199 2187015523
12:01:09:Unit 00:Working on ALZHEIMER DISEASE AMYLOID
12:01:09:Unit 00:Client config unavailable.
12:01:09:Unit 00:Starting GUI Server
12:01:13:Unit 02:Using Gromacs checkpoints
12:01:13:Unit 02:Mapping NT from 1 to 1 
12:01:14:Unit 02:Resuming from checkpoint
12:01:14:Unit 02:Verified 02/wudata_01.log
12:01:14:Unit 02:Verified 02/wudata_01.trr
12:01:14:Unit 02:Verified 02/wudata_01.xtc
12:01:14:Unit 02:Verified 02/wudata_01.edr
12:01:15:Unit 02:Completed 292260 out of 750000 steps  (38%)
12:01:18:Unit 00:Resuming from checkpoint
12:01:18:Unit 00:fcCheckPointResume: retreived and current tpr file hash:
12:01:18:Unit 00:   0   2932735169   2932735169
12:01:18:Unit 00:   1   1049138205   1049138205
12:01:18:Unit 00:   2    187498599    187498599
12:01:18:Unit 00:   3   3625615199   3625615199
12:01:18:Unit 00:   4   2187015523   2187015523
12:01:18:Unit 00:fcCheckPointResume: file hashes same.
12:01:18:Unit 00:fcCheckPointResume: state restored.
12:01:18:Unit 00:fcCheckPointResume: name 00/wudata_01.log Verified 00/wudata_01.log
12:01:18:Unit 00:fcCheckPointResume: name 00/wudata_01.trr Verified 00/wudata_01.trr
12:01:18:Unit 00:fcCheckPointResume: name 00/wudata_01.xtc Verified 00/wudata_01.xtc
12:01:18:Unit 00:fcCheckPointResume: name 00/wudata_01.edr Verified 00/wudata_01.edr
12:01:18:Unit 00:fcCheckPointResume: state restored 2
12:01:18:Unit 00:Resumed from checkpoint
12:01:18:Unit 00:Setting checkpoint frequency: 500000
12:01:18:Unit 00:Completed  10500001 out of 50000000 steps (21%).
12:03:57:WARNING: Exception: Failed to send results to work server: Upload failed
12:03:57:Trying to send results to collection server
12:03:57:Unit 01: Uploading 2.37MiB to 171.67.108.26
12:03:57:Connecting to 171.67.108.26:8080
12:03:59:WARNING: WorkServer connection failed on port 8080 trying 80
12:03:59:Connecting to 171.67.108.26:80
12:04:00:ERROR: Exception: Failed to connect to 171.67.108.26:80: No connection could be made because the target machine actively refused it.
12:04:01:Sending unit results: id:01 state:SEND error:OK project:11294 run:10 clone:359 gen:30 core:0x16 unit:0x0000001e0a3b1e5c4d9a1d888f9d8464
12:04:01:Unit 01: Uploading 2.37MiB to 171.64.65.56
12:04:01:Connecting to 171.64.65.56:8080
12:04:13:Unit 02:Completed 292500 out of 750000 steps  (39%)
12:04:33:WARNING: Exception: Failed to send results to work server: Upload failed
12:04:33:Trying to send results to collection server
12:04:33:Unit 01: Uploading 2.37MiB to 171.67.108.26
12:04:33:Connecting to 171.67.108.26:8080
12:04:35:WARNING: WorkServer connection failed on port 8080 trying 80
12:04:35:Connecting to 171.67.108.26:80
12:04:37:ERROR: Exception: Failed to connect to 171.67.108.26:80: No connection could be made because the target machine actively refused it.
12:05:01:Sending unit results: id:01 state:SEND error:OK project:11294 run:10 clone:359 gen:30 core:0x16 unit:0x0000001e0a3b1e5c4d9a1d888f9d8464
12:05:01:Unit 01: Uploading 2.37MiB to 171.64.65.56
12:05:01:Connecting to 171.64.65.56:8080
12:05:10:Unit 01: 0.16%
12:07:43:WARNING: Exception: Failed to send results to work server: Upload failed
12:07:43:Trying to send results to collection server
12:07:43:Unit 01: Uploading 2.37MiB to 171.67.108.26
12:07:43:Connecting to 171.67.108.26:8080
12:07:45:WARNING: WorkServer connection failed on port 8080 trying 80
12:07:45:Connecting to 171.67.108.26:80
12:07:46:ERROR: Exception: Failed to connect to 171.67.108.26:80: No connection could be made because the target machine actively refused it.
12:07:46:Sending unit results: id:01 state:SEND error:OK project:11294 run:10 clone:359 gen:30 core:0x16 unit:0x0000001e0a3b1e5c4d9a1d888f9d8464
12:07:47:Unit 01: Uploading 2.37MiB to 171.64.65.56
12:07:47:Connecting to 171.64.65.56:8080
12:08:11:Unit 00:Completed  11000000 out of 50000000 steps (22%).
12:10:23:WARNING: Exception: Failed to send results to work server: Upload failed
12:10:23:Trying to send results to collection server
12:10:23:Unit 01: Uploading 2.37MiB to 171.67.108.26
12:10:23:Connecting to 171.67.108.26:8080
12:10:25:WARNING: WorkServer connection failed on port 8080 trying 80
12:10:25:Connecting to 171.67.108.26:80
12:10:26:ERROR: Exception: Failed to connect to 171.67.108.26:80: No connection could be made because the target machine actively refused it.
12:10:26:Sending unit results: id:01 state:SEND error:OK project:11294 run:10 clone:359 gen:30 core:0x16 unit:0x0000001e0a3b1e5c4d9a1d888f9d8464
12:10:26:Unit 01: Uploading 2.37MiB to 171.64.65.56
12:10:26:Connecting to 171.64.65.56:8080
12:10:57:WARNING: Exception: Failed to send results to work server: Upload failed
12:10:57:Trying to send results to collection server
12:10:57:Unit 01: Uploading 2.37MiB to 171.67.108.26
12:10:57:Connecting to 171.67.108.26:8080
12:10:59:WARNING: WorkServer connection failed on port 8080 trying 80
12:10:59:Connecting to 171.67.108.26:80
12:11:00:ERROR: Exception: Failed to connect to 171.67.108.26:80: No connection could be made because the target machine actively refused it.
12:14:41:Sending unit results: id:01 state:SEND error:OK project:11294 run:10 clone:359 gen:30 core:0x16 unit:0x0000001e0a3b1e5c4d9a1d888f9d8464
12:14:41:Unit 01: Uploading 2.37MiB to 171.64.65.56
12:14:41:Connecting to 171.64.65.56:8080
12:15:50:Unit 00:Completed  11500000 out of 50000000 steps (23%).
12:17:17:WARNING: Exception: Failed to send results to work server: Upload failed
12:17:17:Trying to send results to collection server
12:17:17:Unit 01: Uploading 2.37MiB to 171.67.108.26
12:17:17:Connecting to 171.67.108.26:8080
12:17:19:WARNING: WorkServer connection failed on port 8080 trying 80
12:17:19:Connecting to 171.67.108.26:80
12:17:20:ERROR: Exception: Failed to connect to 171.67.108.26:80: No connection could be made because the target machine actively refused it.
12:21:32:Sending unit results: id:01 state:SEND error:OK project:11294 run:10 clone:359 gen:30 core:0x16 unit:0x0000001e0a3b1e5c4d9a1d888f9d8464
12:21:32:Unit 01: Uploading 2.37MiB to 171.64.65.56
12:21:32:Connecting to 171.64.65.56:8080
12:22:05:WARNING: Exception: Failed to send results to work server: Upload failed
12:22:05:Trying to send results to collection server
12:22:05:Unit 01: Uploading 2.37MiB to 171.67.108.26
12:22:05:Connecting to 171.67.108.26:8080
12:22:07:WARNING: WorkServer connection failed on port 8080 trying 80
12:22:07:Connecting to 171.67.108.26:80
12:22:08:ERROR: Exception: Failed to connect to 171.67.108.26:80: No connection could be made because the target machine actively refused it.
12:23:29:Unit 00:Completed  12000000 out of 50000000 steps (24%).
12:31:08:Unit 00:Completed  12500000 out of 50000000 steps (25%).
12:32:38:Sending unit results: id:01 state:SEND error:OK project:11294 run:10 clone:359 gen:30 core:0x16 unit:0x0000001e0a3b1e5c4d9a1d888f9d8464
12:32:38:Unit 01: Uploading 2.37MiB to 171.64.65.56
12:32:38:Connecting to 171.64.65.56:8080
12:33:08:WARNING: Exception: Failed to send results to work server: Upload failed
12:33:08:Trying to send results to collection server
12:33:08:Unit 01: Uploading 2.37MiB to 171.67.108.26
12:33:09:Connecting to 171.67.108.26:8080
12:33:10:WARNING: WorkServer connection failed on port 8080 trying 80
12:33:10:Connecting to 171.67.108.26:80
12:33:12:ERROR: Exception: Failed to connect to 171.67.108.26:80: No connection could be made because the target machine actively refused it.
12:38:51:Unit 00:Completed  13000000 out of 50000000 steps (26%).
I hope this server will be fixed soon as have another WU for the same IP address that will be completed this evening PROJECT ID 11293.


Topic merge and retitle. ~sorto'
Mactin
Posts: 225
Joined: Sun Dec 02, 2007 1:08 pm
Location: Outremont, Montréal, Québec

171.64.65.56 down ?

Post by Mactin »

I've been trying to send (during the night) a WU back to 171.64.65.56 (and get another WU to fold) sinse 0700U.

At 1300U (0900L) I switched off advanced and got a WU from 171.64.65.102

Could someone please check the server ?

logs:

Code: Select all

07:17:30:Unit 03:Folding@home Core Shutdown: FINISHED_UNIT
07:17:30:FahCore, running Unit 03, returned: FINISHED_UNIT (100 = 0x64)
07:17:30:Sending unit results: id:03 state:SEND error:OK project:11294 run:3 clone:332 gen:59 core:0x16 unit:0x0000003d0a3b1e5c4d9a1c7d4dc45b87
07:17:30:Unit 03: Uploading 2.37MiB to 171.64.65.56
07:17:30:Connecting to 171.64.65.56:8080
07:17:41:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:17:49:WARNING: Exception: Failed to send results to work server: Upload failed
07:17:49:Trying to send results to collection server
07:17:49:Unit 03: Uploading 2.37MiB to 171.67.108.26
07:17:49:Connecting to 171.67.108.26:8080
07:17:51:WARNING: WorkServer connection failed on port 8080 trying 80
07:17:51:Connecting to 171.67.108.26:80
07:17:52:ERROR: Exception: Failed to connect to 171.67.108.26:80: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée.
07:17:52:Sending unit results: id:03 state:SEND error:OK project:11294 run:3 clone:332 gen:59 core:0x16 unit:0x0000003d0a3b1e5c4d9a1c7d4dc45b87
07:17:52:Unit 03: Uploading 2.37MiB to 171.64.65.56
07:17:52:Connecting to 171.64.65.56:8080
07:18:12:WARNING: Exception: Failed to send results to work server: Upload failed
07:18:12:Trying to send results to collection server
07:18:12:Unit 03: Uploading 2.37MiB to 171.67.108.26
07:18:12:Connecting to 171.67.108.26:8080
07:18:13:WARNING: WorkServer connection failed on port 8080 trying 80
07:18:13:Connecting to 171.67.108.26:80
07:18:14:ERROR: Exception: Failed to connect to 171.67.108.26:80: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée.
07:18:52:Sending unit results: id:03 state:SEND error:OK project:11294 run:3 clone:332 gen:59 core:0x16 unit:0x0000003d0a3b1e5c4d9a1c7d4dc45b87
07:18:52:Unit 03: Uploading 2.37MiB to 171.64.65.56
07:18:52:Connecting to 171.64.65.56:8080
07:19:14:WARNING: Exception: Failed to send results to work server: Upload failed
07:19:14:Trying to send results to collection server
07:19:14:Unit 03: Uploading 2.37MiB to 171.67.108.26
07:19:14:Connecting to 171.67.108.26:8080
07:19:15:WARNING: WorkServer connection failed on port 8080 trying 80
07:19:15:Connecting to 171.67.108.26:80
07:19:17:ERROR: Exception: Failed to connect to 171.67.108.26:80: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée.
07:19:58:Connecting to assign-GPU.stanford.edu:80
07:19:59:News: Welcome to Folding@Home
07:19:59:Assigned to work server 171.64.65.56
07:19:59:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:19:59:Connecting to 171.64.65.56:8080
07:20:20:WARNING: WorkServer connection failed on port 8080 trying 80
07:20:20:Connecting to 171.64.65.56:80
07:20:29:Sending unit results: id:03 state:SEND error:OK project:11294 run:3 clone:332 gen:59 core:0x16 unit:0x0000003d0a3b1e5c4d9a1c7d4dc45b87
07:20:30:Unit 03: Uploading 2.37MiB to 171.64.65.56
07:20:30:Connecting to 171.64.65.56:8080
07:20:41:ERROR: Exception: Failed to connect to 171.64.65.56:80: Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu.
07:20:51:WARNING: Exception: Failed to send results to work server: Upload failed
07:20:51:Trying to send results to collection server
07:20:51:Unit 03: Uploading 2.37MiB to 171.67.108.26
07:20:51:Connecting to 171.67.108.26:8080
07:20:53:WARNING: WorkServer connection failed on port 8080 trying 80
07:20:53:Connecting to 171.67.108.26:80
07:20:54:ERROR: Exception: Failed to connect to 171.67.108.26:80: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée.
07:23:07:Sending unit results: id:03 state:SEND error:OK project:11294 run:3 clone:332 gen:59 core:0x16 unit:0x0000003d0a3b1e5c4d9a1c7d4dc45b87
07:23:07:Unit 03: Uploading 2.37MiB to 171.64.65.56
07:23:07:Connecting to 171.64.65.56:8080
07:23:16:Unit 03: 0.16%
07:24:13:Connecting to assign-GPU.stanford.edu:80
07:24:13:News: Welcome to Folding@Home
07:24:13:Assigned to work server 171.64.65.56
07:24:13:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:24:13:Connecting to 171.64.65.56:8080
07:24:46:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:24:46:Cleaning up Unit 00
07:24:46:Connecting to assign-GPU.stanford.edu:80
07:24:46:News: Welcome to Folding@Home
07:24:46:Assigned to work server 171.64.65.56
07:24:46:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:24:47:Connecting to 171.64.65.56:8080
07:25:20:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:25:20:Connecting to assign-GPU.stanford.edu:80
07:25:20:News: Welcome to Folding@Home
07:25:20:Assigned to work server 171.64.65.56
07:25:20:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:25:20:Connecting to 171.64.65.56:8080
07:25:53:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:26:13:WARNING: Exception: Failed to send results to work server: Upload failed
07:26:13:Trying to send results to collection server
07:26:13:Unit 03: Uploading 2.37MiB to 171.67.108.26
07:26:13:Connecting to 171.67.108.26:8080
07:26:14:WARNING: WorkServer connection failed on port 8080 trying 80
07:26:14:Connecting to 171.67.108.26:80
07:26:16:ERROR: Exception: Failed to connect to 171.67.108.26:80: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée.
07:26:20:Connecting to assign-GPU.stanford.edu:80
07:26:20:News: Welcome to Folding@Home
07:26:20:Assigned to work server 171.64.65.56
07:26:20:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:26:20:Connecting to 171.64.65.56:8080
07:26:41:WARNING: WorkServer connection failed on port 8080 trying 80
07:26:41:Connecting to 171.64.65.56:80
07:27:14:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:27:21:Sending unit results: id:03 state:SEND error:OK project:11294 run:3 clone:332 gen:59 core:0x16 unit:0x0000003d0a3b1e5c4d9a1c7d4dc45b87
07:27:21:Unit 03: Uploading 2.37MiB to 171.64.65.56
07:27:21:Connecting to 171.64.65.56:8080
07:27:40:WARNING: Exception: Failed to send results to work server: Upload failed
07:27:40:Trying to send results to collection server
07:27:40:Unit 03: Uploading 2.37MiB to 171.67.108.26
07:27:40:Connecting to 171.67.108.26:8080
07:27:42:WARNING: WorkServer connection failed on port 8080 trying 80
07:27:42:Connecting to 171.67.108.26:80
07:27:43:ERROR: Exception: Failed to connect to 171.67.108.26:80: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée.
07:27:57:Connecting to assign-GPU.stanford.edu:80
07:27:57:News: Welcome to Folding@Home
07:27:57:Assigned to work server 171.64.65.56
07:27:57:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:27:57:Connecting to 171.64.65.56:8080
07:28:30:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:30:34:Connecting to assign-GPU.stanford.edu:80
07:30:34:News: Welcome to Folding@Home
07:30:34:Assigned to work server 171.64.65.56
07:30:34:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:30:34:Connecting to 171.64.65.56:8080
07:30:56:WARNING: WorkServer connection failed on port 8080 trying 80
07:30:56:Connecting to 171.64.65.56:80
07:31:35:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:34:12:Sending unit results: id:03 state:SEND error:OK project:11294 run:3 clone:332 gen:59 core:0x16 unit:0x0000003d0a3b1e5c4d9a1c7d4dc45b87
07:34:13:Unit 03: Uploading 2.37MiB to 171.64.65.56
07:34:13:Connecting to 171.64.65.56:8080
07:34:22:Unit 03: 0.16%
07:34:49:Connecting to assign-GPU.stanford.edu:80
07:34:49:News: Welcome to Folding@Home
07:34:49:Assigned to work server 171.64.65.56
07:34:49:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:34:49:Connecting to 171.64.65.56:8080
07:35:22:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:35:22:Cleaning up Unit 01
07:35:22:Connecting to assign-GPU.stanford.edu:80
07:35:22:News: Welcome to Folding@Home
07:35:22:Assigned to work server 171.64.65.56
07:35:22:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:35:22:Connecting to 171.64.65.56:8080
07:35:44:WARNING: WorkServer connection failed on port 8080 trying 80
07:35:44:Connecting to 171.64.65.56:80
07:36:05:ERROR: Exception: Failed to connect to 171.64.65.56:80: Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu.
07:36:05:Connecting to assign-GPU.stanford.edu:80
07:36:05:News: Welcome to Folding@Home
07:36:05:Assigned to work server 171.64.65.56
07:36:05:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:36:05:Connecting to 171.64.65.56:8080
07:36:24:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:37:05:Connecting to assign-GPU.stanford.edu:80
07:37:05:News: Welcome to Folding@Home
07:37:05:Assigned to work server 171.64.65.56
07:37:05:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:37:05:Connecting to 171.64.65.56:8080
07:37:19:WARNING: Exception: Failed to send results to work server: Upload failed
07:37:19:Trying to send results to collection server
07:37:19:Unit 03: Uploading 2.37MiB to 171.67.108.26
07:37:19:Connecting to 171.67.108.26:8080
07:37:20:WARNING: WorkServer connection failed on port 8080 trying 80
07:37:20:Connecting to 171.67.108.26:80
07:37:21:ERROR: Exception: Failed to connect to 171.67.108.26:80: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée.
07:37:26:WARNING: WorkServer connection failed on port 8080 trying 80
07:37:26:Connecting to 171.64.65.56:80
07:37:45:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:38:42:Connecting to assign-GPU.stanford.edu:80
07:38:42:News: Welcome to Folding@Home
07:38:42:Assigned to work server 171.64.65.56
07:38:42:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:38:42:Connecting to 171.64.65.56:8080
07:39:22:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:41:20:Connecting to assign-GPU.stanford.edu:80
07:41:20:News: Welcome to Folding@Home
07:41:20:Assigned to work server 171.64.65.56
07:41:20:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:41:20:Connecting to 171.64.65.56:8080
07:41:41:WARNING: WorkServer connection failed on port 8080 trying 80
07:41:41:Connecting to 171.64.65.56:80
07:42:00:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:43:25:Unit 02:Completed 32500 out of 250000 steps  (13%)
07:45:18:Sending unit results: id:03 state:SEND error:OK project:11294 run:3 clone:332 gen:59 core:0x16 unit:0x0000003d0a3b1e5c4d9a1c7d4dc45b87
07:45:18:Unit 03: Uploading 2.37MiB to 171.64.65.56
07:45:18:Connecting to 171.64.65.56:8080
07:45:34:Connecting to assign-GPU.stanford.edu:80
07:45:34:News: Welcome to Folding@Home
07:45:34:Assigned to work server 171.64.65.56
07:45:34:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:45:34:Connecting to 171.64.65.56:8080
07:45:39:WARNING: WorkServer connection failed on port 8080 trying 80
07:45:39:Connecting to 171.64.65.56:80
07:45:48:Unit 03: 0.16%
07:46:13:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:46:13:Cleaning up Unit 00
07:46:13:Connecting to assign-GPU.stanford.edu:80
07:46:14:News: Welcome to Folding@Home
07:46:14:Assigned to work server 171.64.65.56
07:46:14:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:46:14:Connecting to 171.64.65.56:8080
07:46:47:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:46:47:Connecting to assign-GPU.stanford.edu:80
07:46:47:News: Welcome to Folding@Home
07:46:47:Assigned to work server 171.64.65.56
07:46:47:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:46:47:Connecting to 171.64.65.56:8080
07:47:08:WARNING: WorkServer connection failed on port 8080 trying 80
07:47:08:Connecting to 171.64.65.56:80
07:47:29:ERROR: Exception: Failed to connect to 171.64.65.56:80: Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu.
07:47:47:Connecting to assign-GPU.stanford.edu:80
07:47:47:News: Welcome to Folding@Home
07:47:47:Assigned to work server 171.64.65.56
07:47:47:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:47:47:Connecting to 171.64.65.56:8080
07:48:26:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:48:45:WARNING: Exception: Failed to send results to work server: Upload failed
07:48:45:Trying to send results to collection server
07:48:45:Unit 03: Uploading 2.37MiB to 171.67.108.26
07:48:45:Connecting to 171.67.108.26:8080
07:48:47:WARNING: WorkServer connection failed on port 8080 trying 80
07:48:47:Connecting to 171.67.108.26:80
07:48:48:ERROR: Exception: Failed to connect to 171.67.108.26:80: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée.
07:49:24:Connecting to assign-GPU.stanford.edu:80
07:49:24:News: Welcome to Folding@Home
07:49:24:Assigned to work server 171.64.65.56
07:49:24:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:49:24:Connecting to 171.64.65.56:8080
07:49:45:WARNING: WorkServer connection failed on port 8080 trying 80
07:49:45:Connecting to 171.64.65.56:80
07:50:05:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:52:01:Connecting to assign-GPU.stanford.edu:80
07:52:01:News: Welcome to Folding@Home
07:52:01:Assigned to work server 171.64.65.56
07:52:01:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:52:01:Connecting to 171.64.65.56:8080
07:52:22:WARNING: WorkServer connection failed on port 8080 trying 80
07:52:22:Connecting to 171.64.65.56:80
07:52:44:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:56:15:Connecting to assign-GPU.stanford.edu:80
07:56:16:News: Welcome to Folding@Home
07:56:16:Assigned to work server 171.64.65.56
07:56:16:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:56:16:Connecting to 171.64.65.56:8080
07:56:37:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:56:37:Cleaning up Unit 01
07:56:37:Connecting to assign-GPU.stanford.edu:80
07:56:37:News: Welcome to Folding@Home
07:56:37:Assigned to work server 171.64.65.56
07:56:37:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:56:37:Connecting to 171.64.65.56:8080
07:56:56:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:56:57:Connecting to assign-GPU.stanford.edu:80
07:56:57:News: Welcome to Folding@Home
07:56:57:Assigned to work server 171.64.65.56
07:56:57:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:56:57:Connecting to 171.64.65.56:8080
07:57:18:WARNING: WorkServer connection failed on port 8080 trying 80
07:57:18:Connecting to 171.64.65.56:80
07:57:37:ERROR: Exception: 10002: Received short response, expected 512 bytes, got 0
07:57:57:Connecting to assign-GPU.stanford.edu:80
07:57:57:News: Welcome to Folding@Home
07:57:57:Assigned to work server 171.64.65.56
07:57:57:Requesting new work unit for slot 01: READY gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
07:57:57:Connecting to 171.64.65.56:8080
Image
sortofageek
Site Admin
Posts: 3110
Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:

Re: 171.64.65.56 down ?

Post by sortofageek »

Server status reports a high CPU load.

At the bottom of the server status page, please see this note:
CPULOAD tells how many processes are running (in the past 1, 5, and 15 minutes). When this number gets above 2-3, the server is probably heavily loaded.
If too many folders try repeatedly to return WUs manually, this just makes an overload problem worse. The best way is to let your client do what it does best, periodically try again at appropriate intervals. In the meantime, you should be getting more work to do and can work around that slot until the WU is able to return home.
sortofageek
Site Admin
Posts: 3110
Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:

Re: Failed to connect to 171.67.108.26:80

Post by sortofageek »

@mfrisbyuk

Your title referred to 171.67.108.26, which is the collection server. The work server is 171.64.65.56.

I am going to merge your post with the topic already started for that work server.


The server troubleshooting topic is stickied at the top of the "Issues with a specific server" forum here: viewtopic.php?f=18&t=17794

For more info on why we shouldn't be reporting the collection server, please see the fourth post in that topic.
sortofageek
Site Admin
Posts: 3110
Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:

Re: 171.64.65.56 down ?

Post by sortofageek »

There is another report by PerryC here ----> viewtopic.php?f=19&t=19872
DarkFoss
Posts: 129
Joined: Fri Apr 16, 2010 11:43 pm
Hardware configuration: AMD 5800X3D Asus ROG Strix X570-E Gaming WiFi II bios 5031 G-Skill TridentZ Neo 3600mhz Asrock Tachi RX 7900XTX Corsair rm850x psu Asus PG32UQXR EK Elite 360 D-rgb aio Win 11pro/Kubuntu 2404.2 LTS Kernel 6.11.x HWE LowLatency UPS BX1500G
Location: Galifrey

Re: Problem returning WUs to 171.64.65.56 - high CPU load

Post by DarkFoss »

You can add me to the list. I have 2 comps trying to send the same wu's..everything is the same as the op..guess the wu's an older one since CS 171.67.108.26 has been in standby mode all month according to the log page.WS 171.64.65.56 doesn't even have 171.67.108.26 listed as a CS..171.64.122.86 171.67.108.25 are listed..to bad traffic directed at 171.67.108.26 can't be redirected to 171.67.108.25 That would sort things out quickly.
Image
VijayPande
Pande Group Member
Posts: 2058
Joined: Fri Nov 30, 2007 6:25 am
Location: Stanford

Re: Problem returning WUs to 171.64.65.56 - high CPU load

Post by VijayPande »

We're looking into this now. Since it's the weekend, our sysadmin staff will likely take a bit longer to get to this one.
Prof. Vijay Pande, PhD
Departments of Chemistry, Structural Biology, and Computer Science
Chair, Biophysics
Director, Folding@home Distributed Computing Project
Stanford University
Grandpa_01
Posts: 1122
Joined: Wed Mar 04, 2009 7:36 am
Hardware configuration: 3 - Supermicro H8QGi-F AMD MC 6174=144 cores 2.5Ghz, 96GB G.Skill DDR3 1333Mhz Ubuntu 10.10
2 - Asus P6X58D-E i7 980X 4.4Ghz 6GB DDR3 2000 A-Data 64GB SSD Ubuntu 10.10
1 - Asus Rampage Gene III 17 970 4.3Ghz DDR3 2000 2-500GB Segate 7200.11 0-Raid Ubuntu 10.10
1 - Asus G73JH Laptop i7 740QM 1.86Ghz ATI 5870M

Re: Problem returning WUs to 171.64.65.56 - high CPU load

Post by Grandpa_01 »

VijayPande wrote:We're looking into this now. Since it's the weekend, our sysadmin staff will likely take a bit longer to get to this one.
I think they went the wrong way with the fix :ewink:

Code: Select all

Sat Oct 22 16:00:10 PDT 2011  171.64.65.56  GPU  vspg4  -  full  DOWN  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  1  171.64.122.86
171.67.108.25
 -  -  -  W; W;  10000, 10000  6.999, 6.999  -  49, 49  64, 64  -  -  ; , 1, 1  A, B  8080G, 8080G  -  -  -  -  -  -  -  vspg4   
Sat Oct 22 17:00:09 PDT 2011  171.64.65.56  GPU  vspg4  -  full  DOWN  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  1  171.64.122.86
171.67.108.25
 -  -  -  W; W;  10000, 10000  6.999, 6.999  -  49, 49  64, 64  -  -  ; , 1, 1  A, B  8080G, 8080G  -  -  -  -  -  -  -  vspg4   
Sat Oct 22 18:00:11 PDT 2011  171.64.65.56  GPU  vspg4  -  full  DOWN  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  1  171.64.122.86
171.67.108.25
 -  -  -  W; W;  10000, 10000  6.999, 6.999  -  49, 49  64, 64  -  -  ; , 1, 1  A, B  8080G, 8080G  -  -  -  -  -  -  -  vspg4   
Sat Oct 22 19:00:10 PDT 2011  171.64.65.56  GPU  vspg4  -  full  DOWN  
Image
2 - SM H8QGi-F AMD 6xxx=112 cores @ 3.2 & 3.9Ghz
5 - SM X9QRI-f+ Intel 4650 = 320 cores @ 3.15Ghz
2 - I7 980X 4.4Ghz 2-GTX680
1 - 2700k 4.4Ghz GTX680
Total = 464 cores folding
VijayPande
Pande Group Member
Posts: 2058
Joined: Fri Nov 30, 2007 6:25 am
Location: Stanford

Re: Problem returning WUs to 171.64.65.56 - high CPU load

Post by VijayPande »

Here's an update. The machine had to be restarted, and then it spent some time fsck-ing. It's back up now (~8am Sunday morning, pacific time).
Prof. Vijay Pande, PhD
Departments of Chemistry, Structural Biology, and Computer Science
Chair, Biophysics
Director, Folding@home Distributed Computing Project
Stanford University
sortofageek
Site Admin
Posts: 3110
Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:

Re: Problem returning WUs to 171.64.65.56 - high CPU load

Post by sortofageek »

Code: Select all

Sun Oct 23 06:00:10 PDT 2011  171.64.65.56  GPU  vspg4  lin5  full  Reject  0.06  0  0  -  17883  5995  -1  0  2210  2210  2210  -  -  -  -  0  0  -  -  1  171.64.122.86
171.67.108.25
 -  0  0  W; W;  10000, 10000  6.999, 6.999  -  49, 49  64, 64  -  -  ; , 1, 1  A, B  8080G, 8080G  -  -  -  -  0  lin5  1  vspg4   
Sun Oct 23 07:00:10 PDT 2011  171.64.65.56  GPU  vspg4  lin5  full  Accepting  0.03  5  0  -  17883  5995  -1  0  2457  2457  2457  -  -  -  -  21  0  -  -  1  171.64.122.86
171.67.108.25
 -  0  1  W; W;  10000, 10000  6.999, 6.999  -  49, 49  64, 64  -  -  ; , 1, 1  A, B  8080G, 8080G  -  -  -  -  0  lin5  1  vspg4   
Sun Oct 23 08:00:10 PDT 2011  171.64.65.56  GPU  vspg4  lin5  full  Accepting  0.07  0  0  999  17883  5995  -1  0  2474  2474  2474  -  -  3  -  10  0  -  -  1  171.64.122.86
171.67.108.25
 -  0  1  W; W;  10000, 10000  6.999, 6.999  -  49, 49  64, 64  -  -  ; , 1, 1  A, B  8080G, 8080G  -  -  -  -  0  lin5  1  vspg4   

Yes, looking healthy again. Thank you, Professor Pande. :)
mfrisbyuk
Posts: 9
Joined: Mon Oct 17, 2011 12:30 pm

Re: Problem returning WUs to 171.64.65.56 - Resolved

Post by mfrisbyuk »

WU returned thanks - @sortofageek
Post Reply