"Martin G. Diehl" wrote:

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>

Checking in on Sunday night I had several clients showing a blank
where my user name should be, and zero CPU time and WUs completed. (I
don't use SQ or any other add-ons.) They were running fine -- no
"fatal errors" or the like -- but clearly there was something wrong
with the user info. I just used "Change/Create Login" to reenter my
address-of-record and the information was restored. I don't know what
may have happened to any WUs completed before I arrived ... at any
rate, the only explanation I could think of was that it was something
to do with the time change: all the affected systems had made the
switch automatically, while all the systems that needed their clocks
to be adjusted manually were unaffected.

-- 
Odysseus 14# @ 33Y