-
제목
"No pg_hba.conf entry" connection error in PostgreSQL agent -
설명
The PostgreSQL agent cannot monitor due to the following error
No pg_hba.conf entry - FATAL: no pg_hba.conf entry for host "host", user "user"…
-
원인
The pg_hba.conf file is the authentication gateway to the PostgreSQL server. Users must be specified in this file in order to connect to the server. -
해결 방안
The entry for the user can be in several different formats, but the important thing to remember is that the user must be able to connect from the agent location and that it should be allowed to connect to all databases. Options like SSL and auth-method can be set at the discretion of the client, though generally for a POC, it’s easiest to not require SSL and use either “trust” or “md5” as the auth-method. More information on the pga_hba.conf file can be found:
https://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html
Typically this issue is related to SSL settings in the PostgreSQL agent in which changing the SSL mode to preferred and unchecking the "use java truststore" checkbox resolves the issue.
For PostgreSQL on Amazon RDS
It is recommended to try using SSL mode = required in the Agent Status Properties for the PostgreSQL agent.
For PostgreSQL on Azure Flexible Server
By default the PostgreSQL on Azure Flexible server always has SSL turned on at the Azure level so using the SSL mode = preferred and turning off the "use truststore checkbox" has been found to work.
Note: Connection errors may appear with an IPv6 address in the connection error within the database agent log like this. This can happen even though the host and FglAM both use IPV4 only.
Caused by: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "2001:0db8:85a3:0000:0000:8a2e:0370:7334", user "TESTUSER", database "postgres", no encryption
Note: (2001:0db8:85a3:0000:0000:8a2e:0370:7334 is not a real IPV6 address, this is only used as an example)