Smoke
Distributed Computing Elite Member
Ack, it appears my SetiQueue Server must have done a ?shutdown?, ?reboot? on its own and the TeAm Smokeball SetiQueue has gotten messed up.
I remember this happening once before. Do any of you ?Q? operators remember having anything like this happen to you?
Upon rebooting, it seems the Q loses its email address and creates a ?New Q?. Unlike the last time when I immediately went into the inner workings of SetiQueue trying to fix it without knowing what was wrong, this time I just filled in the missing ?Seti Email Address? and let it run. Upon receiving a WU from a Client it seems to move them to the new Q and remove them from the old Q. It looks like all I have to do is wait for all of the Clients to send in WUs and the Q should heal itself. Fingers crossed. :Q
The heart of the matter is ?Mr. Steady? (the dual CPU Q server) may have a stability problem. If this happens once more, I?ll have to move the Q to another computer and rename ?Smoke #2? to something more appropriate. 😛 This last time this happened I lost a Supermicro SSA-370 motherboard. :|
I remember this happening once before. Do any of you ?Q? operators remember having anything like this happen to you?
Upon rebooting, it seems the Q loses its email address and creates a ?New Q?. Unlike the last time when I immediately went into the inner workings of SetiQueue trying to fix it without knowing what was wrong, this time I just filled in the missing ?Seti Email Address? and let it run. Upon receiving a WU from a Client it seems to move them to the new Q and remove them from the old Q. It looks like all I have to do is wait for all of the Clients to send in WUs and the Q should heal itself. Fingers crossed. :Q
The heart of the matter is ?Mr. Steady? (the dual CPU Q server) may have a stability problem. If this happens once more, I?ll have to move the Q to another computer and rename ?Smoke #2? to something more appropriate. 😛 This last time this happened I lost a Supermicro SSA-370 motherboard. :|
