FTP/GIT/WWW server move

[Dave Page-7]

On Friday 30 November at 1200 GMT, the server that hosts our primary
FTP server, GIT server and one of the website mirrors will be moved to
a new data center. Downtime is expected to be two to three hours.

Apologies for any inconvenience this may cause.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
PGDay.EU 2009 Conference: http://2009.pgday.eu/start

--
Sent via pgsql-www mailing list (pgsql-www@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www

[Dave Page-7]

On Thu, Oct 29, 2009 at 9:35 AM, Dave Page <dpage@...> wrote:
> On Friday 30 November at 1200 GMT, the server that hosts our primary
> FTP server, GIT server and one of the website mirrors will be moved to
> a new data center. Downtime is expected to be two to three hours.
>
> Apologies for any inconvenience this may cause.

This work is now complete.

All services should work as normal - except possibly DNS resolution of
'ftp.postgresql.org' for which an old record may be cached for a few
hours yet.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
PGDay.EU 2009 Conference: http://2009.pgday.eu/start

--
Sent via pgsql-www mailing list (pgsql-www@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www

[Peter Eisentraut-2]

On fre, 2009-10-30 at 13:28 +0000, Dave Page wrote:

> On Thu, Oct 29, 2009 at 9:35 AM, Dave Page <dpage@...> wrote:
> > On Friday 30 November at 1200 GMT, the server that hosts our primary
> > FTP server, GIT server and one of the website mirrors will be moved to
> > a new data center. Downtime is expected to be two to three hours.
> >
> > Apologies for any inconvenience this may cause.
>
> This work is now complete.
>
> All services should work as normal - except possibly DNS resolution of
> 'ftp.postgresql.org' for which an old record may be cached for a few
> hours yet.

I have been getting this for the last couple of days:

$ git fetch origin
fatal: The remote end hung up unexpectedly

[remote "origin"]
    url = git://git.postgresql.org/git/postgresql.git
    fetch = +refs/heads/*:refs/remotes/origin/*

Something not quite right there?


--
Sent via pgsql-www mailing list (pgsql-www@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www

[Magnus Hagander-2]

On Sat, Oct 31, 2009 at 09:54, Peter Eisentraut <peter_e@...> wrote:

On fre, 2009-10-30 at 13:28 +0000, Dave Page wrote:
> On Thu, Oct 29, 2009 at 9:35 AM, Dave Page <dpage@...> wrote:
> > On Friday 30 November at 1200 GMT, the server that hosts our primary
> > FTP server, GIT server and one of the website mirrors will be moved to
> > a new data center. Downtime is expected to be two to three hours.
> >
> > Apologies for any inconvenience this may cause.
>
> This work is now complete.
>
> All services should work as normal - except possibly DNS resolution of
> 'ftp.postgresql.org' for which an old record may be cached for a few
> hours yet.

I have been getting this for the last couple of days:

$ git fetch origin
fatal: The remote end hung up unexpectedly

[remote "origin"]
   url = git://git.postgresql.org/git/postgresql.git
   fetch = +refs/heads/*:refs/remotes/origin/*

Something not quite right there?

I restarted git-daemon and now it seems to work again. I've seen this happen before, that git-daemon sometimes falls over if it's started too early. I have no real idea why.

My testing clearly only included git-pull:ing over ssh :S

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/