• 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.

setiqueue problems

K

Kris

Senior member
Can somebody give me a hand? I am trying to use setiQ to get WUs from setiQ.
Here is the data:
Small bnc network with a server, no internet connection.
Server has extra nic installed.
Laptop outside above network has internet connection.
SetiQ installed on laptop, filled with WUs.
Laptop disconnected from internet, rebooted and connected to server above using spare nic.
Server has setiQ.
Server has Driver (proxy 127.0.0.1)

When I get to the point where it wants an email address (driver I mean) it fails to find a connection and sits there, just looking, I presume.
In other words, when I enter my email, all activity ceases.

Any ideas?
Thanks, Kris
 
Zeruty gets credit for the idea.
In another thread this was suggested:



<< This is what I am thinking....
Set up a SetiQ on the laptop....
get it to download a whole bunch of wu's
also set up a SetiQ one of the one the machines from the network
set all the machines on the network to use the SetiQ machine as the proxy
so the setiq on the network will have tons of wu's and the other machines will feed from it. when you bring the laptop in each day, hook it to the network and have the network's setiq download and upload from the laptop
take the laptop to the network connection, and let it upload and download from berkeley or orange kid's setiq

I think this would work... but how to set up the setiq's....is something I dont know how to do so I can't help ya with it. someone else will step up to the plate, I'm sure. .... >>






Unfortunately, Zeruty was right there at the last, I can't figure that part out.
 
Didn't have time to read everything.

You need a client to send a WU in to the SETIQ to get an account setup on the SETIQ before it'll let you login on the client or DL any WUs.
 
When setting up SETI on non-Internet computers, I've found that using IsOs' service install (see Sukhoi's Help Thread for a link) worked, I didn't run into any of those problems. If you go that route, you can easily edit the SETIDr.cfg file that comes with it to use your own proxy rather than OK's, and you can stop it from running as a service by removing the registry modifications it makes after you've installed it.
 
Thanks for thinking about it Sukhoi and Darkmajiq.

Still can't get things working even after considering your advice and doing my best to apply it. Maybe more ideas will materialize, I am probably overlooking something. But it bothers me that 4ghz are just sitting there doing nothing because I can't outsmart the seti email requirement...

I'm inclined to start swearing...



edit...
I suppose I should mention that I did get the WU's to the server, I just can't get the IsOs install recommendation to work on the network machines.
I hate networking.
 
When you input your email in setidriver it needs to connect to the internet. I would do this on a machine that can connect to the internet and then copy it over to that machine. Or maybe I am reading the question wrong?
 


<< When you input your email in setidriver it needs to connect to the internet. >>



Yes, exactly the problem, which dm suggests the IsOs install can circumvent.



<< I would do this on a machine that can connect to the internet and then copy it over to that machine. >>



You may be onto something there. I think it's worth a shot. I will think about how to try it and let you know.
Thanks.
 
can you just copy over the user_info.sah file from another machine with seti cli and setidriver setup on? just copy over the user_info.sah and you shouldnt have to enter the email address... well at least I dont think you would have to. I am just going off of what I've heard from other people here....
 
From my experience with that I think the install by IsOs will work for that maybe. If it doesn't though you could try my idea and who knows may get lucky.
 
Lets see..you have two instances of SETIQ running. One on the laptop, one on the server. Then you have the SETI clients on the workstations.

First off, get some WUs into the SETIQ on the laptop. To do this you might just want to run the CLI with the -proxy switch. So go to a MS-DOS prompt and type "setiXXXXXX.exe -proxy 192.168.0.1:5517". Use the IP# of the laptop's NIC, and whatever port SETIQ is running at. This will allow you to get some WU DLed to your account on SETIQ on the laptop. Oh BTW, you need to send in a completed WU first to SETIQ before it will connect to SETI to DL more WU.

Now connect the laptop to the server. Do the same thing with the CLI on the server as you did for the laptop. Make sure in the SETIQ preferences on the server that you have the IP# and port of the laptop SETIQ as the proxy server for the server SETIQ. This should pull the WU off the laptop SETIQ and onto the server SETIQ.

Now go onto your workstations and install SETI Driver, using the server SETIQ's IP# and port as the proxy server in SETI Driver. 🙂
 
OK, here's how i would do it:

Install SetiQ on the laptop, and set it up to connect to OK or direct to Berkeley, and then run Seti with SetiDriver on the laptop. Set it for the first time to not use a proxy and connect directly to Berkeley. When it has downloaded the WU, set it to point to the SetiQ on the laptop, and let it finish crunching the WU. When it is finished, the SetiQ on the laptop will connect to the internet, and download some WUs.

Next, copy the entire Seti directory on the laptop, and place it on each of the computers on the other network. This will give a few duplicate results, but is by far the easiest way. When you copy these across make sure you set it up to use the SetiQ running on the computer with 2 NICs.

Leave the network connected to the laptop, then when a client completes a WU on the network, it will connect to the SetiQ on the 2 nic computer, which will in turn connect to the SetiQ on the laptop, and download WUs from there. If you set the Max. Queue depth to be 14 days on both, then you should not ever run out of WUs. Then, every week or so connect the LAN SetiQ to the laptop, then connect the laptop to the internet.

I hope this all makes sense, i have tried to set it out as simply as possible, and in the exact order i would do it. I have not tried this method, it is just off the top of my head using my knowledge of Seti and SetiQ.

Good luck 🙂

ConfusedBW
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top