Finally got Seti Queue up and running. Now all I need is...

[minendo]

Some Work Units:Q:frown:



I am trying to get Seti Queue up and running, but I really have no idea how to go about it. I've got the program running and wanted to see if anyone can connect to it.

Link

Is there anyone here that would be willing to help me get it set up so that I can get some work units. Thanks.

 

[nagger]

yep it works

minendo
SetiQueue Work Units

General:
Home
Settings
Stats

Reports:
Users
Queues
Clients
Summary

WUs:
>Waiting
Pending
Results
History

Admin:
Login
Tools
Log

<http://128.211.174.133:5517/3/1/CC99FF/b.gif>

No Queued Work Units

 

[minendo]

<< No Queued Work Units >>


That is where I am stuck. How do I go about getting some queued work units?

 

[Tarca]

Looks good

look below lol

 

[Tarca]

Once you complete a WU and send it to the Queue it will download some.

You might want to open the down load time a little more. and add a couple of days to the min/max queue depth.

 

[minendo]

<< Once you complete a WU and send it to the Queue it will download some. >>


I tired to send on in, but it wont go.

 

[RaySun2Be]

I would say it is the continuing Berkeley bandwidth issue you are running up against.

 

[Tarca]

Do you have the ip set in your seti driver? select proxy server and 128.211.174.133 should be in your host window on setidriver.

 

[minendo]

<< I would say it is the continuing Berkeley bandwidth issue you are running up against. >>


Now that bandwidth problem would make it so that one of my clients can't upload to my Queue?

 

[minendo]

<< Do you have the ip set in your seti driver? select proxy server and 128.211.174.133 should be in your host window on setidriver. >>


Yeah that is set up, but still nothing.

 

[serialb]

It should work. Just point your clients to your Q. It will show up there.

Once you attempt to connect, a user and a client will show up. Just upload a few WUs to it.

 

[minendo]

Error

Above is what I see when a client tries to upload a completed WU.

 

[serialb]

minendo,

I "think" you should leave your IP & Subnet Mask to 0.0.0.0. Can you try that?

 

[Poof]

minendo - I can't resolve your link..

BUT... you are trying to set up your queue at sortof a bad time. When a client connects for the first time, some info (like the user_info.sah) gets transfered to the queue and then SETI needs to slowly begin to fill the queue up. This may take some time normally when the queue is first created...let alone now, when the connections are so bad.

You may have to babysit it for awhile until you can get some WUs in.

 

[minendo]

<< minendo,

I "think" you should leave your IP & Subnet Mask to 0.0.0.0. Can you try that? >>


just changed them. now its time to test it out

 

[Eltano1]

The IP in your SetiDriver and SetiQ should be your own pc IP address, I'm running my Q that way and I have not problems. Try and see what happens.

Eltano

 

[Poof]

I looked at the log from the queue and it looks "normal". There's a client registered and a queue setup. The log indicates that the poor queue is trying to download WUs and is getting a timeout from SETI.

And as long as the queue doesn't have any WUs in it, then the client won't be able to get one until the queue gets some.

You might be able to point the queue to someone else's queue to get some WUs. Then change the setting back to go to SETI overnight when hopefully, things will be better.

 

[serialb]

There you go, minendo. It should be operating fine now.

BTW, 3047471 is me.

 

[Poof]

BTW, 3047471 is me.

LOL!

 

[minendo]

Thanks to everyone for their help.

 

[minendo]

Looks like everything is running fine now. All I need is some work units.