New pproxy location [Archive]

Darkness Productions

04-04-2003, 04:50 PM

Can I get everyone who's using my pproxy to switch the keyserver location to proxy.dp.cx? It still (currently) points to the same location, but this way, should I need to change it in the future, I'll be able to.

Thanks again to everyone :D

Darkness Productions

04-05-2003, 06:57 PM

Can everyone let me know when/if you all can get your clients moved over? I just want to make sure that everyone is using the updated location.

Thanks again.

rshepard

04-05-2003, 07:10 PM

all done--:thumbs:

Beyond

04-05-2003, 07:35 PM

Done ;)

magnav0x

04-05-2003, 10:24 PM

I got a couple more machines to move over, but they will be changed by the say Tuesday or so.

rshepard

04-06-2003, 12:50 PM

is the new location broken today? I am getting
"ENOENT: no entry for requested name "
messages. The old proxy location seems to be OK....

Chinasaur

04-06-2003, 01:24 PM

dp,

A possible bug on the proxy stats viewing page..http://stats.dp.cx/ogr/byemail.html

On my Mac using IE (gack) flickering on the bottom status bar is -

stats.dp.cx/ogr/images/flags/ca.png

For what it's worth :)

Thanks for the proxy and the stats pages :)

:cheers:

magnav0x

04-06-2003, 01:36 PM

I also got a connection problem with the proxy.dp.cx on my last packet fetch/flush. Has worked fine up until then.

IronBits

04-06-2003, 01:49 PM

So there is no confusion, it should read
keyserver=proxy.dp.cx:2064 ;)

alpha

04-07-2003, 02:51 AM

Originally posted by Darkness Productions
Can everyone let me know when/if you all can get your clients moved over? I just want to make sure that everyone is using the updated location.

Roger. Haven't flushed since yesterday but all seemed well then.

Darkness Productions

04-07-2003, 08:43 AM

That may just be DNS trying to propagate everywhere. Hopefully, it'll all be over soon.

Originally posted by magnav0x
I also got a connection problem with the proxy.dp.cx on my last packet fetch/flush. Has worked fine up until then.

rshepard

04-07-2003, 08:48 AM

That may just be DNS trying to propagate everywhere. Hopefully, it'll all be over

Must be the case- I put everything back on the new address, and seems to be OK now :thumbs:

Darkness Productions

04-10-2003, 11:00 AM

Ok. Just as an FYI, proxy.dp.cx will now point to stibnite's pproxy. However, since all you lucky people changed so that you were pointing to proxy.dp.cx, this won't affect any of you. How about that? :) I will be forwarding stibnite the pproxy logs that I have, so that all the stats information will be there for everyone.

You'll be able to find pproxy stats at http://stats.allaboutuptime.net/rc5-72/ and http://stats.allaboutuptime.net/ogr/

Thanks again for helping out!

Glen

the-mk

04-10-2003, 01:17 PM

Hi!

proxy.dp.cx points to nowhere, so I can't download any OGR-workunits :cry: I can't nslookup this host :( Any idea what happend/what is happening?

[EDIT:]
A suggestion: could you "redirect" your http://stats.dp.cx/ogr/byemail.html to the new address? Just with that code:

<html>
<meta http-equiv="refresh" content="0 URL=http://stats.allaboutuptime.net/ogr/byemail.html">

rshepard

04-10-2003, 01:20 PM

you might try setting it this way:
keyserver=12.220.136.22:2064
and see if that helps

Darkness Productions

04-10-2003, 01:30 PM

The dns for proxy.dp.cx has been going for a while now. However, DNS is silly like that, so who knows. I'd prefer if you all didn't access it via IP directly, but if you do, I'll live until DNS fixes itself.

the-mk

04-10-2003, 01:31 PM

Hmm, now I can lookup proxy.dp.cx with nslookup :confused:
Now I can fetch/flush my OGR work again...

funny thing...

and I haven't finished my last suggestion-"EDIT" :D

<html>
<meta http-equiv="refresh" content="0 URL=http://stats.allaboutuptime.net/ogr/byemail.html">
</html>

or redirect to http://stats.allaboutuptime.net/ogr/ in general

the-mk

04-10-2003, 01:52 PM

I know that I'm :spank: but there is another question:

My clients are fetching/flushing to proxy.dp.cx, why can't I see myself on that http://stats.allaboutuptime.net/ogr/byemail.html site? (and: yes, I've something flushed! Thanks to that small OGR-24-blocks that made it possible)

[EDIT:] but now it works... funny thing again...

magnav0x

04-10-2003, 04:39 PM

I've been getting a LOT of small OGR packets today. In fact I don't think I've seen one that's taken more than 5 minutes to complete yet.

PY 222

04-10-2003, 05:00 PM

Me too!

I got a shocked that my computer manage to crunch through over 20 workunits in a matter of hours.

What gives? Could this be OGR-24 packets? :confused:

magnav0x

04-10-2003, 06:07 PM

Yes they are OGR24 packets

Beyond

04-11-2003, 05:26 PM

/me thinks stibnite needs to up his buffers on the proxy from the default "20" stubs as I seem to be starving for stubs since dnet switiched to handing out OGR 24 stubs. (well not really running out but my own proxy is normally at a 3 day reserve level but it is falling as I cannot seem to replenish the stock fully from stibnite's proxy :( )

the-mk

04-14-2003, 09:57 AM

Why are the OGR-proxy-stats at http://stats.allaboutuptime.net/ogr/byemail.html not up to date while the RC5-72 are?

Timestamp of last update: <<Last Updated GMT: 14 Apr 2003 04:05>>

Now its in the afternoon (GMT) and not 4 a.m. GMT.

And I just wonderd myself why I've only flushed 300 GNodes today.

Darkness Productions

04-14-2003, 10:45 AM

The version of ppstats that stibnite is running seems to have some "issues". I've given him the version that I have so that he can at least keep something up and running. I'll see if I can't get a hold of him to increase his buffer size, oh, say 10 fold ;)

Originally posted by the-mk
Why are the OGR-proxy-stats at http://stats.allaboutuptime.net/ogr/byemail.html not up to date while the RC5-72 are?

Timestamp of last update: <<Last Updated GMT: 14 Apr 2003 04:05>>

Now its in the afternoon (GMT) and not 4 a.m. GMT.

And I just wonderd myself why I've only flushed 300 GNodes today.