Having a bad day with seti

[racecar12]

This mourning it was so slow, and it took 1.5hrs to cache only 9 of my wu's before leaving for work, and still no conectivety (peak hrs). I am getting an audible sound thru the tv on my pc when seti spy is running and without being able to get wu's up and down I can't renew the client......Now to seti que. I downloaded seti que for the second time, after cleaning bs spyware from another prog with a format last night, and still can't figure out the que. I just must be stupid or something.

I have read the instructions maybe a dozen times but just can't get the sob to work. I am trying to releive a little stress by not having to upload each individual system by using the the que. Login? me as racecar12 and my pw does not work. Nothing I do seems to work. I can't set the # of que's to dl in que settings, can't log on. Done this twice now with absolutly no luck. Does it take a little rocket science knowledge? Am I suppose to know how this sob works because their instructions have little to be desire IMO.

Could I just be overlooking the obvios? Ugggggg.....

Sorry for the rant, just frustrated

 

[JigPu]

We all have days like that.... SETI just makes us mad...

As to the cache problem... I can't be much of a help there.... I had problems trying to set it up myself, and managed to figure it out after about an hour of trying. But then I deleted it for some reason.


Right now, I have to steal WUHistory.dat from my friend so I can install SETIGate... SETIMonitor is getting on my nerves again. Every time it loads a new WU up, it un-hides SETI and I'm scared that people will close it...

Hope somebody can help you out!!
JigPu

 

[racecar12]

LOL 60k/min

 

[Greg M]

I installed SETIQueue fairly easily. I just tried to not think about it that hard. I still haven't figured out how to make it cache the number of WU's I want by setting the number of days I want cached. Apparently the Queue server is using an algorithm that is smarter than I am. I still use the individual cruncher caches to act as a buffer.

The SETI@Home server IP address is the address of the system on which you are installing the SETIQueue software. All of the crunchers on the network have the SETI Driver proxy set to the IP of the Queue server and port 5517. If the queue server is also crunching, you set the proxy for the localhost as 127.0.0.1 port 5517.

 

[LandShark]

what exactly is wrong? or didn't work on Queue?

let me see if i could help since i've installed one in my machine. and the worst case, u can use my Queue server

i guess the most problem that peopel had is to setting it up for each client to connect the server. if it's in ur local network (LAN), u just point each machine to the server's ip address and the default port (or whatever port u've assigned). e.g. 192.168.1.101 if that's ur Queue server's local (LAN) ip address.

if thru internet, then u'll need to replace that ip address into the ip address from ur isp. e.g. 23.656.13.3 something like that. but that "only" work if u got a statis ip. if u got a dynamic ip from ur isp (like me & audiman), then i would suggest u to use some kinda forwarding service/program like no-ip.com (that's what we r using) to update ur ip address all the time and to forward any request to u.

as for the caching in Queue. it consisently check/update on ur daily completed/return WU, and adjust it accordingly to the days that u've specificed. it works in different way as SETIDriver. let's say u set it to 10days max., 7days min. cache (which i would suggest as minimal), last month u've ave. 10WU/day, then Queue will fill the cache in between 70-100WU. but if this month u add rigs, and ave. 20WU/day, Queue will automatic adjust the cache size to 140WUmin., all the way to 200WU max.

hope this will help. if not, let me know exactly what's wrong or u can check on my Queue server's setting to have some idea.

http://landshark.myftp.org:5517

good luck

 

[hallen]

Greg- Click on Settings then Queue Settings

When the Select Queue window opens double click where it says Q0001 under #

Then the Queue Settings window opens up. Enter a number in the override box. Then click OK.

That should help you prime the pump.

Later you can click the Download WU's box off to return wu's only. Don't forget to turn it back on for more wu's.

Harvey

 

[hallen]

Racecar- You might not get any dl/ul activity until SetiDriver has sent or asked for a wu from/to SetiQueue.

Try hitting transmit with the proxy server set for Setique. Keep the Desired Cache Size small until it's doing what you want.

Harvey

edit: All of this is when you have a connection to the Internet.

 

[davidsnot]

And don't forget that when you get a new client connected to SetiQueue, it sets up an account for it. It may take longer to get the first queue. The second will go much faster.

Also, don't forget to point at the right proxy port with the client.