Can not upload to 171.67.108.52

Moderators: Site Moderators, FAHC Science Team

Post Reply
John_Weatherman
Posts: 289
Joined: Sun Dec 02, 2007 4:31 am
Location: Carrizo Plain National Monument, California
Contact:

Can not upload to 171.67.108.52

Post by John_Weatherman »

Second unsucessfull attempt to upload WU 9201 (615,0,104)

Code: Select all

*********************** Log Started 2014-08-04T08:08:40Z ***********************
08:08:40:************************* Folding@home Client *************************
08:08:40:      Website: http://folding.stanford.edu/
08:08:40:    Copyright: (c) 2009-2014 Stanford University
08:08:40:       Author: Joseph Coffland <[email protected]>
08:08:40:         Args: 
08:08:40:       Config: C:/FAH7.44/FAHClient/config.xml
08:08:40:******************************** Build ********************************
08:08:40:      Version: 7.4.4
08:08:40:         Date: Mar 4 2014
08:08:40:         Time: 20:26:54
08:08:40:      SVN Rev: 4130
08:08:40:       Branch: fah/trunk/client
08:08:40:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
08:08:40:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
08:08:40:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
08:08:40:     Platform: win32 XP
08:08:40:         Bits: 32
08:08:40:         Mode: Release
08:08:40:******************************* System ********************************
08:08:40:          CPU: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
08:08:40:       CPU ID: GenuineIntel Family 6 Model 15 Stepping 6
08:08:40:         CPUs: 2
08:08:40:       Memory: 2.00GiB
08:08:40:  Free Memory: 1.10GiB
08:08:40:      Threads: WINDOWS_THREADS
08:08:40:   OS Version: 6.1
08:08:40:  Has Battery: false
08:08:40:   On Battery: false
08:08:40:   UTC Offset: 2
08:08:40:          PID: 6100
08:08:40:          CWD: C:/FAH7.44/FAHClient
08:08:40:           OS: Windows 7 Professional Service Pack 1
08:08:40:      OS Arch: X86
08:08:40:         GPUs: 1
08:08:40:        GPU 0: NVIDIA:2 GF116 [GeForce GTS 450]
08:08:40:         CUDA: 2.1
08:08:40:  CUDA Driver: 6050
08:08:40:Win32 Service: false
08:08:40:***********************************************************************
08:08:40:<config>
08:08:40:  <!-- Folding Core -->
08:08:40:  <checkpoint v='10'/>
08:08:40:
08:08:40:  <!-- Network -->
08:08:40:  <proxy v=':8080'/>
08:08:40:
08:08:40:  <!-- Slot Control -->
08:08:40:  <power v='full'/>
08:08:40:
08:08:40:  <!-- User Information -->
08:08:40:  <passkey v='********************************'/>
08:08:40:  <team v='48913'/>
08:08:40:  <user v='John_Weatherman'/>
08:08:40:
08:08:40:  <!-- Folding Slots -->
08:08:40:  <slot id='0' type='CPU'/>
08:08:40:  <slot id='1' type='GPU'/>
08:08:40:</config>
08:08:40:Trying to access database...
08:08:42:Successfully acquired database lock
08:08:42:Enabled folding slot 00: READY cpu:1
08:08:42:Enabled folding slot 01: READY gpu:0:GF116 [GeForce GTS 450]
08:08:43:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:9201 run:615 clone:0 gen:104 core:0x17 unit:0x000000726652edc45399ee320443d0be
08:08:44:WU02:FS01:Uploading 8.38MiB to 171.67.108.52
08:08:44:WU00:FS01:Starting
08:08:44:WU02:FS01:Connecting to 171.67.108.52:8080
08:08:44:WU00:FS01:Running FahCore: C:\FAH7.44\FAHClient/FAHCoreWrapper.exe C:/FAH7.44/FAHClient/cores/web.stanford.edu/~pande/Win32/x86/NVIDIA/Fermi/Core_17.fah/FahCore_17.exe -dir 00 -suffix 01 -version 704 -lifeline 6100 -checkpoint 10 -gpu 0 -gpu-vendor nvidia
08:08:44:WU00:FS01:Started FahCore on PID 2276
08:08:44:WU00:FS01:Core PID:2216
08:08:44:WU00:FS01:FahCore 0x17 started
08:08:45:WU01:FS00:Starting
08:08:45:WU01:FS00:Running FahCore: C:\FAH7.44\FAHClient/FAHCoreWrapper.exe C:/FAH7.44/FAHClient/cores/web.stanford.edu/~pande/Win32/x86/Core_a4.fah/FahCore_a4.exe -dir 01 -suffix 01 -version 704 -lifeline 6100 -checkpoint 10
08:08:45:WU01:FS00:Started FahCore on PID 4300
08:08:46:WU01:FS00:Core PID:2244
08:08:46:WU01:FS00:FahCore 0xa4 started
08:08:47:WU01:FS00:0xa4:
08:08:47:WU01:FS00:0xa4:*------------------------------*
08:08:47:WU01:FS00:0xa4:Folding@Home Gromacs GB Core
08:08:47:WU01:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
08:08:47:WU00:FS01:0x17:*********************** Log Started 2014-08-04T08:08:46Z ***********************
08:08:47:WU01:FS00:0xa4:
08:08:47:WU00:FS01:0x17:Project: 13000 (Run 865, Clone 0, Gen 28)
08:08:47:WU01:FS00:0xa4:Preparing to commence simulation
08:08:47:WU00:FS01:0x17:Unit: 0x00000058538b3db753108fca191746f3
08:08:47:WU01:FS00:0xa4:- Ensuring status. Please wait.
08:08:47:WU00:FS01:0x17:CPU: 0x00000000000000000000000000000000
08:08:47:WU00:FS01:0x17:Machine: 1
08:08:47:WU00:FS01:0x17:Digital signatures verified
08:08:47:WU00:FS01:0x17:Folding@home GPU core17
08:08:47:WU00:FS01:0x17:Version 0.0.52
08:08:56:WU01:FS00:0xa4:- Looking at optimizations...
08:08:56:WU01:FS00:0xa4:- Working with standard loops on this execution.
08:08:56:WU01:FS00:0xa4:- Previous termination of core was improper.
08:08:56:WU01:FS00:0xa4:- Files status OK
08:08:56:WU01:FS00:0xa4:- Expanded 117526 -> 266072 (decompressed 226.3 percent)
08:08:56:WU01:FS00:0xa4:Called DecompressByteArray: compressed_data_size=117526 data_size=266072, decompressed_data_size=266072 diff=0
08:08:56:WU01:FS00:0xa4:- Digital signature verified
08:08:56:WU01:FS00:0xa4:
08:08:56:WU01:FS00:0xa4:Project: 6369 (Run 33, Clone 80, Gen 3)
08:08:56:WU01:FS00:0xa4:
08:08:56:WU01:FS00:0xa4:Entering M.D.
08:08:58:WU02:FS01:Upload 7.46%
08:09:02:WU01:FS00:0xa4:Using Gromacs checkpoints
08:09:02:WU01:FS00:0xa4:Mapping NT from 1 to 1 
08:09:04:WU02:FS01:Upload 8.21%
08:09:05:WU01:FS00:0xa4:Resuming from checkpoint
08:09:06:WU01:FS00:0xa4:Verified 01/wudata_01.log
08:09:06:WU01:FS00:0xa4:Verified 01/wudata_01.trr
08:09:06:WU01:FS00:0xa4:Verified 01/wudata_01.xtc
08:09:06:WU01:FS00:0xa4:Verified 01/wudata_01.edr
08:09:06:WU01:FS00:0xa4:Completed 2051050 out of 5000000 steps  (41%)
08:09:10:WU02:FS01:Upload 8.95%
08:09:19:WU02:FS01:Upload 10.45%
08:09:26:WU02:FS01:Upload 11.94%
08:09:35:WU02:FS01:Upload 12.68%
08:09:42:WU02:FS01:Upload 14.92%
08:09:49:WU02:FS01:Upload 16.41%
08:09:56:WU02:FS01:Upload 17.91%
08:10:03:WU02:FS01:Upload 19.40%
08:10:13:WU02:FS01:Upload 20.89%
08:10:21:WU02:FS01:Upload 23.13%
08:10:30:WU02:FS01:Upload 24.62%
08:10:38:WU02:FS01:Upload 26.86%
08:10:44:WU02:FS01:Upload 28.35%
08:10:51:WU02:FS01:Upload 29.84%
08:10:58:WU02:FS01:Upload 31.34%
08:11:06:WU02:FS01:Upload 32.83%
08:11:12:WU02:FS01:Upload 33.57%
08:11:19:WU02:FS01:Upload 35.07%
08:11:26:WU02:FS01:Upload 36.56%
08:11:35:WU02:FS01:Upload 38.80%
08:11:43:WU02:FS01:Upload 40.29%
08:11:53:WU02:FS01:Upload 41.78%
08:12:01:WU02:FS01:Upload 43.27%
08:12:12:WU02:FS01:Upload 44.76%
08:12:22:WU02:FS01:Upload 46.26%
08:12:31:WU02:FS01:Upload 47.75%
08:12:39:WU02:FS01:Upload 49.24%
08:12:48:WU02:FS01:Upload 50.73%
08:12:55:WU02:FS01:Upload 51.48%
08:13:02:WU02:FS01:Upload 52.97%
08:13:13:WU02:FS01:Upload 54.46%
08:13:19:WU02:FS01:Upload 55.96%
08:13:27:WU02:FS01:Upload 57.45%
08:13:33:WU02:FS01:Upload 58.94%
08:13:44:WU02:FS01:Upload 60.43%
08:13:50:WU02:FS01:Upload 61.18%
08:14:00:WU02:FS01:Upload 62.67%
08:14:06:WU02:FS01:Upload 64.16%
08:14:14:WU02:FS01:Upload 65.65%
08:14:20:WU02:FS01:Upload 67.15%
08:14:28:WU02:FS01:Upload 68.64%
08:14:38:WU02:FS01:Upload 70.13%
08:14:46:WU02:FS01:Upload 71.62%
08:14:52:WU02:FS01:Upload 72.37%
08:14:58:WU02:FS01:Upload 73.86%
08:15:05:WU02:FS01:Upload 74.61%
08:15:13:WU02:FS01:Upload 76.85%
08:15:25:WU02:FS01:Upload 79.08%
08:15:31:WU02:FS01:Upload 79.83%
08:15:40:WU02:FS01:Upload 81.32%
08:15:46:WU02:FS01:Upload 82.07%
08:15:54:WU02:FS01:Upload 83.56%
08:16:04:WU02:FS01:Upload 85.05%
08:16:13:WU02:FS01:Upload 85.80%
08:16:21:WU02:FS01:Upload 87.29%
08:16:29:WU02:FS01:Upload 88.04%
08:16:41:WU02:FS01:Upload 90.27%
08:16:49:WU02:FS01:Upload 91.77%
08:16:56:WU02:FS01:Upload 92.51%
08:17:06:WU02:FS01:Upload 94.01%
08:17:15:WU02:FS01:Upload 94.75%
08:17:23:WU02:FS01:Upload 96.24%
08:17:26:WU00:FS01:0x17:Completed 0 out of 5000000 steps (0%)
08:17:26:WU00:FS01:0x17:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
08:17:33:WU02:FS01:Upload 98.48%
08:17:43:WU02:FS01:Upload 99.97%
and there it sits.No problems my end with connecting so is the server having problems?
P5-133XL
Posts: 2948
Joined: Sun Dec 02, 2007 4:36 am
Hardware configuration: Machine #1:

