Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 7FF09632E2F for ; Tue, 7 Apr 2009 08:58:49 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 74038-04 for ; Tue, 7 Apr 2009 08:58:47 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by mail.postgresql.org (Postfix) with ESMTP id ABC1A632A81 for ; Tue, 7 Apr 2009 08:58:47 -0300 (ADT) Received: by yx-out-2324.google.com with SMTP id 8so1765578yxm.73 for ; Tue, 07 Apr 2009 04:58:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.227.9 with SMTP id z9mr200802ybg.218.1239105526460; Tue, 07 Apr 2009 04:58:46 -0700 (PDT) In-Reply-To: <937d27e10904070310w25ffbaeet342719c79d7485fe@mail.gmail.com> References: <200904071139.49895.guillaume@lelarge.info> <49DB25E5.9080002@iol.ie> <937d27e10904070310w25ffbaeet342719c79d7485fe@mail.gmail.com> Date: Tue, 7 Apr 2009 12:58:46 +0100 Message-ID: <937d27e10904070458v2624438dnb02b1ad77cf52895@mail.gmail.com> Subject: Re: Blank home page for www.postgresql.org From: Dave Page To: rod@iol.ie Cc: Guillaume Lelarge , PostgreSQL www Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200904/21 X-Sequence-Number: 16888 On Tue, Apr 7, 2009 at 11:10 AM, Dave Page wrote: > On Tue, Apr 7, 2009 at 11:07 AM, Raymond O'Donnell wrote: >> On 07/04/2009 10:39, Guillaume Lelarge wrote: >> >>> Not sure why but the home page of http://www.postgresql.org/ is completely >>> empty. But http://www.postgresql.org/docs/ (and others, that's just an >>> example) works. >> >> Actually, I'm not seeing the CSS for any of the main sections, though >> the HTML is coming through OK. The front page is completely blank. > > The master server has run out of disk space for some (currently > unknown) reason. Once I've figured that out and fixed it, I need to > figure out why Nagios didn't warn us :-( Should be OK now. I've got the docs rebuilding at the moment as some of those pages may have got broken. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com