SetiQueue question.

[Hellburner]

Due to the recent bandwidth problems I recently upgraded from a setiq .75e command line version to the 1.8a GUI version. I believe I have everything configured so it only connects in the middle of the night, that's when it actually uploads and downloads everything. The program, however, also initiates a connection every time results are received from a cruncher. It does not appear to actually ever use the connection, but I would prefer if it didn't initiate the connection in the first place. It's a Microsoft network, the queue is running on a win2000 box, the gateway is a win98se box using Microsoft ICS, all the crunchers are the CLI version. Anybody know how to stop the connection initiation?

My suspicions lead me to the server connection type, currently winsock direct as per the installation default, I don't know what the old commandline setiqueue used. But before possibly spending several days sorting this out I figured some of you early adopters might have the answer for me

 

[Confused]

I believe that it should only connect automatically when a client requests a WU, but there are no WUs in the queue, so the override comes into play, or possibly when the queue is not high enough

Give it a while to connect and fill up it's caches and see if it still does it. however, it shouldn't trigger a connection unless the queue is empty

BTW, take a look at "My Seti Help Page" in my sig, go to the SetiQ section, if that does not help, click on the link at the bottom of the section, it has all you need to know about almost every single part of SetiQ


Hope this helps


ConfusedBW

 

[Hellburner]

I've got it up and running with all queues filled, it's just the anomolous connections I want to kill.

 

[Smoke]

I think I understand what you are asking. If I do, then go to the Server Settings and UNCHECK "Override time for passthrough operations" and "Override time for empty queues". You should have a check mark next to "Manual connect". Right below that is where you would set the "Online Start Time" and the "Online End Time".

Is this what you are looking for?

 

[Hellburner]

I already have those disabled, and I believe the manual connect would disable the late night operations.

 

[Poof]

Have you checked through the Setiqueue log to see what might be triggering the spurious connects? Could help with a diagnosis...

 

[Smoke]

You're right on the manual connect...my bad there. But it is very strange indeed that it still attempts to passthrough with those "Overrides" unchecked. I just took another look and I don't know what else to recommend.

 

[Hellburner]

.
.
.
...wu completed
...wu given
.
.
.
No clues in the logs

looks like might be time to play with the connection protocols.

 

[Smoke]

I noticed that I'm using "WinINetDefault". Why don't you try that.

 

[Hellburner]

I just finished trying that one, ... still initiates a connection... now I'm trying wininet direct...

 

[Hellburner]

...That one didn't work either... ???

 

[Poof]

Well... there's one logical one left... "WinSockDirect", which is what I had to switch mine too after my Comcast went through its transition... I kept getting a series of weird "Invalid Server Response" errors until I changed that. Before the transition, it worked fine with "WinInetDefault".

 

[Hellburner]

Winsock direct is where I started from... Perhaps it's time to ask Ken...