Re: Moving developer.classpath.org Xen session

2006-12-28 Thread Jim Pick
Jim Pick wrote:
 Hi,
 
 It appears that the ISP in Seattle where I'm renting colo space for one
 of my Xen servers has gotten itself listed in the Spamhaus blacklists.
 
 I'm hosting developer.classpath.org on that particular server.  It's
 being used for the Classpath mailing lists, so being blacklisted by
 Spamhaus is not good.  I imagine that many (most?) people won't even get
 this message.
 
 In order to resolve this, I'm going to transfer the Xen session to
 another server I have in San Jose, California.
 
 So, in about an hour, I'm going to turn off the Xen session, rsync the
 data to my other server, and update the DNS.  There shouldn't be much
 more than an hour of downtime if all goes well.
 
 Actually, this is the second time this has happened.  The last time, the
 ISP managed to get themselves de-blacklisted just before I was about to
 lose patience and switch.  Now it's happened again.  :-(
 
 Also, does anybody have an recommendations for co-locating a 1U server
 in Seattle or Vancouver, B.C. that's inexpensive, but still reputable?
 
 Sorry about all this...

Okay.  It looks like the move worked.  If I missed anything, please send
me an email.

Cheers,

 - Jim



Re: Moving developer.classpath.org Xen session

2006-12-28 Thread Mark Wielaard
Hi Jim,

On Thu, 2006-12-28 at 00:54 -0800, Jim Pick wrote:
 Okay.  It looks like the move worked.  If I missed anything, please send
 me an email.

Thanks! Everything seems to work just fine. Mail flows again, the
developer.classpath.org mediation wiki works and the planet shows your
post about the move :)

Cheers,

Mark




Moving developer.classpath.org Xen session

2006-12-27 Thread Jim Pick
Hi,

It appears that the ISP in Seattle where I'm renting colo space for one
of my Xen servers has gotten itself listed in the Spamhaus blacklists.

I'm hosting developer.classpath.org on that particular server.  It's
being used for the Classpath mailing lists, so being blacklisted by
Spamhaus is not good.  I imagine that many (most?) people won't even get
this message.

In order to resolve this, I'm going to transfer the Xen session to
another server I have in San Jose, California.

So, in about an hour, I'm going to turn off the Xen session, rsync the
data to my other server, and update the DNS.  There shouldn't be much
more than an hour of downtime if all goes well.

Actually, this is the second time this has happened.  The last time, the
ISP managed to get themselves de-blacklisted just before I was about to
lose patience and switch.  Now it's happened again.  :-(

Also, does anybody have an recommendations for co-locating a 1U server
in Seattle or Vancouver, B.C. that's inexpensive, but still reputable?

Sorry about all this...

Cheers,

 - Jim