Is it this bad for anybody else?

[Engineer]

Baz,

Go to the Queue Server menu under "Settings"

Change the connection type to WinInet Proxy.

Set Proxy server to "federation.2y.net" (minus the quotes) with the port set to 443.

No need for a login or password......(I don't think....?)

Once in..you may have to shut down and restart it to get it to kick in...

Let me know if you want to try...

 

[blcjr]

Two answers!

Okay, Engineer, let's give it a try. Anything you need to do to get ready? Tell me when, and I'll make the change, restart SetiQ, and we'll see what happens.

We may want to put a time limit or something on this. Any problems with you handling >300 wu's from me? I'd hate to just make my problem you're problem. Maybe I should spread the love around?

-baz

 

[IndyJaws]

Baz,

I probably should have noted that I only had 70 or 80 WU's in my queue, so that could explain why all mine were flushed. It's obviously able to do some fetching/flushing during the day, since I would have 4 times that number if it weren't connecting at all. Hope your experiment with Engineer works out! Let me know if I can be of any more help.

 

[RaySun2Be]

Also,
If you are concerned with getting fresh WUs, would it help to change the Processing Priority to download WUs into SETIQ first? So that if you get a connection, it will try to grab new WUs before uploading WUs,so at least the herd is fed?

Or does it matter?

Also, could we start a thread dedicated to the best SETIQ settings for the current situation? (best as in getting completed WUs out, fresh ones in, what Q to use, times of day, what should be enabled/disabled in the Q settings, etc.)

Should we be sending WUs to Orange Kid's considering his Q is backing up faster than it can flush? Should we then use another team Q as an alternative, or just try our luck with Berkeley?

 

[Engineer]

Baz,

I should be here for about the next 45 minutes....I've logged onto my Queue.....I've got 750 WU's....around 400 for my stuff...but my home PC and my work Queue have enough for 10 days

When you start...it should send me 1 WU and shouldn't receive any unless Berekely is working. I'll then go and move a couple hundred over to your Newly created queue in mine.

All we can do is see if it'll work....worth a shot...and sorta fun for me to play with the Queue

Let er rip!

(Not you Ray...I know what you'll be ripping! :Q)

 

[micron]

<< (Not you Ray...I know what you'll be ripping! :Q) >>

:Q

 

[IndyJaws]

Hmmm...I just checked something and it doesn't seem quite right...

When all of this started, I changed my minimum depth to 7 days, 10 days for maximum. At appx. 300 WU/day, that should be at least 2100 WU's. However it says I only have 748 downloaded WU's (and has had appx. that amount for several days now). What's up?

 

[RaySun2Be]

<< (Not you Ray...I know what you'll be ripping! :Q) >>



Hey! What did I do?

Try to post some relevant thoughts and suggestions, and all I get is this? :Q


[affected English accent trying to sound like a French person]

I fart in your general direction, you Federation-type pig dog....

[/affected English accent trying to sound like a French person]

 

[Poof]

I fart in your general direction, you Federation-type pig dog....

:Q

ROTFLMAO Ray!!!!!!!

(Engineer - look out. Ray has that Platinum cane! )

Indy - it could be that your queue wasn't able to be connected long enough to get that many WUs downloaded. It might have worked before the bandwidth problems, but now, it appears that trying to maintain huge queues will be difficult...

This is good info to know for anyone managing any of the TeAm queues. Perhaps there will ultimately be a WU "cut-off" point in order to ensure optimum upload/download capability during a 24-hour period before constipation begins (might as well use the ole RC5 pproxy terms here, cause that's what's happening... )

 

[poopaskoopa]

No. I'm not a big cruncher like some of y'all, so I probably don't feel the pain as much. I average in the 40s in daily production, and I haven't noticed any drops. I use SETI Driver only on all my crunchers, and I think I keep about 7~10 days worth of WUs on each machine.

 

[Engineer]

[Obe-Wan_Kenobe] Use the Farts Ray....use the Farts ! Let your Innards flow.... :Q [/Obe-Wan_Kenobe]

 

[IndyJaws]

<< [Obe-Wan_Kenobe] Use the Farts Ray....use the Farts ! Let your Innards flow.... :Q [/Obe-Wan_Kenobe] >>



:Q

LOL

 

[blcjr]

Okay, Engineer, I've pointed my Q to yours. Now I'll wait a bit and see what happens.

-Bazilla

 

[micron]

<< [Obe-Wan_Kenobe] Use the Farts Ray....use the Farts ! Let your Innards flow.... :Q [/Obe-Wan_Kenobe] >>

ROTFL!

 

[RaySun2Be]

<< [Obe-Wan_Kenobe] Use the Farts Ray....use the Farts ! Let your Innards flow.... :Q [/Obe-Wan_Kenobe] >>



Now that's just plain GROSS, Engineer.

LOL!

 

[Engineer]

Baz...gave you 250 WU's to start with...will monitor and let you know!

http://federation.2y.net:443/default.htm

WU's flowing in

 

[blcjr]

One thing about all this that isn't making sense as far as my problems are concerned is that Berkeley claims the cap should only affect outbound traffic, not inbound traffic. Well then, why cannot I upload my wu's to Berkeley? I can understand the timeouts and failed connections getting wu's for my cache. I don't understand the timeouts and failed connections uploading completed wu's.

IAC, I've just uploaded a completed wu to Engineer's Q. I'm now waiting to see what happens with it.

-baz

 

[blcjr]

Whoa, talk about "breaking wind"! I'm unleashing a huge one right now in the direction of Engineer. Hope his head is turned the other way.

-baz

 

[blcjr]

Yeah, they're flowing in all right. I'm down about 180 in the past few minutes. Feels good to get them out of my system. Just hope they don't clog yours up too much.

-baz

 

[Engineer]

We'll see.....so far, my Queue runs slow during the day, but empties them out at night...and has been empty most of the day...it has been sending...but very slowly!

The speed, by the way is 3 Mbits down...1.1Mbits up

The PC is a 1.4GHz TBird with 512Megs DDR on ECS board...but will be upgraded shortly

We'll monitor it for 24 hours and see what happens

 

[blcjr]

"sending...slowly" I can take. It was the "sending...not at all" that was getting on my nerves.

Anyway, I agree...we need at least 24 hours to see how this shakes out.

Thanks a bunch.

-baz

 

[Engineer]

<< January 29, 2002

The campus wide outbound bandwidth cap is set at 70Mb/s. We are getting only around 10Mb/s of this during the day but are getting all we need at night. The best time for connecting varies but is roughly for the 2 hours on either side of 1:00 PST, or 9:00 UT.
>>



From Berkeley....if anyone missed the amount of DATA in and out!

 

[blcjr]

I read that too. But that only pertains to outbound traffic. Inbound traffic is not supposed to be an issue:

The current (new) policy is for SETI@home to get all excess capacity in outbound bandwidth (inbound is not an issue).

However, current server status is that they are dropping a lot of connections:

The data server is up and running, but dropping connections

Right now the data server machine is up, but not all clients are able to connect. This is due to our server being swamped with requests, and usually happens right after a server outage, or if there are greater network/database problems we are currently trying to fix. Please try connecting later.



I think the first problem -- bandwidth cap -- has led to the second. The second is what I've been seeing.

-baz

 

[JustStarting]

I set my max time between retries to like 10 minutes or so. If there is anything queued to go up or down, it will try every 10 minutes. My connections have been limited also- usually between 12AM- 6AM EST stuff flows freely for me.

 

[seaquake]

Maybe we should just dump the results to floppy disk and mail it to them. It seems like they'll get there faster!