pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Lane Van Ingen <lvaningen@esncc.com>
Cc: Chris Hoover <revoohc@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Semi OT - Anyone monitoring PostgreSQL with nagios
Date: Tue, 8 Nov 2005 12:56:01 -0600
Message-ID: <20051108185601.GH19551@pervasive.com> (raw)
In-Reply-To: <EKEMKEFLOMKDDLIALABIEEMICEAA.lvaningen@esncc.com>
References: <20051107223811.GJ19551@pervasive.com>
	<EKEMKEFLOMKDDLIALABIEEMICEAA.lvaningen@esncc.com>

Same as -t -c...

On Tue, Nov 08, 2005 at 08:10:28AM -0500, Lane Van Ingen wrote:
> What does the 'c' part of the -tc command do? It is not documented in
> any information I have.
> 
> -----Original Message-----
> From: pgsql-admin-owner@postgresql.org
> [mailto:pgsql-admin-owner@postgresql.org]On Behalf Of Jim C. Nasby
> Sent: Monday, November 07, 2005 5:38 PM
> To: Chris Hoover
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Semi OT - Anyone monitoring PostgreSQL with nagios
> 
> 
> 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
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
> 
>                http://www.postgresql.org/docs/faq
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
> 
>                http://www.postgresql.org/docs/faq
> 

-- 
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



view thread (7+ messages)

Message-ID: <20051108185601.GH19551@pervasive.com>
Permalink:  ../20051108185601.GH19551@pervasive.com/
Also on:    postgresql.org/message-id/20051108185601.GH19551@pervasive.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jnasby@pervasive.com, lvaningen@esncc.com, revoohc@gmail.com
  Subject: Re: Semi OT - Anyone monitoring PostgreSQL with nagios
  In-Reply-To: <20051108185601.GH19551@pervasive.com>
  References: <20051107223811.GJ19551@pervasive.com> <EKEMKEFLOMKDDLIALABIEEMICEAA.lvaningen@esncc.com> <20051108185601.GH19551@pervasive.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox