FAH GPU Tracker V2

FAH GPU Tracker V2 is a Folding@Home Client tracking and control program


    Can't seem to get a bigadv

    Share

    B2K24
    BETA Team Member

    Posts : 102
    Join date : 2010-06-09

    Can't seem to get a bigadv

    Post by B2K24 on Fri Jul 09, 2010 11:15 pm

    I'm unsure what the problem is in getting bigadv WU

    It looks like to me the server should be accepting. Any ideas?

    http://fah-web.stanford.edu/logs/171.67.108.22.log.html

    http://fah-web.stanford.edu/serverstat.html


    Code:
    # Windows SMP Console Edition #################################################
    ###############################################################################

                          Folding@Home Client Version 6.30

                              http://folding.stanford.edu

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

    Launch directory: G:\FAH GPU Tracker V2\SMP
    Executable: G:\FAH GPU Tracker V2\SMP\FAH.exe
    Arguments: -oneunit -forceasm -smp -verbosity 9 -bigadv

    [03:57:40] - Ask before connecting: No
    [03:57:40] - User name: B2K24 (Team 86565)
    [03:57:40] - User ID: 45B911FE33F611CE
    [03:57:40] - Machine ID: 2
    [03:57:40]
    [03:57:40] Could not open work queue, generating new queue...
    [03:57:40] - Preparing to get new work unit...
    [03:57:40] - Autosending finished units... [July 10 03:57:40 UTC]
    [03:57:40] Cleaning up work directory
    [03:57:40] Trying to send all finished work units
    [03:57:40] + No unsent completed units remaining.
    [03:57:40] - Autosend completed
    [03:57:40] + Attempting to get work packet
    [03:57:40] Passkey found
    [03:57:40] - Will indicate memory of 6135 MB
    [03:57:40] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 10, Stepping: 5
    [03:57:40] - Connecting to assignment server
    [03:57:40] Connecting to http://assign.stanford.edu:8080/
    [03:57:41] Posted data.
    [03:57:41] Initial: 43AB; - Successful: assigned to (171.67.108.22).
    [03:57:41] + News From Folding@Home: Welcome to Folding@Home
    [03:57:41] Loaded queue successfully.
    [03:57:41] Sent data
    [03:57:41] Connecting to http://171.67.108.22:8080/
    [03:57:49] Posted data.
    [03:57:49] Initial: 0000; - Error: Work packet too large
    [03:57:49] - Attempt #1  to get work failed, and no other work to do.
    Waiting before retry.
    [03:57:58] + Attempting to get work packet
    [03:57:58] Passkey found
    [03:57:58] - Will indicate memory of 6135 MB
    [03:57:58] - Connecting to assignment server
    [03:57:58] Connecting to http://assign.stanford.edu:8080/
    [03:57:59] Posted data.
    [03:57:59] Initial: 43AB; - Successful: assigned to (171.67.108.22).
    [03:57:59] + News From Folding@Home: Welcome to Folding@Home
    [03:57:59] Loaded queue successfully.
    [03:57:59] Sent data
    [03:57:59] Connecting to http://171.67.108.22:8080/
    [03:58:10] Posted data.
    [03:58:10] Initial: 0000; - Error: Work packet too large
    [03:58:10] - Attempt #2  to get work failed, and no other work to do.
    Waiting before retry.
    [03:58:30] + Attempting to get work packet
    [03:58:30] Passkey found
    [03:58:30] - Will indicate memory of 6135 MB
    [03:58:30] - Connecting to assignment server
    [03:58:30] Connecting to http://assign.stanford.edu:8080/
    [03:58:30] Posted data.
    [03:58:30] Initial: 43AB; - Successful: assigned to (171.67.108.22).
    [03:58:30] + News From Folding@Home: Welcome to Folding@Home
    [03:58:31] Loaded queue successfully.
    [03:58:31] Sent data
    [03:58:31] Connecting to http://171.67.108.22:8080/
    [03:58:39] Posted data.
    [03:58:39] Initial: 0000; - Error: Work packet too large
    [03:58:39] - Attempt #3  to get work failed, and no other work to do.
    Waiting before retry.
    [03:59:12] + Attempting to get work packet
    [03:59:12] Passkey found
    [03:59:12] - Will indicate memory of 6135 MB
    [03:59:12] - Connecting to assignment server
    [03:59:12] Connecting to http://assign.stanford.edu:8080/
    [03:59:13] Posted data.
    [03:59:13] Initial: 43AB; - Successful: assigned to (171.67.108.22).
    [03:59:13] + News From Folding@Home: Welcome to Folding@Home
    [03:59:13] Loaded queue successfully.
    [03:59:13] Sent data
    [03:59:13] Connecting to http://171.67.108.22:8080/
    [03:59:21] Posted data.
    [03:59:21] Initial: 0000; - Error: Work packet too large
    [03:59:21] - Attempt #4  to get work failed, and no other work to do.
    Waiting before retry.
    [04:00:07] + Attempting to get work packet
    [04:00:07] Passkey found
    [04:00:07] - Will indicate memory of 6135 MB
    [04:00:07] - Connecting to assignment server
    [04:00:07] Connecting to http://assign.stanford.edu:8080/
    [04:00:08] Posted data.
    [04:00:08] Initial: 43AB; - Successful: assigned to (171.67.108.22).
    [04:00:08] + News From Folding@Home: Welcome to Folding@Home
    [04:00:08] Loaded queue successfully.
    [04:00:08] Sent data
    [04:00:08] Connecting to http://171.67.108.22:8080/
    [04:00:17] Posted data.
    [04:00:17] Initial: 0000; - Error: Work packet too large
    [04:00:17] - Attempt #5  to get work failed, and no other work to do.
    Waiting before retry.
    [04:01:39] + Attempting to get work packet
    [04:01:39] Passkey found
    [04:01:39] - Will indicate memory of 6135 MB
    [04:01:39] - Connecting to assignment server
    [04:01:39] Connecting to http://assign.stanford.edu:8080/
    [04:01:39] Posted data.
    [04:01:39] Initial: 43AB; - Successful: assigned to (171.67.108.22).
    [04:01:39] + News From Folding@Home: Welcome to Folding@Home
    [04:01:40] Loaded queue successfully.
    [04:01:40] Sent data
    [04:01:40] Connecting to http://171.67.108.22:8080/
    [04:01:41] Posted data.
    [04:01:41] Initial: 0000; + Could not connect to Work Server
    [04:01:41] - Attempt #6  to get work failed, and no other work to do.
    Waiting before retry.
    [04:04:23] + Attempting to get work packet
    [04:04:23] Passkey found
    [04:04:23] - Will indicate memory of 6135 MB
    [04:04:23] - Connecting to assignment server
    [04:04:23] Connecting to http://assign.stanford.edu:8080/
    [04:04:24] Posted data.
    [04:04:24] Initial: 43AB; - Successful: assigned to (171.67.108.22).
    [04:04:24] + News From Folding@Home: Welcome to Folding@Home
    [04:04:24] Loaded queue successfully.
    [04:04:24] Sent data
    [04:04:24] Connecting to http://171.67.108.22:8080/
    [04:04:25] Posted data.
    [04:04:25] Initial: 0000; + Could not connect to Work Server
    [04:04:25] - Attempt #7  to get work failed, and no other work to do.
    Waiting before retry.
    [04:09:46] + Attempting to get work packet
    [04:09:46] Passkey found
    [04:09:46] - Will indicate memory of 6135 MB
    [04:09:46] - Connecting to assignment server
    [04:09:46] Connecting to http://assign.stanford.edu:8080/
    [04:09:46] Posted data.
    [04:09:46] Initial: 43AB; - Successful: assigned to (171.67.108.22).
    [04:09:46] + News From Folding@Home: Welcome to Folding@Home
    [04:09:47] Loaded queue successfully.
    [04:09:47] Sent data
    [04:09:47] Connecting to http://171.67.108.22:8080/
    [04:09:48] Posted data.
    [04:09:48] Initial: 0000; + Could not connect to Work Server
    [04:09:48] - Attempt #8  to get work failed, and no other work to do.
    Waiting before retry.
    avatar
    CadBane
    Dev Team Member

    Posts : 79
    Join date : 2010-05-26
    Age : 25
    Location : Colorado
    Job/hobbies : Site Webmaster/Folding@Home, TrackerV2 Development

    Re: Can't seem to get a bigadv

    Post by CadBane on Sat Jul 10, 2010 3:43 pm

    The server doesn't seem to want to give out any at the moment because I am getting the same behavior.


    _________________
    The Kill-Jacker


    avatar
    jedi95
    Dev Team Member

    Posts : 307
    Join date : 2010-05-26
    Job/hobbies : FAH GPU Tracker V2 Developer

    Re: Can't seem to get a bigadv

    Post by jedi95 on Sat Jul 10, 2010 5:55 pm

    Yeah, there are posts all over about the lack of available bigadv WUs for Windows SMP.

    B2K24
    BETA Team Member

    Posts : 102
    Join date : 2010-06-09

    Re: Can't seem to get a bigadv

    Post by B2K24 on Sat Jul 10, 2010 8:05 pm

    OK thanks for the confirmation. I'm assuming many people were lazy to set up a VM or run Linux is why their was always WU available few months ago.
    I guess many people on windows SMP with i7's requesting more than what Stanford can assign.

    Sponsored content

    Re: Can't seem to get a bigadv

    Post by Sponsored content


      Current date/time is Fri Nov 24, 2017 10:38 pm