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> 

-- 
Martin G. Diehl

Reality -- That which remains after you stop thinking 
about it.  

All replies and comments accepted and considered.  
Adoption of your suggestions are at my sole discretion.  
Award criteria are unpublished and are considered to 
be a trade secret.  As such, awards for your responses 
cannot be guaranteed.  Incoming flames may be stored 
for use during severe winters or may be circulated for 
deep analysis, peer review, and/or literary criticism.