SETIQ 3 beta2a unstable as service

[ColinP]

I haven't fully figured it out yet but I keep having to restart the service.
It's something to do with failed connections to it from clients but I don't know what....
Also, I'm having trouble with machines on different networks...
I have set the subnet mask in the Queue server settings to 0.0.0.0..
Some machines connect, some don't...

I'll update later if I figure anything out..

cheers,

Col

 

[Robor]

I'm not sure if it's the same version but rleach2 told me he had problems with the new SetiQ on his Win98SE machine. It kept hogging all his system resources. His system was reacting very slowly and when he looked at system resources it was in the low 20's. I'm still using the old SetiQ myself. It's working fine after the host file change.

Rob

 

[Poof]

I'm with Robor... In my case, I never got chance to install and try the new setiqueue, so the old one is still up and running and cranking just fine, after having done the hosts file work-around.

A couple of buddies of mine are having troubles with the new setiqueue on ME. Whenever a machine connects to it with a result, they say the icon disappears and the queue crashes... After alot of frustration, they're trying to get their old queues back up again...

I'm not expecting perfection out of the new setiqueue at this point, but it's a shame that Ken decided to re-write the whole thing right before the cutover...

 

[artemedes]

Yep, I am having similar problems. Updated to the newest version of SetiQ on friday and it crashed sunday morning. I wasnt' able to get it restarted until just a few minutes ago since it is on my work machine. It transfereed about 10 WU before correctly before shutting down. I may rely on only berkeley servers until this gets developed a little more.

 

[artemedes]

Just thought I would provide some info. Maybe we can find some consistency with the problem.

Setiq is running on a win98se box and is not running as a service, just boots as an icon in the startup folder. I also have the subnet at 0.0.0.0.0. I thought this would make it easier for my clients at home to connect to this computer at work.

before i loaded beta 2 I would get an error when trying to browse clients from the same machine as the setiq, but works fine from others. Http server is set to any IP.

Can't think of anything else that might be important.

 

[Fardringle]

It looks like this problem may somehow be related to setting the IP mask to 0.0.0.0. My work Q used to crash quite frequently until version 1h, but it hasn't crashed once since then with the IP mask set to match that of our local network..

 

[ColinP]

Then of course, all the machines on other networks won't connect !!!!!



Col

 

[JWMiddleton]

I had Beta2a running this weekend at work. This morning I returned to find SetiDriver on my machine without a WU. Transmit was up and asking for my Email ID. I typed it in and nothing happened. Then I noticed the SetiQ Icon in the Systray disappear. I stopped SetiDriver, restarted SetiQ and SetiDriver then all worked well. According to SetiSpy the last WU was about 10:00 PM Sat. Lost 1 1/2 days. Guess I have to load up SetiDriver until this is resolved.

 

[Assimilator1]

Have any of you tried Beta2b?

BTW I'm still sticking with the old SETIQ for now ,though my 2nd in comm seems quite happy with the new version ,he seemed to think it was more stable than the old 1!

 

[JWMiddleton]

Assim1: Beta2b is not available for download yet. He ofter puts info in the History Page as he build the new version, then it shows up in the Download section when complete.

 

[ColinP]

I have tried running the old SetiQ (0.78b) but I just get "server returned error -1".
I've put the host file patch in and can ping shserver.ssl.berkeley.edu and shserver2.ssl.berkeley.edu from the SetiQ box, both resolve to 128.32.18.166.
I still have a number of clients running 3.0, unfortunately, I don't have direct acces to them and have to rely on a friend to upgrade, and he's very busy....
I don't know if the mix of clients is causing the problem.

I'm also using port 5512 on the new SetiQ as this was easier than changing all of the clients.

Another problem is that it won't download more than 1 WU per queue even though the individual queues all believe they should have anything up to 150 WUs in them...



Col

 

[Rattledagger]

ColinP, if you're using 3.01 or older clients, you can get error message then connecting. Except for a couple of clients that aren't released yet, all results returned with old clients is discarded and no credit given. You can see if there's an error-message in user_info.txt for this.

Setiq doesn't download any wu if the last client connected to setiq isn't 3.03 or later. If get_work_unit.txt and lookup_user_name.txt has 3/3 as version, you should have been able to connect, but remember the servers had an outage today.

As for running as service, you must install with setiqueue.exe -i. Putting the new setiq in the same directory as 0.78b and keep running as old service doesn't work.

Hope some of this is useful...

Hey Assimilator1, no you won't get my results

 

[Assimilator1]

Hi
What results?

 

[ColinP]

Hi Rattledagger,

thanks for your reply, unfortunatley, I've already done everything you said !!!!!

I don't get much time for SETI these days with my new job...
I'll try the latest release see how it goes...

cheers,

Col