X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id CC17BD7C3B for ; Mon, 7 Nov 2005 18:38:12 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 00919-03 for ; Mon, 7 Nov 2005 22:38:07 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from flake.decibel.org (flake.decibel.org [67.100.216.10]) by svr1.postgresql.org (Postfix) with ESMTP id 28E19D7C12 for ; Mon, 7 Nov 2005 18:38:09 -0400 (AST) Received: by flake.decibel.org (Postfix, from userid 1001) id 56F7615257; Mon, 7 Nov 2005 16:38:11 -0600 (CST) Date: Mon, 7 Nov 2005 16:38:11 -0600 From: "Jim C. Nasby" To: Chris Hoover Cc: pgsql-admin@postgresql.org Subject: Re: Semi OT - Anyone monitoring PostgreSQL with nagios Message-ID: <20051107223811.GJ19551@pervasive.com> References: <1d219a6f0511071318s567a2576k4ee103a8b32522bd@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1d219a6f0511071318s567a2576k4ee103a8b32522bd@mail.gmail.com> X-Operating-System: FreeBSD 4.11-RELEASE-p10 i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.007 required=5 tests=[AWL=0.007] X-Spam-Score: 0.007 X-Spam-Level: X-Archive-Number: 200511/55 X-Sequence-Number: 19428 I'm not familiar with Nagios, but you should be able to do something like psql -tc 'select 1' database to see if it's alive and accepting queries. On Mon, Nov 07, 2005 at 04:18:55PM -0500, Chris Hoover wrote: > Is anyone using Nagios to monitor PostgreSQL? > > If so, is there any way to check for more than just your PostgreSQL instance > being up? > > This weekend, we had an issue where a database shutdown failed due to a > rogue query that would not die w/o a kill -9 being done on it. The database > remained up and accepted connections only to tell the connection to go away > because the database was shutting down. > > This up and accepting connections caused our Nagios instance to not report > the database being down. > > Any ideas on how to get around this? > > Thanks, > > Chris -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461