171.67.108.45:80 and 171.64.65.35:80 - Empty work server...

Moderators: Site Moderators, PandeGroup

171.67.108.45:80 and 171.64.65.35:80 - Empty work server...

Postby STFC9F22 » Thu Nov 09, 2017 7:54 pm

Hi,
Since 4 November I’ve experienced several instances of the exception ‘Could not get an assignment’ from servers 171.67.108.45:80 and 171.64.65.35:80.

I am only folding on my GPU (GTX1070) and as far as I am aware nothing has changed at my end (I have successfully folded 50 WUs between instances of this issue). It has been particularly bad today (9 November). Here is my latest log.

Code: Select all
*********************** Log Started 2017-11-09T16:41:54Z ***********************
16:41:54:************************* Folding@home Client *************************
16:41:54:      Website: http://folding.stanford.edu/
16:41:54:    Copyright: (c) 2009-2014 Stanford University
16:41:54:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
16:41:54:         Args:
16:41:54:       Config: C:/Users/Malcolm/AppData/Roaming/FAHClient/config.xml
16:41:54:******************************** Build ********************************
16:41:54:      Version: 7.4.4
16:41:54:         Date: Mar 4 2014
16:41:54:         Time: 20:26:54
16:41:54:      SVN Rev: 4130
16:41:54:       Branch: fah/trunk/client
16:41:54:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
16:41:54:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
16:41:54:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
16:41:54:     Platform: win32 XP
16:41:54:         Bits: 32
16:41:54:         Mode: Release
16:41:54:******************************* System ********************************
16:41:54:          CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
16:41:54:       CPU ID: GenuineIntel Family 6 Model 60 Stepping 3
16:41:54:         CPUs: 8
16:41:54:       Memory: 15.86GiB
16:41:54:  Free Memory: 12.40GiB
16:41:54:      Threads: WINDOWS_THREADS
16:41:54:   OS Version: 6.2
16:41:54:  Has Battery: false
16:41:54:   On Battery: false
16:41:54:   UTC Offset: 0
16:41:54:          PID: 10284
16:41:54:          CWD: C:/Users/Malcolm/AppData/Roaming/FAHClient
16:41:54:           OS: Windows 10 Home
16:41:54:      OS Arch: AMD64
16:41:54:         GPUs: 2
16:41:54:        GPU 0: NVIDIA:7 GP104 [GeForce GTX 1070] 6463
16:41:54:        GPU 1: UNSUPPORTED: NV3 [PCI]
16:41:54:         CUDA: 6.1
16:41:54:  CUDA Driver: 9010
16:41:54:Win32 Service: false
16:41:54:***********************************************************************
16:41:54:<config>
16:41:54:  <!-- Folding Core -->
16:41:54:  <checkpoint v='30'/>
16:41:54:
16:41:54:  <!-- Network -->
16:41:54:  <proxy v=':8080'/>
16:41:54:
16:41:54:  <!-- Slot Control -->
16:41:54:  <power v='full'/>
16:41:54:
16:41:54:  <!-- User Information -->
16:41:54:  <passkey v='********************************'/>
16:41:54:  <user v='STFC9F22'/>
16:41:54:
16:41:54:  <!-- Folding Slots -->
16:41:54:  <slot id='1' type='GPU'>
16:41:54:    <max-packet-size v='small'/>
16:41:54:    <next-unit-percentage v='100'/>
16:41:54:    <pause-on-start v='true'/>
16:41:54:  </slot>
16:41:54:</config>
16:41:54:Trying to access database...
16:41:54:Successfully acquired database lock
16:41:54:Enabled folding slot 01: PAUSED gpu:0:GP104 [GeForce GTX 1070] 6463 (by user)
16:42:12:FS01:Unpaused
16:42:12:WU00:FS01:Connecting to 171.67.108.45:80
16:42:13:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
16:42:13:WU00:FS01:Connecting to 171.64.65.35:80
16:42:14:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
16:42:14:ERROR:WU00:FS01:Exception: Could not get an assignment
16:42:14:WU00:FS01:Connecting to 171.67.108.45:80
16:42:15:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
16:42:15:WU00:FS01:Connecting to 171.64.65.35:80
16:42:16:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
16:42:16:ERROR:WU00:FS01:Exception: Could not get an assignment
16:43:14:WU00:FS01:Connecting to 171.67.108.45:80
16:43:15:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
16:43:15:WU00:FS01:Connecting to 171.64.65.35:80
16:43:16:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
16:43:16:ERROR:WU00:FS01:Exception: Could not get an assignment
16:44:51:WU00:FS01:Connecting to 171.67.108.45:80
16:44:52:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
16:44:52:WU00:FS01:Connecting to 171.64.65.35:80
16:44:53:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
16:44:53:ERROR:WU00:FS01:Exception: Could not get an assignment
16:47:29:WU00:FS01:Connecting to 171.67.108.45:80
16:47:29:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
16:47:29:WU00:FS01:Connecting to 171.64.65.35:80
16:47:30:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
16:47:30:ERROR:WU00:FS01:Exception: Could not get an assignment
16:51:43:WU00:FS01:Connecting to 171.67.108.45:80
16:51:44:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
16:51:44:WU00:FS01:Connecting to 171.64.65.35:80
16:51:45:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
16:51:45:ERROR:WU00:FS01:Exception: Could not get an assignment
16:58:34:WU00:FS01:Connecting to 171.67.108.45:80
16:58:35:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
16:58:35:WU00:FS01:Connecting to 171.64.65.35:80
16:58:36:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
16:58:36:ERROR:WU00:FS01:Exception: Could not get an assignment
17:09:40:WU00:FS01:Connecting to 171.67.108.45:80
17:09:41:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
17:09:41:WU00:FS01:Connecting to 171.64.65.35:80
17:09:42:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
17:09:42:ERROR:WU00:FS01:Exception: Could not get an assignment
17:27:37:WU00:FS01:Connecting to 171.67.108.45:80
17:27:38:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
17:27:38:WU00:FS01:Connecting to 171.64.65.35:80
17:27:38:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
17:27:38:ERROR:WU00:FS01:Exception: Could not get an assignment
17:56:39:WU00:FS01:Connecting to 171.67.108.45:80
17:56:40:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
17:56:40:WU00:FS01:Connecting to 171.64.65.35:80
17:56:40:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
17:56:40:ERROR:WU00:FS01:Exception: Could not get an assignment
18:43:38:WU00:FS01:Connecting to 171.67.108.45:80
18:43:39:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
18:43:39:WU00:FS01:Connecting to 171.64.65.35:80
18:43:40:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
18:43:40:ERROR:WU00:FS01:Exception: Could not get an assignment


