Folding Forum

Community driven support forum for Folding@home
https://foldingforum.org/

WU's Not Being Assigned by 171.67.108.102/171.67.108.105/?

https://foldingforum.org/viewtopic.php?t=30024

Page 3 of 10

Re: Exception: Server did not assign work unit

Posted: Sat May 27, 2017 2:36 pm
by foldy
I tried to download a new work unit and 171.67.108.45 this time redirected to 171.64.65.84 and I got a work unit.

I don't think it is possible to exclude assignment servers using firewall rules. The client will still try the IPs and then fail the same way.

Re: Exception: Server did not assign work unit

Posted: Sat May 27, 2017 2:42 pm
by SteveWillis
Blocking the ip immediately worked for me on my Linux box and has continued to work. I tried everything else unsuccessfully.

viewtopic.php?f=18&t=30026

Re: GPU cannot get work

Posted: Sat May 27, 2017 2:47 pm
by PS3EdOlkkola
It looks like the server 171.67.108.105 needs a reboot/restart -- or hopefully nothing more drastic -- to get it running again. Anyone awake in CA yet to get a handle on this problem? I was on-track to achieve slightly over 1 billion points this month, but if this doesn't get fixed it ain't happening.

Re: Exception: Server did not assign work unit

Posted: Sat May 27, 2017 2:51 pm
by foldy
If this is really working then on Windows the cmd looks like this:
netsh advfirewall firewall add rule name="FahClient workaround" dir=in interface=any action=block remoteip=171.67.108.105
To remove again:
netsh advfirewall firewall delete rule name="FahClient workaround"
Put them in a admin cmd shell and press enter key. It should say OK.

Re: Exception: Server did not assign work unit

Posted: Sat May 27, 2017 2:52 pm
by Aurum
ifolder wrote:
ifolder wrote:Hi,

FAHClient connects to 171.67.108.45 that keeps on assigning the same work server 171.67.108.105 which doesn't assign any work unit.

Shouldn't 171.67.108.45 detect that same client or IP is asking again for WS and assign another work server instead of dumbly assigning the same one again and again and again??
An even better option would be to implement in the next FAHClient version the fact that when the WS did not assign a WU, FAHClient gives this information, alongside with the IP of the faulty WS, on its next WU request so that a different WS should be assigned. And several requests like this should raise an alarm about the faulty WS.
We recommended that about 6 months ago along with other things and still no 7.4.17.

I'm back to not getting WUs. My requests switch work servers but I'm still coming up short.
I wonder if they don't have enough in the queue :?: :?: :?:

Re: Exception: Server did not assign work unit

Posted: Sat May 27, 2017 2:58 pm
by Aurum
Is there someone that can shut down 171.67.108.45 or reset it :?: :?: :?:

Code: Select all

14:52:41:WU02:FS00:Connecting to 171.67.108.45:8080
14:52:42:WU02:FS00:Assigned to work server 155.247.166.220
When F@H switches work servers I get a WU. Until it switches I get rejected:

Code: Select all

14:52:57:WU02:FS01:Connecting to 171.67.108.45:80
14:52:57:WU02:FS01:Assigned to work server 140.163.4.245

Re: 171.67.108.102 not assigning work units

Posted: Sat May 27, 2017 3:03 pm
by Joe_H
I have merged the five separate topics on the same problem and am in the middle of writing a message to report this to PG.

Re: WU's Not Being Assigned by 171.67.108.102/171.67.108.105

Posted: Sat May 27, 2017 5:01 pm
by des1957
Thanks to Steve Willis, both of my GPUs are running again. His method for Linux worked fine.

Re: WU's Not Being Assigned by 171.67.108.102/171.67.108.105

Posted: Sat May 27, 2017 5:53 pm
by Leonardo
I had two machines, both Windows 10, with the downloading problem. Here's what worked for me: On one machine, in the console manually alternated the setting from Fold to Pause; the other machine I rebooted and it picked up a work unit right away.

Re: WU's Not Being Assigned by 171.67.108.102/171.67.108.105

Posted: Sat May 27, 2017 6:34 pm
by SteveWillis
des1957 wrote:Thanks to Steve Willis, both of my GPUs are running again. His method for Linux worked fine.
Thanks for the upvote :-)

I didn't mention that your firewall has to be enabled.

Code: Select all

sudo ufw enable

Re: WU's Not Being Assigned by 171.67.108.102/171.67.108.105

Posted: Sat May 27, 2017 6:56 pm
by Aurum
I just noticed that when work server 140.163.4.241 with 61,356 WUs in its queue it does not assign me one it switches me to WS 140.163.4.241 with NO WUs in its queue and hangs:

Code: Select all

18:48:36:WU01:FS03:Connecting to 171.67.108.45:80
18:48:38:WU01:FS03:Assigned to work server 140.163.4.241
18:48:38:WU01:FS03:Requesting new work unit for slot 03: READY gpu:2:GP104 [GeForce GTX 1070] from 140.163.4.241
18:48:38:WU01:FS03:Connecting to 140.163.4.241:8080
18:48:41:ERROR:WU01:FS03:Exception: Server did not assign work unit
http://fah-web.stanford.edu/pybeta/serverstat.html

