| From: | "Andrej Ricnik-Bay" <andrej(dot)groups(at)gmail(dot)com> |
|---|---|
| To: | pgsql-list(at)nullmx(dot)com |
| Cc: | "General PostgreSQL List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Postgres with daemontools or similar |
| Date: | 2008-02-05 00:00:45 |
| Message-ID: | b35603930802041600r2c88750ck205cf2e9f75fc102@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 05/02/2008, Chuck D. <pgsql-list(at)nullmx(dot)com> wrote:
> would never know if there was an issue. I was also looking into monit.
I don't know what others recommend, but I'd be violently opposed to
the automatic re-starting for the very reason you mention above.
Monitoring it via monit, nagios or which other tools you have at hand
sounds very sensible to me, and I'd go with that for sure.
> What is the best way to monitor the postmaster and notify or restart on
> problems? What solutions have other SysAdmin's incorporated successfully?
Nagios here, with e-Mail and pager alerts. Monitoring the postmasters
presence and the ability to connect to 5432 ....
Cheers,
Andrej
--
Please don't top post, and don't use HTML e-Mail :} Make your quotes concise.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-05 00:12:17 | Re: encoding does not match server's locale |
| Previous Message | Tom Lane | 2008-02-04 23:57:05 | Re: Out of Memory errors while running pg_dump |