If there is nothing untoward in my log and there is a potential issue with the server can I suggest a possible line of investigation. I notice there are reports of Windows Creators update installing NVIDIA drivers which omit OpenCL / CUDA. When something similar happened to me through WIndows Update (in February) the result was a continuous download and almost immediate dumping of WUs which I noticed and stopped on the third WU – I don’t know if FAH has any way of recognising such circumstances and automatically halting it but, if not, is it possible that large numbers of WUs are being dumped by folders unaware of that issue?
STFC9F22
 
Posts: 16
Joined: Fri Jul 06, 2012 7:14 pm

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby foldy » Thu Nov 09, 2017 8:46 pm

I have this too with my gtx 1080 Ti and had to set "max-packet-size=big" in FAHControl->Configure->Expert to make it download new work units again.
foldy
 
Posts: 1130
Joined: Sat Dec 01, 2012 3:43 pm

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby STFC9F22 » Thu Nov 09, 2017 9:01 pm

Hi foldy,

Thanks for your advice - I've just tried setting "max-packet-size=big" as you suggest (saved and restarted) but unfortunately in my case it did not work.
STFC9F22
 
Posts: 16
Joined: Fri Jul 06, 2012 7:14 pm

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby STFC9F22 » Sat Nov 11, 2017 2:24 pm

