[Scotttheking]

Subject says all.
I'll post some when I have some.

[Scotttheking]

Ok, here's the news.
The DNS has been switched, seti.macnn.com is now pointing to me.
It shouldn't take more then a day to update for everyone.
When you connect to my proxy, you will have to wait for your queue to be initialized, which can now take a few minutes, thanks to berkeley being slower then usual.
Just be patient, and it will work.

[sideus]

Thanks Scott. I was running my own seti proxy, but now I will switch over to yours and let my computer do other tasks.

BTW, the proxy uses port 5517 correct? So it would be seti.macnn.com:5517

[ 05-19-2002: Message edited by: sideus ]

[SkiBikeSki]

Originally posted by sideus:
<STRONG>
BTW, the proxy uses port 5517 correct? So it would be seti.macnn.com:5517

[ 05-19-2002: Message edited by: sideus ]</STRONG>

That's correct. But what Scott meant was that for while the domain name seti.macnn.com was pointing someplace, else now now it's back to him since he's up and running again.

[Scotttheking]

Status:

DNS changes are taking effect, and I've got a couple of users now. I'm sure I'll see the rest in the next day or two. I haven't noticed the net being slower, which is good.

FYI, the client connects to berkeley at night, meaning 10pm to 6am. This way it doesn't interfere with normal surfing too much
It's first priority is to download new work units, not upload results, so if berkeley is backed up it may take time. I'll try and get reader50 to time the stats runs so that you see dumps the same day.

--Scott

[Kate]

Seti has been down for maintenance, but aside from this I still cannot get new work downloaded by either Seti itself or via the MacNN proxy.
All my computers are waiting for new work to download since a day. Anyone else seeing this?

....ah, see, seti.macnn.com:5517 :unknown host, my DNS seems to update late.
back to Seti itself and the long waiting queue....

[ 05-23-2002: Message edited by: Kate ]

[Scotttheking]

Originally posted by Kate:
<STRONG>Seti has been down for maintenance, but aside from this I still cannot get new work downloaded by either Seti itself or via the MacNN proxy.
All my computers are waiting for new work to download since a day. Anyone else seeing this?

....ah, see, seti.macnn.com:5517 :unknown host, my DNS seems to update late.
back to Seti itself and the long waiting queue....

[ 05-23-2002: Message edited by: Kate ]</STRONG>

As posted on the seti front page, their servers were down quite a bit yesterday.
Just try putting seti.macnn.com:5517 in your web browser. If the page loads, then it means your DNS has updated, and you can begin using it.

Also note that the proxy has to get a work unit to give you. I've been manually transferring WUs from one person's queue to another, but I'm not too fast. The point of the proxy is to use it now so that when berkeley goes down you still have WUs. It doesn't help to connect to it while berkeley is down.

[sideus]

Berkeley must be really backed up. Concerning the uploading of completed work units. I completed about 9 WUs yesterday, but my total WUs completed only went up by 1. If results are not uploaded, about what time frame will SETI re-send a WU I've completed to another client?

[reader50]

Originally posted by sideus:
<STRONG>... If results are not uploaded, about what time frame will SETI re-send a WU I've completed to another client?</STRONG>

They do not say exactly, but I suspect it's several weeks.

Note that all SETI units are believed to be crunched by at least two people anyway for security reasons, so there would be no hurry on one unit being returned.

[Scotttheking]

First, they send each WU out at least 3 times. Don't worry about it taking a while, the result will still count.

Status report. The proxy is slowly losing WUs, as it has a hard time getting any from berkeley, which seems to be the case for everyone. If you decide to use it, PLEASE do not give up and leave, because then the proxy will eventually get a WU, and it will just sit there, and it's annoying for me to have to manage a bunch of user's queues that are inactive. Also, if you haven't connected in 5 days, I will take your WUs and move them to other users.

If anyone is running a buffer locally, please tell me. I see a few users are downloading a ton of work and then not returning, and I need to know if it's a local buffer. If it is, DO NOT BUFFER MORE THEN 2 DAYS WORTH (preferably less). You don't need a 2 week buffer, and it messes up how the proxy works when you take a ton at once (it thinks you are bigger then you are, and increases how much it buffers, at a cost to other users).

Edit: if you are wondering where your results are, they aren't lost, they are in a different proxy which right now has 1400 results to send back.

--Scott

[ 05-24-2002: Message edited by: Scotttheking ]