Page 1 of 1
assign3.stanford.edu:8080
Posted: Tue Jul 15, 2014 12:02 am
by ChristianVirtual
This morning on my virtual Linux SMP:3
2014-07-14:23:54:57:WARNING:WU01:FS00:Failed to get assignment from 'assign3.stanford.edu:8080': Failed to connect to assign3.stanford.edu:8080: Connection refused
2014-07-14:23:54:57:WU01:FS00:Connecting to assign4.stanford.edu:80
2014-07-14:23:54:58:WU01:FS00:News:
2014-07-14:23:54:58:WARNING:WU01:FS00:Failed to get assignment from 'assign4.stanford.edu:80': Empty work server assignment
2014-07-14:23:54:58:ERROR:WU01:FS00:Exception: Could not get an assignment
Problems with assignment servers?
Posted: Tue Jul 15, 2014 12:22 am
by bigvbguy
I have had several machines today be suddenly unable to get work assignments. Most of my machines are running the bigadv work units, but I have even tried removing that setting from the client config and I still fail to get work assignments. Here is the last part of my log:
Code: Select all
22:04:39:WU01:FS00:0xa3:Completed 495000 out of 500000 steps (99%)
22:04:40:WU00:FS00:Connecting to 171.67.108.200:8080
22:04:40:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: Connection refused
22:04:40:WU00:FS00:Connecting to 171.64.65.121:80
22:04:41:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.121:80': Empty work server assignment
22:04:41:ERROR:WU00:FS00:Exception: Could not get an assignment
22:04:41:WU00:FS00:Connecting to 171.67.108.200:8080
22:04:41:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: Connection refused
22:04:41:WU00:FS00:Connecting to 171.64.65.121:80
22:04:41:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.121:80': Empty work server assignment
22:04:41:ERROR:WU00:FS00:Exception: Could not get an assignment
22:05:41:WU00:FS00:Connecting to 171.67.108.200:8080
22:05:41:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: Connection refused
22:05:41:WU00:FS00:Connecting to 171.64.65.121:80
22:05:41:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.121:80': Empty work server assignment
22:05:41:ERROR:WU00:FS00:Exception: Could not get an assignment
22:07:18:WU00:FS00:Connecting to 171.67.108.200:8080
22:07:18:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: Connection refused
22:07:18:WU00:FS00:Connecting to 171.64.65.121:80
22:07:19:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.121:80': Empty work server assignment
22:07:19:ERROR:WU00:FS00:Exception: Could not get an assignment
22:08:51:WU01:FS00:0xa3:Completed 500000 out of 500000 steps (100%)
22:08:53:WU01:FS00:0xa3:DynamicWrapper: Finished Work Unit: sleep=10000
22:09:03:WU01:FS00:0xa3:
22:09:03:WU01:FS00:0xa3:Finished Work Unit:
22:09:03:WU01:FS00:0xa3:- Reading up to 8056320 from "01/wudata_01.trr": Read 8056320
22:09:03:WU01:FS00:0xa3:trr file hash check passed.
22:09:03:WU01:FS00:0xa3:edr file hash check passed.
22:09:03:WU01:FS00:0xa3:logfile size: 59568
22:09:03:WU01:FS00:0xa3:Leaving Run
22:09:06:WU01:FS00:0xa3:- Writing 8152720 bytes of core data to disk...
22:09:08:WU01:FS00:0xa3:Done: 8152208 -> 7529231 (compressed to 92.3 percent)
22:09:08:WU01:FS00:0xa3: ... Done.
22:09:56:WU00:FS00:Connecting to 171.67.108.200:8080
22:09:56:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: Connection refused
22:09:56:WU00:FS00:Connecting to 171.64.65.121:80
22:09:56:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.121:80': Empty work server assignment
22:09:56:ERROR:WU00:FS00:Exception: Could not get an assignment
22:14:10:WU00:FS00:Connecting to 171.67.108.200:8080
22:14:10:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: Connection refused
22:14:10:WU00:FS00:Connecting to 171.64.65.121:80
22:14:10:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.121:80': Empty work server assignment
22:14:10:ERROR:WU00:FS00:Exception: Could not get an assignment
22:17:00:WU01:FS00:0xa3:- Shutting down core
22:17:00:WU01:FS00:0xa3:
22:17:00:WU01:FS00:0xa3:Folding@home Core Shutdown: FINISHED_UNIT
22:18:06:WU01:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
22:18:06:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:8568 run:1 clone:9 gen:465 core:0xa3 unit:0x0000248a0a3b1e59522881a76212fd8e
22:18:07:WU01:FS00:Uploading 7.18MiB to 128.143.231.202
22:18:07:WU01:FS00:Connecting to 128.143.231.202:8080
22:18:11:WU01:FS00:Upload complete
22:18:11:WU01:FS00:Server responded WORK_ACK (400)
22:18:11:WU01:FS00:Final credit estimate, 19406.00 points
22:18:11:WU01:FS00:Cleaning up
22:21:01:WU00:FS00:Connecting to 171.67.108.200:8080
22:21:01:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: Connection refused
22:21:01:WU00:FS00:Connecting to 171.64.65.121:80
22:21:01:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.121:80': Empty work server assignment
22:21:01:ERROR:WU00:FS00:Exception: Could not get an assignment
22:32:06:WU00:FS00:Connecting to 171.67.108.200:8080
22:32:07:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: Connection refused
22:32:07:WU00:FS00:Connecting to 171.64.65.121:80
22:32:07:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.121:80': Empty work server assignment
22:32:07:ERROR:WU00:FS00:Exception: Could not get an assignment
22:50:03:WU00:FS00:Connecting to 171.67.108.200:8080
22:50:03:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: Connection refused
22:50:03:WU00:FS00:Connecting to 171.64.65.121:80
22:50:04:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.121:80': Empty work server assignment
22:50:04:ERROR:WU00:FS00:Exception: Could not get an assignment
23:19:05:WU00:FS00:Connecting to 171.67.108.200:8080
23:19:06:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: Connection refused
23:19:06:WU00:FS00:Connecting to 171.64.65.121:80
23:19:06:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.121:80': Empty work server assignment
23:19:06:ERROR:WU00:FS00:Exception: Could not get an assignment
00:06:04:WU00:FS00:Connecting to 171.67.108.200:8080
00:06:04:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: Connection refused
00:06:04:WU00:FS00:Connecting to 171.64.65.121:80
00:06:05:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.121:80': Empty work server assignment
00:06:05:ERROR:WU00:FS00:Exception: Could not get an assignment
As you can see, my machine successfully completed a work unit (and uploaded it) but has been unable to pull a new assignment for a couple of hours. Is this a known issue?
Any suggestions?
Re: Problems with assignment servers?
Posted: Tue Jul 15, 2014 12:27 am
by bigvbguy
By the way, this is happening on 8 different machines, all running the 7.4.4.1 linux client. The machines range in cpu count from 8 to 144.
Re: Problems with assignment servers?
Posted: Tue Jul 15, 2014 12:31 am
by bruce
I had just reported a problem with 171.67.108.200 before reading this.
(I'm not sure about 171.64.65.121 yet, but an Empty work server assignment generally means the projects that match your request are either out of WUs or their servers are down. The assignment server, itself is working but can't find anything within your restrictions.)
Re: Problems with assignment servers?
Posted: Tue Jul 15, 2014 12:39 am
by EXT64
I am seeing this as well, though only on my SMP rig (v6). GPU received work ok.
Code: Select all
[23:31:13] Connecting to http://assign.stanford.edu:8080/
[23:31:14] - Couldn't send HTTP request to server
[23:31:14] + Could not connect to Assignment Server
[23:31:14] Connecting to http://assign2.stanford.edu:80/
[23:31:14] Posted data.
[23:31:14] Initial: 0000; + Could not authenticate Assignment Server 2 response
[23:31:14] + Couldn't get work instructions.
[23:31:14] - Attempt #10 to get work failed, and no other work to do.
Waiting before retry.
Re: assign3.stanford.edu:8080
Posted: Tue Jul 15, 2014 12:57 am
by AlanH
Same problem here. Mac OS X SMP clients on two Macs.
Re: assign3.stanford.edu:8080
Posted: Tue Jul 15, 2014 2:01 am
by EXT64
Yep, I am seeing this as well on all my CPU Clients (SMP and BigAdv).
Re: assign3.stanford.edu:8080
Posted: Tue Jul 15, 2014 3:52 am
by VijayPande
Should be all set now.
Re: assign3.stanford.edu:8080
Posted: Tue Jul 15, 2014 4:25 am
by PantherX
Confirmed that it is now working:
Code: Select all
03:39:12:WU00:FS00:Connecting to 171.67.108.200:8080
03:39:13:WARNING:WU00:FS00:Failed to get assignment from '171.67.108.200:8080': Failed to connect to 171.67.108.200:8080: No connection could be made because the target machine actively refused it.
03:39:13:WU00:FS00:Connecting to 171.64.65.121:80
03:39:14:WARNING:WU00:FS00:Failed to get assignment from '171.64.65.121:80': Empty work server assignment
03:39:14:ERROR:WU00:FS00:Exception: Could not get an assignment
04:08:14:WU00:FS00:Connecting to 171.67.108.200:8080
04:08:15:WU00:FS00:Assigned to work server 171.67.108.60
04:08:15:WU00:FS00:Requesting new work unit for slot 00: READY cpu:6 from 171.67.108.60
04:08:15:WU00:FS00:Connecting to 171.67.108.60:8080
04:08:16:WU00:FS00:Downloading 531.97KiB
04:08:19:WU00:FS00:Download complete
04:08:19:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:9500 run:3940 clone:0 gen:329 core:0xa4 unit:0x0000015e6652edcc53643234d590d84f
04:08:19:WU00:FS00:Downloading core from http://web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah
04:08:19:WU00:FS00:Connecting to web.stanford.edu:80
04:08:20:WU00:FS00:FahCore a4: Downloading 2.89MiB
04:08:26:WU00:FS00:FahCore a4: 21.64%
04:08:32:WU00:FS00:FahCore a4: 47.61%
04:08:38:WU00:FS00:FahCore a4: 71.42%
04:08:44:WU00:FS00:FahCore a4: 95.22%
04:08:45:WU00:FS00:FahCore a4: Download complete
04:08:45:WU00:FS00:Valid core signature
04:08:45:WU00:FS00:Unpacked 9.59MiB to cores/web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe
04:08:45:WU00:FS00:Starting
04:08:45:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/PantherX/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 704 -lifeline 4988 -checkpoint 15 -np 6
04:08:46:WU00:FS00:Started FahCore on PID 4148
04:08:46:WU00:FS00:Core PID:4168
04:08:46:WU00:FS00:FahCore 0xa4 started
04:08:47:WU00:FS00:0xa4:
04:08:47:WU00:FS00:0xa4:*------------------------------*
04:08:47:WU00:FS00:0xa4:Folding@Home Gromacs GB Core
04:08:47:WU00:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
04:08:47:WU00:FS00:0xa4:
04:08:47:WU00:FS00:0xa4:Preparing to commence simulation
04:08:47:WU00:FS00:0xa4:- Looking at optimizations...
04:08:47:WU00:FS00:0xa4:- Created dyn
04:08:47:WU00:FS00:0xa4:- Files status OK
04:08:48:WU00:FS00:0xa4:- Expanded 544230 -> 1305980 (decompressed 239.9 percent)
04:08:48:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=544230 data_size=1305980, decompressed_data_size=1305980 diff=0
04:08:48:WU00:FS00:0xa4:- Digital signature verified
04:08:48:WU00:FS00:0xa4:
04:08:48:WU00:FS00:0xa4:Project: 9500 (Run 3940, Clone 0, Gen 329)
04:08:48:WU00:FS00:0xa4:
04:08:48:WU00:FS00:0xa4:Assembly optimizations on if available.
04:08:48:WU00:FS00:0xa4:Entering M.D.
04:08:54:WU00:FS00:0xa4:Mapping NT from 6 to 6
04:08:54:WU00:FS00:0xa4:Completed 0 out of 250000 steps (0%)
04:09:41:WU00:FS00:0xa4:Completed 2500 out of 250000 steps (1%)
04:10:28:WU00:FS00:0xa4:Completed 5000 out of 250000 steps (2%)
04:11:15:WU00:FS00:0xa4:Completed 7500 out of 250000 steps (3%)
Re: assign3.stanford.edu:8080
Posted: Fri Jul 25, 2014 8:51 pm
by cheechi
About the same time as this thread started (I do not remember the exact date sorry) I stopped being able to get work on my GPU client. It is still running 6.41 however I upgraded to v7 today and still no work for the GPU. IF the CPU was ever unable to get work I missed it.
In the past, deleting work, log, and queue files have helped in getting work again when this happened, which is why the log only starts today. Sorry there is not much useful in the pasted log but if anyone could give me a suggestion or if there are any known assignment server issues, please point me in the right direction.
Code: Select all
--- Opening Log file [July 25 17:31:51 UTC]
# Windows GPU Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.41r2
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: D:\fah\gpu
Executable: D:\fah\gpu\Folding@home-Win32-GPU.exe
[17:31:51] - Ask before connecting: No
[17:31:51] - User name: cheechi (Team 186785)
[17:31:51] - User ID: 250042D4497857D7
[17:31:51] - Machine ID: 2
[17:31:51]
[17:31:51] Gpu type=2 species=13.
[17:31:51] Loaded queue successfully.
[17:31:51] - Preparing to get new work unit...
[17:31:51] Cleaning up work directory
[17:31:51] + Attempting to get work packet
[17:31:51] Gpu type=2 species=13.
[17:31:51] - Connecting to assignment server
[17:31:52] + No appropriate work server was available; will try again in a bit.
[17:31:52] + Couldn't get work instructions.
[17:31:52] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[17:32:08] + Attempting to get work packet
[17:32:08] Gpu type=2 species=13.
[17:32:08] - Connecting to assignment server
[17:32:08] + No appropriate work server was available; will try again in a bit.
[17:32:08] + Couldn't get work instructions.
[17:32:08] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[17:32:30] + Attempting to get work packet
[17:32:30] Gpu type=2 species=13.
[17:32:30] - Connecting to assignment server
[17:32:30] + No appropriate work server was available; will try again in a bit.
[17:32:30] + Couldn't get work instructions.
[17:32:30] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[17:33:02] + Attempting to get work packet
[17:33:02] Gpu type=2 species=13.
[17:33:02] - Connecting to assignment server
[17:33:02] + No appropriate work server was available; will try again in a bit.
[17:33:02] + Couldn't get work instructions.
[17:33:02] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[17:33:43] + Attempting to get work packet
[17:33:43] Gpu type=2 species=13.
[17:33:43] - Connecting to assignment server
[17:33:43] + No appropriate work server was available; will try again in a bit.
[17:33:43] + Couldn't get work instructions.
[17:33:43] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[17:35:12] + Attempting to get work packet
[17:35:12] Gpu type=2 species=13.
[17:35:12] - Connecting to assignment server
[17:35:13] + No appropriate work server was available; will try again in a bit.
[17:35:13] + Couldn't get work instructions.
[17:35:13] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[17:38:06] + Attempting to get work packet
[17:38:06] Gpu type=2 species=13.
[17:38:06] - Connecting to assignment server
[17:38:06] + No appropriate work server was available; will try again in a bit.
[17:38:06] + Couldn't get work instructions.
[17:38:06] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[17:43:37] + Attempting to get work packet
[17:43:37] Gpu type=2 species=13.
[17:43:37] - Connecting to assignment server
[17:43:38] + No appropriate work server was available; will try again in a bit.
[17:43:38] + Couldn't get work instructions.
[17:43:38] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.
[17:54:30] + Attempting to get work packet
[17:54:30] Gpu type=2 species=13.
[17:54:30] - Connecting to assignment server
[17:54:31] + No appropriate work server was available; will try again in a bit.
[17:54:31] + Couldn't get work instructions.
[17:54:31] - Attempt #9 to get work failed, and no other work to do.
Waiting before retry.
[18:15:54] + Attempting to get work packet
[18:15:54] Gpu type=2 species=13.
[18:15:54] - Connecting to assignment server
[18:15:55] + No appropriate work server was available; will try again in a bit.
[18:15:55] + Couldn't get work instructions.
[18:15:55] - Attempt #10 to get work failed, and no other work to do.
Waiting before retry.
[18:58:36] + Attempting to get work packet
[18:58:36] Gpu type=2 species=13.
[18:58:36] - Connecting to assignment server
[18:58:36] + No appropriate work server was available; will try again in a bit.
[18:58:36] + Couldn't get work instructions.
[18:58:36] - Attempt #11 to get work failed, and no other work to do.
Waiting before retry.
[19:46:49] + Attempting to get work packet
[19:46:49] Gpu type=2 species=13.
[19:46:49] - Connecting to assignment server
[19:46:50] + No appropriate work server was available; will try again in a bit.
[19:46:50] + Couldn't get work instructions.
[19:46:50] - Attempt #12 to get work failed, and no other work to do.
Waiting before retry.
Folding@Home Client Shutdown.
Re: assign3.stanford.edu:8080
Posted: Fri Jul 25, 2014 9:45 pm
by bruce
The server assign3 is not used by V6, just assign.stanford.edu and assign2.stanford.edu for CPU projects and assign-gpu.stanford.edu for GPU projects so your question has nothing to do with this discussion. Assign3.stanford.edu is used by V7, so if, as you say, you upgraded, please post that log.
If you look up the last log in which you DID get an assignment for your GPU, you probably got it from 171.67.108.11 and the discussion about end-of-life for your GPU can be found here:
viewtopic.php?f=18&t=26481
If my guesses are correct, I can move your question to that topi where it will be come a "me-too" post.
Re: assign3.stanford.edu:8080
Posted: Fri Jul 25, 2014 9:50 pm
by cheechi
Here is the v7 log. Sorry to ask in the wrong place, just saw the similarity in the timeframe and took a shot.
Shame about the GPU, it's not that old really. Considering we're still supporting P4 single core cpu's right?
This doesn't look like it matches any of the servers discussed there.
Code: Select all
21:47:09:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Failed to connect to 171.64.65.160:80: No connection could be made because the target machine actively refused it.
Code: Select all
20:33:49:Saving configuration to config.xml
20:33:49:<config>
20:33:49: <!-- Network -->
20:33:49: <proxy v=':8080'/>
20:33:49:
20:33:49: <!-- User Information -->
20:33:49: <passkey v='********************************'/>
20:33:49: <team v='186785'/>
20:33:49: <user v='cheechi'/>
20:33:49:
20:33:49: <!-- Folding Slots -->
20:33:49: <slot id='0' type='CPU'/>
20:33:49: <slot id='1' type='GPU'/>
20:33:49:</config>
20:34:15:FS00:Shutting core down
20:34:23:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
20:34:23:WU00:FS00:Starting
20:34:23:WARNING:WU00:FS00:Changed SMP threads from 2 to 3 this can cause some work units to fail
20:34:23:WU00:FS00:Running FahCore: "D:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" "D:/Program Files (x86)/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/Core_a3.fah/FahCore_a3.exe" -dir 00 -suffix 01 -version 704 -lifeline 1788 -checkpoint 15 -np 3
20:34:23:WU00:FS00:Started FahCore on PID 860
20:34:23:WU00:FS00:Core PID:3052
20:34:23:WU00:FS00:FahCore 0xa3 started
20:34:23:WU00:FS00:0xa3:
20:34:23:WU00:FS00:0xa3:*------------------------------*
20:34:23:WU00:FS00:0xa3:Folding@Home Gromacs SMP Core
20:34:23:WU00:FS00:0xa3:Version 2.27 (Dec. 15, 2010)
20:34:23:WU00:FS00:0xa3:
20:34:23:WU00:FS00:0xa3:Preparing to commence simulation
20:34:23:WU00:FS00:0xa3:- Looking at optimizations...
20:34:23:WU00:FS00:0xa3:- Files status OK
20:34:23:WU00:FS00:0xa3:- Expanded 3812367 -> 4169428 (decompressed 109.3 percent)
20:34:23:WU00:FS00:0xa3:Called DecompressByteArray: compressed_data_size=3812367 data_size=4169428, decompressed_data_size=4169428 diff=0
20:34:23:WU00:FS00:0xa3:- Digital signature verified
20:34:23:WU00:FS00:0xa3:
20:34:23:WU00:FS00:0xa3:Project: 6099 (Run 2, Clone 99, Gen 491)
20:34:23:WU00:FS00:0xa3:
20:34:23:WU00:FS00:0xa3:Assembly optimizations on if available.
20:34:23:WU00:FS00:0xa3:Entering M.D.
20:34:29:WU00:FS00:0xa3:Mapping NT from 3 to 3
20:34:30:WU00:FS00:0xa3:Completed 0 out of 500000 steps (0%)
20:34:42:Saving configuration to config.xml
20:34:42:<config>
20:34:42: <!-- Network -->
20:34:42: <proxy v=':8080'/>
20:34:42:
20:34:42: <!-- Slot Control -->
20:34:42: <power v='full'/>
20:34:42:
20:34:42: <!-- User Information -->
20:34:42: <passkey v='********************************'/>
20:34:42: <team v='186785'/>
20:34:42: <user v='cheechi'/>
20:34:42:
20:34:42: <!-- Folding Slots -->
20:34:42: <slot id='0' type='CPU'/>
20:34:42: <slot id='1' type='GPU'/>
20:34:42:</config>
20:35:20:WU01:FS01:Connecting to 171.67.108.201:80
20:35:21:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
20:35:21:WU01:FS01:Connecting to 171.64.65.160:80
20:35:22:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Failed to connect to 171.64.65.160:80: No connection could be made because the target machine actively refused it.
20:35:22:ERROR:WU01:FS01:Exception: Could not get an assignment
20:37:46:13:127.0.0.1:New Web connection
20:37:57:WU01:FS01:Connecting to 171.67.108.201:80
20:37:58:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
20:37:58:WU01:FS01:Connecting to 171.64.65.160:80
20:37:59:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Failed to connect to 171.64.65.160:80: No connection could be made because the target machine actively refused it.
20:37:59:ERROR:WU01:FS01:Exception: Could not get an assignment
20:42:12:WU01:FS01:Connecting to 171.67.108.201:80
20:42:12:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
20:42:12:WU01:FS01:Connecting to 171.64.65.160:80
20:42:14:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Failed to connect to 171.64.65.160:80: No connection could be made because the target machine actively refused it.
20:42:14:ERROR:WU01:FS01:Exception: Could not get an assignment
20:49:03:WU01:FS01:Connecting to 171.67.108.201:80
20:49:03:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
20:49:03:WU01:FS01:Connecting to 171.64.65.160:80
20:49:05:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Failed to connect to 171.64.65.160:80: No connection could be made because the target machine actively refused it.
20:49:05:ERROR:WU01:FS01:Exception: Could not get an assignment
20:56:42:WU00:FS00:0xa3:Completed 5000 out of 500000 steps (1%)
21:00:08:WU01:FS01:Connecting to 171.67.108.201:80
21:00:09:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
21:00:09:WU01:FS01:Connecting to 171.64.65.160:80
21:00:10:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Failed to connect to 171.64.65.160:80: No connection could be made because the target machine actively refused it.
21:00:10:ERROR:WU01:FS01:Exception: Could not get an assignment
21:18:06:WU01:FS01:Connecting to 171.67.108.201:80
21:18:06:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
21:18:06:WU01:FS01:Connecting to 171.64.65.160:80
21:18:07:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Failed to connect to 171.64.65.160:80: No connection could be made because the target machine actively refused it.
21:18:07:ERROR:WU01:FS01:Exception: Could not get an assignment
21:18:38:WU00:FS00:0xa3:Completed 10000 out of 500000 steps (2%)
21:40:38:WU00:FS00:0xa3:Completed 15000 out of 500000 steps (3%)
21:47:07:WU01:FS01:Connecting to 171.67.108.201:80
21:47:08:WARNING:WU01:FS01:Failed to get assignment from '171.67.108.201:80': Empty work server assignment
21:47:08:WU01:FS01:Connecting to 171.64.65.160:80
21:47:09:WARNING:WU01:FS01:Failed to get assignment from '171.64.65.160:80': Failed to connect to 171.64.65.160:80: No connection could be made because the target machine actively refused it.
21:47:09:ERROR:WU01:FS01:Exception: Could not get an assignment
Re: assign3.stanford.edu:8080
Posted: Fri Jul 25, 2014 9:59 pm
by bruce
If you open
http://assign3.stanford.edu/ you will now get an "OK" indicating that the problem associated with this topic has been fixed. The original error was "Connection refused" which is very different than "Empty work server assignment"
Re: assign3.stanford.edu:8080
Posted: Fri Jul 25, 2014 11:30 pm
by cheechi
ok thanks bruce. It had been a long day and this was the most recent thread that came up in the search. Sorry it wasn't more relevant to my question.
So if I understand properly, the only issue is the GPU is no longer supported?
Re: assign3.stanford.edu:8080
Posted: Fri Jul 25, 2014 11:44 pm
by 7im
cheechi wrote:snip
Considering we're still supporting P4 single core cpu's right?
snip
While no official End Of Life notice has been sent out for single core systems, the work availability for those systems has been limited for quite some time, very much like the older GPUs. This has been discussed in the forum several times.
So while the answer is still Yes, it may not be that way for very much longer. Hard to guess the future.