If anyone else is experiencing this issue I suggest you read the thread 'WU's Not Being Assigned by 171.67.108.102/171.67.108.105/?' at viewtopic.php?f=18&t=30024 It seems to describe the same problem where the client is stuck polling a pair of servers that do not issue WU’s. That thread proposes several possible workarounds the simplest of which is to choose or change a specific cause (If you are using the V 7.4.4 Advanced Client Control this is found under Configure-> Advanced -> Cause Preference). Here in the UK it’s starting to get a little chilly and as I use the PC for background heating I’d already moved to supporting GPUGrid.net before I read that thread so I do not know whether that would have worked in this case.

For information, if anyone is investigating the cause of this particular issue - prior to 4 November (when I first noticed instances of the issue) I believe I was picking up Projects in the 9xxx range and after that solely projects 13147 and 13148 until downloads stopped completely around midday on 9 November, my Cause Preference was set to 'Any', and as stated in my original post I was only folding with a GTX1070. Also it may be significant that 171.67.108.45 and 171.64.65.35 do not appear in the Server stats page and are not listed against any Currently Running Projects at http://fah-web.stanford.edu/psummary.html
STFC9F22
 
Posts: 16
Joined: Fri Jul 06, 2012 7:14 pm

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby bruce » Sat Nov 11, 2017 4:56 pm

171.67.108.45 and 171.64.65.35 are not listed as Work Servers because they're not Work Servers; they're assignment servers. When they search for a server that has WUs that meet your client's requirements and they find that there are no such work servers, the message says "Empty work server assignment"

With the released client, all you have to do is configure your client to look for WUs which use 7 CPUs. There are no such WUs, and so when the AS searches, it finds there are no WS satisfying your requirements. (There are other ways to force the AS to issue this message.) In this

In that particular case, the beta client is smart enough to negotiate the request and ask the AS to search for 6 CPUs in spite of your requirement to use 7.

In your case, the real question is why are there no assignments for a NVIDIA:7 GPU.
The only reason I can think of is that the assignment of some projects which are small enough to run inefficiently on GPUs with lots of shaders have been excluded because folks griped about their low PPD.
bruce
 
Posts: 21403
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby foldy » Sun Nov 12, 2017 10:06 am

But then resetting "max-packet-size=small" to "big" should have helped?
foldy
 
Posts: 1130
Joined: Sat Dec 01, 2012 3:43 pm

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby STFC9F22 » Mon Nov 13, 2017 12:59 am

Bruce thanks for explaining the infrastructure – I take it then that donors have no visibility of server stats on whether assignment servers are functioning correctly.

As regards, the potential “max-packet-size = big” workaround I only tried it briefly getting four further instances of the error before removing it and turning the client off. I had no ‘Extra Client Options’ set explicitly in Configure -> Expert before or after that, but perhaps I needed to let it run for longer?

On running the Client Control again on Friday morning (UK), 10 November, I was still unable to download Work Units, and believing that my only option then would be to install the Beta client, which I had read has a memory leak, I chose instead to move to GPUGrid. For me this appears to be a slightly more donor friendly system, although having now read some of their forum it seems they too are short of IT Support resources and suffer similar problems.

I guess there are many donors running GTX1070 cards but given the low number of hits on this thread it doesn’t appear that many could have been affected by this issue. That being the case and the fact that I’ve moved to GPUGrid, it might be not worth you spending much time pursuing this, but thank you for your help on this and other issues over the years – I’ve always found your expertise and advice to be particularly helpful.
STFC9F22
 
Posts: 16
Joined: Fri Jul 06, 2012 7:14 pm

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby suprleg » Tue Nov 14, 2017 4:20 pm

I've been having the same problem for several weeks, has there been any resolution to the issue?
The 1070 picks up a wu if I reboot the system, but within 12 hours the error begins.

