Page 1 of 1

Cancelling a bad work file?

Posted: Thu Jan 12, 2017 12:47 am
by techman05
folding at homes been trying to download a work file but it says its unknown and credit unknown. How do I tell the program to iqnore it and pull a new work file.

it shows the work ip as 0.0.0.0 and collection server as 0.0.0.0

Thanks

Re: Cancelling a bad work file?

Posted: Thu Jan 12, 2017 12:50 am
by bruce
Please post the first few pages of your log per the instructions in the signature of this post.

Re: Cancelling a bad work file?

Posted: Thu Jan 12, 2017 12:53 am
by techman05
Here's the log. Also note I don't have this set for auto start.

Code: Select all

*********************** Log Started 2017-01-12T00:50:14Z ***********************
00:50:14:************************* Folding@home Client *************************
00:50:14:      Website: http://folding.stanford.edu/
00:50:14:    Copyright: (c) 2009-2014 Stanford University
00:50:14:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
00:50:14:         Args: --open-web-control
00:50:14:       Config: D:/Roaming/FAHClient/config.xml
00:50:14:******************************** Build ********************************
00:50:14:      Version: 7.4.4
00:50:14:         Date: Mar 4 2014
00:50:14:         Time: 20:26:54
00:50:14:      SVN Rev: 4130
00:50:14:       Branch: fah/trunk/client
00:50:14:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
00:50:14:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
00:50:14:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
00:50:14:     Platform: win32 XP
00:50:14:         Bits: 32
00:50:14:         Mode: Release
00:50:14:******************************* System ********************************
00:50:14:          CPU: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
00:50:14:       CPU ID: GenuineIntel Family 6 Model 94 Stepping 3
00:50:14:         CPUs: 8
00:50:14:       Memory: 15.68GiB
00:50:14:  Free Memory: 13.36GiB
00:50:14:      Threads: WINDOWS_THREADS
00:50:14:   OS Version: 6.1
00:50:14:  Has Battery: true
00:50:14:   On Battery: false
00:50:14:   UTC Offset: -5
00:50:14:          PID: 3044
00:50:14:          CWD: D:/Roaming/FAHClient
00:50:14:           OS: Windows 7 Home Premium
00:50:14:      OS Arch: AMD64
00:50:14:         GPUs: 0
00:50:14:         CUDA: Not detected
00:50:14:Win32 Service: false
00:50:14:***********************************************************************
00:50:14:<config>
00:50:14:  <!-- Slot Control -->
00:50:14:  <power v='MEDIUM'/>
00:50:14:
00:50:14:  <!-- User Information -->
00:50:14:  <team v='231300'/>
00:50:14:  <user v='techman05'/>
00:50:14:
00:50:14:  <!-- Folding Slots -->
00:50:14:  <slot id='0' type='CPU'>
00:50:14:    <paused v='true'/>
00:50:14:  </slot>
00:50:14:</config>
00:50:14:Trying to access database...
00:50:14:Successfully acquired database lock
00:50:14:Enabled folding slot 00: PAUSED cpu:7 (by user)
00:50:16:16:127.0.0.1:New Web connection
00:50:59:FS00:Unpaused
00:51:00:WU00:FS00:Connecting to 171.67.108.45:8080
00:51:00:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:51:00:WU00:FS00:Connecting to 171.64.65.35:80
00:51:00:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:51:00:ERROR:WU00:FS00:Exception: Could not get an assignment
00:51:01:WU00:FS00:Connecting to 171.67.108.45:8080
00:51:01:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.45:8080': Empty work server assignment
00:51:01:WU00:FS00:Connecting to 171.64.65.35:80
00:51:01:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
00:51:01:ERROR:WU00:FS00:Exception: Could not get an assignment
00:51:15:Saving configuration to config.xml
00:51:15:<config>
00:51:15:  <!-- Slot Control -->
00:51:15:  <power v='MEDIUM'/>
00:51:15:

