171.67.108.26 - not accepting WUs? [True. CS offline]

Moderators: Site Moderators, FAHC Science Team

Mancunian_Nick
Posts: 21
Joined: Tue Apr 30, 2013 12:00 pm

171.67.108.26 - not accepting WUs? [True. CS offline]

Post by Mancunian_Nick »

Hi guys

Forgive me but this is something I don't think I've seen before, or if it's happened not noticed it until now so thought I'd report it. I have had my PC on hibernation for a few hours and turned it back on about 20 minutes ago and got this in my log (apologies if this is rather long?)

Code: Select all

******************************* Date: 2013-05-08 *******************************
00:10:46:WARNING:WU02:FS01:Detected clock skew (6 hours 14 mins), adjusting time estimates
00:10:48:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.26:80: A socket operation was attempted to an unreachable network.
00:10:48:WU01:FS00:Sending unit results: id:01 state:SEND error:DUMPED project:10501 run:394 clone:0 gen:1419 core:0x11 unit:0x00000c2b6652eda54b6ea9fb000099ea
00:10:49:WU00:FS00:0x11:Tpr hash 00/wudata_01.tpr:  1971980774 2429354591 681773406 1481081120 3711057117
00:10:49:WU00:FS00:0x11:
00:10:49:WU00:FS00:0x11:Calling fah_main args: 14 usage=100
00:10:49:WU00:FS00:0x11:
00:10:53:WU01:FS00:Uploading 2.31KiB to 171.67.108.21
00:10:53:WU01:FS00:Connecting to 171.67.108.21:8080
00:10:53:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
00:10:53:WU01:FS00:Connecting to 171.67.108.21:80
00:11:00:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to connect to 171.67.108.21:80: A socket operation was attempted to an unreachable network.
00:11:00:WU01:FS00:Trying to send results to collection server
00:11:05:WU01:FS00:Uploading 2.31KiB to 171.67.108.26
00:11:05:WU01:FS00:Connecting to 171.67.108.26:8080
00:11:14:FS00:Shutting core down
00:11:21:WU00:FS00:0x11:Client no longer detected. Shutting down core 
00:11:21:WU00:FS00:0x11:
00:11:21:WU00:FS00:0x11:Folding@home Core Shutdown: CLIENT_DIED
00:11:26:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
00:11:26:WU01:FS00:Connecting to 171.67.108.26:80
00:11:29:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
00:11:47:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.26: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.
00:11:48:WU01:FS00:Sending unit results: id:01 state:SEND error:DUMPED project:10501 run:394 clone:0 gen:1419 core:0x11 unit:0x00000c2b6652eda54b6ea9fb000099ea
00:11:50:WU01:FS00:Uploading 2.31KiB to 171.67.108.21
00:11:50:WU01:FS00:Connecting to 171.67.108.21:8080
00:11:51:WARNING:WU01:FS00:Exception: Failed to send results to work server: 10001: Server responded: HTTP_BAD_REQUEST
00:11:51:WU01:FS00:Trying to send results to collection server
00:11:53:WU01:FS00:Uploading 2.31KiB to 171.67.108.26
00:11:53:WU01:FS00:Connecting to 171.67.108.26:8080
00:12:14:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
00:12:14:WU01:FS00:Connecting to 171.67.108.26:80
00:12:35:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.26: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.
00:13:25:WU01:FS00:Sending unit results: id:01 state:SEND error:DUMPED project:10501 run:394 clone:0 gen:1419 core:0x11 unit:0x00000c2b6652eda54b6ea9fb000099ea
00:13:25:WU01:FS00:Uploading 2.31KiB to 171.67.108.21
00:13:25:WU01:FS00:Connecting to 171.67.108.21:8080
00:13:26:WARNING:WU01:FS00:Exception: Failed to send results to work server: 10001: Server responded: HTTP_BAD_REQUEST
00:13:26:WU01:FS00:Trying to send results to collection server
00:13:26:WU01:FS00:Uploading 2.31KiB to 171.67.108.26
00:13:26:WU01:FS00:Connecting to 171.67.108.26:8080
00:13:47:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
00:13:47:WU01:FS00:Connecting to 171.67.108.26:80
00:14:09:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.26: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.
00:16:02:WU01:FS00:Sending unit results: id:01 state:SEND error:DUMPED project:10501 run:394 clone:0 gen:1419 core:0x11 unit:0x00000c2b6652eda54b6ea9fb000099ea
00:16:03:WU01:FS00:Uploading 2.31KiB to 171.67.108.21
00:16:03:WU01:FS00:Connecting to 171.67.108.21:8080
00:16:03:WARNING:WU01:FS00:Exception: Failed to send results to work server: 10001: Server responded: HTTP_BAD_REQUEST
00:16:03:WU01:FS00:Trying to send results to collection server
00:16:03:WU01:FS00:Uploading 2.31KiB to 171.67.108.26
00:16:03:WU01:FS00:Connecting to 171.67.108.26:8080
00:16:24:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
00:16:24:WU01:FS00:Connecting to 171.67.108.26:80
00:16:45:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.26: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.
00:20:17:WU01:FS00:Sending unit results: id:01 state:SEND error:DUMPED project:10501 run:394 clone:0 gen:1419 core:0x11 unit:0x00000c2b6652eda54b6ea9fb000099ea
00:20:17:WU01:FS00:Uploading 2.31KiB to 171.67.108.21
00:20:17:WU01:FS00:Connecting to 171.67.108.21:8080
00:20:18:WARNING:WU01:FS00:Too many failed attempts to report WORK_DUMPED, dumping
00:20:18:WARNING:WU01:FS00:Exception: Failed to send results to work server: 10001: Server responded: HTTP_BAD_REQUEST
00:20:18:WU01:FS00:Trying to send results to collection server
00:20:18:WU01:FS00:Uploading 2.31KiB to 171.67.108.26
00:20:18:WU01:FS00:Connecting to 171.67.108.26:8080
00:20:39:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
00:20:39:WU01:FS00:Connecting to 171.67.108.26:80
00:21:00:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.26: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.
00:21:00:WU01:FS00:Cleaning up
I'm using version 7.3.6 for Windows (7 Ultimate 64bit) and am particularly puzzled by the last line of the log - cleaning up. Does this mean the work file(s) has been deleted? Nothing has happened since as far as I can see except on the client status (ID 01 - sending work units or whatever it was) has now gone. I first Googled the IP address and discovered a similar thread to this from February 2010 where there was a similar problem with this IP/server although I'm not suggesting a connection.