Edit: In checking other machines on my LAN I see that the Win7 pro clients are all experiencing this issue, however the Linux clients are not having trouble picking up new wu's. One of the Linux machines has the same card, GTX960, configured the same as a Windows machine unable to get new work...
Code: Select all
01:34:44:************************* Folding@home Client *************************
01:34:44:      Website: http://folding.stanford.edu/
01:34:44:    Copyright: (c) 2009-2014 Stanford University
01:34:44:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
01:34:44:         Args: --open-web-control
01:34:44:       Config: C:/Users/suprleg/AppData/Roaming/FAHClient/config.xml
01:34:44:******************************** Build ********************************
01:34:44:      Version: 7.4.4
01:34:44:         Date: Mar 4 2014
01:34:44:         Time: 20:26:54
01:34:44:      SVN Rev: 4130
01:34:44:       Branch: fah/trunk/client
01:34:44:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
01:34:44:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
01:34:44:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
01:34:44:     Platform: win32 XP
01:34:44:         Bits: 32
01:34:44:         Mode: Release
01:34:44:******************************* System ********************************
01:34:44:          CPU: Intel(R) Core(TM) i5-3450 CPU @ 3.10GHz
01:34:44:       CPU ID: GenuineIntel Family 6 Model 58 Stepping 9
01:34:44:         CPUs: 4
01:34:44:       Memory: 3.47GiB
01:34:44:  Free Memory: 1.85GiB
01:34:44:      Threads: WINDOWS_THREADS
01:34:44:   OS Version: 6.1
01:34:44:  Has Battery: false
01:34:44:   On Battery: false
01:34:44:   UTC Offset: -8
01:34:44:          PID: 7924
01:34:44:          CWD: C:/Users/suprleg/AppData/Roaming/FAHClient
01:34:44:           OS: Windows 7 Professional Service Pack 1
01:34:44:      OS Arch: X86
01:34:44:         GPUs: 2
01:34:44:        GPU 0: UNSUPPORTED: NV3 [PCI]
01:34:44:        GPU 1: NVIDIA:7 GP104 [GeForce GTX 1070] 6463
01:34:44:         CUDA: 6.1
01:34:44:  CUDA Driver: 8000
01:34:44:Win32 Service: false
01:34:44:***********************************************************************
01:34:44:<config>
01:34:44:  <!-- Network -->
01:34:44:  <proxy v=':8080'/>
01:34:44:
01:34:44:  <!-- User Information -->
01:34:44:  <passkey v='********************************'/>
01:34:44:  <team v='4'/>
01:34:44:  <user v='suprleg'/>
01:34:44:
01:34:44:  <!-- Folding Slots -->
01:34:44:  <slot id='0' type='CPU'>
01:34:44:    <client-type v='advanced'/>
01:34:44:  </slot>
01:34:44:  <slot id='1' type='GPU'>
01:34:44:    <client-type v='advanced'/>
01:34:44:  </slot>
01:34:44:</config>




Code: Select all
*********************** Log Started 2017-11-14T01:34:44Z ***********************
06:07:01:WARNING:WU02:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
06:07:02:WARNING:WU02:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
06:07:02:ERROR:WU02:FS01:Exception: Could not get an assignment
06:07:02:WARNING:WU02:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
06:07:03:WARNING:WU02:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
06:07:03:ERROR:WU02:FS01:Exception: Could not get an assignment
06:08:02:WARNING:WU02:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
06:08:02:WARNING:WU02:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
06:08:02:ERROR:WU02:FS01:Exception: Could not get an assignment
06:09:39:WARNING:WU02:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
06:09:40:WARNING:WU02:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
06:09:40:ERROR:WU02:FS01:Exception: Could not get an assignment
06:12:17:WARNING:WU02:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
06:12:17:ERROR:WU02:FS01:Exception: Server did not assign work unit
06:16:31:WARNING:WU02:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
06:16:31:WARNING:WU02:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
06:16:31:ERROR:WU02:FS01:Exception: Could not get an assignment
******************************* Date: 2017-11-14 *******************************
10:55:26:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
10:55:26:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
10:55:26:ERROR:WU01:FS01:Exception: Could not get an assignment
10:55:27:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
10:55:27:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
10:55:27:ERROR:WU01:FS01:Exception: Could not get an assignment
10:56:27:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
10:56:27:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
10:56:27:ERROR:WU01:FS01:Exception: Could not get an assignment
10:58:04:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
******************************* Date: 2017-11-14 *******************************
15:40:04:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
15:40:05:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
15:40:05:ERROR:WU00:FS01:Exception: Could not get an assignment
15:40:05:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
15:40:06:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
15:40:06:ERROR:WU00:FS01:Exception: Could not get an assignment
15:41:05:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
15:41:06:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
15:41:06:ERROR:WU00:FS01:Exception: Could not get an assignment
15:42:43:ERROR:WU00:FS01:Exception: Server did not assign work unit
15:45:20:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
15:45:20:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
15:45:20:ERROR:WU00:FS01:Exception: Could not get an assignment
15:49:34:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
15:49:34:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
15:49:34:ERROR:WU00:FS01:Exception: Could not get an assignment
15:56:25:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
15:56:25:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
15:56:25:ERROR:WU00:FS01:Exception: Could not get an assignment
16:07:31:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
16:07:31:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
16:07:31:ERROR:WU00:FS01:Exception: Could not get an assignment
User avatar
suprleg
 
