X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 402EB9F9C9E; Wed, 17 May 2006 06:23:05 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 62441-03; Wed, 17 May 2006 06:22:56 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by postgresql.org (Postfix) with ESMTP id 16D599FA19B; Wed, 17 May 2006 06:22:56 -0300 (ADT) Received: from mailgate.vale-housing.co.uk ([194.217.48.34] helo=vale-housing.co.uk) by anchor-post-34.mail.demon.net with esmtp (Exim 4.42) id 1FgIF4-000EIP-Eo; Wed, 17 May 2006 09:22:54 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: developer.pgadmin.org/nagios.pgadmin.org server - update Date: Wed, 17 May 2006 10:22:53 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: developer.pgadmin.org/nagios.pgadmin.org server - update Thread-Index: AcZ5k3nXKhxKmodtTfy5FB+mac+keQ== From: "Dave Page" To: , "pgsql-www" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/81 X-Sequence-Number: 10044 Just a quick update on the server problem I was experiencing... Swapped out the memory on Monday, and put the old sticks into a different box for testing. The memory appears fault free after 24 hours of memtest86, however the server, whilst appearing fine, threw another error during last night's tape backup. I've swapped out the mobo & CPU this morning (which coupled with an ARP cache on a router was the cause of this mornings noise from Nagios on the -slaves list) so we'll see how that goes.=20 I'm currently working on the system again but being careful to keep an eye on the logs and keep additional backups of my work around just in case. I'd advise anyone working on the PostgreSQL website, pgAdmin or the Nagios install to do the same. Once I have the last cable for the new server I'll move it all across once and for all. Cheers, Dave. PS. For those that are wondering what this has to do with the pgsql-www list, nagios.pgadmin.org monitors all the postgresql.org servers, and a number of the webteam use developer.pgadmin.org as a dev machine for the main PostgreSQL website.