Incidently, I keep a close eye on my team points and position and for the last several days now (2 or 3 at least) I've not moved - at position 236 with 873 points and a 3 which, I presume, is the number of completed work units sent? Does this mean if my work units have been trashed/deleted that I won't get the points? That's quite frustrating if indeed that's the case. Guess I'll keep watching the logs and hope for the best later on.

Mod Edit: Added Code Tags - PantherX
PantherX
Site Moderator
Posts: 6986
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:

Re: 171.67.108.26 - not accepting work units?

Post by PantherX »

Please note that the Work Server is currently operating as fine as I get OK in my web browser (port 80 and 8080) and Server Status is showing everything working as normal. The Work Server IP is this:
00:10:53:WU01:FS00:Connecting to 171.67.108.21:8080

Try opening these in your Web Browser:
http://171.67.108.21:80/
http://171.67.108.21:8080/
If everything is fine on your end, you should get "OK" in your web browser.

What you are focusing on is the Collection Server and it is already known that some don't work. In this case, this Server isn't meant to be operational and is shown as such in the Server Status:
00:13:26:WU01:FS00:Connecting to 171.67.108.26:8080

Since the Work Server is up and running, it should have accepted your WU. However, your client decided to dump the WU so you will not get any points for this:
00:20:18:WARNING:WU01:FS00:Too many failed attempts to report WORK_DUMPED, dumping

Has something changed on your network? Did you upgrade any Anti-Virus application or Network related software? is this happening frequently?
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Mancunian_Nick
Posts: 21
Joined: Tue Apr 30, 2013 12:00 pm

Re: 171.67.108.26 - not accepting work units?

Post by Mancunian_Nick »

PantherX wrote:Please note that the Work Server is currently operating as fine as I get OK in my web browser (port 80 and 8080) and Server Status is showing everything working as normal. The Work Server IP is this:
00:10:53:WU01:FS00:Connecting to 171.67.108.21:8080

Try opening these in your Web Browser:
http://171.67.108.21:80/
http://171.67.108.21:8080/
If everything is fine on your end, you should get "OK" in your web browser.

What you are focusing on is the Collection Server and it is already known that some don't work. In this case, this Server isn't meant to be operational and is shown as such in the Server Status:
00:13:26:WU01:FS00:Connecting to 171.67.108.26:8080

Since the Work Server is up and running, it should have accepted your WU. However, your client decided to dump the WU so you will not get any points for this:
00:20:18:WARNING:WU01:FS00:Too many failed attempts to report WORK_DUMPED, dumping

Has something changed on your network? Did you upgrade any Anti-Virus application or Network related software? is this happening frequently?
Hello Panther

Thank you for your prompt reply.

