• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Lot's of Corrupt SETI WU's Lately

B

BadThad

Lifer
I've been doing SETI for over 4 years and have never seen this. Almost every one of my PC's running driver and 3.03CLI has had a corrupt wu that won't transmit over the past 3 weeks. Today the CLI showed me an error I've never seen before (didn't see this with the others):

"Corrupt user ID. Please exit SETI@home, delete user_info.sah and result.sah and restart SETI@home. This problem results from a server side error that has been fixed."

With the other corruptions, SETI simply wouldn't transmit the result nor receive new work. Simply deleting the contents of the corrupted folder fixes the problem...but it sucks, lol.
 
There is a way to SAVE the completed WUs.

Use the SEARCH function and look in your Seti Folder for "user_info.sah".

You should get a result of one file for each of your cached WUs (both crunched/not transmitted and un-crunched/waiting to be worked on) plus one that resides in the root directory of your S@H Folder.

The one in the root should be fine. Look at it and notice the number in the "id=" and the number in the "key=" areas.

Now look at the other "user_info.sah" files and see if you find any that don't have lines that match those numbers. If you find any ... those are "defective".

To fix the "defective WUs":

1. Shut down SETI so you can do the following.

2. Copy the good "user_info.sah" file (the one in the root of your Seti Folder) and paste it to the folder of the defective WU(s).

3. Use WordPad and open the good "user_info.sah" file and notice the numbers in the 2nd and 3rd lines (id= and key=).

4. If you have found a completed WU that is defective, you should have a "result.sah" file (I think WUs that have not been crunched have a "result_header.sah"). Open the RESULT.SAH file in the defective WU. Replace the "-1" in the user_id= with the proper number AND replace the "0" in the user_key= with the proper number.

5. Restart SETI and everything should be good to go.

Remember each Seti installation can have one or more of these "defective WUs" so just because you found one does not mean you have completely fixed the situation.
 
I think I found a better way to find the defective WUs. During the write-up of my last post I realized that we really only need to search for:
"defective WUs that are completed". :Q

So just do a search of your SETI FOLDER for result.sah files. That should shorten your search considerably. 🙂
 
Now you tell me, hehehehe. I tossed about 10 wu's because of this. 🙁

Thanks Smokey, I'll give that a try next time I see it.
 
Hey, we need every last WU we can get.

You say you tossed them out but they are probably still in your RECYCLE BIN. Restore them and fix them. 🙂
 
Man, I've gotten some REALLY tough wu's on ALL my herd the week or so...my numbers are down because of long wu's. How the hell did you get sweet wu's?

Do some of you guys "cheat" by deleting the tough wu's out of your caches? 🙁
 
Deleting "tough" wu?
Well, for me, the wu taking longest time to crunch is "normal" wu, so starting to delete all wu between around 0.2 & 1 or something isn't advisable... 😉
 
Originally posted by: badthad
Man, I've gotten some REALLY tough wu's on ALL my herd the week or so...my numbers are down because of long wu's. How the hell did you get sweet wu's?

Do some of you guys "cheat" by deleting the tough wu's out of your caches? 🙁
Click to expand...

I took a quick look. The last time a had a WU with an AR less than 0.400 was Oct. 14th. Though i haven't been getting too many "sweet" ones either in that time. Most are between 0.426 & 0.950.
Last night though i had 5 WU's in a row that had too much RFI & processed inside of 4 minutes.

There is a setting in SETI Q to look for sweet WU's.

I don't bother deleting WU's . I crunch what i get.
 
I've also been seeing an abnormal number of wu's with HUGE peaks. Anyone else notice that? Perhaps they're re-evaluating some of the stronger signals??
 
If these are completed work units you don't want to lose exit setidrive and move them into another folder. Then start setidriver back up and set your cashe again and click the tranmit button. You will have to chose option #2 and enter the email address you are using for seti. It will then download new work units with your correct info. You can then use that info to change the bad info in your completed work units. To tranmit them after you fix them up the size of your cashe by ten and exit setidriver. Change the name of each folder to the same as the ten empty folder setidriver just made and paste and cut the ten completed work units into the ten empty folders overwriting when asked . Restart setidriver and you should have 10 completed work units to tranmit.

If they're not completed work units just delete them all and start over.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top