Help Please, SM12 Cant Connect To The Work Server

JimboraeJimborae Newbury, Berks, UK New
edited October 2006 in Folding@Home
SM12 hasn't been able to connect to the work server to download anything for a couple of days now. Anybody got any ideas??? And yes she does have a working internet connection.

Cheers

Jim

Comments

  • edited October 2006
    Can you post a snippet of the log for us, Jim?

    BTW, if you have it configured to do timeless wu work, that is the problem. Stanford isn't sending out any timeless work any more, so if you have it configured for timeless it just won't get any work. :) Just reset it it for folding only or no-preference.
  • JimboraeJimborae Newbury, Berks, UK New
    edited October 2006
    muddocktor wrote:
    Can you post a snippet of the log for us, Jim?

    BTW, if you have it configured to do timeless wu work, that is the problem. Stanford isn't sending out any timeless work any more, so if you have it configured for timeless it just won't get any work. :) Just reset it it for folding only or no-preference.


    Hi Mud, that could just well be it, I'll check now....Nope don't think that was the problem.

    I'll post the log when I get home from work tonight, thanks


    Jim
  • edited October 2006
    OK, sounds good, Jim. Post a logfile snippet and also it wouldn't hurt to post a screenie of the config opened in wordpad too. :)
  • JimboraeJimborae Newbury, Berks, UK New
    edited October 2006
    Right here's the relevant part of the log file.

    [02:10:41] Finished Work Unit:
    [02:10:41] - Reading up to 13848 from "work/wudata_02.arc": Read 13848
    [02:10:41] - Reading up to 2234904 from "work/wudata_02.xtc": Read 2234904
    [02:10:41] goefile size: 0
    [02:10:41] logfile size: 577798
    [02:10:41] Leaving Run
    [02:10:44] - Writing 3452870 bytes of core data to disk...
    [02:10:47] Done: 3452358 -> 2561922 (compressed to 74.2 percent)
    [02:10:47] ... Done.
    [02:10:47] - Shutting down core
    [02:10:47]
    [02:10:47] Folding@home Core Shutdown: FINISHED_UNIT
    [02:10:51] CoreStatus = 64 (100)
    [02:10:51] Sending work to server


    [02:10:51] + Attempting to send results
    [02:39:21] Couldn't send HTTP request to server (wininet)
    [02:39:21] + Could not connect to Work Server (results)
    [02:39:21] (171.65.103.160:8080)
    [02:39:21] - Error: Could not transmit unit 02 (completed October 14) to work server.
    [02:39:21] Keeping unit 02 in queue.


    [02:39:21] + Attempting to send results
    [02:56:11] + Results successfully sent
    [02:56:11] Thank you for your contribution to Folding@Home.
    [02:56:11] + Number of Units Completed: 81

    [02:56:11] - Preparing to get new work unit...
    [02:56:11] + Attempting to get work packet
    [02:56:11] - Connecting to assignment server
    [02:56:11] - Successful: assigned to (171.65.103.158).
    [02:56:11] + News From Folding@Home: Welcome to Folding@Home
    [02:56:12] Loaded queue successfully.
    [03:56:16] Couldn't send HTTP request to server (wininet)
    [03:56:16] + Could not connect to Work Server
    [03:56:16] - Error: Attempt #1 to get work failed, and no other work to do.
    Waiting before retry.
    [03:56:31] + Attempting to get work packet
    [03:56:31] - Connecting to assignment server
    [03:56:35] - Successful: assigned to (171.65.103.158).
    [03:56:35] + News From Folding@Home: Welcome to Folding@Home
    [03:56:35] Loaded queue successfully.
    [04:57:11] + Could not get Work unit data from Work Server
    [04:57:11] - Error: Attempt #2 to get work failed, and no other work to do.
    Waiting before retry.
    [04:57:35] + Attempting to get work packet
    [04:57:35] - Connecting to assignment server
    [04:58:01] Couldn't send HTTP request to server (wininet)
    [04:58:01] + Could not connect to Assignment Server
    [05:02:04] - Successful: assigned to (171.65.103.158).
    [05:02:04] + News From Folding@Home: Welcome to Folding@Home
    [05:02:04] Loaded queue successfully.
    [06:02:04] Couldn't send HTTP request to server (wininet)
    [06:02:04] + Could not connect to Work Server
    [06:02:04] - Error: Attempt #3 to get work failed, and no other work to do.
    Waiting before retry.
    [06:02:32] + Attempting to get work packet
    [06:02:32] - Connecting to assignment server
    [07:02:38] Couldn't send HTTP request to server (wininet)
    [07:02:38] + Could not connect to Assignment Server
    [07:02:54] - Successful: assigned to (171.65.103.158).
    [07:02:54] + News From Folding@Home: Welcome to Folding@Home
    [07:02:54] Loaded queue successfully.
    [08:02:55] Couldn't send HTTP request to server (wininet)
    [08:02:55] + Could not connect to Work Server
    [08:02:55] - Error: Attempt #4 to get work failed, and no other work to do.
    Waiting before retry.
    [08:03:43] + Attempting to get work packet
    [08:03:43] - Connecting to assignment server
    [08:05:17] - Successful: assigned to (171.65.103.158).
    [08:05:17] + News From Folding@Home: Welcome to Folding@Home
    [08:05:17] Loaded queue successfully.
    [09:06:03] + Could not get Work unit data from Work Server
    [09:06:03] - Error: Attempt #5 to get work failed, and no other work to do.
    Waiting before retry.
    [09:07:33] + Attempting to get work packet
    [09:07:33] - Connecting to assignment server

    Folding@Home Client Shutdown.
  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited October 2006
    Completely wipe your F@H install and install it from scratch - especially make sure your client.cfg is wiped out. This is the timeless WU problem. Make sure you use all default options (except you can still use bigpackets if you have more than 512mb of ram in SM12) and it should work.
  • JimboraeJimborae Newbury, Berks, UK New
    edited October 2006
    Hmmm F@H seems to know that you're on case Prime as it's just managed to download a WU and SM12 is now crunching again. Wierd :smokin: :vimp:

    Think I'll keep a close eye on her for the next week to check it doesn't go screwy again.

    Cheers guys.

    Jim
  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited October 2006
    :thumbsup: another one back on the boards! :D thanks, Jimbo!
  • edited October 2006
    Actually, the server that it was trying to get work from was a regualr work server and not a timeless server. The timeless servers were 112, 120 adn 133, if I remember right.

    One thing I've seen is that the setting for using IE settings can fubar stuff. If you aren't connecting then either check or uncheck the box for it in that gui client, then restart the client, Jim.
Sign In or Register to comment.