Thunderstorm has caused SetiQueue to create a second Q?

[Smoke]

I had a bad thunderstorm cause a momentary power outage last night. You might know the only machine not on a UPS was my SetiQueue server.

It looks like the same thing that happened about a month or two ago has happened again.

The computer is set to start up after a power loss but on the boot up there was a screen telling me that my SetiQueue didn?t have an e-mail address. Sure enough it appeared the SetiQueue had lost some of its settings. I put my e-mail address in and then noticed it didn?t have the SETI NAME so I put that in. It looked like everything was all right so I just let it go.

This morning I woke up and looked at the CLIENTS and only noticed about half of them showing up? Upon further inspection it appears I now have a second Q: Q0002 in addition to the one I had: Q0001. This is what happened about two months ago that ended up with me losing my Q and eventually having to buy a new router. Now the router never shut down because it is on a UPS. And it appears to be OK.

I looked into the LOGS and saw that after the 9:05 PM power outage the SetiQueue just created Q0002 and started putting CLIENTS in there as they sent in completed WUs. It seems to be doing all of this without any intervention on my part. Q0001 and Q0002 are identical. I can?t move WUs between them with the built in functions of SetiQueue. It is sort of like the two Qs are linked.

I screwed around with the different files last time and eventually screwed the whole SetiQueue up. So this time I?m going to just leave it alone and let it do whatever it wants to do. It seems that CLIENTS are sending in WUs and getting new replacements. There are two things that don?t seem right but I?m not sure what to do about them.

1. The large amount of cached WUs in Q1 does not seem to be getting used by the CLIENTS as they send in completed WUS. They get their replacement WUs from the newly created Q0002.
2. I don?t like the idea that now I have two Qs instead of one. Sort of an aesthetics thing I guess but it is just not neat.

Have you ever heard of anything like this? And what should I do if anything?

 

[IJump]

I had something very similar happen. I had most of my setiqueue.ini file wiped out. I am pretty sure I was able to transfer all of the WUs from the old queue to the new one. Then I think I disabled the old queues after I was sure the weren't being used.

At thios point, I only have the active queues (Three of them are Q0002, but they work.)

I let all of my clients cycle through for a few days in the new queue before I did all of that though.

 

[Smoke]

Well, that's my plan for the moment. Just wait it out for a few days before I try to "fix" anything.

 

[networkman]

Hmm.. maybe this has something to with 1.21 Gigawatts!? :Q

 

[Engineer]

Greg,

I've had that happen twice....went to look at the Queue several times in the past and all the settings were gone. Not sure what caused it, but it was a pain to set all the names, etc. back up. Would be nice to know what it was and if there is a recovery....

 

[Assimilator1]

Wierd ,how about saving the SETIQ.ini to another HDD for any future problems?

 

[Smoke]

That's probably a good idea, Ass1. When things get back to normal (if they do) I will do that.

 

[Confused]

Originally posted by: networkman
Hmm.. maybe this has something to with 1.21 Gigawatts!? :Q

I love those films!

Greg, you're computer must have been doing 88mph and it went back in time to a time when there were no settings

 

[Smoke]

Einstein, huh? That might be the case but there just seems to be something wrong with that theory. There has got to be something faster than light ... Warp 2, Warp 3, ...

 

[networkman]

186,000 miles per second - it's not just a good idea, it's the law!

 

[muttley]

thats really still below the speed of light.

186287.490 miles per second but this has to be in a vacuum
299,792,458 m/s meters per second

speeds are slower in other medium air is almost the same as vacuum.

does this count as a neff???