I have tried both links in my browser as you suggested and yes they both give me "OK"

I'll be the first to admit I'm not particularly techie minded especially where folding client is concerned. I just noticed all the failed attempts and the clearing line, as I said in my original post.

I don't know why it didn't accept my WU but it clearly didn't and this is most frustrating as it was quite a long WU as far as I know. Nothing has changed - not running a network, just a lone/sole PC.

I can't say if it's happening frequently as it's the first time I've seen this, although I usually hibernate my PC around 6pm each evening (UK time) and again when I go to bed around 2 or 3am, sometimes later. It would certainly explain why I've not been getting more points in the last few days - shame the client can't give points on a daily basis depending on the word done rather than only waiting until the whole WU has been done - but maybe that's simply wishful thinking. I've only had one line in the log since the one I posted originally - 01:04:59:WU02:FS01:0xa4:Completed 1275000 out of 2500000 steps (51%) but I think that's the other work unit - I seem to always have 2 on the go - one in my cpu and one in my gpu, although the gpu is almost invariably not working as it's "Paused: waiting for idle" and as I'm usually working on the computer doing something or other when it's on, it's unlikely those will progress very much at all - but I suppose it's not doing any harm although seems rather pointless having it really. If I was rich and could afford to leave my PC connected all the time even when I'm not using it, I daresay it would start working then. Oh well never mind. :)
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.67.108.26 - not accepting work units?

Post by bruce »

There's a reasonably good chance that you're experiencing the problem described in Ticket #983 and it's also somehow related to hibernation (maybe the client tried re-sending too quickly after ending hibernation or something like that). If so, exiting the client and restarting it will probably cure it -- or simply rebooting. Let us know.
Mancunian_Nick
Posts: 21
Joined: Tue Apr 30, 2013 12:00 pm

Re: 171.67.108.26 - not accepting work units?

Post by Mancunian_Nick »

Thanks Bruce. You may well be right as I've just re-opened my folding client after having it closed for a while whilst I was doing other things on my PC and whilst the actual computer wasn't in hibernation immediately before I started it, I noticed once again more work units being dumped being unable to send (what a waste of time and energy - REALLY frustating/annoying me this is) work unit(s) - this time on 171.67.108.25 - no idea if it's in any way related/connected to 171.67.108.26 or not but here's my log from after restarting my client.

Code: Select all

