Page 1 of 1

Can not upload to 140.163.4.235

Posted: Thu Aug 14, 2014 9:57 am
by artoar_11

Code: Select all

*********************** Log Started 2014-08-14T09:42:07Z ***********************
09:42:07:************************* Folding@home Client *************************
09:42:07:      Website: http://folding.stanford.edu/
09:42:07:    Copyright: (c) 2009-2012 Stanford University
09:42:07:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
09:42:07:         Args: --lifeline 1188 --command-port=36330
09:42:07:       Config: C:/Users/Arto/AppData/Roaming/FAHClient/config.xml
09:42:07:******************************** Build ********************************
09:42:07:      Version: 7.2.9
09:42:07:         Date: Oct 3 2012
09:42:07:         Time: 18:05:48
09:42:07:      SVN Rev: 3578
09:42:07:       Branch: fah/trunk/client
09:42:07:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
09:42:07:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
09:42:07:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
09:42:07:     Platform: win32 XP
09:42:07:         Bits: 32
09:42:07:         Mode: Release
09:42:07:******************************* System ********************************
09:42:07:          CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
09:42:07:       CPU ID: GenuineIntel Family 6 Model 42 Stepping 7
09:42:07:         CPUs: 4
09:42:07:       Memory: 3.90GiB
09:42:07:  Free Memory: 2.28GiB
09:42:07:      Threads: WINDOWS_THREADS
09:42:07:   On Battery: false
09:42:07:   UTC offset: 3
09:42:07:          PID: 4968
09:42:07:          CWD: C:/Users/Arto/AppData/Roaming/FAHClient
09:42:07:           OS: Windows 7 Professional
09:42:07:      OS Arch: AMD64
09:42:07:         GPUs: 1
09:42:07:        GPU 0: NVIDIA:3 GK106 [GeForce GTX 650 Ti]
09:42:07:         CUDA: 3.0
09:42:07:  CUDA Driver: 5050
09:42:07:Win32 Service: false
09:42:07:***********************************************************************
09:42:07:<config>
09:42:07:  <!-- FahCore Control -->
09:42:07:  <checkpoint v='9'/>
09:42:07:
09:42:07:  <!-- Folding Slot Configuration -->
09:42:07:  <gpu v='true'/>
09:42:07:
09:42:07:  <!-- Network -->
09:42:07:  <proxy v=':8080'/>
09:42:07:
09:42:07:  <!-- User Information -->
09:42:07:  <passkey v='********************************'/>
09:42:07:  <team v='224497'/>
09:42:07:  <user v='artoar_home'/>
09:42:07:
09:42:07:  <!-- Folding Slots -->
09:42:07:  <slot id='0' type='GPU'>
09:42:07:    <client-type v='beta'/>
09:42:07:    <core-priority v='low'/>
09:42:07:    <next-unit-percentage v='100'/>
09:42:07:    <pause-on-start v='false'/>
09:42:07:  </slot>
09:42:07:  <slot id='1' type='SMP'>
09:42:07:    <client-type v='beta'/>
09:42:07:    <cpus v='3'/>
09:42:07:    <next-unit-percentage v='100'/>
09:42:07:    <pause-on-start v='true'/>
09:42:07:  </slot>
09:42:07:</config>
09:42:07:Trying to access database...
09:42:07:Successfully acquired database lock
09:42:07:Enabled folding slot 00: READY gpu:0:"GK106 [GeForce GTX 650 Ti]"
09:42:07:Enabled folding slot 01: PAUSED smp:3
09:42:07:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:10471 run:0 clone:59 gen:7 core:0x18 unit:0x00000008538b3dbb53bea8c911fcff97
09:42:07:WU01:FS00:Uploading 11.07MiB to 140.163.4.235
09:42:07:WU00:FS00:Starting
09:42:07:WU01:FS00:Connecting to 140.163.4.235:8080
09:42:07:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/Arto/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/beta/Core_17.fah/FahCore_17.exe -dir 00 -suffix 01 -version 702 -lifeline 4968 -checkpoint 9 -gpu 0
09:42:07:WU00:FS00:Started FahCore on PID 4504
09:42:07:WU00:FS00:Core PID:2372
09:42:07:WU00:FS00:FahCore 0x17 started
09:42:08:WU00:FS00:0x17:*********************** Log Started 2014-08-14T09:42:07Z ***********************
09:42:08:WU00:FS00:0x17:Project: 9202 (Run 6, Clone 3, Gen 73)
09:42:08:WU00:FS00:0x17:Unit: 0x00000050664f2dd0539febbac4c0d49a
09:42:08:WU00:FS00:0x17:CPU: 0x00000000000000000000000000000000
09:42:08:WU00:FS00:0x17:Machine: 0
09:42:08:WU00:FS00:0x17:Digital signatures verified
09:42:08:WU00:FS00:0x17:Folding@home GPU core17
09:42:08:WU00:FS00:0x17:Version 0.0.55
09:42:08:WU00:FS00:0x17:  Found a checkpoint file
09:42:11:Server connection id=1 on 0.0.0.0:36330 from 127.0.0.1
09:42:24:WU00:FS00:0x17:Completed 750000 out of 5000000 steps (15%)
09:42:24:WU00:FS00:0x17:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
09:42:28:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
09:42:28:WU01:FS00:Connecting to 140.163.4.235:80
09:42:49:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 140.163.4.235: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:42:49:WU01:FS00:Trying to send results to collection server
09:42:49:WU01:FS00:Uploading 11.07MiB to 140.163.4.241
09:42:49:WU01:FS00:Connecting to 140.163.4.241:8080
09:43:10:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
09:43:10:WU01:FS00:Connecting to 140.163.4.241:80
09:43:31:ERROR:WU01:FS00:Exception: Failed to connect to 140.163.4.241: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:43:31:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:10471 run:0 clone:59 gen:7 core:0x18 unit:0x00000008538b3dbb53bea8c911fcff97
09:43:32:WU01:FS00:Uploading 11.07MiB to 140.163.4.235
09:43:32:WU01:FS00:Connecting to 140.163.4.235:8080
09:43:53:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
09:43:53:WU01:FS00:Connecting to 140.163.4.235:80
09:44:14:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 140.163.4.235: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:44:14:WU01:FS00:Trying to send results to collection server
09:44:14:WU01:FS00:Uploading 11.07MiB to 140.163.4.241
09:44:14:WU01:FS00:Connecting to 140.163.4.241:8080
09:44:35:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
09:44:35:WU01:FS00:Connecting to 140.163.4.241:80
09:44:56:ERROR:WU01:FS00:Exception: Failed to connect to 140.163.4.241: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:44:56:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:10471 run:0 clone:59 gen:7 core:0x18 unit:0x00000008538b3dbb53bea8c911fcff97
09:44:56:WU01:FS00:Uploading 11.07MiB to 140.163.4.235
09:44:56:WU01:FS00:Connecting to 140.163.4.235:8080
09:45:17:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
09:45:17:WU01:FS00:Connecting to 140.163.4.235:80
09:45:38:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 140.163.4.235: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:45:38:WU01:FS00:Trying to send results to collection server
09:45:38:WU01:FS00:Uploading 11.07MiB to 140.163.4.241
09:45:38:WU01:FS00:Connecting to 140.163.4.241:8080
09:45:59:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
09:45:59:WU01:FS00:Connecting to 140.163.4.241:80
I rebooted several times FAHControl, same.
Browser (Chrome) says: "This web page is not available"

