Page 1 of 2
Connection problem 18.218.241.186 & 155.247.164.214
Posted: Sun Mar 15, 2020 9:00 am
by NathanJanssens
I've been getting this for about 12 hours or so now? It's setting me up to connect to two servers, but both seem to fail.
Code: Select all
08:48:16:WU00:FS00:Connecting to 65.254.110.245:8080
08:48:17:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
08:48:17:WU00:FS00:Connecting to 18.218.241.186:80
08:48:17:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
08:48:17:ERROR:WU00:FS00:Exception: Could not get an assignment
08:49:54:WU00:FS00:Connecting to 65.254.110.245:8080
08:49:54:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
08:49:54:WU00:FS00:Connecting to 18.218.241.186:80
08:49:54:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
08:49:54:ERROR:WU00:FS00:Exception: Could not get an assignment
08:52:31:WU00:FS00:Connecting to 65.254.110.245:8080
08:52:31:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
08:52:31:WU00:FS00:Connecting to 18.218.241.186:80
08:52:32:WU00:FS00:Assigned to work server 155.247.164.214
08:52:32:WU00:FS00:Requesting new work unit for slot 00: READY cpu:6 from 155.247.164.214
08:52:32:WU00:FS00:Connecting to 155.247.164.214:8080
08:52:32:ERROR:WU00:FS00:Exception: 10001: Server responded: HTTP_SERVICE_UNAVAILABLE
08:56:45:WU00:FS00:Connecting to 65.254.110.245:8080
08:56:46:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
08:56:46:WU00:FS00:Connecting to 18.218.241.186:80
08:56:46:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
08:56:46:ERROR:WU00:FS00:Exception: Could not get an assignment
I guess this holds some relevant information:
Code: Select all
08:44:36:************************* Folding@home Client *************************
08:44:36: Website: https://foldingathome.org/
08:44:36: Copyright: (c) 2009-2018 foldingathome.org
08:44:36: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
08:44:36: Args:
08:44:36: Config: C:\Users\janss\AppData\Roaming\FAHClient\config.xml
08:44:36:******************************** Build ********************************
08:44:36: Version: 7.5.1
08:44:36: Date: May 11 2018
08:44:36: Time: 13:06:32
08:44:36: Repository: Git
08:44:36: Revision: 4705bf53c635f88b8fe85af7675557e15d491ff0
08:44:36: Branch: master
08:44:36: Compiler: Visual C++ 2008
08:44:36: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
08:44:36: Platform: win32 10
08:44:36: Bits: 32
08:44:36: Mode: Release
08:44:36:******************************* System ********************************
08:44:36: CPU: AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx
08:44:36: CPU ID: AuthenticAMD Family 23 Model 24 Stepping 1
08:44:36: CPUs: 8
08:44:36: Memory: 13.94GiB
08:44:36: Free Memory: 11.33GiB
08:44:36: Threads: WINDOWS_THREADS
08:44:36: OS Version: 6.2
08:44:36: Has Battery: true
08:44:36: On Battery: false
08:44:36: UTC Offset: 1
08:44:36: PID: 11864
08:44:36: CWD: C:\Users\janss\AppData\Roaming\FAHClient
08:44:36: OS: Windows 10 Home
08:44:36: OS Arch: AMD64
08:44:36: GPUs: 1
08:44:36: GPU 0: Bus:3 Slot:0 Func:0 AMD:6 Navi 14 [Radeon RX 5500/5500M / Pro
08:44:36: 5500M]
08:44:36: CUDA: Not detected: Failed to open dynamic library 'nvcuda.dll': The
08:44:36: specified module could not be found.
08:44:36:
08:44:36:OpenCL Device 0: Platform:0 Device:0 Bus:3 Slot:0 Compute:1.2 Driver:2906.10
08:44:36:OpenCL Device 1: Platform:0 Device:1 Bus:7 Slot:0 Compute:1.2 Driver:2906.10
08:44:36: Win32 Service: false
08:44:36:***********************************************************************
08:44:36:<config>
08:44:36: <!-- Folding Core -->
08:44:36: <checkpoint v='3'/>
08:44:36:
08:44:36: <!-- Network -->
08:44:36: <proxy v=':8080'/>
08:44:36:
08:44:36: <!-- Slot Control -->
08:44:36: <pause-on-battery v='false'/>
08:44:36:
08:44:36: <!-- User Information -->
08:44:36: <passkey v='********************************'/>
08:44:36: <user v='NathanJanssens'/>
08:44:36:
08:44:36: <!-- Folding Slots -->
08:44:36: <slot id='0' type='CPU'>
08:44:36: <paused v='true'/>
08:44:36: </slot>
08:44:36: <slot id='1' type='GPU'>
08:44:36: <paused v='true'/>
08:44:36: </slot>
08:44:36:</config>
08:44:36:Trying to access database...
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Sun Mar 15, 2020 12:18 pm
by jonault
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Sun Mar 15, 2020 9:02 pm
by ChrisKFoldingAtHome
Someone need to up those servers! I have packages to upload!
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Sun Mar 15, 2020 9:21 pm
by Nathan_P
ChrisKFoldingAtHome wrote:Someone need to up those servers! I have packages to upload!
All the new donors are overwhelming whatever new servers are being added
Its frustrating for everyone but at least its a good problem to have
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Sun Mar 15, 2020 9:59 pm
by rickoic
Not really a good problem as when the servers drop like flies NO work gets done. Perhaps the sudden increase causes it to even out in the long run, but right now there is probably less work getting done.
If we now have twice the number of folders working as we had a week ago, then the only solution is twice the servers (can't happen over night). Just like the response world wide to the virus, without accurate beginning data (China) then all plans based on that data are flawed. GIGO. Garbage In Garbage Out is the old expression.
Kinda reminds me of when they upped our teletype machines from 60 wpm to 120 wpm. The old parts worked good at 60, but had to work differently at 120. Never knew when you walked into the teletype room whether a machine would start throwing parts at you or not.
So everyone just needs to stay cool and allow things to smooth out, as they will. May be slower than what we would like, but unless your Johnny on the spot you don't know the problems happening.
P.S. Forgot to say, teletype machines down time doubled, but we had spare machines to plug into their slots and activate with patch cords.
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Mon Mar 16, 2020 12:29 am
by SombraGuerrero
I tell 'ya, it's not a very good look to have all these newcomers come in, and the first thing they experience is that the servers can't handle the load. For those of us who have been doing this for a very long time and understand the history and how this all works, it's not a big deal, we get it, but this is just going to drive new people away.
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Mon Mar 16, 2020 2:17 am
by bruce
SombraGuerrero wrote:... we get it, but this is just going to drive new people away.
True, but that shouldn't stop the admins from doing their best to fix whatever they can. ..
Nobody wants to drive anybody away, but whoever is still here when the problems are resolved will still be able to work on the unsolved Science.
At the server level, they've put out a call to folks who got biochem degrees over past years and I'm seeing some old familiar names of people who are now doing FAH like they did as a Grad Student. There are a lot of dedicated people working behind the scenes.
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Mon Mar 16, 2020 3:49 am
by SombraGuerrero
Absolutely, it's just that while I appreciate and admire Nvidia and Intel's intent, it is unfortunate that they didn't reach out beforehand and factor the repercussions of their calls to arms. Although on the other hand, the fact that so many people hopped on that we ran out of WUs is awesome!
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Mon Mar 16, 2020 2:57 pm
by 46caliber
Like so many, I'm new and often in the logs I see no WU's available. Totally understandable given the overwhelming addition of new folders.
I did want to post this though, as it is not just a WU unavailable log:
14:45:47:WU00:FS00:Connecting to 18.218.241.186:80
14:45:47:WU00:FS00:Assigned to work server 155.247.166.219
14:45:47:WU00:FS00:Requesting new work unit for slot 00: READY cpu:32 from 155.247.166.219
14:45:47:WU00:FS00:Connecting to 155.247.166.219:8080
14:45:47:ERROR:WU00:FS00:Exception: 10001: Server responded: HTTP_SERVICE_UNAVAILABLE
Could just be the work servers are inundated with WU requests and that causes the HTTP service to hiccup. But wanted to share.
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Mon Mar 16, 2020 3:44 pm
by Biffa
Or Nvidia and Intel could have supplied some servers/resources/bandwidth/etc before encouraging everyone
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Mon Mar 16, 2020 4:37 pm
by schertt
You guys act like work units spawn magically out of some piece of hardware just because it's turned on. It's the PEOPLE involved that make these work units.
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Mon Mar 16, 2020 5:06 pm
by Nathan_P
46caliber wrote:Like so many, I'm new and often in the logs I see no WU's available. Totally understandable given the overwhelming addition of new folders.
I did want to post this though, as it is not just a WU unavailable log:
14:45:47:WU00:FS00:Connecting to 18.218.241.186:80
14:45:47:WU00:FS00:Assigned to work server 155.247.166.219
14:45:47:WU00:FS00:Requesting new work unit for slot 00: READY cpu:32 from 155.247.166.219
14:45:47:WU00:FS00:Connecting to 155.247.166.219:8080
14:45:47:ERROR:WU00:FS00:Exception: 10001: Server responded: HTTP_SERVICE_UNAVAILABLE
Could just be the work servers are inundated with WU requests and that causes the HTTP service to hiccup. But wanted to share.
Correct, the HTTP service has a hiccup.
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Mon Mar 16, 2020 6:12 pm
by SombraGuerrero
schertt wrote:You guys act like work units spawn magically out of some piece of hardware just because it's turned on. It's the PEOPLE involved that make these work units.
Well yes, but it’s both things. Having the WU supply devoured is actually cool in a way, just because it’s an unprecedented level of activity. On the other hand, the servers *are* overwhelmed, so it would have been nice to get some support from the big guns in that space.
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Mon Mar 16, 2020 6:13 pm
by Nathan_P
SombraGuerrero wrote:schertt wrote:You guys act like work units spawn magically out of some piece of hardware just because it's turned on. It's the PEOPLE involved that make these work units.
Well yes, but it’s both things. Having the WU supply devoured is actually cool in a way, just because it’s an unprecedented level of activity. On the other hand, the servers *are* overwhelmed, so it would have been nice to get some support from the big guns in that space.
Lets hope, i cant say much but discussions are taking place.....
Re: Connection problem 18.218.241.186 & 155.247.164.214
Posted: Mon Mar 16, 2020 8:26 pm
by krilenko
Funny fact is that some donors like Default (Team 0) and CoreWeave doesn't seem to have any problems at all getting new WUs while others sometimes wait for hours to get one.