17:04:40:</config>
17:04:40:Trying to access database...
17:04:40:Successfully acquired database lock
17:04:40:Enabled folding slot 00: PAUSED gpu:0:G94 [GeForce 9600 GT] (waiting for idle)
17:04:40:Enabled folding slot 01: READY cpu:1
17:04:41:WU01:FS00:Sending unit results: id:01 state:SEND error:DUMPED project:5772 run:1 clone:277 gen:3018 core:0x11 unit:0x48874a2e518cdb100bca01150001168c
17:04:42:WU01:FS00:Uploading 3.77KiB to 171.67.108.11
17:04:42:WU00:FS01:Starting
17:04:42:WU00:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/Nick/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 703 -lifeline 120804 -checkpoint 15
17:04:42:WU01:FS00:Connecting to 171.67.108.11:8080
17:04:42:WU00:FS01:Started FahCore on PID 126480
17:04:46:WU00:FS01:Core PID:128152
17:04:46:WU00:FS01:FahCore 0xa4 started
17:04:46:WU00:FS01:0xa4:
17:04:46:WU00:FS01:0xa4:*------------------------------*
17:04:46:WU00:FS01:0xa4:Folding@Home Gromacs GB Core
17:04:46:WU00:FS01:0xa4:Version 2.27 (Dec. 15, 2010)
17:04:46:WU00:FS01:0xa4:
17:04:46:WU00:FS01:0xa4:Preparing to commence simulation
17:04:46:WU00:FS01:0xa4:- Looking at optimizations...
17:04:46:WU00:FS01:0xa4:- Files status OK
17:04:47:WU00:FS01:0xa4:- Expanded 1086852 -> 3059672 (decompressed 281.5 percent)
17:04:47:WU00:FS01:0xa4:Called DecompressByteArray: compressed_data_size=1086852 data_size=3059672, decompressed_data_size=3059672 diff=0
17:04:47:WU00:FS01:0xa4:- Digital signature verified
17:04:47:WU00:FS01:0xa4:
17:04:47:WU00:FS01:0xa4:Project: 8082 (Run 25, Clone 1, Gen 54)
17:04:47:WU00:FS01:0xa4:
17:04:47:WU00:FS01:0xa4:Assembly optimizations on if available.
17:04:47:WU00:FS01:0xa4:Entering M.D.
17:04:48:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to read stream
17:04:48:WU01:FS00:Trying to send results to collection server
17:04:48:WU01:FS00:Uploading 3.77KiB to 171.67.108.25
17:04:48:WU01:FS00:Connecting to 171.67.108.25:8080
17:04:53:WU00:FS01:0xa4:Using Gromacs checkpoints
17:04:54:WU00:FS01:0xa4:Mapping NT from 1 to 1 
17:04:54:WU00:FS01:0xa4:Resuming from checkpoint
17:04:54:WU00:FS01:0xa4:Verified 00/wudata_01.log
17:04:54:WU00:FS01:0xa4:Verified 00/wudata_01.trr
17:04:55:WU00:FS01:0xa4:Verified 00/wudata_01.xtc
17:04:55:WU00:FS01:0xa4:Verified 00/wudata_01.edr
17:04:55:WU00:FS01:0xa4:Completed 372560 out of 500000 steps  (74%)
17:05:09:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
17:05:09:WU01:FS00:Connecting to 171.67.108.25:80
17:05:30:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.25: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.
17:05:39:WU01:FS00:Sending unit results: id:01 state:SEND error:DUMPED project:5772 run:1 clone:277 gen:3018 core:0x11 unit:0x48874a2e518cdb100bca01150001168c
17:05:39:WU01:FS00:Uploading 3.77KiB to 171.67.108.11
17:05:39:WU01:FS00:Connecting to 171.67.108.11:8080
17:05:40:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to read stream
17:05:40:WU01:FS00:Trying to send results to collection server
17:05:40:WU01:FS00:Uploading 3.77KiB to 171.67.108.25
17:05:40:WU01:FS00:Connecting to 171.67.108.25:8080
17:06:01:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
17:06:01:WU01:FS00:Connecting to 171.67.108.25:80
17:06:22:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.25: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.
17:06:39:WU01:FS00:Sending unit results: id:01 state:SEND error:DUMPED project:5772 run:1 clone:277 gen:3018 core:0x11 unit:0x48874a2e518cdb100bca01150001168c
17:06:39:WU01:FS00:Uploading 3.77KiB to 171.67.108.11
17:06:39:WU01:FS00:Connecting to 171.67.108.11:8080
17:06:39:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to read stream
17:06:39:WU01:FS00:Trying to send results to collection server
17:06:40:WU01:FS00:Uploading 3.77KiB to 171.67.108.25
17:06:40:WU01:FS00:Connecting to 171.67.108.25:8080
17:07:01:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
17:07:01:WU01:FS00:Connecting to 171.67.108.25:80
17:07:22:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.25: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.
17:07:43:Removing old file 'configs/config-20130430-111250.xml'
17:07:43:Saving configuration to config.xml
17:07:43:<config>
17:07:43:  <!-- Network -->
17:07:43:  <proxy v=':8080'/>
17:07:43:
17:07:43:  <!-- Slot Control -->
17:07:43:  <pause-on-battery v='false'/>
17:07:43:
17:07:43:  <!-- User Information -->
17:07:43:  <passkey v='********************************'/>
17:07:43:  <team v='55186'/>
17:07:43:  <user v='Nick_Jay'/>
17:07:43:
17:07:43:  <!-- Folding Slots -->
17:07:43:  <slot id='0' type='GPU'/>
17:07:43:  <slot id='1' type='CPU'/>
17:07:43:</config>
17:08:16:WU01:FS00:Sending unit results: id:01 state:SEND error:DUMPED project:5772 run:1 clone:277 gen:3018 core:0x11 unit:0x48874a2e518cdb100bca01150001168c
17:08:16:WU01:FS00:Uploading 3.77KiB to 171.67.108.11
17:08:16:WU01:FS00:Connecting to 171.67.108.11:8080
17:08:16:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to read stream
17:08:16:WU01:FS00:Trying to send results to collection server
17:08:16:WU01:FS00:Uploading 3.77KiB to 171.67.108.25
17:08:16:WU01:FS00:Connecting to 171.67.108.25:8080
17:08:37:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
17:08:37:WU01:FS00:Connecting to 171.67.108.25:80
17:08:59:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.25: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.
17:10:53:WU01:FS00:Sending unit results: id:01 state:SEND error:DUMPED project:5772 run:1 clone:277 gen:3018 core:0x11 unit:0x48874a2e518cdb100bca01150001168c
17:10:53:WU01:FS00:Uploading 3.77KiB to 171.67.108.11
17:10:53:WU01:FS00:Connecting to 171.67.108.11:8080
17:10:54:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to read stream
17:10:54:WU01:FS00:Trying to send results to collection server
17:10:54:WU01:FS00:Uploading 3.77KiB to 171.67.108.25
17:10:54:WU01:FS00:Connecting to 171.67.108.25:8080
17:11:15:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
17:11:15:WU01:FS00:Connecting to 171.67.108.25:80
17:11:36:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.25: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.
Just gone back to my client to see if there are any other messages and if perhaps it sent the WU but got this now, continuing from above ...

