gs_ctl build 时报错FATAL: Forbid remote connection with initial user

适用范围

gs_ctl build 时报错FATAL:  Forbid remote connection with initial user.

问题概述

MogDB 3.0.0版本手动增加备库，在主库和新备库的postgresql.conf中增加了replconninfo后执行gs_ctl build时报错FATAL:  Forbid remote connection with initial user.

[omm@node3 data]$ gs_ctl build -D /mogdb/data/ -b full -M standby
[2024-02-29 10:37:14.804][63977][][gs_ctl]: gs_ctl full build ,datadir is /mogdb/data
waiting for server to shut down.... done
server stopped
[2024-02-29 10:37:15.817][63977][][gs_ctl]: current workdir is (/mogdb/data).
[2024-02-29 10:37:15.817][63977][][gs_ctl]: fopen build pid file "/mogdb/data/gs_build.pid" success
[2024-02-29 10:37:15.817][63977][][gs_ctl]: fprintf build pid file "/mogdb/data/gs_build.pid" success
[2024-02-29 10:37:15.818][63977][][gs_ctl]: fsync build pid file "/mogdb/data/gs_build.pid" success
[2024-02-29 10:37:15.819][63977][][gs_ctl]: set gaussdb state file when full build build:db state(BUILDING_STATE), server mode(STANDBY_MODE), build mode(FULL_BUILD).
[2024-02-29 10:37:15.830][63977][dn_6001][gs_ctl]: build connection to 192.168.75.142 failed cause FATAL:  Forbid remote connection with initial user.
FATAL:  Forbid remote connection with initial user.
.
[2024-02-29 10:37:15.830][63977][dn_6001][gs_ctl]: build try host(192.168.75.142) port(26001) failed
[2024-02-29 10:37:15.830][63977][dn_6001][gs_ctl]: could not connect to server.
[2024-02-29 10:37:15.830][63977][dn_6001][gs_ctl]: full build failed(/mogdb/data).
[omm@node3 data]$

问题原因

初始用户不支持远程登录，build时pg_hba.conf缺少配置导致在build时备库通过26000端口使用初始用户远程连接备库。

解决方案

在pg_hba.conf中增加host    replication     omm        192.168.75.144/32            trust

[omm@node1 ~]$ cat /mogdb/data/pg_hba.conf
# PostgreSQL Client Authentication Configuration File
# ===================================================
#
# Refer to the "Client Authentication" section in the PostgreSQL
# documentation for a complete description of this file.  A short
# synopsis follows.
#
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access.  Records take one of these forms:
#
# local      DATABASE  USER  METHOD  [OPTIONS]
# host       DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
# hostssl    DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
# hostnossl  DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
#
# (The uppercase items must be replaced by actual values.)
#
# The first field is the connection type: "local" is a Unix-domain
# socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
# "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
# plain TCP/IP socket.
#
# DATABASE can be "all", "sameuser", "samerole", "replication", a
# database name, or a comma-separated list thereof. The "all"
# keyword does not match "replication". Access to replication
# must be enabled in a separate record (see example below).
#
# USER can be "all", a user name, a group name prefixed with "+", or a
# comma-separated list thereof.  In both the DATABASE and USER fields
# you can also write a file name prefixed with "@" to include names
# from a separate file.
#
# ADDRESS specifies the set of hosts the record matches.  It can be a
# host name, or it is made up of an IP address and a CIDR mask that is
# an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that
# specifies the number of significant bits in the mask.  A host name
# that starts with a dot (.) matches a suffix of the actual host name.
# Alternatively, you can write an IP address and netmask in separate
# columns to specify the set of hosts.  Instead of a CIDR-address, you
# can write "samehost" to match any of the server's own IP addresses,
# or "samenet" to match any address in any subnet that the server is
# directly connected to.
#
# METHOD can be "trust", "reject", "md5", "sha256" or "cert".
# "sha256" is preferred since

#
# OPTIONS are a set of options for the authentication in the format
# NAME=VALUE.  The available options depend on the different
# authentication methods -- refer to the "Client Authentication"
# section in the documentation for a list of which options are
# available for which authentication methods.
#
# Database and user names containing spaces, commas, quotes and other
# special characters must be quoted.  Quoting one of the keywords
# "all", "sameuser", "samerole" or "replication" makes the name lose
# its special character, and just match a database or username with
# that name.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal.  If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect.  You can
# use "pg_ctl reload" to do that.

# Put your actual configuration here
# ----------------------------------
#
# If you want to allow non-local connections, you need to add more
# "host" records.  In that case you will also need to make PostgreSQL
# listen on a non-local interface via the listen_addresses
# configuration parameter, or via the -i or -h command line switches.
#
# NOTICE:
# ----------------------------------
#
# When you configure this file, please configure it from top to bottom,
# higher priority needs to be configured in front.

# CAUTION: Configuring the system for local "trust" authentication
# allows any local user to connect as any PostgreSQL user, including
# the database sysadmin.  If you do not trust all your local users,
# use another authentication method.


# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
local   all             all                                     trust
host    all    omm    192.168.75.142/32    trust
host    all    omm    192.168.75.143/32    trust
host    all    omm    192.168.75.144/32    trust
# IPv4 local connections:
host    all             all             127.0.0.1/32            trust
host    all    all    192.168.75.142/32    sha256
host    all    all    192.168.75.143/32    sha256
host    all    all    192.168.75.144/32    sha256
# IPv6 local connections:
host    all             all             ::1/128                 trust
# Allow replication connections from localhost, by a user with the
# replication privilege.
#local   replication     omm                                trust
#host    replication     omm        127.0.0.1/32            trust
#host    replication     omm        ::1/128                 trust
host    replication     omm        192.168.75.144/32            trust
[omm@node1 ~]$