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

SETI Queue help needed

Jeff7

Jeff7

Lifer
Someone suggested that I try SETI Queue, so I did; 45 minutes later, I still can't figure out how the thing is supposed to work. When the client tries to connect to the SETI Queue server, it says "gethostbyname: No such file or directory."
When I do Browse->Clients, it sees no clients. The File->Connect option is also greyed out. I have followed the online instructions, but it will not work.
 
Have your clients already been initialized (d/l a wu from seti@home)? When I first setup SQ, it took 3 days for one of my machines to hook up and be recognized by SQ, because the first wu a client processes must be d/l directly from the berkeley servers. Once that happens, point SD to your SQ proxy, and all should be good. With all the bandwidth cap probs at berkeley right now, it can take some time.
 
This is on my main PC running the GUI client. I just now finished a WU direct from Berkeley. I directed the client to use a proxy server at 192.168.0.100:5517 which is what SetiQueue is configured as. The client says "Cannot connect to server." It's the same stuff as what was happening in the previous description.
 
My GUI seti client just finished another WU from Berkeley, and I directed it's proxy to 192.168.0.100:5517, which is what SETI Queue is set to listen for. The client still says it can't connect to the server, and SETIQueue's browse options still show no clients.
 
Are the client and the queue on the same machine? If so, try changing the queue to "localhost:5517".
 
Yes. What do you mean set the queue to that? Do you mean to configure SETIQueue to do that? If so, how do I do that? It asks only for an IP address and not a name.

And yes, they are both on the same system.
 
Yes, that did it! I set the Queue and the client to look at port 80, and the client for localhost. It downloaded through the proxy. Thanks for that advice; it works!😀
 
Sorry I missed your in-between question but glad you got it going!

SETI (and Setiqueue) use a "gethostbyname" call which looks for a hostname somewhere that is resolvable. Yes, this is technobabble, but true. 😛

[EDIT: Oh and to correct what I said earlier - yes YOU are correct, the client would be -proxy localhost:5517 and not the queue! 🙂]
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top