When reloading the pg_hba.conf after making a change to the file, the user gets the following error messages:
2015-06-16 11:02:32.753451 AST,,,p87538,th-674248928,,,,0,,,seg-1,,,,,"LOG","00000","received SIGHUP, reloading configuration files",,,,,,,0,,"postmaster.c",4316, 2015-06-16 11:02:32.755368 AST,,,p87538,th-674248928,,,,0,,,seg-1,,,,,"LOG","F0000","invalid authentication method ""0.0.0.0/0""",,,,,"line 103 of configuration file ""/data/master/gpseg-1/pg_hba.conf""",,0,,"hba.c",1095, 2015-06-16 11:02:32.756075 AST,,,p87538,th-674248928,,,,0,,,seg-1,,,,,"WARNING","01000","pg_hba.conf not reloaded",,,,,,,0,,"postmaster.c",4345,
The above error message is a result of the following entry in the pg_hba.conf file:
local all gpadmin 0.0.0.0/0 md5
This issue occurs for a local connection to the GPDB. The user cannot specify an IP address in the pg_hba.conf file for an entry for local.
The authentication method can be "ident, trust or md5". The local host does not use an IP address when trying to connect to the database, it uses a socket only.
The correct entry for a local connection can be any of the following:
local all gpadmin ident local all gpadmin trust local all gpadmin md5