Intel Q9450; 2x2GB=8GB Ram; Gigabyte GA-X48-DS4 Motherboard; PC Power and Cooling Q750 PS; 2x GTX 460; Windows Server 2008 X64 (SP1).

Machine #2:

Intel Q6600; 2x2GB=4GB Ram; Gigabyte GA-X48-DS4 Motherboard; PC Power and Cooling Q750 PS; 2x GTX 460 video card; Windows 7 X64.

Machine 3:

Dell Dimension 8400, 3.2GHz P4 4x512GB Ram, Video card GTX 460, Windows 7 X32

I am currently folding just on the 5x GTX 460's for aprox. 70K PPD
Location: Salem. OR USA

Re: Can not upload to 171.67.108.52

Post by P5-133XL »

You can safely delete the WU. It actually succeeded uploading and being credited, probably from the first time since the time stamp is 7 hours earlier than the log you showed.

Hi John_Weatherman (team 48913),
Your WU (P9201 R615 C0 G104) was added to the stats database on 2014-08-04 01:04:25 for 8344 points of credit.

P.S. It would be nice if you didn't cut the log short and actually showed the uploading failure messages.
Image
John_Weatherman
Posts: 289
Joined: Sun Dec 02, 2007 4:31 am
Location: Carrizo Plain National Monument, California
Contact:

