problem with getting a new WU (solved itself)

Moderators: Site Moderators, PandeGroup

problem with getting a new WU (solved itself)

Postby beer » Thu Oct 04, 2012 7:19 am

Hi

My mashine is to silences because is not receiving any new units. What should I do?
Code: Select all
--- Opening Log file [October 4 06:56:40 UTC]


# Windows SMP Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.34

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Users\jove\Desktop\FAH GPU Tracker V2\SMP
Executable: C:\Users\jove\Desktop\FAH GPU Tracker V2\FAH.exe
Arguments: -oneunit -forceasm -smp

[06:56:40] - Ask before connecting: No
[06:56:40] - User name: jonasvejlin (Team 0)
[06:56:40] - User ID: 6FAE2A2430FD42B
[06:56:40] - Machine ID: 2
[06:56:40]
[06:56:40] Work directory not found. Creating...
[06:56:40] Could not open work queue, generating new queue...
[06:56:40] - Preparing to get new work unit...
[06:56:40] Cleaning up work directory
[06:56:40] + Attempting to get work packet
[06:56:40] Passkey found
[06:56:40] - Connecting to assignment server
[06:56:41] - Successful: assigned to (171.67.108.58).
[06:56:41] + News From Folding@Home: Welcome to Folding@Home
[06:56:41] Loaded queue successfully.
[06:56:42] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[06:57:01] + Attempting to get work packet
[06:57:01] Passkey found
[06:57:01] - Connecting to assignment server
[06:57:02] - Successful: assigned to (171.67.108.58).
[06:57:02] + News From Folding@Home: Welcome to Folding@Home
[06:57:02] Loaded queue successfully.
[06:57:03] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[06:57:15] + Attempting to get work packet
[06:57:15] Passkey found
[06:57:15] - Connecting to assignment server
[06:57:16] - Successful: assigned to (171.67.108.58).
[06:57:16] + News From Folding@Home: Welcome to Folding@Home
[06:57:16] Loaded queue successfully.
[06:57:17] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[06:57:44] + Attempting to get work packet
[06:57:44] Passkey found
[06:57:44] - Connecting to assignment server
[06:57:45] - Successful: assigned to (171.67.108.58).
[06:57:45] + News From Folding@Home: Welcome to Folding@Home
[06:57:45] Loaded queue successfully.
[06:57:46] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[06:58:39] + Attempting to get work packet
[06:58:39] Passkey found
[06:58:39] - Connecting to assignment server
[06:58:40] - Successful: assigned to (171.67.108.58).
[06:58:40] + News From Folding@Home: Welcome to Folding@Home
[06:58:40] Loaded queue successfully.
[06:58:41] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[07:00:02] + Attempting to get work packet
[07:00:02] Passkey found
[07:00:02] - Connecting to assignment server
[07:00:03] - Successful: assigned to (171.67.108.58).
[07:00:03] + News From Folding@Home: Welcome to Folding@Home
[07:00:03] Loaded queue successfully.
[07:00:04] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[07:02:47] + Attempting to get work packet
[07:02:47] Passkey found
[07:02:47] - Connecting to assignment server
[07:02:48] - Successful: assigned to (171.67.108.58).
[07:02:48] + News From Folding@Home: Welcome to Folding@Home
[07:02:49] Loaded queue successfully.
[07:02:49] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[07:08:21] + Attempting to get work packet
[07:08:21] Passkey found
[07:08:21] - Connecting to assignment server
[07:08:22] - Successful: assigned to (171.67.108.58).
[07:08:22] + News From Folding@Home: Welcome to Folding@Home
[07:08:22] Loaded queue successfully.
[07:08:23] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
Last edited by beer on Thu Oct 04, 2012 8:01 am, edited 1 time in total.
beer
 
Posts: 162
Joined: Tue Dec 13, 2011 11:18 am

Re: problem with getting a new WU

Postby beer » Thu Oct 04, 2012 7:34 am