Re: Can not upload to 140.163.4.235

Posted: Thu Aug 14, 2014 2:28 pm
by artoar_11
Whatever it was, the problem was gone.

Final credit estimate, 35220.00 points

Re: Can not upload to 140.163.4.235

Posted: Sun Nov 30, 2014 4:55 pm
by RABishop
I've also been stuck for several hours now on 140.163.4.235. You click on the server, and it isn't there. .235 was gone, and so failed to do the download of the new job, and couldn't upload the finished one since it isn't there. So the finished job isn't "really" finished, just 99.99% for 3-4 hours at this point--something is really fouled up with that one, since it says I'm making in excess of 2M points per day, and growing all the time. Even better, I have another system due to finish a job with this SAME nonexistent server in about 7 hours. The one that's been waiting is worth about 29k points. The one that still has 7 hours to go is a bit over 50k points, of course, with time bonuses that are ticking away in one case, and will be so in 7 hours if .235 doesn't come back by then. Neither of them is on THIS computer, so I won't bother with the log stuff which is problem to move here; it doesn't really matter if the server is off line anyway, which it is and has been for a long time.

Re: Can not upload to 140.163.4.235

Posted: Sun Nov 30, 2014 5:04 pm
by RABishop
Ah, I take it back. I DO have a job on this computer also using this apparently defunct server. That one has 15 hours to go. Anyone want to take odds on whether it'll be fixed before THIS Monday--(another problem was supposed to be fixed by LAST Monday, with another server that didn't actually go away that I noticed b4 I had a power failure early this morning here. When I got all the systems back up, the stuff that had been waiting for over a week was finally gone; so I'm not sure what happened to it); I'm betting it will sit quite a while. In another 2 hours, if the 50k job hasn't fed out, I'm just going to delete the slot and reenter it. The 50k job can make that much in a few hours when it's working right.