Code: Select all

17:12:57:13:127.0.0.1:New Web connection
17:13:57:WARNING:Exception: 29:127.0.0.1: Send error: 10053: An established connection was aborted by the software in your host machine.
17:14:04:WARNING:Exception: 20:127.0.0.1: Send error: 10053: An established connection was aborted by the software in your host machine.
17:15:07:WU01:FS00:Sending unit results: id:01 state:SEND error:DUMPED project:5772 run:1 clone:277 gen:3018 core:0x11 unit:0x48874a2e518cdb100bca01150001168c
17:15:07:WU01:FS00:Uploading 3.77KiB to 171.67.108.11
17:15:07:WU01:FS00:Connecting to 171.67.108.11:8080
17:15:08:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to read stream
17:15:08:WU01:FS00:Trying to send results to collection server
17:15:08:WU01:FS00:Uploading 3.77KiB to 171.67.108.25
17:15:08:WU01:FS00:Connecting to 171.67.108.25:8080
17:15:29:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
17:15:29:WU01:FS00:Connecting to 171.67.108.25:80
17:15:50:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.25: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.
Oh well I'll check out that ticket you quoted above and see what that says. In the meantime I'm going for a brew and watch some telly. Hope this doesn't keep happening because I haven't got much more hair to pull out now!! lol

Thanks again Bruce

Mod Edit: Added Code Tags - PantherX
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.67.108.26 - not accepting work units?

Post by bruce »

Sorry, but that ticket isn't going to explain it. Upon seeing more of your log, it's clear that all of the errors are about a single problem, and it's one that occurred quite some time ago. No matter what originally happened, the WU is not going to upload to 171.67.108.25 because that server has been taken off-line and there's nothing you can do to redirect it to another server.

I'm not sure what happened. It might be useful to search through your old logs, but unless you can find a spot where project:5772 run:1 clone:277 gen:3018 was downloaded and post from there up until an hour or two after it started trying to upload, we'll never know.

Actually knowing isn't going to change anything. Project:5772 run:1 clone:277 gen:3018 is not going to upload to 171.67.108.25 no matter what you do.

If slot 01 is currently folding, click Finish and wait until that WU uploads. Then delete slot 01 and create a new one with the same characteristics. That should reset any misconfiguration associated with the slot, including this DUMPED problem.
Mancunian_Nick
Posts: 21
Joined: Tue Apr 30, 2013 12:00 pm

Re: 171.67.108.26 - not accepting work units?

Post by Mancunian_Nick »

Hi Bruce. You're right it didn't explain it - didn't really understand a word to be honest - too techie for me lol. I understand YOU a lot better though so thank you for your patience. I delete/clear the logs fairly regularly although I do look at them fairly frequently just to see what's happening, which is how I noticed. I've just had a look at the client status just now and there are 2 folding slots: "00 Paused: Waiting for idle" in yellow and "01 Running CPU:1" in green. Below that under work queue there are 3 entries: 00 Running (green), 01 Send and 03 Ready plus some PRCG numbers and numbers in brackets which I presume don't mean much in this instance. Would I be right to assume it's the 01 Send in the work queue you're suggesting I delete? If so how do I do that please? I can highlight it by clicking on it but then I can't see a way to delete it. As I've said before, I'm not very techie minded where computers are concerned, although I have been using them quite a long time. :) Oh I mustn't forget to say you mention creating a new slot with the same characteristics. Please can you explain in simple terms how I'd do that please, step by step? I wouldn't have a clue how to do that to be honest with you.

Thank you for your patience. I really appreciate it.
Nick
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.67.108.26 - not accepting work units?

Post by bruce »

First, regarding the log, the current log shows what's happening and what has happened since the last time the client software was restarted. Older logs are kept in a separate folder named with the date and time until you get more than a certain number of them. That gives you the ability to search recent history. At some point, this WU was dumped -- probably because of some error, but without the log, it's impossible to know that. At that time, the client tried to report the missing WU so it could be issued to somebody else quickly. The value of a DUMPED report is not worth anything after somebody else completes the WU.

Deleting a WU is frowned upon. Nobody wants people to be doing it so it's was not designed to be easy. I did say that deleting the slot and recreating it would clear anything associated with that slot -- including the WU that's currently running, so I recommended letting it finish before doing that.
Mancunian_Nick
Posts: 21
Joined: Tue Apr 30, 2013 12:00 pm

