Skip site navigation (1) Skip section navigation (2)

Re: Infrastructure monitoring

From: Guido Barosio <gbarosio(at)gmail(dot)com>
To: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, John Hansen <john(at)geeknet(dot)com(dot)au>, pgsql-www(at)postgresql(dot)org, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Subject: Re: Infrastructure monitoring
Date: 2006-01-14 02:51:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-www
Actually it seems to be as easy as requesting a GET to
If a script is able to handle the http codes, then alerts could be triggered
upon events.

The search failure was due to a 503 error being dispatched from the server.


Am I wrong?

Tho, thinking about content,  there is an opensource doing a job such as
siteconf ( but I can't remember the name atm.

But I understand that the search problem was not a *content* problem itself.


On 1/14/06, Marc G. Fournier <scrappy(at)postgresql(dot)org> wrote:
> On Fri, 13 Jan 2006, Josh Berkus wrote:
> > Jim,
> >
> >> Search has been down for at least 2 days now, and this certainly isn't
> >> the first time it's happened. There's also been cases of archives
> >> getting stuck, and probably other outages besides those that went on
> >> until someone email'd about it.
> >>
> >> Would it be difficult to setup something to monitor these various
> >> services? I know there's at least one OSS tool to do it, though I have
> >> no idea how hard it would be to tie that into the current
> >> infrastructure.
> >
> > We have an open offer of Hyperic licenses, and they support FreeBSD now.
> Not to discount the offer ... but, what exactly would that provide us?  We
> already monitor the *servers*, its what is inside of the servers that
> needs better monitoring ... knowing nothing about Hyperic, does that
> provide something for that?
> In the case of the archives, for instance, the problem was a perl process
> that for some unknown reason got stuck randomly ... removed that in favor
> of an awk script, and it hasn't done it since ... i also redirected cron's
> email to scrappy(at)postgresql(dot)org, so that any errors show up in my mailbox
> instead of roots, so I get an hourly reminder that things are running well
> ...
> In the case of search ... John would be better at answering that, but when
> he and I talked this past week, he mentioned that he was moving it all
> over to two new servers, which I changed the DNS for on Wednesday ...
> As I've said above ... physical servers are being monitored, so if anyone
> has some ideas on how we can improve "content monitoring", for lack of a
> better word, I know I'm all ears ...
> Again, if Hyperic can offer something for this, let me know ...
> ----
> Marc G. Fournier           Hub.Org Networking Services (
> )
> Email: scrappy(at)hub(dot)org           Yahoo!: yscrappy              ICQ:
> 7615664
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

/"\   ASCII Ribbon Campaign  .
\ / - NO HTML/RTF in e-mail  .
X  - NO Word docs in e-mail .
/ \ -----------------------------------------------------------------

In response to

pgsql-www by date

Next:From: John HansenDate: 2006-01-14 09:22:09
Subject: Re: Infrastructure monitoring
Previous:From: Marc G. FournierDate: 2006-01-14 02:16:59
Subject: Re: Infrastructure monitoring

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group