Message-ID: <44496809.1030001@commandprompt.com>
Date: Fri, 21 Apr 2006 16:17:29 -0700
From: "Joshua D. Drake" <jd@commandprompt.com>
Organization: Command Prompt, Inc.
User-Agent: Mail/News 1.5 (X11/20060309)
MIME-Version: 1.0
To: "Jim C. Nasby" <jnasby@pervasive.com>
CC: Dave Page <dpage@vale-housing.co.uk>,
 Magnus Hagander <mha@sollentuna.net>,
	"Marc G. Fournier" <scrappy@postgresql.org>, greg@turnstep.com,
	pgsql-www@postgresql.org
Subject: Re: Gborg still down
References: 
 <E7F85A1B5FF8D44C8A1AF6885BC9A0E4011C9EBF@ratbert.vale-housing.co.uk>
	<20060421224531.GV49405@pervasive.com>
In-Reply-To: <20060421224531.GV49405@pervasive.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jim C. Nasby wrote:
> On Fri, Apr 21, 2006 at 08:41:00PM +0100, Dave Page wrote:
>> Most of the servers are not hosted by hub these days - we have them
>> pretty well distributed around the world these days.
> 
> Well, wherever they're hosted monitoring has been an issue for as long
> as I can remember. Search not getting updated, list archives not
> updated, sites down, etc.

Well Search has been resolved as it was moved to us and has been kicking 
arse since then. Archives has not had any server side problems in longer 
then I can remember.

> If individuals hosting these various services aren't monitoring them
> adequately then the project itself should be monitoring them. Plus
> there's servers/services that I suspect won't get monitored very well by
> their owners (mirrors come to mind...)

It may be helpful to understand that a lot of the servers are mirrors 
(like archives) and even if archives is doing just fine the source for 
archives may be having problems (which has been the case).

Joshua D. Drake


-- 

            === The PostgreSQL Company: Command Prompt, Inc. ===
      Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
      Providing the most comprehensive  PostgreSQL solutions since 1997
                     http://www.commandprompt.com/