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 44F50D8298 for ; Mon, 7 Nov 2005 17:18:55 -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 57314-06 for ; Mon, 7 Nov 2005 21:18:52 +0000 (GMT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.201]) by svr1.postgresql.org (Postfix) with ESMTP id 8310FD6E2C for ; Mon, 7 Nov 2005 17:18:53 -0400 (AST) Received: by xproxy.gmail.com with SMTP id s14so526669wxc for ; Mon, 07 Nov 2005 13:18:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=oilcP/jaSl1mdrbYNM4CforKqyW5tpbTqGUoX++g75A3UzIcfAjw3KSy2Ga91hFAnKByNHy0BgjTYxYKSARc6e6qcBj+4dtz0DBanGTHiZurKbH8wMrY1871ErLHNzfSEbUnH9qtZNI9j91BWcO6wd5ApPD7CM99aDsdMAdVqZI= Received: by 10.70.23.12 with SMTP id 12mr5458123wxw; Mon, 07 Nov 2005 13:18:55 -0800 (PST) Received: by 10.70.87.11 with HTTP; Mon, 7 Nov 2005 13:18:55 -0800 (PST) Message-ID: <1d219a6f0511071318s567a2576k4ee103a8b32522bd@mail.gmail.com> Date: Mon, 7 Nov 2005 16:18:55 -0500 From: Chris Hoover To: pgsql-admin@postgresql.org Subject: Semi OT - Anyone monitoring PostgreSQL with nagios MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_23309_26482312.1131398335483" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=1.536 required=5 tests=[AWL=-0.742, HTML_10_20=0.945, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.332] X-Spam-Score: 1.536 X-Spam-Level: * X-Archive-Number: 200511/54 X-Sequence-Number: 19427 ------=_Part_23309_26482312.1131398335483 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Is anyone using Nagios to monitor PostgreSQL? If so, is there any way to check for more than just your PostgreSQL instanc= e 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 ------=_Part_23309_26482312.1131398335483 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Is anyone using Nagios to monitor PostgreSQL?

If so, is there any way to check for more than just your PostgreSQL instanc= e 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
------=_Part_23309_26482312.1131398335483--