SETI - Duplicates - HELP!

[OhioDude]

Starting at around 3:00 PM yesterday, every single result SetiQueue sends to Berkeley is being rejected as a duplicate... 😕

Anybody else having similar problems?

 

[Unforgiven]

my queue is uploading just fine over the past 24 hours. is this only from 1 client in particular or many?

 

[OhioDude]

Every client's wu's are rejected by Berkeley as a dupe.

😕

 

[amdxborg]

Mine is working fine as well...maybe you should rename the folder with queued wu, and create new one so you can download some fresh wu.

Oh have you restarted the queue yet?

 

[Smoke]

George,

I've seen no such problem.

Question: Do the WUs have different Seti Names?

How many machines are submitting the WUs?

 

[OhioDude]

Something is hosed in SetiQueue. Everytime I try to browse to 127.0.0.1:5517, SQ crashes.

I think I'm going to wipe out all my queue folders and reinstall SetiQueue. 🙁

 

[Smoke]

You should save the completed WUs for they probably are all right.

Paste them back in once you get your Q running properly again. 😉

 

[Dalephi]

I have had the same problem with SetiQueue in the past. The only way I could fix it was to delete SetiQueue and then reinstall. There may have been a way to fix it, but it was beyond my knowledge.

When my queue did that I did not show any duplicates though.

 

[Assimilator1]

Originally posted by: OhioDude
Something is hosed in SetiQueue. Everytime I try to browse to 127.0.0.1:5517, SQ crashes.

🙁

I've had that when .ini files get corrupted or wiped.
Go to SETIQ window,settings,Queue settings & check to see if your normal sub Qs are there along with the corect SETI version No.

I've noticed that if your PC gets a forced shutdown that SETIQ in particular is vunerable to files getting corrupted ,especially with Win2k &amp; XP:roll:,&amp; often its the crucial .ini files for clients &amp; sub queues(<--- spelling Smoke?😉).

Best thing to do in the future is to make backup copies of boot.ini &amp; SetiQ.ini in the SetiQueue dir ,client.ini in the Client dir,the user.ini's, &amp; the Queue.ini's in the Q0001 etc dirs.
I don't bother with each client ini within the Q0001 (etc) dir as that would take too long😛
Just create the backup ini's within their original place ,they don't seem to get effected by power offs.