X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 9FEBD9DC82A for ; Thu, 2 Feb 2006 14:04:59 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 35856-01 for ; Thu, 2 Feb 2006 14:04:57 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by postgresql.org (Postfix) with ESMTP id 3E6109DC847 for ; Thu, 2 Feb 2006 14:04:55 -0400 (AST) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id k12I4hcO040185 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 2 Feb 2006 11:04:47 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.4/8.13.4) with ESMTP id k12I4g3l007669; Thu, 2 Feb 2006 11:04:42 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.4/8.13.4/Submit) id k12I4gDm007668; Thu, 2 Feb 2006 11:04:42 -0700 (MST) (envelope-from mfuhr) Date: Thu, 2 Feb 2006 11:04:42 -0700 From: Michael Fuhr To: "mcelroy, tim" Cc: "'pgsql-admin@postgresql.org'" Subject: Re: Postmaster errors Message-ID: <20060202180441.GA98478@winnie.fuhr.org> References: <0C4841B42F87D51195BD00B0D020F5CB044B2341@morpheus.bostonstock.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0C4841B42F87D51195BD00B0D020F5CB044B2341@morpheus.bostonstock.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.115 required=5 tests=[AWL=0.115] X-Spam-Score: 0.115 X-Spam-Level: X-Archive-Number: 200602/24 X-Sequence-Number: 20445 On Thu, Feb 02, 2006 at 12:34:44PM -0500, mcelroy, tim wrote: > That was it, a fellow admin is watching the postmaster with OpenNMS.... I think OpenNMS has a way to set up a custom poller that can do anything you want (e.g., connect to the database, issue a query, check the results). I was playing with that a year or two ago; at that time the OpenNMS documentation was pretty scant but I remember coming across the feature in the release notes or some other document. Monitoring the database with such a poller would tell you more about whether the service is available than a simple TCP connect does. -- Michael Fuhr