Re: 171.67.108.26 - not accepting WUs? [True. CS offline]

Post by Mancunian_Nick »

Sorry Bruce I'm a little confused again. You say deleting a WU is frowned upon which is why it's not easy (ok understandable) and you recommend letting it finish before doing that but isn't it merely going to keep failing as before? I've actually left my computer on most of the evening with the folding client running. Here's an extract of the more recent log -

Code: Select all

19:27:23:WU01:FS00:Connecting to 171.67.108.11:8080
19:27:23:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to read stream
19:27:23:WU01:FS00:Trying to send results to collection server
19:27:23:WU01:FS00:Uploading 3.77KiB to 171.67.108.25
19:27:23:WU01:FS00:Connecting to 171.67.108.25:8080
19:27:44:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
19:27:44:WU01:FS00:Connecting to 171.67.108.25:80
19:28:06:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.25: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.
19:58:31:WU00:FS01:0xa4:Completed 390000 out of 500000 steps  (78%)
20:31:44:WU00:FS01:0xa4:Completed 395000 out of 500000 steps  (79%)
20:43:24:WU01:FS00:Sending unit results: id:01 state:SEND error:DUMPED project:5772 run:1 clone:277 gen:3018 core:0x11 unit:0x48874a2e518cdb100bca01150001168c
20:43:24:WU01:FS00:Uploading 3.77KiB to 171.67.108.11
20:43:24:WU01:FS00:Connecting to 171.67.108.11:8080
20:43:24:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to read stream
20:43:24:WU01:FS00:Trying to send results to collection server
20:43:25:WU01:FS00:Uploading 3.77KiB to 171.67.108.25
20:43:25:WU01:FS00:Connecting to 171.67.108.25:8080
20:43:46:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
20:43:46:WU01:FS00:Connecting to 171.67.108.25:80
20:44:07:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.25: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.
21:05:32:WU00:FS01:0xa4:Completed 400000 out of 500000 steps  (80%)
21:39:31:WU00:FS01:0xa4:Completed 405000 out of 500000 steps  (81%)
22:14:16:WU00:FS01:0xa4:Completed 410000 out of 500000 steps  (82%)
22:46:23:WU01:FS00:Sending unit results: id:01 state:SEND error:DUMPED project:5772 run:1 clone:277 gen:3018 core:0x11 unit:0x48874a2e518cdb100bca01150001168c
22:46:23:WU01:FS00:Uploading 3.77KiB to 171.67.108.11
22:46:23:WU01:FS00:Connecting to 171.67.108.11:8080
22:46:24:WARNING:WU01:FS00:Exception: Failed to send results to work server: Failed to read stream
22:46:24:WU01:FS00:Trying to send results to collection server
22:46:24:WU01:FS00:Uploading 3.77KiB to 171.67.108.25
22:46:24:WU01:FS00:Connecting to 171.67.108.25:8080
22:46:45:WARNING:WU01:FS00:WorkServer connection failed on port 8080 trying 80
22:46:45:WU01:FS00:Connecting to 171.67.108.25:80
22:47:06:ERROR:WU01:FS00:Exception: Failed to connect to 171.67.108.25: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.
22:48:10:WU00:FS01:0xa4:Completed 415000 out of 500000 steps  (83%)
23:22:13:WU00:FS01:0xa4:Completed 420000 out of 500000 steps  (84%)
******************************* Date: 2013-05-13 *******************************
23:56:13:WU00:FS01:0xa4:Completed 425000 out of 500000 steps  (85%)
I notice that it last failed to send/connect at 22.47.06 and hasn't tried connecting again and there's a work unit WU00:FS01 at 85% complete. Is it that one you are suggesting I let complete? Once it has will that clear/get rid of the other failed WU trying to upload? Then won't it download a new WU or is that what we want it it do and then let it carry on?

Thanks again, Nick
00:29:17:WU00:FS01:0xa4:Completed 430000 out of 500000 steps (86%)
01:02:24:WU00:FS01:0xa4:Completed 435000 out of 500000 steps (87%)
01:36:28:WU00:FS01:0xa4:Completed 440000 out of 500000 steps (88%)

Mod Edit: Added Code Tags - PantherX
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.67.108.26 - not accepting WUs? [True. CS offline]

Post by bruce »

