Why is the agent showing an error in my postgres discovery about authentication failed for user “postgres”?
The Postgres plugin attempts to log into the database server using the username and password of “postgres”. In many installations, this is a default superuser and will work. However, it is also possible that this login could fail for a number of reasons: • The “postgres” user has been deleted. • The password for the “postgres” user has been changed. • On Linux, the administrative login has been set to “ident sameuser”. In many cases, this can be alleviated as follows: • Inventory the discovered Postgres resource. Its availability will show as down and it will not find any child resources. • Navigate to the inventory tab for the Postgres resource. • Under Connection Properties, click the Edit button. • Change the “role name” and “role password” fields to reflect a valid super user account on the Postgres instance. Additionally, Postgres may need to be changed on Linux systems to allow password based logins (i.e. “md5” v. “ident sameuser” settings in the pg_hba.conf file). Consult the Po
Related Questions
- Why do I get a message like "Failed to authenticate client as Postgres user using unknown authentication type:be_recvauth: unrecognized message type: 65536" when I try to connect to a datasource?
- Why is the agent showing an error in my PostgreSQL discovery about authentication failed for user "postgres"?
- Why is the agent showing an error in my postgres discovery about authentication failed for user "postgres"?
