[check_postgres] check_postgres_query_time - Getting "invalid query returned" more often now

[Greg Sabino Mullane]

> I'm still getting these perhaps 25% of the time.  I've tried using the
> debug options, but what I can't get my head around is why it's doing the
> following when it gives the invalid query.
> 
> Starting run_command with "SELECT setting FROM pg_settings WHERE name =
> 'server_version'"

It does this when a query goes wrong to make sure that the version of
Postgres you are using supports the current action. If it doesn't, it can
give a better error message.

> With --debugoutput=u the check tends to return 0 / OK all the time,
> however it does sometimes output the following:
> 

Try adding this at line 2848, so maybe we can see the database error that
is getting thrown:

if (!defined $db->{slurp}) {
  add_unknown;
}

> perl check_postgres_query_time --warning='3 minutes' --critical='5
> minutes' -db=SEE -H=localhost --debugoutput=u

Perhaps try with --debugoutput=a which will make all responses a little
more verbose, but not excessively so.

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
Url : https://mail.endcrypt.com/pipermail/check_postgres/attachments/20081008/cc8c4ffb/signature.bin