SETI: Queue Whoes: Edit, Fixed

[paf077]

Hi All,
Has anyone else been having porblems with SetiQ?:disgust:

Mine has reset about 4 times in the last month, (no more users or clients until
new results are sent) and now nothing connects.
Always get errno2?
nothing connected for the last 12 hours!:|

I can't even connect from my own lan.
Anybody want to try to get to it? paf077.dns2go.com:5517

Thanks, if this doesn't work I'm taking it down!!!!


Paf

 

[Slaughter]

It prolly seems to reset 4 times last month becuase you have "Keep logs for" set for 7 days. I have mine set for 365 for good ol yearly logs...now I just need to have the queue up for that long.

 

[Smoke]

Got to your Q just fine using this link

The length of time that you keep logs has nothing to do with the Q resetting itself. The Q should NOT reset itself unless the computer upon which it resides is having problems. Is your Q machine "stable" or is it OCed to the hilt?

 

[JWMiddleton]

paf077, Mine reset itself on 7/1/02, after an "unscheduled" system reboot. I can only assume that a file got corrupted. I noticed it a few hours later and was horrified cause the counters all went back to zero!:Q I shutdownt the queue and copied some of the files from the new one to the corrupted one and got most stuff back. My stats on the SetiQueue web site stopped as of 7/1/02.

 

[Smoke]

I had problems when I tired setting up my Q on my first and only "Dualie", 2X PIII 1.00 GHz (Smoke #2 on the TeAm Smokeball SetiQueue) on an Acorp board. I started getting NEW Qs installed?

I only had one SETI Account at that time ... "TeAM Smokeball" which was setup as Q0001. I thought things were really running smoothly when I noticed that TS was not advancing in the Top 100 of SetiQueue Users like it had been doing? I never bothered looking at the Qs Page in SetiQueue because there was only one Q0001 and what would be the point ... right? Well, I found there were now Q0001, Q0002, and Q0003! :Q

And all of the Qxxxx were TeAm Smokeball? It appeared that each new Q was starting over and CLIENTS were being moved from the previous Qxxxxs when they returned WUs? I was completely confused and I could not find help on this anywhere.

In an attempt to get all my stuff back together in "one" Qxxxx I started copying and pasting and ended up getting things completely "knockered".

I ended up installing SetiQueue on another computer and the problem stopped.

It turned out, un-beknown to me, that the "Dualie" was rebooting itself from time to time. This "Dualie" is in my workshop, where it is not under my direct observation. When I would check SetiWatch I would find that it was working just fine like all of my other computers. What was going on is that the "case fan" on the front (the computers in my workshop are all facing the wall with their backsides facing out for easy access) had crapped out and the system was getting overheated. I had set the BIOS to "startup after a power loss" so the computer would not just shutdown but would reboot itself... over and over again.

Anyway, this shutting down due to overheating must have corrupted one or more of the SetiQueue files. I remember having to reset the password each time a new Q was created but I was not sure what that was all about, even to this day, but definitely something was corrupted.

Therefore, I recommend whenever you get a strange SetiQueue shutdown, check all of your fans and make sure your computer is not getting overheated.

 

[paf077]

Thanks guys, but i finally got it sorted out! It seems the new detonator drivers messed up the registry and setiQ.
I ghosted back to Dec 31th and everything worked fine. updated the vid card with the same drivers and guess what??
Same problem. so I reghosted and I'll keep the o;d drivers for now. :frown:


Paf