Results 1 to 40 of 56

Thread: Report Primes from the 1st Drive K=3401-3999 Port 7771 {Closed}

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Ancient Haggis Hound Angus's Avatar
    Join Date
    Jan 2002
    Location
    Seattle/Norfolk Island
    Posts
    828
    That's real odd. I stopped one of the clients, edited the config file from port 7773 to 7771, saved the file and restarted the client sometime over the weekend.

    It's the same client that was working up to that point on the other port. I'll try a different port when I get near the box again in a few hours.

    I have two copies of the client running on a dual core box, each client from it's own folder.

    Edit: I changed the offending client to 7772 and it's working fine.

    Quote Originally Posted by PCZ View Post
    Angus
    Enter the prime you found at the top 5000 site.

    We will try to work out why your client is behaving strangely.

    PS
    In the mean time please check the time and date on the PC.

    The server handed out that test to you today and still thinks it is in progress.
    Recognized Angus when you get work but not when you return it most odd.

    There is a 24hr deadline but you didn't exceed that
    Gut feeling at the moment is a corrupt client.
    Last edited by Angus; 09-22-2009 at 10:46 PM.

  2. #2
    Administrator PCZ's Avatar
    Join Date
    Jun 2003
    Location
    Chertsey Surrey UK
    Posts
    2,428
    Angus

    I see you in the stats on port 7771 is it working now ?

  3. #3
    Ancient Haggis Hound Angus's Avatar
    Join Date
    Jan 2002
    Location
    Seattle/Norfolk Island
    Posts
    828
    Yes, it's working now.

    I think I figured out it's some weird interaction with the llrnet-remote GUI window. I didn't close the window when I originally switched to 7771, just killed and restarted the client. It must have some sort of cached connection settings for the upload (downloads worked OK).

  4. #4
    Quote Originally Posted by Angus View Post
    Yes, it's working now.

    I think I figured out it's some weird interaction with the llrnet-remote GUI window. I didn't close the window when I originally switched to 7771, just killed and restarted the client. It must have some sort of cached connection settings for the upload (downloads worked OK).

    I think Shish has a similar problem, he has a boatload of rejected results coming in on the 7773 server.
    -:Beyond:-


  5. #5
    Administrator PCZ's Avatar
    Join Date
    Jun 2003
    Location
    Chertsey Surrey UK
    Posts
    2,428
    3743*2^495958-1

  6. #6
    Administrator AMDave's Avatar
    Join Date
    Sep 2004
    Location
    deep in a while-loop
    Posts
    1,948
    You cannot simply switch between ports without 'running down' the cache.

    If you have work from port-A in the cache and switch to port-B then port-B will reject the port-A work.

    To switch from 1 port to another you should run down the cache first.

    WUCacheSize in the client config file will set how many workunits the client will download at a time.

    When you want to empty the cache, edit the cache size to 1.
    Stop and restart the client so that it registers the new setting.
    Keep tabs on the number of lines in the file workfile.txt.
    When it gets down to 2 lines, remove the '-- ' comment mark from in front of the 'once=1'
    then stop and restart the client and it will complete the last workunit and shut down.
    Then re-insert the '--' comment mark in front of the 'once=1' (or it will only do 1 wu when you restart)
    Then change your port number and restart the client.

    This will avoid errors and ensure that you get all the credit for your hard work.
    . . . . . ___
    . . . . . . .\___/\______
    . . . . . . . \__AMD___\\__
    -----------------------------------------

  7. #7
    Ancient Haggis Hound Angus's Avatar
    Join Date
    Jan 2002
    Location
    Seattle/Norfolk Island
    Posts
    828
    I only have a cache of 4. I expected it to reject those (soimetimes I don't remember to empty the cache), but then the ones it pulled from the new port were all being rejected - a couple of days worth.

    I expect it was still trying to send them to the old port for some reason.

    Quote Originally Posted by AMDave View Post
    You cannot simply switch between ports without 'running down' the cache.

    If you have work from port-A in the cache and switch to port-B then port-B will reject the port-A work.

    To switch from 1 port to another you should run down the cache first.

    WUCacheSize in the client config file will set how many workunits the client will download at a time.

    When you want to empty the cache, edit the cache size to 1.
    Stop and restart the client so that it registers the new setting.
    Keep tabs on the number of lines in the file workfile.txt.
    When it gets down to 2 lines, remove the '-- ' comment mark from in front of the 'once=1'
    then stop and restart the client and it will complete the last workunit and shut down.
    Then re-insert the '--' comment mark in front of the 'once=1' (or it will only do 1 wu when you restart)
    Then change your port number and restart the client.

    This will avoid errors and ensure that you get all the credit for your hard work.

  8. #8
    3481*2^495859-1
    -:Beyond:-


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •