• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DOH! Two times this week my (normally) rock solid .75e SetiQ crashed!

R

Robor

Elite Member
Maybe I jinxed it by bragging how stable my "old" SetiQ is? Maybe it's Win98SE's fault? I never reboot any of my boxes other than my primary machine and even then it's rare. Monday I came home from work and SetiWatch showed none of my clients running. I restarted SetiQ and started the client on all of my boxes. Everything looked fine. Today I came home and found the same thing only my SetiQ reported only 4WU/day average! That sucks. My home fleet does between 11-15 WU/day. I'll bet it crashed shortly after my restarting it Monday. Probably cost me between 25-30 WU's over that time and as we all know, they are not recoverable! 🙁

This time I restarted all of the boxes, then SetiQ, then the clients. I will be sure to monitor it more closely this time. Hopefully I haven't got a SetiQ problem.

Rob
 
Just go to the new SetiQ....
It comes ready to install as a service, has more stats and features than you can shake a stick at, a HTML interface from which you can configure it.....I could go on...

Honestly, you'll never look back..

🙂

Col
 
Robor
Either way I hope you sort your probs out ,maybe you could install SETIDriver on those remote clients with 1 days worth of WU's incase SETIQ dies again

ColinP
Whilst I have been tempted to use the new GUI version & have now passed 2 milestones in the old SETIQ (over 1yrs use & over 1000 WU's on my own Q 🙂) ,I still stick with the old 1 because the result log is much easier to read & I don't know how to put the new Q's log file into Excel properly!
 
Yeah Robor - you need to upgrade to 0.78b! 😉

Seriously though, I have both 0.78 and the beta4b (haven't downloaded the beta4c yet). I've been running the new one for about a week and a half and sure it has alot of fancy dancy graphics and html and stuff, but I still like my plain old text console, believe it or not. 😀

I'm currently giving this new one a shot for a period before I decide... 🙂
 
I think I'm running .78 on an NT Server at work. I'll jinx it now and say it's *never* crashed. If I do upgrade to the new client can I set it to accept connections on port 5512? I have no desire to go around and reconfigure my 43 work clients to port 5517.

Thanks!

Rob
 
🙂

Yeah I thought the same too.....
But you can set it to whatever port you like..... i.e. 5512.

There are loads of features like moving WUs between queues, moving overdue one's back into a queue... It also predicts when a WU should finish based on averages so it's an easy way to see if somebody has killed a client....

Only thing is, if you do upgrade, flush out your old queue first i.e. set it down to 1 day or something and flush all results.. Yu can't move them to the new queue..

cheers,

Col
 
Hmmm... It can run on port 5512 as a service and has more features? Looks like I'll be upgrading on my next EOM (end of month) work weekend. I'll probably upgrade my SetiQ at home tonight as a test.

Thanks for the help all! 🙂

Rob
 
It takes a bit of work, but it's actually not that difficult to move work from the old SetiQ to the new version...

First, set up the new Q to listen on a temporary port and set its proxy address to the address and port of the old Q. Then, have one client connect to the new Q and request work (or send a result). This will cause the new Q to set up a client and queue and will start downloading WU's from the old Q. It won't download very many, but once it has been configured, go into your SetiQueue/User.xxxxxxx/Q0001 directory and edit the QUEUE.INI file. There are two lines in that file for OverrideMin and OverrideMax. Set the Max line to whatever is left in the old Q, then restart the new Q program. Manually tell the new Q to connect (click File, Connect or Right-click anywhere on the skymap and click connect) and it will then download all remaining work from the old Q. Then, just disable the old Q program and change the new Q's port to the port the old Q was using and reset the address on the temporary client and your other clients will keep running as if nothing has changed.

Note: This procedure only works if all of your clients are running the same version of the SETI client, as the new Q creates different queues for different clients and separates the WU's accordingly. If you have different clients and OS's, then have one client of each type connect to the new Q before having it download all remaining work from the old system..

Edit: Missed one thing... Once you have finished setting things up, make sure you reset the new Q's proxy address to the actual Internet proxy address on your network (or set it to nothing-or OK's address-if you don't use a proxy to access the Internet...) 🙂
 
:| GRRRRRRRRRRRRRRR! :|

Came home today to find my old .75e SetiQ crashed again. I killed the entire directory, results.log, queued WU's, all of it. Downloaded the new SetiQ and got it running after a little plugging around. Seems to be working okay now. Hopefully this one stays stable. If not I'm going to have to look at the system as a problem.

Rob
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top