Page 2 of 2

Re: 155.247.166.219:8080

Posted: Sun Feb 03, 2013 1:48 pm
by hisui
>>art_l_j_PlanetAMD64
how to apply that key?
and this problem with 155.247.166.219:8080 seems persistence,after I've turned off the proxy,I cant get wu from that server again,what shall I do?
how to switch wu providing server?

Re: 155.247.166.219:8080

Posted: Sun Feb 03, 2013 4:27 pm
by art_l_j_PlanetAMD64
hisui wrote:>>art_l_j_PlanetAMD64
how to apply that key?
and this problem with 155.247.166.219:8080 seems persistence,after I've turned off the proxy,I cant get wu from that server again,what shall I do?
how to switch wu providing server?
To apply the passkey, please do this:
  • In FAHControl, click on 'Configure', and select the 'Identity' tab
  • Type or copy/paste the passkey that you received in the email, into the two Passkey entries
  • Click on 'Save'
  • Repeat this procedure on each folding computer, if you have more than one
It is OK to use your proxy server, but it is much safer if you can find the FQDN (Fully Qualified Domain Name) for your proxy server. Using the wildcards in the IP address could result in your system being connected to some server that is not the one you wanted to use. From your log file, you are connected to proxy server 210.101.131.231:8080, so you can enter that data in the FAHControl 'Configure -> Proxy' information, even if you cannot find the FQDN.

Re: 155.247.166.219:8080

Posted: Mon Feb 04, 2013 9:25 am
by hisui
thx for ur help regard passkey,I've acquired one,but problem with 155.247.166.219:8080 still persists,I'm unable to acquired wu for over 8 hours

Code: Select all

*********************** Log Started 2013-02-03T22:59:46Z ***********************
22:59:46:************************* Folding@home Client *************************
22:59:46:      Website: http://folding.stanford.edu/
22:59:46:    Copyright: (c) 2009-2012 Stanford University
22:59:46:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
22:59:46:         Args: --lifeline 3208 --command-port=36330
22:59:46:       Config: E:/FAHCdata/config.xml
22:59:46:******************************** Build ********************************
22:59:46:      Version: 7.2.9
22:59:46:         Date: Oct 3 2012
22:59:46:         Time: 18:05:48
22:59:46:      SVN Rev: 3578
22:59:46:       Branch: fah/trunk/client
22:59:46:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
22:59:46:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
22:59:46:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
22:59:46:     Platform: win32 XP
22:59:46:         Bits: 32
22:59:46:         Mode: Release
22:59:46:******************************* System ********************************
22:59:46:          CPU: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
22:59:46:       CPU ID: GenuineIntel Family 6 Model 23 Stepping 10
22:59:46:         CPUs: 4
22:59:46:       Memory: 3.93GiB
22:59:46:  Free Memory: 2.94GiB
22:59:46:      Threads: WINDOWS_THREADS
22:59:46:   On Battery: false
22:59:46:   UTC offset: 8
22:59:46:          PID: 144
22:59:46:          CWD: E:/FAHCdata
22:59:46:           OS: Microsoft Windows Server 2003 Service Pack 2
22:59:46:      OS Arch: X86
22:59:46:         GPUs: 1
22:59:46:        GPU 0: NVIDIA:1 G98 [GeForce 9300 GE]
22:59:46:         CUDA: Not detected
22:59:46:Win32 Service: false
22:59:46:***********************************************************************
22:59:46:<config>
22:59:46:  <!-- Network -->
22:59:46:  <proxy v='210.101.131.231:8080'/>
22:59:46:
22:59:46:  <!-- User Information -->
22:59:46:  <passkey v='********************************'/>
22:59:46:  <user v='Hisui'/>
22:59:46:
22:59:46:  <!-- Folding Slots -->
22:59:46:  <slot id='0' type='SMP'>
22:59:46:    <cpus v='2'/>
22:59:46:  </slot>
22:59:46:</config>
22:59:46:Trying to access database...
22:59:46:Successfully acquired database lock
22:59:46:Enabled folding slot 00: READY smp:2
22:59:46:WU00:FS00:Connecting to assign3.stanford.edu:8080
22:59:46:WU00:FS00:News: Welcome to Folding@Home
22:59:46:WU00:FS00:Assigned to work server 155.247.166.219
22:59:46:WU00:FS00:Requesting new work unit for slot 00: READY smp:2 from 155.247.166.219
22:59:46:WU00:FS00:Connecting to 155.247.166.219:8080
22:59:47:ERROR:WU00:FS00:Exception: Server did not assign work unit
then myclient was assigned to other wu providing server but not able to acquired workable wu

