gpinitsystem failed with error "Failed to substitute ##port"
searchcancel
gpinitsystem failed with error "Failed to substitute ##port"
book
Article ID: 295654
calendar_today
Updated On: 09-13-2019
Products
VMware Tanzu Greenplum
Issue/Introduction
Symptoms: gpinitsystemfails while running. This error can be found in the gpAdminLogs directory report below:
copying template1 to postgres ... 20190310:19:59:55:gpcreateseg.sh:cmtolubcmgpmh01:gpadmin-[FATAL]:-Failed to substitute ##port in /xxx/dataxx/primary/gpsegxx/postgresql.conf on hostxxx Script Exiting!
20190310:19:59:55:gpcreateseg.hostxxx:gpadmin-[FATAL]:-Failed to insert listen_addresses='*' in /xxx/dataxxx/primary/gpsegxxx/postgresql.conf on hostxxx Script Exiting!
20190310:19:59:56:gpcreateseg.hostxxx:gpadmin-[FATAL]:-Failed to substitute #listen_addresses in /xxx/dataxx/primary/gpsegxx/postgresql.conf on cmtolubcmgpsg01-01 Script Exiting!
20190310:19:59:56:gpcreateseg.hostxxx:gpadmin-[FATAL]:-Failed to substitute #listen_addresses in /xxx/dataxx/primary/gpsegxx/postgresql.conf on hostxxx Script Exiting!
20190310:19:59:58:001826 gpcreateseg.hostxxx:gpadmin-[FATAL][14]:-Failed Update pg_hba.conf for master standby address xxx:xxx:xxx
Environment
Cause
When one host is running more than 10 instances, it will need a larger number of SSH connections than the Operating System (OS) default amount.
If the MaxStartups parameter in /etc/ssh/sshd_config is configured to use the default value, it will cause several errors.
Resolution
Add the setting below to the /etc/ssh/sshd_config file at all hosts.