Re: Cancelling a bad work file?

Posted: Thu Jan 12, 2017 1:07 am
by bruce
There's a known issue with the released client software when it is configured to use 7 CPUs.

Option 1: Upgrade to the beta FAH software V7.4.16 which contains a fix.
Option 2:Move the slider from MEDIUM to FULL.

Re: Cancelling a bad work file?

Posted: Thu Jan 12, 2017 1:12 am
by techman05
Where do I look for beta versions? That was one of the first things I did try to do[look for apparently not very well] and reinstall to repair.

Re: Cancelling a bad work file?

Posted: Thu Jan 12, 2017 1:18 am
by techman05
found it

https://folding.stanford.edu/home/beta/

still couldn't find it via the normal page ;(

Re: Cancelling a bad work file?

Posted: Thu Jan 12, 2017 1:19 am
by bruce
You must not have looked very hard.

viewforum.php?f=104

Re: Cancelling a bad work file?

Posted: Thu Jan 12, 2017 1:24 am
by techman05
Thanks I'm chugging along again now.

Re: Cancelling a bad work file?

Posted: Fri Jan 13, 2017 9:02 pm
by GreyWhiskers
I occasionally get this kind of hangup when, for one reason or another, download of a new WU fails, and the client is stuck. This post, I believe, is on-topic, since it helps a user successfully recover from not only the OP's scenario, but also when a download fails for whatever reason freezing the folding slot.

Two parts to this post: What I do, and what I wish the Advanced Control app would do.


A. How I get a "stuck" slot back up folding using Windows (all my folding systems run Windows 10, but the same method will work with Windows 7 or 8):

1. While in the Advanced Control app, note which slot or work queue item needs to be restarted.

2. Pause any other successfully-folding slots ON THE COMPUTER IN QUESTION. If you have a folding farm, don't bother with other computers.

3. Exit from the Advanced Control (maybe not needed, but I do it anyway).

4. Go to the Windows Task Manager, Processes tab. There should be only one FAH task running, the FAH client. Kill the client. This must be done, since in the next step, you will delete the folder containing the partially downloaded or other stuck work unit, and the folder and partial work files are locked by the FAH Client task, so you cannot delete them.

5. Go to the Work folder. On the default Windows install, this is located at c: Users \ [whatever your login ID is] \ App Data \ Roaming \ FAHClient \ Work.

5. Delete the directory folder corresponding to the Work Queue item number you noted in step 1. If you haven't noted which item is the one to be killed, you might note if there is one directory that had a number of files in it - that's an active work unit you probably don't want to stop. If there is a directory folder with just one item in it, that's probably the one you want to kill. Choose wisely, my child, or else :oops: :oops: .

6. Restart FAH. In my system, I restart FAH by selecting a shortcut I have to the web control. Using your browser, it starts the Client, restarts (probably) any paused work units, and downloads a new work unit for the folding slot you need to restart.

7. If the web control page doesn't restart other folding slots, go to the Advanced Control App, and unpause the slot. If you use HFM.net most recent version, you can unpause a slot there too.

This seems awkward, but in fact it took much more time to type the process description than it does to execute the process. And, it doesn't require you reboot your computer.


Part B. What I would like to see the FAH software do.

1. There has been a lot of discussion over the years about having a process within the FAH Advanced control app to allow a user to kill a folding slot work unit, without having to execute the seven step process above. There are pros and cons to making this too easy.

2. Having said that, I would still like to see if a method could be added, maybe for advanced users, to the control app that lets you kill and restart a single folding slot without having to bring the client and all folding slots down and back up.

Re: Cancelling a bad work file?

Posted: Fri Jan 13, 2017 9:34 pm
by techman05
I would have just been happy if there was a timeout (how many times to try) and pull another BUT this appears that it was my chip type causing this and it was 50/50 that the next try wouldn't have failed as well.

Maybe go to the beta link and request?