Code: Select all

08:09:01:WU00:FS00:Connecting to assign3.stanford.edu:8080
08:09:03:WU00:FS00:News: Welcome to Folding@Home
08:09:03:WU00:FS00:Assigned to work server 171.64.65.99
08:09:03:WU00:FS00:Requesting new work unit for slot 00: READY smp:2 from 171.64.65.99
08:09:03:WU00:FS00:Connecting to 171.64.65.99:8080
08:09:08:WU00:FS00:Downloading 1.96MiB

Code: Select all

09:23:16:WU00:FS00:Requesting new work unit for slot 00: READY smp:2 from 155.247.166.219
09:23:16:WU00:FS00:Connecting to 155.247.166.219:8080
09:23:20:ERROR:WU00:FS00:Exception: Server did not assign work unit
and now I'm still unable to acquired new wu

Re: 155.247.166.219:8080

Posted: Mon Feb 04, 2013 10:45 am
by art_l_j_PlanetAMD64
hisui wrote:thx for ur help regard passkey,I've acquired one,but problem with 155.247.166.219:8080 still persists,I'm unable to acquired wu for over 8 hours

and now I'm still unable to acquired new wu
OK, you can use the IP address from your previous connection, I saw it in your first log file. It is 210.101.131.231.
So you can enter it in the Proxy IP like this:
  • In FAHControl, you must be in either the 'Advanced' or 'Expert' mode, selected from the dropdown menu at the upper right
  • Click on 'Configure', and select the 'Proxy' tab
  • Click to 'Enable proxy configuration'
  • In the 'Proxy' area 'Hostname or IP', enter 210.101.131.231
  • Make sure the 'Port' is still 8080
  • Click on 'Save'
That should get the proxy server working for you again.

Re: 155.247.166.219:8080

Posted: Mon Feb 04, 2013 10:46 pm
by hisui
the thing is I dont think it's the problem with connection,connection to 155.247.166.219:8080 is fine,I think it's something wrong with assignment server and 155.247.166.219:8080.Will admin do something to solve this problem?

Pinging 155.247.166.219 with 32 bytes of data:

Reply from 155.247.166.219: bytes=32 time=215ms TTL=49
Reply from 155.247.166.219: bytes=32 time=287ms TTL=49
Reply from 155.247.166.219: bytes=32 time=265ms TTL=49
Reply from 155.247.166.219: bytes=32 time=215ms TTL=49

Code: Select all

| 0   |            |        | 192.168.***.***     | cube141                                 | ...                   |  |  | (private use)             |
| 1   | x----      |        | 124.74.12.235   | -                                       |                       |  |  | 124.74.12.0               |
| 2   | x---       |        | 124.74.12.235   | -                                       |                       |  |  | 124.74.12.0               |
| 3   | x--        |        | 124.74.226.89   | -                                       |                       |  |  | 124.74.226.0              |
| 4   | x--        |        | 124.74.215.129  | -                                       |                       |  |  | 124.74.215.0              |
| 5   | --x---     |        | 202.101.63.122  | -                                       | ?Shanghai, China      |  |  | China Telecom             |
| 6   | -x---      |        | 202.97.33.38    | -                                       | ?(China)              |  |  | CHINANET backbone network |
| 7   | -x--       |        | 202.97.33.190   | -                                       | ?(China)              |  |  | CHINANET backbone network |
| 8   |  --x--     |        | 202.97.50.114   | -                                       | ?(China)              |  |  | FSKWC NET                 |
| 9   |  -x---     |        | 202.97.52.218   | -                                       | ?(China)              |  |  | CHINANET backbone network |
| 10  |  -x--      |        | 152.179.48.93   | TenGigE0-1-0-1.GW6.SJC7.ALTER.NET       | San Jose, CA, USA     |  |  | 152.179.48.0              |
| 11  |  -x--      |        | 152.63.49.201   | 0.xe-3-1-3.XL3.SJC7.ALTER.NET           | San Jose, CA, USA     |  |  | 152.63.49.0               |
| 12  |   -x------ |        | 152.63.2.213    | 0.so-3-1-0.XL3.PHL6.ALTER.NET           | Philadelphia, PA, USA |  |  | 152.63.2.0                |

Re: 155.247.166.219:8080

Posted: Mon Feb 04, 2013 11:38 pm
by art_l_j_PlanetAMD64
hisui wrote:the thing is I dont think it's the problem with connection,connection to 155.247.166.219:8080 is fine,I think it's something wrong with assignment server and 155.247.166.219:8080.Will admin do something to solve this problem?
Making any change to the Assignment Server or the Work Server is the decision of Stanford/PG, so I cannot answer your question.

