baskitcaise wrote:
[...]

Latest episode in the never ending saga for anyone still here :)

Have finished a unit on troubled machine, zipped it up, moved it to other
machine placed in cache and lo and behold it is sent, so it is something on
my machine that is stopping the uploads.

There must be a global lock file or something that is stopping all uploads
from any version of seti whether it is run by cli or ksetispy or Ksetiwatch
no matter where they are situated and no matter what version.

The odd thing I can`t seem to figure out is that it is communicating from the
machine as it connects and downloads new unit to fill the cache.

This has only started happening since the disk crash a few days ago at
Seti@home.

Anyone give me a clue?
 

Corrupt user_info.sah? (If so, copy your backup, or just delete it and relogin to the s@h servers.)

lock.sah file remains even when no s@h process? (If so delete it.)


If you wish to recover the WUs crunched with the corrupted user_info.sah details, then use the following details:

(From a quick check on newsnet sci.astro.seti and alt.sci.seti)

>>>>
I poked around on some archives. Here's what I found to clear up the problem:

1. I deleted the file user_info.sah.

2. I ran seti@home and re-entered my e-mail address. This puts proper data in the user_info.sah and then fails again with the "Unknown Fatal Error: 100"

3. The result.sah file had bad values for "id" and "key". These are the second and third fields in the result.sah. I got the proper values for these from my user_info.sah and corrected the fields in the result.sah.

4. I then started up seti@home again. The result was returned correctly and everything was happy.

Somehow, the user_info.sah gets corrupted and then it corrupts the result.sah with the wrong id and key. You just need to fix those twho things.

Hope they fix whatever is causing this.

--phil
>>>>


and for SETIDriver users:
>>>>
no, but I know how to fix it ;o)

first, copy the file "user_info.sah" from the SETIDriver root directory
into the directories with the "messed up" returns.
Then open the "user_info.sah" with wordpad and the "result.sah" in each
folder that has the "messed up" returns and replace the following info
result.sah                          user_info.sah
-----------                         -------------
user_id=0    with the number from   id=xxxxxxx
user_key=-1  with the number from   key=yyyyyyyy

and then just hit the [Transmit] button in SETIDriver

HTH

--
Robi
>>>>


Good luck,
Martin