Re: Can not upload to 171.67.108.52

Post by John_Weatherman »

Ok, I got no upload completed or failure message and it's trying to upload again. It's still sitting in the work queue.. The first time it got to upload at 99.23% and no more messages for 15 minutes so I assumed it had not completed and rebooted to try again. So is this a bug in the 7.44 client?
P5-133XL
Posts: 2948
Joined: Sun Dec 02, 2007 4:36 am
Hardware configuration: Machine #1:

Intel Q9450; 2x2GB=8GB Ram; Gigabyte GA-X48-DS4 Motherboard; PC Power and Cooling Q750 PS; 2x GTX 460; Windows Server 2008 X64 (SP1).

Machine #2:

Intel Q6600; 2x2GB=4GB Ram; Gigabyte GA-X48-DS4 Motherboard; PC Power and Cooling Q750 PS; 2x GTX 460 video card; Windows 7 X64.

Machine 3:

Dell Dimension 8400, 3.2GHz P4 4x512GB Ram, Video card GTX 460, Windows 7 X32

I am currently folding just on the 5x GTX 460's for aprox. 70K PPD
Location: Salem. OR USA

Re: Can not upload to 171.67.108.52

Post by P5-133XL »

The client is supposed to wait (10-20 minutes?) and if there is no response there is then supposed to be a log entry saying that there was no response and it will try again. There is also a known bug in v7 that for some interrupted uploads the client won't clear it from the queue.