Even with using the Proxy Server, I continue to have this problem on all 3 of my smp:2 machines here:
  1. My #3 system: Johnson-office2 (WinXP SP3, 32-bit)
  2. My #4 system: art-Debian-01 (Debian Linux v6.0.6, 64-bit)
  3. My #5 system: art-Debian-02 (Debian Linux v6.0.6, 64-bit)
Here is the log file from my art-Debian-02 (Debian Linux v6.0.6, 64-bit) computer:

Code: Select all

*********************** Log Started 2013-01-30T09:17:44Z ***********************
09:17:44:************************* Folding@home Client *************************
09:17:44:    Website: http://folding.stanford.edu/
09:17:44:  Copyright: (c) 2009-2012 Stanford University
09:17:44:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
09:17:44:       Args: --child --lifeline 1286 /etc/fahclient/config.xml --run-as
09:17:44:             fahclient --pid-file=/var/run/fahclient.pid --daemon
09:17:44:     Config: /etc/fahclient/config.xml
09:17:44:******************************** Build ********************************
09:17:44:    Version: 7.2.9
09:17:44:       Date: Oct 3 2012
09:17:44:       Time: 10:34:06
09:17:44:    SVN Rev: 3578
09:17:44:     Branch: fah/trunk/client
09:17:44:   Compiler: GNU 4.4.7
09:17:44:    Options: -std=gnu++98 -O3 -funroll-loops -mfpmath=sse -ffast-math
09:17:44:             -fno-unsafe-math-optimizations -msse2
09:17:44:   Platform: linux2 3.2.0-1-amd64
09:17:44:       Bits: 64
09:17:44:       Mode: Release
09:17:44:******************************* System ********************************
09:17:44:        CPU: AMD Athlon(tm) 7550 Dual-Core Processor
09:17:44:     CPU ID: AuthenticAMD Family 16 Model 2 Stepping 3
09:17:44:       CPUs: 2
09:17:44:     Memory: 1.96GiB
09:17:44:Free Memory: 1.87GiB
09:17:44:    Threads: POSIX_THREADS
09:17:44: On Battery: false
09:17:44: UTC offset: -8
09:17:44:        PID: 1296
09:17:44:        CWD: /var/lib/fahclient
09:17:44:         OS: Linux 2.6.32-5-amd64 x86_64
09:17:44:    OS Arch: AMD64
09:17:44:       GPUs: 1
09:17:44:      GPU 0: NVIDIA:1 GT200 [GeForce GTX 260]
09:17:44:       CUDA: Not detected
09:17:44:***********************************************************************
09:17:44:<config>
09:17:44:  <!-- Folding Slot Configuration -->
09:17:44:  <max-packet-size v='big'/>
09:17:44:
09:17:44:  <!-- Network -->
09:17:44:  <proxy v=':8080'/>
09:17:44:
09:17:44:  <!-- User Information -->
09:17:44:  <passkey v='********************************'/>
09:17:44:  <team v='45862'/>
09:17:44:  <user v='art_l_j_PlanetAMD64'/>
09:17:44:
09:17:44:  <!-- Work Unit Control -->
09:17:44:  <next-unit-percentage v='100'/>
09:17:44:
09:17:44:  <!-- Folding Slots -->
09:17:44:  <slot id='0' type='SMP'/>
09:17:44:</config>
09:17:44:Switching to user fahclient
09:17:44:Trying to access database...
09:17:45:Successfully acquired database lock
09:17:45:Enabled folding slot 00: READY smp:2
09:17:45:WU01:FS00:Starting
09:17:45:WU01:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/www.stanford.edu/~pande/Linux/AMD64/Core_a4.fah/FahCore_a4 -dir 01 -suffix 01 -version 702 -lifeline 1296 -checkpoint 15 -np 2
09:17:45:WU01:FS00:Started FahCore on PID 1304
09:17:45:WU01:FS00:Core PID:1312
09:17:45:WU01:FS00:FahCore 0xa4 started
09:17:46:WU01:FS00:0xa4:
09:17:46:WU01:FS00:0xa4:*------------------------------*
09:17:46:WU01:FS00:0xa4:Folding@Home Gromacs GB Core
09:17:46:WU01:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
09:17:46:WU01:FS00:0xa4:
09:17:46:WU01:FS00:0xa4:Preparing to commence simulation
09:17:46:WU01:FS00:0xa4:- Looking at optimizations...
09:17:46:WU01:FS00:0xa4:- Files status OK
09:17:47:WU01:FS00:0xa4:- Expanded 2079169 -> 5386224 (decompressed 259.0 percent)
09:17:47:WU01:FS00:0xa4:Called DecompressByteArray: compressed_data_size=2079169 data_size=5386224, decompressed_data_size=5386224 diff=0
09:17:47:WU01:FS00:0xa4:- Digital signature verified
09:17:47:WU01:FS00:0xa4:
09:17:47:WU01:FS00:0xa4:Project: 7809 (Run 2, Clone 285, Gen 38)
09:17:47:WU01:FS00:0xa4:
09:17:47:WU01:FS00:0xa4:Assembly optimizations on if available.
09:17:47:WU01:FS00:0xa4:Entering M.D.
09:17:53:WU01:FS00:0xa4:Using Gromacs checkpoints
09:17:58:WU01:FS00:0xa4:Resuming from checkpoint
09:17:58:WU01:FS00:0xa4:Verified 01/wudata_01.log
09:17:59:WU01:FS00:0xa4:Verified 01/wudata_01.trr
09:17:59:WU01:FS00:0xa4:Verified 01/wudata_01.xtc
09:17:59:WU01:FS00:0xa4:Verified 01/wudata_01.edr
09:18:00:WU01:FS00:0xa4:Completed 150740 out of 1500000 steps  (10%)
09:28:10:Server connection id=1 on 0.0.0.0:36330 from 127.0.0.1
09:55:09:WU01:FS00:0xa4:Completed 165000 out of 1500000 steps  (11%)