Re: Can not upload to 140.163.4.235

Posted: Sun Nov 30, 2014 10:22 pm
by Joe_H
140.163.4.235 is up and accepting connections at this time. Have you tried the address, http://140.163.4.235 in a browser from your system? You should get an unauthorized message on a blank screen as the server does not have an accessible web page. If you can not reach the server from your system, then additional troubleshooting is necessary to see where the network is failing between your system and the WS/CS.

Re: Can not upload to 140.163.4.235

Posted: Tue Dec 02, 2014 3:06 am
by RABishop
Just now, a job is finishing on another system for the above WS. That job just hit 99% and should have done a download. It did not start the download. Only a few minutes ago I tried clicking on the address in the Advanced Control window, and it takes me to a page where it always seems to take me for a server that isn't working at that time. It's 404, not found. I've tried it from this system, and got 401 unauthorized in Internet Explorer. It's as if the thing doesn't exist, or only comes on for short periods to catch up, which it seems to be doing, eventually, with everything it gives out; but it's annoying wondering how long b4 it catches up and not knowing if it will be 10 minutes or 10 hours late. All the other WS take you to a page when you click on them in the Advanced Control; but, it seems, never this WS.

Re: Can not upload to 140.163.4.235

Posted: Tue Dec 02, 2014 3:16 am
by RABishop
Well, apparently, it already had the next segment of the job waiting in line, because when it reached 8 seconds to go, the new job just popped up in the lower work window of advanced control and began processes a few seconds after that. The completed job still had not sent (and, in my experience, may not send for several minutes, maybe much, much longer than that); but as long as the new job isn't left waiting with that GTX 970 completely idle, I'll take that. Apparently, while I was typing the above, the finished job WAS sent; and now that GTX 970 is assigned to another WS WITH a Backup Server.

Re: Can not upload to 140.163.4.235

Posted: Tue Dec 02, 2014 3:37 am
by Joe_H
When exactly a new WU is downloaded is partly set by the percentage set in FAHControl and in the case of the newer GPU cores, partly by the core being used. The CPU cores A3, A4 and A5 usually download at exactly 99% or whatever is set in the client. There was a bug in older versions of the client where the download was sometimes at a different point than set.

If you are getting 404 messages, that sounds like networking issues between you and that WS at Sloan-Kettering. I have not had a single problem connecting to there. It does not seem to be a regular occurence, yours is the only report since August. As to getting 401 messages or a web page when you click on an address, that all depends on what version of the WS software is being run on that server. Even older versions would just display a blank page or a blank page with an OK in the top left corner.

The gap in time between a WU ending and being sent includes a wait period to make certain all threads have exited, then a period in which the WU is packed up and then uploaded to be returned. During part of that period the freshly downloaded WU can start processing.