Re: Exception: Server did not assign work unit

Posted: Sat May 27, 2017 7:20 pm
by Aurum
foldy wrote:If this is really working then on Windows the cmd looks like this:
netsh advfirewall firewall add rule name="FahClient workaround" dir=in interface=any action=block remoteip=171.67.108.105
To remove again:
netsh advfirewall firewall delete rule name="FahClient workaround"
Foldy I tried your approach and blocked 171.67.108.105 and 140.163.4.241 in my CMD windows as Administrator and it said "ok" and I rebooted. Maybe it works:

Code: Select all

19:12:59:FS04:Unpaused
19:13:00:WU03:FS04:Connecting to 171.67.108.45:80
19:13:00:WU03:FS04:Assigned to work server 171.67.108.105
19:13:00:WU03:FS04:Requesting new work unit for slot 04: READY gpu:3:GP104 [GeForce GTX 1070] from 171.67.108.105
19:13:00:WU03:FS04:Connecting to 171.67.108.105:8080
19:13:00:ERROR:WU03:FS04:Exception: Server did not assign work unit
19:13:00:WU03:FS04:Connecting to 171.67.108.45:80
19:13:01:WU03:FS04:Assigned to work server 140.163.4.245
19:13:01:WU03:FS04:Requesting new work unit for slot 04: READY gpu:3:GP104 [GeForce GTX 1070] from 140.163.4.245
19:13:01:WU03:FS04:Connecting to 140.163.4.245:8080
19:13:01:WU03:FS04:Downloading 14.49MiB
19:13:07:WU03:FS04:Download 47.87%
19:13:11:WU03:FS04:Download complete
This time it switched me to another WS so maybe the cmd did work by getting it to switch. Other rigs still hang on 171.67.108.105 or 140.163.4.241. Do i need to reboot to have this cmd take affect :?:

Re: Exception: Server did not assign work unit

Posted: Sat May 27, 2017 7:38 pm
by Duce H_K_
foldy wrote:If this is really working then on Windows the cmd looks like this:
netsh advfirewall firewall add rule name="FahClient workaround" dir=in interface=any action=block remoteip=171.67.108.105
To remove again:
netsh advfirewall firewall delete rule name="FahClient workaround"

Code: Select all