...

18:58:35:WU01:FS00:0xa4:Completed 1485000 out of 1500000 steps  (99%)
******************************** Date: 01/02/13 ********************************
19:37:50:WU01:FS00:0xa4:Completed 1500000 out of 1500000 steps  (100%)
19:37:50:WU00:FS00:Connecting to assign3.stanford.edu:8080
19:37:50:WU00:FS00:News: Welcome to Folding@Home
19:37:50:WU00:FS00:Assigned to work server 155.247.166.219
19:37:50:WU00:FS00:Requesting new work unit for slot 00: RUNNING smp:2 from 155.247.166.219
19:37:50:WU00:FS00:Connecting to 155.247.166.219:8080
19:37:50:WU01:FS00:0xa4:DynamicWrapper: Finished Work Unit: sleep=10000
[91m19:37:50:ERROR:WU00:FS00:Exception: Server did not assign work unit[0m
19:37:51:WU00:FS00:Connecting to assign3.stanford.edu:8080
19:37:51:WU00:FS00:News: Welcome to Folding@Home
19:37:51:WU00:FS00:Assigned to work server 155.247.166.219
19:37:51:WU00:FS00:Requesting new work unit for slot 00: RUNNING smp:2 from 155.247.166.219
19:37:51:WU00:FS00:Connecting to 155.247.166.219:8080
[91m19:37:51:ERROR:WU00:FS00:Exception: Server did not assign work unit[0m
19:38:00:WU01:FS00:0xa4:
19:38:00:WU01:FS00:0xa4:Finished Work Unit:
19:38:00:WU01:FS00:0xa4:- Reading up to 2908800 from "01/wudata_01.trr": Read 2908800
19:38:00:WU01:FS00:0xa4:trr file hash check passed.
19:38:00:WU01:FS00:0xa4:- Reading up to 1554312 from "01/wudata_01.xtc": Read 1554312
19:38:00:WU01:FS00:0xa4:xtc file hash check passed.
19:38:00:WU01:FS00:0xa4:edr file hash check passed.
19:38:00:WU01:FS00:0xa4:logfile size: 39423
19:38:00:WU01:FS00:0xa4:Leaving Run
19:38:05:WU01:FS00:0xa4:- Writing 4507547 bytes of core data to disk...
19:38:07:WU01:FS00:0xa4:Done: 4507035 -> 4326320 (compressed to 95.9 percent)
19:38:07:WU01:FS00:0xa4:  ... Done.
19:38:08:WU01:FS00:0xa4:- Shutting down core
19:38:08:WU01:FS00:0xa4:
19:38:08:WU01:FS00:0xa4:Folding@home Core Shutdown: FINISHED_UNIT
19:38:08:WU01:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
19:38:08:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:7809 run:2 clone:285 gen:38 core:0xa4 unit:0x000000580a3b1e874e310a13b203f559
19:38:08:WU01:FS00:Uploading 4.13MiB to 171.64.65.99
19:38:08:WU01:FS00:Connecting to 171.64.65.99:8080
19:38:14:WU01:FS00:Upload 42.41%
19:38:20:WU01:FS00:Upload 84.82%
19:38:23:WU01:FS00:Upload complete
19:38:23:WU01:FS00:Server responded WORK_ACK (400)
19:38:23:WU01:FS00:Final credit estimate, 5933.00 points
19:38:23:WU01:FS00:Cleaning up
19:38:51:WU00:FS00:Connecting to assign3.stanford.edu:8080
19:38:51:WU00:FS00:News: Welcome to Folding@Home
19:38:51:WU00:FS00:Assigned to work server 155.247.166.219
19:38:51:WU00:FS00:Requesting new work unit for slot 00: READY smp:2 from 155.247.166.219
19:38:51:WU00:FS00:Connecting to 155.247.166.219:8080
19:38:51:ERROR:WU00:FS00:Exception: Server did not assign work unit

----------------------------------------------------------------------------
Deleted 78 blocks of this, the same as the block just above:

19:38:51:WU00:FS00:Connecting to assign3.stanford.edu:8080
19:38:51:WU00:FS00:News: Welcome to Folding@Home
19:38:51:WU00:FS00:Assigned to work server 155.247.166.219
19:38:51:WU00:FS00:Requesting new work unit for slot 00: READY smp:2 from 155.247.166.219
19:38:51:WU00:FS00:Connecting to 155.247.166.219:8080
19:38:51:ERROR:WU00:FS00:Exception: Server did not assign work unit
----------------------------------------------------------------------------

21:44:04:WU01:FS00:Connecting to assign3.stanford.edu:8080
21:44:04:WU01:FS00:News: Welcome to Folding@Home
21:44:04:WU01:FS00:Assigned to work server 171.67.108.60
21:44:04:WU01:FS00:Requesting new work unit for slot 00: READY smp:2 from 171.67.108.60
21:44:04:WU01:FS00:Connecting to 171.67.108.60:8080
21:44:04:WU01:FS00:Downloading 512.95KiB
21:44:06:WU01:FS00:Download complete
21:44:06:WU01:FS00:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:8028 run:780 clone:3 gen:22 core:0xa4 unit:0x000000246652edcc50e7914be4b73927
21:44:06:WU01:FS00:Starting
21:44:06:WU01:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/www.stanford.edu/~pande/Linux/AMD64/Core_a4.fah/FahCore_a4 -dir 01 -suffix 01 -version 702 -lifeline 1296 -checkpoint 15 -np 2
21:44:06:WU01:FS00:Started FahCore on PID 3737
21:44:06:WU01:FS00:Core PID:3741
21:44:06:WU01:FS00:FahCore 0xa4 started
21:44:06:WU01:FS00:Downloading project 8028 description
21:44:06:WU01:FS00:Connecting to fah-web.stanford.edu:80
21:44:06:WU01:FS00:0xa4:
21:44:06:WU01:FS00:0xa4:*------------------------------*
21:44:06:WU01:FS00:0xa4:Folding@Home Gromacs GB Core
21:44:06:WU01:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
21:44:06:WU01:FS00:0xa4:
21:44:06:WU01:FS00:0xa4:Preparing to commence simulation
21:44:06:WU01:FS00:0xa4:- Looking at optimizations...
21:44:06:WU01:FS00:0xa4:- Created dyn
21:44:06:WU01:FS00:0xa4:- Files status OK
21:44:06:WU01:FS00:0xa4:- Expanded 524746 -> 1189760 (decompressed 226.7 percent)
21:44:06:WU01:FS00:0xa4:Called DecompressByteArray: compressed_data_size=524746 data_size=1189760, decompressed_data_size=1189760 diff=0
21:44:06:WU01:FS00:0xa4:- Digital signature verified
21:44:06:WU01:FS00:0xa4:
21:44:06:WU01:FS00:0xa4:Project: 8028 (Run 780, Clone 3, Gen 22)
21:44:06:WU01:FS00:0xa4:
21:44:06:WU01:FS00:0xa4:Assembly optimizations on if available.
21:44:06:WU01:FS00:0xa4:Entering M.D.
21:44:07:WU01:FS00:Project 8028 description downloaded successfully
21:44:12:WU01:FS00:0xa4:Completed 0 out of 500000 steps  (0%)
21:49:04:WU01:FS00:0xa4:Completed 5000 out of 500000 steps  (1%)

...

05:47:51:WU01:FS00:0xa4:Completed 495000 out of 500000 steps  (99%)
05:52:45:WU01:FS00:0xa4:Completed 500000 out of 500000 steps  (100%)
05:52:45:WU01:FS00:0xa4:DynamicWrapper: Finished Work Unit: sleep=10000
05:52:46:WU00:FS00:Connecting to assign3.stanford.edu:8080
05:52:46:WU00:FS00:News: Welcome to Folding@Home
05:52:46:WU00:FS00:Assigned to work server 155.247.166.219
05:52:46:WU00:FS00:Requesting new work unit for slot 00: RUNNING smp:2 from 155.247.166.219
05:52:46:WU00:FS00:Connecting to 155.247.166.219:8080
05:52:46:ERROR:WU00:FS00:Exception: Server did not assign work unit
05:52:47:WU00:FS00:Connecting to assign3.stanford.edu:8080
05:52:47:WU00:FS00:News: Welcome to Folding@Home
05:52:47:WU00:FS00:Assigned to work server 155.247.166.219
05:52:47:WU00:FS00:Requesting new work unit for slot 00: RUNNING smp:2 from 155.247.166.219
05:52:47:WU00:FS00:Connecting to 155.247.166.219:8080
05:52:47:ERROR:WU00:FS00:Exception: Server did not assign work unit
05:52:55:WU01:FS00:0xa4:
05:52:55:WU01:FS00:0xa4:Finished Work Unit:
05:52:55:WU01:FS00:0xa4:- Reading up to 770208 from "01/wudata_01.trr": Read 770208
05:52:55:WU01:FS00:0xa4:trr file hash check passed.
05:52:55:WU01:FS00:0xa4:- Reading up to 835964 from "01/wudata_01.xtc": Read 835964
05:52:55:WU01:FS00:0xa4:xtc file hash check passed.
05:52:55:WU01:FS00:0xa4:edr file hash check passed.
05:52:55:WU01:FS00:0xa4:logfile size: 27395
05:52:55:WU01:FS00:0xa4:Leaving Run
05:52:57:WU01:FS00:0xa4:- Writing 1642391 bytes of core data to disk...
05:52:58:WU01:FS00:0xa4:Done: 1641879 -> 1579036 (compressed to 96.1 percent)
05:52:58:WU01:FS00:0xa4:  ... Done.
05:52:58:WU01:FS00:0xa4:- Shutting down core
05:52:58:WU01:FS00:0xa4:
05:52:58:WU01:FS00:0xa4:Folding@home Core Shutdown: FINISHED_UNIT
05:52:58:WU01:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
05:52:58:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:8028 run:780 clone:3 gen:22 core:0xa4 unit:0x000000246652edcc50e7914be4b73927
05:52:58:WU01:FS00:Uploading 1.51MiB to 171.67.108.60
05:52:58:WU01:FS00:Connecting to 171.67.108.60:8080
05:53:04:WU01:FS00:Upload complete
05:53:04:WU01:FS00:Server responded WORK_ACK (400)
05:53:04:WU01:FS00:Final credit estimate, 957.00 points
05:53:04:WU01:FS00:Cleaning up
05:53:47:WU00:FS00:Connecting to assign3.stanford.edu:8080
05:53:47:WU00:FS00:News: Welcome to Folding@Home
05:53:47:WU00:FS00:Assigned to work server 155.247.166.219
05:53:47:WU00:FS00:Requesting new work unit for slot 00: READY smp:2 from 155.247.166.219
05:53:47:WU00:FS00:Connecting to 155.247.166.219:8080
05:53:47:ERROR:WU00:FS00:Exception: Server did not assign work unit

----------------------------------------------------------------------------
Deleted 80 blocks of this, the same as the block just above:

05:53:47:WU00:FS00:Connecting to assign3.stanford.edu:8080
05:53:47:WU00:FS00:News: Welcome to Folding@Home
05:53:47:WU00:FS00:Assigned to work server 155.247.166.219
05:53:47:WU00:FS00:Requesting new work unit for slot 00: READY smp:2 from 155.247.166.219
05:53:47:WU00:FS00:Connecting to 155.247.166.219:8080
05:53:47:ERROR:WU00:FS00:Exception: Server did not assign work unit
----------------------------------------------------------------------------

06:36:02:WU00:FS00:Connecting to assign3.stanford.edu:8080
06:36:02:WU00:FS00:News: Welcome to Folding@Home
06:36:02:WU00:FS00:Assigned to work server 155.247.166.219
06:36:02:WU00:FS00:Requesting new work unit for slot 00: READY smp:2 from 155.247.166.219
06:36:02:WU00:FS00:Connecting to 155.247.166.219:8080
06:36:03:ERROR:WU00:FS00:Exception: Server did not assign work unit
06:40:16:WU00:FS00:Connecting to assign3.stanford.edu:8080
06:40:17:WU00:FS00:News: Welcome to Folding@Home
06:40:17:WU00:FS00:Assigned to work server 171.64.65.99
06:40:17:WU00:FS00:Requesting new work unit for slot 00: READY smp:2 from 171.64.65.99
06:40:17:WU00:FS00:Connecting to 171.64.65.99:8080
06:40:18:WU00:FS00:Downloading 1.98MiB
06:40:23:WU00:FS00:Download complete
06:40:23:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:7809 run:8 clone:7 gen:21 core:0xa4 unit:0x000000260a3b1e874e3115eddaacf132
06:40:23:WU00:FS00:Starting
06:40:23:WU00:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/www.stanford.edu/~pande/Linux/AMD64/Core_a4.fah/FahCore_a4 -dir 00 -suffix 01 -version 702 -lifeline 1296 -checkpoint 15 -np 2
06:40:23:WU00:FS00:Started FahCore on PID 3822
06:40:23:WU00:FS00:Core PID:3826
06:40:23:WU00:FS00:FahCore 0xa4 started
06:40:23:WU00:FS00:0xa4:
06:40:23:WU00:FS00:0xa4:*------------------------------*
06:40:23:WU00:FS00:0xa4:Folding@Home Gromacs GB Core
06:40:23:WU00:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
06:40:23:WU00:FS00:0xa4:
06:40:23:WU00:FS00:0xa4:Preparing to commence simulation
06:40:23:WU00:FS00:0xa4:- Looking at optimizations...
06:40:23:WU00:FS00:0xa4:- Created dyn
06:40:23:WU00:FS00:0xa4:- Files status OK
06:40:23:WU00:FS00:0xa4:- Expanded 2079442 -> 5386224 (decompressed 259.0 percent)
06:40:23:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=2079442 data_size=5386224, decompressed_data_size=5386224 diff=0
06:40:23:WU00:FS00:0xa4:- Digital signature verified
06:40:23:WU00:FS00:0xa4:
06:40:23:WU00:FS00:0xa4:Project: 7809 (Run 8, Clone 7, Gen 21)
06:40:23:WU00:FS00:0xa4:
06:40:23:WU00:FS00:0xa4:Assembly optimizations on if available.
06:40:23:WU00:FS00:0xa4:Entering M.D.
06:40:30:WU00:FS00:0xa4:Completed 0 out of 1500000 steps  (0%)
07:19:24:WU00:FS00:0xa4:Completed 15000 out of 1500000 steps  (1%)
******************************** Date: 02/02/13 ********************************
07:58:08:WU00:FS00:0xa4:Completed 30000 out of 1500000 steps  (2%)

...

01:48:11:WU00:FS00:Downloading project 7809 description
01:48:11:WU00:FS00:Connecting to fah-web.stanford.edu:80
01:48:11:WU00:FS00:Project 7809 description downloaded successfully
02:06:51:WU00:FS00:0xa4:Completed 450000 out of 1500000 steps  (30%)
02:45:43:WU00:FS00:0xa4:Completed 465000 out of 1500000 steps  (31%)
******************************** Date: 03/02/13 ********************************
03:24:36:WU00:FS00:0xa4:Completed 480000 out of 1500000 steps  (32%)
04:03:25:WU00:FS00:0xa4:Completed 495000 out of 1500000 steps  (33%)
04:42:22:WU00:FS00:0xa4:Completed 510000 out of 1500000 steps  (34%)
05:08:59:FS00:Paused
05:08:59:FS00:Shutting core down
05:09:04:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
05:11:04:Saving configuration to /etc/fahclient/config.xml
05:11:04:<config>
05:11:04:  <!-- Folding Slot Configuration -->
05:11:04:  <max-packet-size v='big'/>
05:11:04:
05:11:04:  <!-- Network -->
05:11:04:  <proxy v='proxy.vs.shawcable.net:8080'/>
05:11:04:  <proxy-enable v='true'/>
05:11:04:
05:11:04:  <!-- User Information -->
05:11:04:  <passkey v='********************************'/>
05:11:04:  <team v='45862'/>
05:11:04:  <user v='art_l_j_PlanetAMD64'/>
05:11:04:
05:11:04:  <!-- Work Unit Control -->
05:11:04:  <next-unit-percentage v='100'/>
05:11:04:
05:11:04:  <!-- Folding Slots -->
05:11:04:  <slot id='0' type='SMP'/>
05:11:04:</config>
05:11:40:Server connection id=1 ended
[93m05:12:58:WARNING:Caught signal SIGINT(2) on PID 1296[0m
05:12:58:Exiting, please wait. . .
05:12:59:Clean exit

Re: 155.247.166.219:8080

Posted: Mon Feb 04, 2013 11:47 pm
by bruce
hisui wrote:the thing is I dont think it's the problem with connection,connection to 155.247.166.219:8080 is fine,I think it's something wrong with assignment server and 155.247.166.219:8080.Will admin do something to solve this problem?
I spotted the problem and notified the owner of that server.

I was a bit surprised that you suggested that a proxy setting would change anything as long as connections to other servers were working. Apparently that was the wrong idea but I didn't study it carefully. When operating WITHOUT a proxy, the FAHClient attempts to connect to {server_IP}:8080 first. If that fails, it often reverts to {server_IP}:80 but not always. Thus port 8080 is more reliable than port 80. When connecting through a proxy, what determines the port number used at the final destination?

Re: 155.247.166.219:8080

Posted: Tue Feb 05, 2013 12:29 am
by art_l_j_PlanetAMD64
bruce wrote:I spotted the problem and notified the owner of that server.

I was a bit surprised that you suggested that a proxy setting would change anything as long as connections to other servers were working. Apparently that was the wrong idea but I didn't study it carefully. When operating WITHOUT a proxy, the FAHClient attempts to connect to {server_IP}:8080 first. If that fails, it often reverts to {server_IP}:80 but not always. Thus port 8080 is more reliable than port 80. When connecting through a proxy, what determines the port number used at the final destination?
Thanks for your help, bruce. :)

It was probably a coincidence, but as soon as I changed to the proxy server, all 3 of my smp:2 computers started getting assigned to WS 171.67.108.60:8080 by AS assign3.stanford.edu:8080 right away, instead of waiting for 80-100 failures of WS 155.247.166.219:8080. That did not last, as sometime yesterday, the same problem with WS 155.247.166.219:8080 appeared again. So it was another of those times where I was fooled by the apparent 'connection' between changing to the proxy server, and the AS/WS problem appearing to be 'fixed'. :?

As the old saying goes: "Correlation does not imply causation". :ewink:

Re: 155.247.166.219:8080

Posted: Tue Feb 05, 2013 10:48 am
by hisui
art_l_j_PlanetAMD64 wrote:
bruce wrote:I spotted the problem and notified the owner of that server.

I was a bit surprised that you suggested that a proxy setting would change anything as long as connections to other servers were working. Apparently that was the wrong idea but I didn't study it carefully. When operating WITHOUT a proxy, the FAHClient attempts to connect to {server_IP}:8080 first. If that fails, it often reverts to {server_IP}:80 but not always. Thus port 8080 is more reliable than port 80. When connecting through a proxy, what determines the port number used at the final destination?
Thanks for your help, bruce. :)

It was probably a coincidence, but as soon as I changed to the proxy server, all 3 of my smp:2 computers started getting assigned to WS 171.67.108.60:8080 by AS assign3.stanford.edu:8080 right away, instead of waiting for 80-100 failures of WS 155.247.166.219:8080. That did not last, as sometime yesterday, the same problem with WS 155.247.166.219:8080 appeared again. So it was another of those times where I was fooled by the apparent 'connection' between changing to the proxy server, and the AS/WS problem appearing to be 'fixed'. :?

As the old saying goes: "Correlation does not imply causation". :ewink:
have u solved that problem by using proxy or after using proxy for a while the problem resurfaced?

Re: 155.247.166.219:8080

Posted: Tue Feb 05, 2013 11:39 am
by art_l_j_PlanetAMD64
hisui wrote:have u solved that problem by using proxy or after using proxy for a while the problem resurfaced?
Yes, the problem resurfaced, and I had to remove the proxy server, it was causing problems with uploading/downloading. So I am back at the beginning, and we must wait for the problem to be corrected.

Re: 155.247.166.219:8080

Posted: Tue Feb 05, 2013 9:51 pm
by bruce
You're confusing three different things.
1) Specific Work servers may have projects that use one FahCore or another FahCore.
2) There is more than one Assign*.stanford.edu server which can direct you to Work Servers. It's name has nothing to do with what type of work might be on a specific Work Server.
3) A proxy server is not a tool to enable you to bypass the code that directs you to a Work Server that advertises that it has work for your client.

Yes, there's a problem associated with at least one Work Server that has been reported. Neither you or I can fix that problem.

Re: 155.247.166.219:8080

Posted: Wed Feb 06, 2013 6:27 pm
by art_l_j_PlanetAMD64
bruce wrote:I spotted the problem and notified the owner of that server.
Thanks, bruce.

Just an update this morning, my #4 system, art-Debian-01 (Debian Linux v6.0.6, 64-bit), has had 125 failed attempts to get a WU from 155.247.166.219:8080 in the last 3.5 hours.