Martin G. Diehl wrote:

Alex Smariga wrote:

I've been running SetiQueue (latest version) for a couple of months without any problem.  Over the past 24 hours, about 1/2 of my machines are acting funny.  They were in the queue, but not working on legit workunits.  In looking further, I find that their user-info.sah files are blank, or at least have no legit data.

To get them back operaional, I had to delete all the sah files, and then they are back using setiqueue, etc.  Had to lose the current result, but they are back online.

Any idea what is happening?

Alex

--

You read my mind! 
I was just about to submit a question about the same problem. 
This is what I saw. 
The user_info.sah file did not have a good value im the "id=" line.  That caused SETIqueue to create a bogus queue for each instance of a corrupted user_info.sah. So far 3 PCs (out of 14) have been affected.  AFIK, no work units were being processed under the corrupted user_info.sah files. 
I copied a good version of the user_info.sah file to replace the corrupted one in the SETI directory of each of the affected PC's.  I also restarted each affected client PC's.  SETIqueue served a new WU and then about 30 minutes later, deleted the bogus queues. 
Does anyone want to think this was caused by the change back to standard time from daylight savings time?  <g>

That's an interesting theory - but might just be good - I saw one of my machines take a nose dive, a Linux box.  But just restarted the SETI client.  It continued fine, but with a uid of -1 !!??

Hmm, Oh well, time to delete that uid file I think...

Cheers for pointing it out, has anyone seen it without SQ?

John