Posts: 39
Joined: Thu Apr 26, 2012 8:30 pm

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby JimboPalmer » Tue Nov 14, 2017 5:14 pm

01:34:44: <slot id='0' type='CPU'>
01:34:44: <client-type v='advanced'/>
01:34:44: </slot>
01:34:44: <slot id='1' type='GPU'>
01:34:44: <client-type v='advanced'/>

If you take off advanced, do you get WUs?
Tsar of all the Rushers
I tried to remain childlike, all I achieved was childish.
A friend to those who want no friends
JimboPalmer
 
Posts: 631
Joined: Mon Feb 16, 2009 4:12 am
Location: Greenwood MS USA

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby bruce » Wed Nov 15, 2017 3:05 am

STFC9F22 wrote:I take it then that donors have no visibility of server stats on whether assignment servers are functioning correctly.

The only indication I've found that the AS are working properly is to open
http://171.67.108.45 and
http://171.64.65.35

I have seen rare instances where port 80 didn't work, but port 8080 always works unless the AS is off-line entirely -- though sometimes they' have been blocked by the local networking security settings.

If a AS was not functioning, the other serves as a backup but if there was a genuine problem. this board would instantly light up like Las Vegas.
bruce
 
Posts: 21403
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby Joe_H » Wed Nov 15, 2017 3:32 am

As Bruce has posted, the only sure indication of whether or not the AS's are up is going to their addresses in a browser. Even when they last were included on the Server Status page 2-3 years ago or more, the information displayed there was oriented to Work Servers and not very useful in determining AS status.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Joe_H
Site Admin
 
Posts: 4124
Joined: Tue Apr 21, 2009 4:41 pm
Location: W. MA

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby Gary480six » Thu Nov 23, 2017 12:47 pm

I don't know if anyone is still looking into this issue - but I can add one more bit of information to maybe help the research.

I have had three different PCs get stuck with that "Empty work server assignment" message. Same two servers - 171.67.108.45 and 171.64.65.35

Yes - rebooting sometimes helps.. as does changing the Cause Preference. But only for a while. Eventually, the systems end up at these assignment servers - and get stuck.

The video cards were GTX 750Ti and GTX 1050Ti's. One system was on Avast, one was Secure Essentials - one had nothing. In each case, I could ping the AS and get a response - so it wasn't a firewall or ISP problem on my end.

All Fold successfully - when they do get work units.

What I Did figure out.. was that each of the systems in question, were Windows 7 32-bit.

And that this issue has not affected any of the Windows 7 64-bit systems I run.

Could it be that those two assignment servers are assuming the 32-bit OS is XP - and rejecting the work request?
Gary480six
 
Posts: 67
Joined: Mon Jan 21, 2008 6:42 pm

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby Joe_H » Thu Nov 23, 2017 4:22 pm