19:33:51:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.84:80': 10001: Server responded: HTTP_INTERNAL_SERVER_ERROR
19:33:52:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.84:8080': 10001: Server responded: HTTP_INTERNAL_SERVER_ERROR
19:33:53:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
19:33:53:ERROR:WU00:FS00:Exception: Failed to connect to 171.67.108.102:80: blocked by win firewall.
19:33:54:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.84:80': 10001: Server responded: HTTP_INTERNAL_SERVER_ERROR
19:33:54:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.84:8080': 10001: Server responded: HTTP_INTERNAL_SERVER_ERROR
19:33:55:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
19:33:55:ERROR:WU00:FS00:Exception: Failed to connect to 171.67.108.102:80: blocked by win firewall.
19:34:54:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.84:80': 10001: Server responded: HTTP_INTERNAL_SERVER_ERROR
19:34:54:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.84:8080': 10001: Server responded: HTTP_INTERNAL_SERVER_ERROR
19:34:55:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
19:34:55:ERROR:WU00:FS00:Exception: Failed to connect to 171.67.108.102:80: blocked by win firewall.
19:36:31:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.84:80': 10001: Server responded: HTTP_INTERNAL_SERVER_ERROR
19:36:32:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.84:8080': 10001: Server responded: HTTP_INTERNAL_SERVER_ERROR
19:36:33:ERROR:WU00:FS00:Exception: Server did not assign work unit
:(

Re: Exception: Server did not assign work unit

Posted: Sat May 27, 2017 7:49 pm
by Duce H_K_

Code: Select all

19:47:03:<config>
19:47:03:  <!-- Debugging -->
19:47:03:  <gpu-assignment-servers>
19:47:03:    assign-gpu.stanford.edu:80 assign-gpu.stanford.edu:8080 assign-gpu2.stanford.edu:80 assign-gpu3.stanford.edu:80 assign-gpu3.stanford.edu:8080 assign-gpu4.stanford.edu:80 assign-gpu4.stanford.edu:8080
19:47:03:  </gpu-assignment-servers>
19:47:03:
19:47:03:  <!-- Folding Core -->
19:47:03:  <checkpoint v='6'/>
19:47:03:  <core-priority v='low'/>
19:47:03:
19:47:03:  <!-- Folding Slot Configuration -->
19:47:03:  <extra-core-args v='-forceasm -twait=80'/>
19:47:03:
19:47:03:  <!-- HTTP Server -->
19:47:03:  <allow v='0.0.0.0/0'/>
19:47:03:  <deny v='255.255.255.255/255.255.255.255'/>
19:47:03:
19:47:03:  <!-- Network -->
19:47:03:  <proxy v=':8080'/>
19:47:03:
19:47:03:  <!-- Remote Command Server -->
19:47:03:  <command-allow-no-pass v='127.0.0.1,192.168.161.0/25'/>
19:47:03:  <command-deny-no-pass v=''/>
19:47:03:  <command-port v='7936'/>
19:47:03:  <password v='************'/>
19:47:03:
19:47:03:  <!-- Slot Control -->
19:47:03:  <pause-on-battery v='false'/>
19:47:03:  <pause-on-start v='true'/>
19:47:03:  <power v='full'/>
19:47:03:
19:47:03:  <!-- User Information -->
19:47:03:  <passkey v='*'/>
19:47:03:  <team v='47191'/>
19:47:03:
19:47:03:  <!-- Work Unit Control -->
19:47:03:  <next-unit-percentage v='100'/>
19:47:03:
19:47:03:  <!-- Folding Slots -->
19:47:03:  <slot id='0' type='GPU'>
19:47:03:    <gpu-index v='2'/>
19:47:03:  </slot>
19:47:03:  <slot id='1' type='GPU'>
19:47:03:    <gpu-index v='0'/>
19:47:03:    <opencl-index v='0'/>
19:47:03:  </slot>
19:47:03:</config>
19:47:03:Trying to access database...
19:47:03:Successfully acquired database lock
19:47:03:Enabled folding slot 00: PAUSED gpu:2:GP104 [GeForce GTX 1070] 6463 (by user)
19:47:03:Enabled folding slot 01: PAUSED gpu:0:Pitcairn PRO [Radeon HD 7800 Series] (by user)
19:47:14:FS00:Unpaused
19:47:15:ERROR:WU00:FS00:Exception: Could not get IP address for assign-gpu3.stanford.edu:   . 
19:47:15:ERROR:WU00:FS00:Exception: Could not get IP address for assign-gpu3.stanford.edu:   . 
19:47:15:ERROR:WU00:FS00:Exception: Could not get IP address for assign-gpu4.stanford.edu:   . 
19:47:15:ERROR:WU00:FS00:Exception: Could not get IP address for assign-gpu4.stanford.edu:   . 
19:47:15:WU00:FS00:Connecting to 171.67.108.45:80
19:47:16:WU00:FS00:Assigned to work server 171.67.108.102
19:47:16:WU00:FS00:Requesting new work unit for slot 00: READY gpu:2:GP104 [GeForce GTX 1070] 6463 from 171.67.108.102
19:47:16:WU00:FS00:Connecting to 171.67.108.102:8080
19:47:26:WU00:FS00:Downloading 7.07MiB
19:47:32:WU00:FS00:Download 88.43%
19:47:32:WU00:FS00:Download complete
19:47:32:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:13204 run:30 clone:18 gen:18 core:0x21 unit:0x00000009ab436c6657894f0cd5dcade1
19:47:33:WU00:FS00:Starting
19:47:33:WU00:FS00:Running FahCore: C:\NO_UAC\foldingathome/FAHCoreWrapper.exe E:\Docbase\FaH-workdir\cores/fahwebx.stanford.edu/cores/Win32/AMD64/NVIDIA/Fermi/Core_21.fah/FahCore_21.exe -dir 00 -suffix 01 -version 704 -lifeline 3960 -checkpoint 6 -gpu-vendor nvidia -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu 0 -forceasm -twait=80
19:47:33:WU00:FS00:Started FahCore on PID 2340
19:47:33:WU00:FS00:Core PID:2624
19:47:33:WU00:FS00:FahCore 0x21 started
19:47:34:WU00:FS00:0x21:*********************** Log Started 2017-05-27T19:47:34Z ***********************
19:47:34:WU00:FS00:0x21:Project: 13204 (Run 30, Clone 18, Gen 18)
19:47:34:WU00:FS00:0x21:Unit: 0x00000009ab436c6657894f0cd5dcade1
19:47:34:WU00:FS00:0x21:CPU: 0x00000000000000000000000000000000
19:47:34:WU00:FS00:0x21:Machine: 0
19:47:34:WU00:FS00:0x21:Reading tar file core.xml
19:47:34:WU00:FS00:0x21:Reading tar file integrator.xml
19:47:34:WU00:FS00:0x21:Reading tar file state.xml
19:47:35:WU00:FS00:0x21:Reading tar file system.xml
19:47:37:WU00:FS00:0x21:Digital signatures verified
19:47:37:WU00:FS00:0x21:Folding@home GPU Core21 Folding@home Core
19:47:37:WU00:FS00:0x21:Version 0.0.18
:)

Re: Exception: Server did not assign work unit

Posted: Sat May 27, 2017 9:24 pm
by foldy
Aurum wrote:Foldy I tried your approach and blocked 171.67.108.105 and 140.163.4.241 in my CMD windows as Administrator and it said "ok" and I rebooted. Do i need to reboot to have this cmd take affect :?:
No reboot necessary firewall settings are live.

Don't forget to remove the setting when servers fully work again.
All times are UTC
Page 3 of 10

Powered by phpBB® Forum Software © phpBB Limited