171.67.108.11 & 171.67.108.21 down
Posted: Wed Jun 18, 2014 5:44 am
GPU work servers - Could not connect to Work Server (results)171.67.108.11 Could not connect to Work Server 171.67.108.21 - servers out now for about 12 hours. Any news?
Folding Forum
Community driven support forum for Folding@home
https://foldingforum.org/
171.67.108.11 & 171.67.108.21 down
Page 1 of 7
Re: 171.67.108.11 & 171.67.108.21 down
Posted: Wed Jun 18, 2014 7:15 am
Those servers do not look right according to the server status page, so I notified the owner.
Re: 171.67.108.11 & 171.67.108.21 down
Posted: Wed Jun 18, 2014 7:34 am
Thanks for alerting Stanford of the issue. The .11 server has been in reject mode and all attempts to communicate with .21 show failure in the log files, although the assignment server is still routing to it. I confirm the time frame as starting no later than noon PDT, 17 June.
Re: 171.67.108.11 & 171.67.108.21 down
Posted: Wed Jun 18, 2014 7:44 am
Thanks for passing the message on - time to take out the professional's toolkit maybe - a hammer and a screwdriver 
Re: 171.67.108.11 & 171.67.108.21 down
Posted: Wed Jun 18, 2014 7:29 pm
Naaah. The professional toolkit consists of a pair of steel-toed work boots.John_Weatherman wrote:Thanks for passing the message on - time to take out the professional's toolkit maybe - a hammer and a screwdriver
Re: 171.67.108.11 & 171.67.108.21 down
Posted: Wed Jun 18, 2014 9:45 pm
Both still showing "reject" - has somebody pulled out a RJ11 by mistake?
Re: 171.67.108.11 & 171.67.108.21 down
Posted: Wed Jun 18, 2014 9:53 pm
If the server status script could not access these servers at all they would be reported as DOWN. So they are on the network, what the problem is has not been reported yet.
Re: 171.67.108.11 & 171.67.108.21 down
Posted: Thu Jun 19, 2014 12:23 am
We're working on this one now.
Re: 171.67.108.11 & 171.67.108.21 down
Posted: Thu Jun 19, 2014 12:48 am
Problems with uploaden here as well.
Re: 171.67.108.11 & 171.67.108.21 down
Posted: Thu Jun 19, 2014 9:21 am
Both reporting as Down now - is this a step in the right direction?
Re: 171.67.108.11 & 171.67.108.21 down
Posted: Thu Jun 19, 2014 1:44 pm
My guess is that indicates the actual hardware was shutdown, possibly to take care of a component failure. Since Dr. Pande posted they were looking into it at a time that was late afternoon Stanford time, service response might be the following morning.
GPU work units not being assigned from 171.67.108.201
Posted: Fri Jun 20, 2014 7:00 am
Hi
I have been folding since 2009, and my FAH ID is montague-cripps.
I have struck a problem for the first time.
One of my four folding PCs can no longer download GPU work units from the 171.67.108.201 server. This has lasted some four days, and I cannot find a work-around. The other PCs have no problems with either slots. I have pinged it and it responds, but seems to be empty.
The steps I have taken include:
1. re-installing FAH@home
2. deleting the GPU slot (several times)
I can see no way of forcing FAH to log on to a different work server.
The log file is as follows:
Let me know if you need any more information.
Grateful for any help.
I have been folding since 2009, and my FAH ID is montague-cripps.
I have struck a problem for the first time.
One of my four folding PCs can no longer download GPU work units from the 171.67.108.201 server. This has lasted some four days, and I cannot find a work-around. The other PCs have no problems with either slots. I have pinged it and it responds, but seems to be empty.
The steps I have taken include:
1. re-installing FAH@home
2. deleting the GPU slot (several times)
I can see no way of forcing FAH to log on to a different work server.
The log file is as follows:
Code: Select all
06:32:22:Adding folding slot 01: READY gpu:0:GT215 [GeForce GT 240]
06:32:22:Saving configuration to config.xml
06:32:22:<config>
06:32:22: <!-- Network -->
06:32:22: <proxy v=':8080'/>
06:32:22:
06:32:22: <!-- Slot Control -->
06:32:22: <power v='full'/>
06:32:22:
06:32:22: <!-- User Information -->
06:32:22: <passkey v='********************************'/>
06:32:22: <user v='Montague-Cripps'/>
06:32:22:
06:32:22: <!-- Folding Slots -->
06:32:22: <slot id='0' type='CPU'/>
06:32:22: <slot id='1' type='GPU'/>
06:32:22:</config>
06:32:22:FS00:Shutting core down
06:32:23:WU01:FS01:Connecting to 171.67.108.201:80
06:32:23:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
06:32:23:WU01:FS01:Connecting to 171.64.65.160:80
06:32:24:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
06:32:24:ERROR:WU01:FS01:Exception: Could not get an assignment
06:32:24:WU01:FS01:Connecting to 171.67.108.201:80
06:32:25:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
06:32:25:WU01:FS01:Connecting to 171.64.65.160:80
06:32:25:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
06:32:25:ERROR:WU01:FS01:Exception: Could not get an assignment
06:32:27:WU00:FS00:0xa4:Client no longer detected. Shutting down core
06:32:27:WU00:FS00:0xa4:
06:32:27:WU00:FS00:0xa4:Folding@home Core Shutdown: CLIENT_DIED
06:32:28:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
06:32:28:WU00:FS00:Starting
06:32:28:WARNING:WU00:FS00:Changed SMP threads from 4 to 3 this can cause some work units to fail
06:32:28:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/ProgramData/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 704 -lifeline 992 -checkpoint 15 -np 3
06:32:28:WU00:FS00:Started FahCore on PID 6920
06:32:28:WU00:FS00:Core PID:6132
06:32:28:WU00:FS00:FahCore 0xa4 started
06:32:28:WU00:FS00:0xa4:
06:32:28:WU00:FS00:0xa4:*------------------------------*
06:32:28:WU00:FS00:0xa4:Folding@Home Gromacs GB Core
06:32:28:WU00:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
06:32:28:WU00:FS00:0xa4:
06:32:28:WU00:FS00:0xa4:Preparing to commence simulation
06:32:28:WU00:FS00:0xa4:- Looking at optimizations...
06:32:28:WU00:FS00:0xa4:- Files status OK
06:32:28:WU00:FS00:0xa4:- Expanded 117132 -> 264000 (decompressed 225.3 percent)
06:32:28:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=117132 data_size=264000, decompressed_data_size=264000 diff=0
06:32:28:WU00:FS00:0xa4:- Digital signature verified
06:32:28:WU00:FS00:0xa4:
06:32:28:WU00:FS00:0xa4:Project: 6370 (Run 58, Clone 49, Gen 25)
06:32:28:WU00:FS00:0xa4:
06:32:28:WU00:FS00:0xa4:Assembly optimizations on if available.
06:32:28:WU00:FS00:0xa4:Entering M.D.
06:32:34:WU00:FS00:0xa4:Using Gromacs checkpoints
06:32:34:WU00:FS00:0xa4:Mapping NT from 3 to 3
06:32:34:WU00:FS00:0xa4:Resuming from checkpoint
06:32:34:WU00:FS00:0xa4:Verified 00/wudata_01.log
06:32:34:WU00:FS00:0xa4:Verified 00/wudata_01.trr
06:32:34:WU00:FS00:0xa4:Verified 00/wudata_01.xtc
06:32:34:WU00:FS00:0xa4:Verified 00/wudata_01.edr
06:32:34:WU00:FS00:0xa4:Completed 1791140 out of 5000000 steps (35%)
06:32:52:Saving configuration to config.xml
06:32:52:<config>
06:32:52: <!-- Network -->
06:32:52: <proxy v=':8080'/>
06:32:52:
06:32:52: <!-- Slot Control -->
06:32:52: <power v='full'/>
06:32:52:
06:32:52: <!-- User Information -->
06:32:52: <passkey v='********************************'/>
06:32:52: <user v='Montague-Cripps'/>
06:32:52:
06:32:52: <!-- Folding Slots -->
06:32:52: <slot id='0' type='CPU'/>
06:32:52: <slot id='1' type='GPU'/>
06:32:52:</config>
06:33:24:WU01:FS01:Connecting to 171.67.108.201:80
06:33:25:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
06:33:25:WU01:FS01:Connecting to 171.64.65.160:80
06:33:25:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
06:33:25:ERROR:WU01:FS01:Exception: Could not get an assignment
06:33:43:WU00:FS00:0xa4:Completed 1800000 out of 5000000 steps (36%)
06:35:01:WU01:FS01:Connecting to 171.67.108.201:80
06:35:02:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
06:35:02:WU01:FS01:Connecting to 171.64.65.160:80
06:35:02:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
06:35:02:ERROR:WU01:FS01:Exception: Could not get an assignment
06:37:38:WU01:FS01:Connecting to 171.67.108.201:80
06:37:39:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
06:37:39:WU01:FS01:Connecting to 171.64.65.160:80
06:37:40:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
06:37:40:ERROR:WU01:FS01:Exception: Could not get an assignment
06:39:26:WU00:FS00:0xa4:Completed 1850000 out of 5000000 steps (37%)
06:41:53:WU01:FS01:Connecting to 171.67.108.201:80
06:41:53:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
06:41:53:WU01:FS01:Connecting to 171.64.65.160:80
06:41:54:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
06:41:54:ERROR:WU01:FS01:Exception: Could not get an assignment
06:45:01:WU00:FS00:0xa4:Completed 1900000 out of 5000000 steps (38%)
06:48:44:WU01:FS01:Connecting to 171.67.108.201:80
06:48:45:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
06:48:45:WU01:FS01:Connecting to 171.64.65.160:80
06:48:45:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Empty work server assignment
06:48:45:ERROR:WU01:FS01:Exception: Could not get an assignment
06:50:53:WU00:FS00:0xa4:Completed 1950000 out of 5000000 steps (39%)
Grateful for any help.
Re: 171.67.108.11 & 171.67.108.21 down
Posted: Fri Jun 20, 2014 9:31 am
Welcome to the folding@home support forum Nick200.
As you can see I have moved your post to a thread with similar problems. The work servers that assignment servers 171.67.108.201 & 171.64.65.160 would normally send your client to for appropriate work are currently marked as DOWN on the Server Status page and PG is working on the situation. Nothing you can do at this point other that pause your GPU slot and wait for notification from this thread that the servers are working normally again. Make sure you're subscribed to this topic (see link at bottom of page).
As you can see I have moved your post to a thread with similar problems. The work servers that assignment servers 171.67.108.201 & 171.64.65.160 would normally send your client to for appropriate work are currently marked as DOWN on the Server Status page and PG is working on the situation. Nothing you can do at this point other that pause your GPU slot and wait for notification from this thread that the servers are working normally again. Make sure you're subscribed to this topic (see link at bottom of page).
Re: 171.67.108.11 & 171.67.108.21 down
Posted: Sat Jun 21, 2014 5:40 am
I take it that the size 12 boot to the server didn't work and an expert's been called in (coming sometime between 12 and 3 next week)?
Re: No appropriate work server was found
Posted: Sat Jun 21, 2014 8:26 am
Not receiving work.
Pre-Fermi GPUs (2x nV Geforce 9500GT) on Windows XP SP3 (yes, still...)
I know that core 11 is going end-of-life at some point, but couldn't find a clear statement on whether they are actually EOL as of today, 2014-06-21.
There is the reminder about aging cores from Aug 23, 2013 ( https://folding.stanford.edu/home/remin ... -core78-2/ ).
Is there no work because the servers are for the moment not distributing work (for whatever reason) or because the Core 11 have now finally run out of steam?
Edit/update: ah,ok - been moved to this thread. I looked at the server status before posting, saw some GPU servers but couldn't see on the server status page ( http://fah-web.stanford.edu/pybeta/serverstat.html ) where I could work out which GPU server(s) assign the Core 11 WUs. Would it be fair to work on the assumption that 171.67.108.11 and .21 assign Core 11 WUs?
Pre-Fermi GPUs (2x nV Geforce 9500GT) on Windows XP SP3 (yes, still...)
I know that core 11 is going end-of-life at some point, but couldn't find a clear statement on whether they are actually EOL as of today, 2014-06-21.
There is the reminder about aging cores from Aug 23, 2013 ( https://folding.stanford.edu/home/remin ... -core78-2/ ).
Is there no work because the servers are for the moment not distributing work (for whatever reason) or because the Core 11 have now finally run out of steam?
Edit/update: ah,ok - been moved to this thread. I looked at the server status before posting, saw some GPU servers but couldn't see on the server status page ( http://fah-web.stanford.edu/pybeta/serverstat.html ) where I could work out which GPU server(s) assign the Core 11 WUs. Would it be fair to work on the assumption that 171.67.108.11 and .21 assign Core 11 WUs?