I also did try client 7.1.52 but does not seem to work either:
Code: Select all
*********************** Log Started 2012-10-04T07:29:49Z ***********************
07:29:49:************************* Folding@home Client *************************
07:29:49:      Website: http://folding.stanford.edu/
07:29:49:    Copyright: (c) 2009-2012 Stanford University
07:29:49:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
07:29:49:         Args: --lifeline 1144 --command-port=36330
07:29:49:       Config: C:/Users/jove/AppData/Roaming/FAHClient/config.xml
07:29:49:******************************** Build ********************************
07:29:49:      Version: 7.1.52
07:29:49:         Date: Mar 20 2012
07:29:49:         Time: 19:37:42
07:29:49:      SVN Rev: 3515
07:29:49:       Branch: fah/trunk/client
07:29:49:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
07:29:49:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
07:29:49:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT
07:29:49:     Platform: win32 XP
07:29:49:         Bits: 32
07:29:49:         Mode: Release
07:29:49:******************************* System ********************************
07:29:49:          CPU: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
07:29:49:       CPU ID: GenuineIntel Family 6 Model 42 Stepping 7
07:29:49:         CPUs: 8
07:29:49:       Memory: 7.94GiB
07:29:49:  Free Memory: 4.98GiB
07:29:49:      Threads: WINDOWS_THREADS
07:29:49:   On Battery: false
07:29:49:   UTC offset: 2
07:29:49:          PID: 1100
07:29:49:          CWD: C:/Users/jove/AppData/Roaming/FAHClient
07:29:49:           OS: Windows 7 Enterprise
07:29:49:      OS Arch: AMD64
07:29:49:         GPUs: 1
07:29:49:        GPU 0: FERMI:1 GF106GL [Quadro 2000]
07:29:49:         CUDA: 2.1
07:29:49:  CUDA Driver: 4020
07:29:49:Win32 Service: false
07:29:49:***********************************************************************
07:29:49:<config>
07:29:49:  <!-- User Information -->
07:29:49:  <passkey v='********************************'/>
07:29:49:  <user v='jonasvejlin'/>
07:29:49:
07:29:49:  <!-- Folding Slots -->
07:29:49:</config>
07:29:49:Trying to access database...
07:29:49:Successfully acquired database lock
07:29:49:Enabled folding slot 00: READY smp:8
07:29:49:WU00:FS00:Connecting to assign3.stanford.edu:8080
07:29:51:WU00:FS00:Connecting to assign3.stanford.edu:8080
07:29:52:WU00:FS00:News: Welcome to Folding@Home
07:29:52:WU00:FS00:Assigned to work server 171.67.108.58
07:29:52:WU00:FS00:Requesting new work unit for slot 00: READY smp:8 from 171.67.108.58
07:29:52:WU00:FS00:Connecting to 171.67.108.58:8080
07:29:52:Server connection id=1 on 0.0.0.0:36330 from 127.0.0.1
07:29:53:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
07:29:53:WU00:FS00:Connecting to 171.67.108.58:80
07:29:55:ERROR:WU00:FS00:Exception: Failed to connect to 171.67.108.58:80: No connection could be made because the target machine actively refused it.
07:29:55:WU00:FS00:Connecting to assign3.stanford.edu:8080
07:29:55:WU00:FS00:News: Welcome to Folding@Home
07:29:55:WU00:FS00:Assigned to work server 171.67.108.58
07:29:55:WU00:FS00:Requesting new work unit for slot 00: READY smp:8 from 171.67.108.58
07:29:56:WU00:FS00:Connecting to 171.67.108.58:8080
07:29:57:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
07:29:57:WU00:FS00:Connecting to 171.67.108.58:80
07:29:59:ERROR:WU00:FS00:Exception: Failed to connect to 171.67.108.58:80: No connection could be made because the target machine actively refused it.
07:30:55:WU00:FS00:Connecting to assign3.stanford.edu:8080
07:30:56:WU00:FS00:News: Welcome to Folding@Home
07:30:56:WU00:FS00:Assigned to work server 171.67.108.58
07:30:56:WU00:FS00:Requesting new work unit for slot 00: READY smp:8 from 171.67.108.58
07:30:56:WU00:FS00:Connecting to 171.67.108.58:8080
07:30:57:WARNING:WU00:FS00:WorkServer connection failed on port 8080 trying 80
07:30:57:WU00:FS00:Connecting to 171.67.108.58:80
07:30:59:ERROR:WU00:FS00:Exception: Failed to connect to 171.67.108.58:80: No connection could be made because the target machine actively refused it.



This mashine has never had problem with getting WU. It has been crunshing since January
beer
 
Posts: 162
Joined: Tue Dec 13, 2011 11:18 am

Re: problem with getting a new WU (solved itself)

Postby beer » Thu Oct 04, 2012 8:02 am

after a "long" it finally graped a new WU
beer
 
Posts: 162
Joined: Tue Dec 13, 2011 11:18 am

Re: problem with getting a new WU (solved itself)

Postby bruce » Thu Oct 04, 2012 6:42 pm

Could you put start/finish times on the "long" time you're talking about? It would help me in determining the cause and might even help reduce the chances of the same thing happening again. Your report seems to cover a 34 minute time period. Was there more?
... from [October 4 06:56:41 UTC] to 07:30:59
... and always 171.67.108.58

... and did the WU you eventually received come from 171.67.108.58?
bruce
 
Posts: 20837
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: problem with getting a new WU (solved itself)

Postby beer » Sun Oct 07, 2012 9:58 am

The first log is complete and I stoped trying resive a WU from that setup. First log was from client v6 and 2. log is from client v7.1.52 and it was from that it resived a WU. I did not note down witch server that finaly did give me a WU
beer
 
Posts: 162
Joined: Tue Dec 13, 2011 11:18 am


Return to V6.34Beta SMP2 with passkey [Not Bigadv]

Who is online

Users browsing this forum: No registered users and 1 guest

cron