If you look closely at your logs, every request goes through those two AS's. Currently they are the only ones active. The log entry will look about like this for a successful request:
Code: Select all
23:55:57:WU01:FS00:Connecting to 171.67.108.45:8080
23:55:57:WU01:FS00:Assigned to work server 155.247.166.220

First you connect to one of the AS's and then are assigned to a WS address that as of the last update has work for your configuration.

As you have figured out, at least part of the issue is running Win-32. A good portion of the GPU WU's are assigned to 64-bit systems due to the memory requirements for processing. The smaller WU's that are assigned to 32-bit systems may temporarily be all assigned, once some are returned and the next generation WU's created the AS's will get an update showing availability.
Joe_H
Site Admin
 
Posts: 4124
Joined: Tue Apr 21, 2009 4:41 pm
Location: W. MA

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby husq » Sat Nov 25, 2017 11:16 am

WIN7 X86 /client-type=beta /V7.4.4

:arrow:
Code: Select all
11:11:14:Trying to access database...
11:11:14:Successfully acquired database lock
11:11:14:Enabled folding slot 01: READY gpu:0:GM204 [GeForce GTX 970]
11:11:14:Started thread 4 on PID 4184
11:11:14:Started thread 5 on PID 4184
11:11:14:Started thread 7 on PID 4184
11:11:14:Started thread 9 on PID 4184
11:11:14:Started thread 6 on PID 4184
11:11:14:Started thread 8 on PID 4184
11:11:15:WU00:FS01:Connecting to 171.67.108.45:80
11:11:16:WU00:FS01:Assigned to work server 140.163.4.231
11:11:16:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:GM204 [GeForce GTX 970] from 140.163.4.231
11:11:16:WU00:FS01:Connecting to 140.163.4.231:8080
11:11:16:Started thread 10 on PID 4184
11:11:18:Started thread 11 on PID 4184
11:11:20:Started thread 12 on PID 4184
11:11:22:Started thread 13 on PID 4184
11:11:23:ERROR:WU00:FS01:Exception: Server did not assign work unit
11:11:23:WU00:FS01:Connecting to 171.67.108.45:80
11:11:25:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
11:11:25:WU00:FS01:Connecting to 171.64.65.35:80
11:11:26:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
11:11:26:ERROR:WU00:FS01:Exception: Could not get an assignment
11:12:23:WU00:FS01:Connecting to 171.67.108.45:80
11:12:24:WARNING:WU00:FS01:Failed to get assignment from '171.67.108.45:80': Empty work server assignment
11:12:24:WU00:FS01:Connecting to 171.64.65.35:80
11:12:25:WARNING:WU00:FS01:Failed to get assignment from '171.64.65.35:80': Empty work server assignment
11:12:25:ERROR:WU00:FS01:Exception: Could not get an assignment
Image
husq
 
Posts: 16
Joined: Fri Dec 19, 2008 3:58 pm

Re: 171.67.108.45:80 and 171.64.65.35:80 - Empty work server

Postby Gary480six » Sat Nov 25, 2017 2:23 pm

Thanks for that clarification Joe.

I looked at one system... it has 4GB of RAM installed, and System Properties shows 3.24GB 'available' because it's Windows 7 32-bit.

I have a different, 64-bit system Folding just a Core 21 GPU unit right now. Task manager says the Core is only using 152,000K and that the OS, Folding and everything else, is using less than 20% of the Physical Memory. (System Properties shows 7.89GB available on that box)
So the Whole machine - including the GPU Folding, has only needed 1.6GB of RAM.

So why does the assignment server decide that a 32-bit based system with 3.24GB of RAM available (and 2.5GB of Free Memory - according to a recent log file) - does not have enough memory to Fold the larger work units, when a 64-bit system that is successfully Folding, is using less than 2GB of RAM?
Gary480six
 
Posts: 67
Joined: Mon Jan 21, 2008 6:42 pm

Next

Return to Issues with a specific server

Who is online

Users browsing this forum: No registered users and 3 guests

cron