On Tue, 2012-01-03 at 09:44 -0800, David E. Wheeler wrote:
> On Jan 3, 2012, at 9:37 AM, Guillaume Lelarge wrote:
>
> > I don't know of any, but if you do write one, please, submit it to
> > check_postgres.pl.
>
> Yeah, I’m a committer on check_postgres.pl, so the other check_postgres.pl
> folks
On Jan 3, 2012, at 9:37 AM, Guillaume Lelarge wrote:
> I don't know of any, but if you do write one, please, submit it to
> check_postgres.pl.
Yeah, I’m a committer on check_postgres.pl, so the other check_postgres.pl
folks think it’s not a good place for it for some reason I can’t imagine right
On Tue, 2012-01-03 at 09:21 -0800, David E. Wheeler wrote:
> pgAdmins,
>
> Anyone written a Nagios plugin to report pgAgent failures? If not, I expect
> I’ll be writing one, or perhaps submitting one to check_postgres.pl.
>
I don't know of any, but if you do write one, please, submit it to
chec
pgAdmins,
Anyone written a Nagios plugin to report pgAgent failures? If not, I expect
I’ll be writing one, or perhaps submitting one to check_postgres.pl.
Thanks,
David
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.
On Jan 3, 2012, at 1:07 AM, Dave Page wrote:
>> Which is great. However, the /var/log/pgagent_91.log file is still empty.
>> Should I take that to mean that job output is not logged there, but only
>> errors from pgagent itself?
>
> Yes, it's really just a debug log.
Gotcha, thank you.
David
On Mon, Jan 2, 2012 at 7:04 PM, David E. Wheeler wrote:
> On Dec 20, 2011, at 6:00 PM, David E. Wheeler wrote:
>
>>> Oh, OK. We use popen() to execute the task on *nix, and that only
>>> reads STDOUT, so you should handle redirection in your script. I did
>>> spend some time look at this a few yea
