Help!!

HotrodsunHotrodsun Salem, OR
edited October 2003 in Folding@Home
I need help I just keep get this error over and over again. I have try changing versions, changing flags, erasing everything and starting over. I can't seem to get it nailed down. I gone as far as testing every part of my system, and clean the dust out of everything. Does anyone have any Ideas? Thanks, Adam

__________________________________________________

[14:56:57] Sending work to server


[14:56:57] + Attempting to send results
[14:58:30] - Server reports digital signature does not match.
[14:58:30] (May be due to corruption during network transmission or a corrupted file.)
[14:58:30] - Error: Could not transmit unit 01 (completed October 22). Keeping unit in queue.


[14:58:30] + Attempting to send results
[14:59:27] - Server reports digital signature does not match.
[14:59:27] (May be due to corruption during network transmission or a corrupted file.)
[14:59:27] - Error: Could not transmit unit 01 (completed October 22). Keeping unit in queue.

[14:59:27] + Attempting to get work packet
[14:59:27] - Connecting to assignment server
[14:59:28] - Successful: assigned to (171.67.89.149).
[14:59:28] + News From Folding@Home: Welcome to Folding@Home
[14:59:28] Loaded queue successfully.
[14:59:30] + Closed connections

Comments

  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited October 2003
    Are you overclocking?
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited October 2003
    And, is there any chance the new system did not get its Machine ID Hash cleanly??? That might be the problem, the client might not have set up right. You have one work unit. Take the whole Work folder and back it up, and the FAHlog and FAHlog-Prev files.

    Then uninstall the whole F@H client and core installation, download a new client, use same F@H user ID and if this is a new box, a NEW machine ID like 3. Let it set itself up, then quit it and move back what you backed up adn see what happens. If the error reappears you have a corrupt wudata archive, but when I had this the UID Hash had gotten corrupted or I had told two boxes to use the same machine ID number-- THEN, the F@H server would take WUs for only one machine.

    If you are using the Windows GRAPHIC client let us know, we can find the config file that you can edit to tell the new box to use a different machine ID or tell you how to start|run the client with specific codes to force it to reconfigure itself maybe also. Sometimes, copying a client archive to another box can result in two boxes having the same machine user ID and then the servers can object on grounds that two boxes are using one machine ID and same UID and know it by timing of WU turnins.

    Each new box gets its own machine ID usually, and the combo of User ID and Machine ID are made into what is called a hash (hashing takes a string of text and numbers, runs them through something kinda like encryption-- can also be a BASE transaltion, like what Linux uses as Base64 or Base256 for security, essentially the thing you can understand is coded in a different number base system and each machine needs its own) but which is a unique code for each machine if one thinks in plain English. One of the instructions in for installing says to make sure to download a new client for each new machine and folks can get into trouble by copying the archives to multiple boxes if the boxes all try to call in WUs.

    Overclocking can do this also especially if RAM is overheating, having a virus stick junk in your download can (and F@H does not do that, but a virus on your box COULD possibly do this), and having RAM that is acting up or a RAM stick not seated right (just partly in socket all the way,maybe one end not down all the way) can do this, as can RAM that is physically malfunctioning or not matched in speed to other RAM in computer or not set right in BIOS or misdetected by BIOS and not set up except by BIOS(in this last case, could be not compatible with that particular box while not defective in and of itself-- wrong RAM for YOUR computer).

    Try the client stuff first, then try checking the RAM very thoroughly.

    John.
  • HotrodsunHotrodsun Salem, OR
    edited October 2003
    Nope, no overclocking. I am running the console version (dual cpu's). I erased everything and installed everything again, This is not a new system. The problem just started one day and I have not been able to figure it out. So my dual is just folding away making crap, not points. I'll try to install every thing again and see what happen. But I don't think it'll help, Adam
  • HotrodsunHotrodsun Salem, OR
    edited October 2003
    Well I just got done reinstalling everything, I guess well see how things go in a few hours or so. I'll keep you guys posted.
  • muddocktormuddocktor
    edited October 2003
    Adam, did you set up both console versions with different Machine ID's when you set the box up to fold? If you didn't, then that might be the problem, like Ageek said. You can check for this with EMIII. Open it up and highlight the instance you want to check and look in the config info box; it should tell you the Machine ID of each instance you highlight. If you have both instances set up with the same Machine ID, then you will need to change the second one to a different ID. Start up the second instance with the -config flag and then go through the config. Make sure you answer "yes" to the "change advanced options" question so that you can give that instance a different Machine ID than the first instance on that box.

    Hope this helps.:)
  • HotrodsunHotrodsun Salem, OR
    edited October 2003
    Ya, I did that. I set them to 1 and 2, So I know that is not the problem.
  • muddocktormuddocktor
    edited October 2003
    Man, that is a strange problem; I've never seen that one before in almost 2 years of folding.:hrm: Let us know how it turns out; if you are still having the problem you might want to post this over at the folding community forums. There might be someone passing through there that has run across this problem before.
  • mmonninmmonnin Centreville, VA
    edited October 2003
    Internet fine and everything? Firewall somewhere blocking connection?

    Have you tried coping Work folder, queue and log files to another computer and trying it there?
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited October 2003
    I'd run scandisk, just to be sure you don't have some file system shenanigans going on. A thorough HD integrity test might not be a bad idea, either.

    Are you using a download/upload manager? Some of them can ocassionally goof up and corrupt a file transmission.

    And as Ageek mentioned, a virus scan wouldn't be a bad idea, if your "testing every part of my system" didn't already include that.

    Good luck! :wave:
  • HotrodsunHotrodsun Salem, OR
    edited October 2003
    I tried the scan disk already, the drive doc test, I am just connection to the internet directly thru a router like the other four comupters. They don't have any problem getting and receiving WU's. Also I do virus scans weekly, all updated and scanned yesteday. I haven't copied the work folder to a different computer, but I guess I can since I erased everything already, Adam
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited October 2003
    Sounds like you've covered all the bases.

    Maybe somebody at Stanford in the support department could shed some light on the cause of the error.

    :confused:
  • Mt_GoatMt_Goat Head Cheezy Knob Pflugerville (north of Austin) Icrontian
    edited October 2003
    If it is just that the unit couldn't be sent it could be a server issue. BDR, myself and some others had this happen and it finally went. I had one that didn't send for over a day , lost track of how many attempts were made then when the next one finished it wouldn't go either. Right about 1/2 way through the third project from when this started the other 2 were successful and the ne xt one went when it completed. This happened to me 2 other times with only one unit each but theay all went eventually.
  • edcentricedcentric near Milwaukee, Wisconsin Icrontian
    edited October 2003
    Over the last week I have had a couple htat didn't return due to corruption. I am not sure of hte exact message, I was out and my wife was sending them. My guess is that it is realted to a specific work unit.
  • HotrodsunHotrodsun Salem, OR
    edited October 2003
    MTgoat I had like 8 wu's que'd up that had this problem, Also, I was wondering if someone could point me a link to the stanford site, so I can post this question there. Thanks, Adam
  • BDRBDR
    edited October 2003
    I ended up uninstalling F@H and reinstalling it on the one I was having problems with.
  • HotrodsunHotrodsun Salem, OR
    edited October 2003
    I did that twice already
  • BDRBDR
    edited October 2003
    http://forum.folding-community.org/index.php

    Maybe they can help.
  • mmonninmmonnin Centreville, VA
    edited October 2003
    There are only 9 spots in the queue. After that it dumps the WU in the queue and starts a new one. Start another client in a different folder before you lose all your work.
  • HotrodsunHotrodsun Salem, OR
    edited October 2003
    To late, I erased everything. Including the folder's I ran the clients from.:(
Sign In or Register to comment.