You have two or more WUs. One for project 5772 run:1 clone:277 gen:3018 which is no longer being processed but it's results have still been tryinig to upload. Another for a WU which is being processed -- which you reported was at 88% at that time. By now, that WU will have probably finished and uploaded and a new one has been assigned. You do not want to dump the one that can still be completed and that's what the FINISH function is for. The client will complete the active WU, upload the results but will NOT request a new assignment. That way the only WU you'll have is the one which is failing to upload. Then you can delete the slot.
Mancunian_Nick
Posts: 21
Joined: Tue Apr 30, 2013 12:00 pm

Re: 171.67.108.26 - not accepting WUs? [True. CS offline]

Post by Mancunian_Nick »

Thanks, Bruce. 8082 is now at 98% (still running) so should be finished in just over an hour (ETA). After that I should be able to delete the slot as you say. All I need now please is for you to let me know if you'd be so kind how I do that and any other steps I need to take? You said something about recreating the slot or something or will that get done automatically?

It's a shame the software doesn't automatically reject any 'spent' WUs that have passed/finished and clean up automatically but maybe that's just in an ideal world. :)
PantherX
Site Moderator
Posts: 6986
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:

Re: 171.67.108.26 - not accepting WUs? [True. CS offline]

Post by PantherX »

The WU is automatically deleted once it reaches it's deadline. This varies for each project.

Please look at this guide and see if you can follow it -> http://folding.stanford.edu/English/WinGuide#ntoc8 If you have further questions, we would be glad to help you out.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Mancunian_Nick
Posts: 21
Joined: Tue Apr 30, 2013 12:00 pm

Re: 171.67.108.26 - not accepting WUs? [True. CS offline]

Post by Mancunian_Nick »

Hello Panther. Thank you kindly for that. I've had a quick look at the link but it's for experts and I'm definitely far from that so I'm not going to do anything it says, unless you or bruce or another super moderator/user advises me to do so.

Just for your information, a work unit or all work units (?) for 8082 has been sent without problem so as Bruce advised, that went without a hitch, thankfully.

My current work queue now lists the following:-

01 Send 0% Project 5772 - this is obviously (?) the work unit which is giving these problems I assume.

02 Running (in green) for Project 8083 so this is obviously (again ?) a new project/work unit being correctly processed

03 Ready (in cyan) 0% for Project 5786

I presume the last entry is also a problem that needs resolving somehow or should I just leave everything for the moment? As I said, a work unit was sent without error and a new project downloaded. The only thing which seems to have happened (or not?) is that the WU(s?) haven't been deleted for some reason, or is this 'normal'?

Please would one of you kindly advise how I should proceed - whether that's to leave everything as it is and just keep a watching brief or delete something which, to be honest, I don't think I'd be very confident with. Although I'm no computer newbie by any means, I'm simply not that techie minded, as I've said before so thank you for any further help/advice/insight you can offer. Let me just say once more, I really appreciate your patience both of you. :)

All the best for now, Nick (I'll check back later and see what you advise)
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.67.108.26 - not accepting WUs? [True. CS offline]

Post by bruce »

Have you used the advanced control application (FAHControl) or the Web Control application that comes up in your browser? Whenever one WU finishes, normally a new one will download and start. In your case, a WU from project 8082 finished and uploaded and a new assignment from Project 8083 has started. My objective was to avoid the download of the 8083 assignment by using the FINISH function which can be found in the advanced control. That didn't happen so either we'll need to wait (again) or discard an assignment that can be completed. If you don't use the FINISH function, that will keep happening.

Project 5786 and 5772 are for a GPU. Projects 8082 and 8083 are for your CPU. Apparently your GPU is not folding and your CPU is.

Your config does show two slots:

17:07:43: <slot id='0' type='GPU'/>
17:07:43: <slot id='1' type='CPU'/>

The last WU your CPU completed was 2013-05-12 01:07:25 (5765) and the last WU your GPU completed was 2013-05-14 11:19:37 (8082). Your CPU seems to be making progress normally.

For our purposes, we can ignore the CPU and it's WUs and concentrate on your GPU. According to your earlier report, your GPU was "Paused: waiting for idle" so it only works when your computer is idle. How many hours per day your computer is running and how many hours per day it's running but idle are important figures. We should always see your GPU making some progress overnight and probably some other times if the day.

You didn't post the top section of your log and I don't see where you mentioned which GPU you have so I'm going to have to do a little guesswork here and if anything isn't accurate please correct me.
1) You probably have an older, slower GPU compared to many that are found on systems customized for Games. That determines how much progress is made during each quarter hour the GPU is folding.
2) Your computer MIGHT be configured to save power by sleeping whenever it's idle.

Multiply the number of quarter hours your GPU folds by it's actual speed and we can estimate how much calendar time it takes to finish the assigned WU.

