PostgreSQL has been paging for three days



7 years ago
4 years ago


(Reporter: laura, Assigned: scabral)





7 years ago
Every couple of minutes for the last couple of days (starting 6/1 at 3.53am ET) nagios has paged on all of the PostgreSQL monitors on Socorro, as follows:

ERROR: Password for user nagiosdaemon:

While this doesn't sound like a horrible problem, the reason this is critical is that it means we can't see any real problems with PostgreSQL, so it's effectively been unmonitored all weekend.   

The concerning thing is that 50 or so minutes earlier on Friday, we were getting real pages ("Could not find a suitable psql executable"), for which I also don't know the root cause.

If there's a maintenance bug for around that time window, I don't think I'm cced on it - if there is one, please add me.

Comment 1

7 years ago
Taking this for now - I've paged mpressman.
Assignee: server-ops-database → scabral

Comment 2

7 years ago
I'll note that shows that master01 is all green.

Also, here's a sample of the page from Laura - so it *is* coming from phx nagios...

Subject: 	** PROBLEM alert - Connection is UNKNOWN **
Date: 	Sun, 03 Jun 2012 07:59:33 -0700
From: (nagios)

***** Nagios  *****

Notification Type: PROBLEM

Service: PostgreSQL Connection

Date/Time: 06-03-2012 07:59:33

Additional Info:

ERROR: Password for user nagiosdaemon:
I also worked on this with rhelmer on friday and was able to manually connect from nagios to tp-socorro01-master01 just fine as nagiosdaemon. I think we need to give this to someone who knows about nagios as to why this is alerting, but not showing the alerts in the system

Comment 4

7 years ago
Thanx, Matt.
The for socorro is the same as the for the general postgres check

Comment 6

7 years ago
Indeed, this is the URL that shows the problems:

And there was already another ticket open for this:

Comment 7

7 years ago
I think I found the problem - the nagios check doesn't specify a password for the nagiosdaemon user. On the old phx monitoring system, there was a .pgpass file in the nagios user's homedir. I've copied that and the permissions, so hopefully that will fix it (I have to wait a few minutes for the next check to go).
sheeri: nice catch!

Comment 9

7 years ago
Well, you did the first steps - make sure that the nagios user could connect with the right password. So that made me think, "what password is the nagiosdaemon user *trying* to use, and why would it be different from one nagios to the next". I'm familiar with Nagios, and our setup doesn't have any differences, so it had to be that somehow magically one machine used a password and the other didn't. MySQL has .my.cnf files, so I figured pg might have something similar....


2 of the 4 paging checks have gone green, I'll wait until they're all green to close this ticket.
See Also: → bug 758856

Comment 10

7 years ago
Closing, it was the .pgpass file that fixed it.

are all green now.
Last Resolved: 7 years ago
Resolution: --- → FIXED

Comment 11

7 years ago
Thanks guys!
Whoops, sorry I didn't realize this was alerting laura! I set this up in -dev on Fri and had opened Bug 760596 to grant access. Had no idea about .pgpass, sorry again!

Comment 13

7 years ago
It was sending to an e-mail alias, so it wasn't actually paging anyone (but it should have...that's a matter for another ticket).
Product: → Data & BI Services Team
You need to log in before you can comment on or make changes to this bug.