You can safely delete the WU by first pausing the client (so that there is no file lock active) then deleting the 02 folder in the work folder (Start->All programs->FAHClient->Data directory->Work) then delete 02 and finally unpause the client. The client will eventually detect the removed queue entry and clean itself up.
Image
John_Weatherman
Posts: 289
Joined: Sun Dec 02, 2007 4:31 am
Location: Carrizo Plain National Monument, California
Contact:

Re: Can not upload to 171.67.108.52

Post by John_Weatherman »

Thanks for the info. I've deleted the work folder. As it seems to have uploaded on the first attempt, it maybe is an idea for other folders to see what is written on their logs to check for messages?
Joe_H
Site Admin
Posts: 7926
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: Can not upload to 171.67.108.52

Post by Joe_H »

The log will show no acknowledgement of the upload, but without one of the mods checking anyone running into this would not know whether or not the upload actually succeeded. This does point to a network problem between the server and your system causing the ACK to be lost or dropped. In this case it is not a bug in the client, the issue about interrupted uploads and not retrying P5-133XL mentioned is unrelated to your problem.

What you should see in your log is a sequence of messages like this:

Code: Select all

10:53:38:WU00:FS00:Upload 91.82%
10:53:44:WU00:FS00:Upload 96.86%
10:53:55:WU00:FS00:Upload complete
10:53:56:WU00:FS00:Server responded WORK_ACK (400)
10:53:56:WU00:FS00:Final credit estimate, 4320.00 points
10:53:56:WU00:FS00:Cleaning up
Without the WORK_ACK the client will keep retrying. Why you did not see one could be because it was dropped by your ISP, or your router did not pass it through, or another reason.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
John_Weatherman
Posts: 289
Joined: Sun Dec 02, 2007 4:31 am
Location: Carrizo Plain National Monument, California
Contact:

Re: Can not upload to 171.67.108.52

Post by John_Weatherman »

On the same machine I uploaded the previously complteted GPU WU project 13000 (2065, 3. 40) to server at 140.163.4.231 and got the WORK_ACK(400) message.So I assume the problem lies with the server at Stanford's end.It also uploaded a lot quicker!
Joe_H
Site Admin
Posts: 7926
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: Can not upload to 171.67.108.52

Post by Joe_H »

If the problem was with the server, then we would be getting a lot more reports of uploading issues. However, the issue could be anywhere in between the server and your systems, some routers drop what they consider redundant packets like ACK's. The two machines are definitely in two different IP domains.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
John_Weatherman
Posts: 289
Joined: Sun Dec 02, 2007 4:31 am
Location: Carrizo Plain National Monument, California
Contact:

Re: Can not upload to 171.67.108.52

Post by John_Weatherman »

OK, after a little questioning of my ISP, they claim that they don't drop ACK messages when things get busy, so .... Anybody got any ideas? I'm returning work but these 2 WUs have got me stumped. Message me if you've got any ideas or things to check. Thanks fellow Folders!
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Can not upload to 171.67.108.52

Post by bruce »

I'd look more closely at the options in your router.
Post Reply