If that result is always shorter than the deadline, good. If it exceeds the WU's deadline we might be better off NOT folding with the GPU.

I can't make any reasonable assumptions about the patterns of usage your computer sees so I can't really make a recommendation here. If your computer is going to be off-line enough of the time between now and when project 5786 expires, we might as well just dump it now. If it's going to be completed before the PREFERRED DEADLINE ("timeout") then we should finish it before deleting the slot. If, on average, your computer will be finishing GPU WUs before the timeout, you should continue folding on both the CPU and the GPU. If, on average, your computer will NOT be finishing GPU WUs before the timeout, we should permanently disable the GPU or you should move the slider-bar to FULL. If you do the latter, you might experience "screen lag" from the use of the GPU and it may or may not be something you consider acceptable.
Mancunian_Nick
Posts: 21
Joined: Tue Apr 30, 2013 12:00 pm

Re: 171.67.108.26 - not accepting WUs? [True. CS offline]

Post by Mancunian_Nick »

Hello Bruce

Thanks again for your input. Please find here the start of my session earlier (yesterday - Tuesday 15th May 2013) when I started the session. You can see the GPU details. You're right usually it's not worth my GPU running but at the moment I do leave it running more than usual as I'm converting and burning some DVDs so I've had it on unattended until 5am this morning (Wednesday 16th May) and so currently my 03 Ready (in cyan) which was yesterday 0% is now 32%. Not much I know but probably not worth the effort sticking to it for a couple of days although might be worth stopping/halting the use of the GPU though as you suggest right away? I've just realised I'm using the FAH Control - Client Control for Expert Users application, not the web viewer. It's the one I downloaded. Did I download the wrong one? Not sure but anyway I'll try to find that finish button and press it. 8033 is still running just fine on the CPU. :)

I'll leave you with that start of the log you mentioned (thanks for 'coding it' Panther. I don't know how to do that or I'd save you the trouble :)) and come back when I've had a drink of tea - 5.30am and I thought it was 1am when I woke up in front of the telly half hour ago. lol.

Code: Select all

*********************** Log Started 2013-05-14T14:08:25Z ***********************
14:08:25:************************* Folding@home Client *************************
14:08:25:      Website: http://folding.stanford.edu/
14:08:25:    Copyright: (c) 2009-2013 Stanford University
14:08:25:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
14:08:25:         Args: --open-web-control
14:08:25:       Config: C:/Users/Nick/AppData/Roaming/FAHClient/config.xml
14:08:25:******************************** Build ********************************
14:08:25:      Version: 7.3.6
14:08:25:         Date: Feb 18 2013
14:08:25:         Time: 15:25:17
14:08:25:      SVN Rev: 3923
14:08:25:       Branch: fah/trunk/client
14:08:25:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
14:08:25:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
14:08:25:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
14:08:25:     Platform: win32 XP
14:08:25:         Bits: 32
14:08:25:         Mode: Release
14:08:25:******************************* System ********************************
14:08:25:          CPU: AMD Athlon(tm) 7750 Dual-Core Processor
14:08:25:       CPU ID: AuthenticAMD Family 16 Model 2 Stepping 3
14:08:25:         CPUs: 2
14:08:25:       Memory: 4.00GiB
14:08:25:  Free Memory: 1.18GiB
14:08:25:      Threads: WINDOWS_THREADS
14:08:25:  Has Battery: false
14:08:25:   On Battery: false
14:08:25:   UTC offset: 1
14:08:25:          PID: 138216
14:08:25:          CWD: C:/Users/Nick/AppData/Roaming/FAHClient
14:08:25:           OS: Windows 7 Ultimate
14:08:25:      OS Arch: AMD64
14:08:25:         GPUs: 1
14:08:25:        GPU 0: NVIDIA:1 G94 [GeForce 9600 GT]
14:08:25:         CUDA: 1.1
14:08:25:  CUDA Driver: 5000
14:08:25:Win32 Service: false
14:08:25:***********************************************************************
14:08:25:<config>
14:08:25:  <!-- Network -->
14:08:25:  <proxy v=':8080'/>
14:08:25:
14:08:25:  <!-- Slot Control -->
14:08:25:  <pause-on-battery v='false'/>
14:08:25:
14:08:25:  <!-- User Information -->
14:08:25:  <passkey v='********************************'/>
14:08:25:  <team v='55186'/>
14:08:25:  <user v='Nick_Jay'/>
14:08:25:
14:08:25:  <!-- Folding Slots -->
14:08:25:  <slot id='0' type='GPU'/>
14:08:25:  <slot id='1' type='CPU'/>
14:08:25:</config>
Added Code tags
Post Reply