原 GreenPlum初始化时一直卡住“Completed restart of Greenplum instance in production mode”，psql postgres 命令也一直卡住，警告Failed to connect to template1

发布日期 2023年11月20日 · 已更新 2024年9月14日  

0    391    2

Tags： 原创故障处理GreenPlum数据库初始化Failed to connect to template1Timeout expired connecting to template1

👉 本文共约483个字，系统预计阅读时间或需2分钟。

显示/隐藏全文目录

目录

• 问题
• 原因1
• 原因2
• 总结
• 参考

问题

[gpadmin@master ~]$ gpinitsystem -c gpconfigs/gpinitsystem_config -h gpconfigs/gpinitsystem_hostfile 20210302:09:48:54:017684 gpinitsystem:master:gpadmin-[INFO]:-Checking configuration parameters, please wait... 20210302:09:48:54:017684 gpinitsystem:master:gpadmin-[INFO]:-Reading Greenplum configuration file gpconfigs/gpinitsystem_config 20210302:09:48:54:017684 gpinitsystem:master:gpadmin-[INFO]:-Locale has not been set in gpconfigs/gpinitsystem_config, will set to default value 20210302:09:48:55:017684 gpinitsystem:master:gpadmin-[INFO]:-Locale set to en_US.utf8 。。。。。。。。。。。。。。。 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:-Process results... 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:----------------------------------------------------- 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:- Successful segment starts = 3 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:- Failed segment starts = 0 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:- Skipped segment starts (segments are marked down in configuration) = 0 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:----------------------------------------------------- 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:-Successfully started 3 of 3 segment instances 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:----------------------------------------------------- 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:-Starting Master instance master directory /home/gpadmin/data/master/gpseg-1 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:-Command pg_ctl reports Master master instance active 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:-Connecting to dbname='template1' connect_timeout=15 20210302:10:02:23:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 1/4 20210302:10:02:38:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 2/4 20210302:10:02:53:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 3/4 20210302:10:03:08:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 4/4 20210302:10:03:08:020392 gpstart:master:gpadmin-[WARNING]:-Failed to connect to template1 20210302:10:03:08:020392 gpstart:master:gpadmin-[INFO]:-No standby master configured. skipping... 20210302:10:03:08:020392 gpstart:master:gpadmin-[INFO]:-Check status of database with gpstate utility 20210302:10:03:09:017684 gpinitsystem:master:gpadmin-[INFO]:-Completed restart of Greenplum instance in production mode

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

[gpadmin@master ~]$ gpinitsystem -c gpconfigs/gpinitsystem_config -h gpconfigs/gpinitsystem_hostfile 20210302:09:48:54:017684 gpinitsystem:master:gpadmin-[INFO]:-Checking configuration parameters, please wait... 20210302:09:48:54:017684 gpinitsystem:master:gpadmin-[INFO]:-Reading Greenplum configuration file gpconfigs/gpinitsystem_config 20210302:09:48:54:017684 gpinitsystem:master:gpadmin-[INFO]:-Locale has not been set in gpconfigs/gpinitsystem_config, will set to default value 20210302:09:48:55:017684 gpinitsystem:master:gpadmin-[INFO]:-Locale set to en_US.utf8 。。。。。。。。。。。。。。。 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:-Process results... 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:----------------------------------------------------- 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:- Successful segment starts = 3 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:- Failed segment starts = 0 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:- Skipped segment starts (segments are marked down in configuration) = 0 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:----------------------------------------------------- 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:-Successfully started 3 of 3 segment instances 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:----------------------------------------------------- 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:-Starting Master instance master directory /home/gpadmin/data/master/gpseg-1 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:-Command pg_ctl reports Master master instance active 20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:-Connecting to dbname='template1' connect_timeout=15 20210302:10:02:23:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 1/4 20210302:10:02:38:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 2/4 20210302:10:02:53:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 3/4 20210302:10:03:08:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 4/4 20210302:10:03:08:020392 gpstart:master:gpadmin-[WARNING]:-Failed to connect to template1 20210302:10:03:08:020392 gpstart:master:gpadmin-[INFO]:-No standby master configured. skipping... 20210302:10:03:08:020392 gpstart:master:gpadmin-[INFO]:-Check status of database with gpstate utility 20210302:10:03:09:017684 gpinitsystem:master:gpadmin-[INFO]:-Completed restart of Greenplum instance in production mode

主要报错：

20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:-Connecting to dbname='template1' connect_timeout=15 20210302:10:02:23:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 1/4 20210302:10:02:38:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 2/4 20210302:10:02:53:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 3/4 20210302:10:03:08:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 4/4 20210302:10:03:08:020392 gpstart:master:gpadmin-[WARNING]:-Failed to connect to template1

1 2 3 4 5 6

20210302:10:02:08:020392 gpstart:master:gpadmin-[INFO]:-Connecting to dbname='template1' connect_timeout=15 20210302:10:02:23:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 1/4 20210302:10:02:38:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 2/4 20210302:10:02:53:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 3/4 20210302:10:03:08:020392 gpstart:master:gpadmin-[WARNING]:-Timeout expired connecting to template1, attempt 4/4 20210302:10:03:08:020392 gpstart:master:gpadmin-[WARNING]:-Failed to connect to template1

原因1

集群中有某个segment节点的防火墙没有关闭，直接关闭该节点的防火墙后原程序会继续执行的。

在某些情况下，防火墙会自动启动，所以会导致我们的GreenPlum安装失败，所以，可以做如下操作：

sed -i s/SELINUX=enforcing/SELINUX=disabled/g /etc/selinux/config setenforce 0 systemctl unmask firewalld.service systemctl start firewalld.service firewall-cmd --add-port=0-65535/tcp --permanent firewall-cmd --add-port=0-65535/udp --permanent firewall-cmd --reload firewall-cmd --list-ports systemctl stop firewalld.service systemctl disable firewalld.service systemctl mask firewalld.service systemctl status firewalld.service

1 2 3 4 5 6 7 8 9 10 11 12 13 14

sed -i s/SELINUX=enforcing/SELINUX=disabled/g /etc/selinux/config setenforce 0 systemctl unmask firewalld.service systemctl start firewalld.service   firewall-cmd --add-port=0-65535/tcp --permanent firewall-cmd --add-port=0-65535/udp --permanent firewall-cmd --reload firewall-cmd --list-ports   systemctl stop firewalld.service systemctl disable firewalld.service systemctl mask  firewalld.service systemctl status firewalld.service

本人提供Oracle(OCP、OCM)、MySQL(OCP)、PostgreSQL(PGCA、PGCE、PGCM)等数据库的培训和考证业务，私聊QQ646634621或微信dbaup66，谢谢！

后续精彩内容已被站长无情隐藏，请输入验证码解锁本文！

验证码：

获取验证码： 请先关注本站微信公众号，然后回复“验证码”，获取验证码。在微信里搜索“AiDBA”或者“dbaup6”或者微信扫描右侧二维码都可以关注本站微信公众号。

相关文章

• gpcc监控不显示内存、cpu等资源
• GreenPlum查询报错could not open file "base/231962/24824104": No such file or directory (seg44 slice2 192.168.163.54:6014 pid=1499766)
• GreenPlum数据库不定时报错interconnect error connection closed prematurely、timed out waiting for response from motion receiver during TCP interconnect teardown
• GreenPlum查询表有数据，但是drop表报错does not exist，vacuumdb也报错
• gpload加载数据报错 ProgrammingError: ERROR: column "relstorage" does not exist（GP7中的pg_class没有relstorage字段）
• gpload加载数据报错 UnboundLocalError: local variable 'has_seq_bool' referenced before assignment
• GreenPlum启动报错ModuleNotFoundError: No module named 'gppylib'
• GreenPlum查询参数报错schema gp_toolkit does not exist
• GreenPlum启动报错could not load library /usr/local/greenplum-db-6.27.0/lib/postgresql/pg_cron.so的故障处理
• GreenPlum严重故障导致不能启库的解决办法（pg_resetxlog重置日志）
• 初始化GreenPlum数据库实例时报错ssh_exchange_identification: connection reset by peer
• GreenPlum查询状态报错 [WARNING]:-could not query segment
• 使用gpmon登陆gpcc报错Error: User gpmon is not allowed to login Command Center.
• GreenPlum启动数据库报错pre-existing shared memory block
• GreenPlum数据库SQL查询卡慢，报错或告警 Interconnect encountered a network error, please check your network
• gprecoverseg恢复GreenPlum的时候报错“gprecoverseg failed(Reason ''ascii' codec can't encode character u'\u2018' in positition 229: ordinal not in range(128)'）exiting”
• GreenPlum查询报错failed to initialize zstd stream: Allocation error : not enough memory
• GreenPlum在何时会发生自动故障切换、节点漂移及如何排查（OOM）
• GreenPlum空间满不能启动的处理办法
• GreenPlum报错ERROR: Canceling query because of high VMEM usage 或 ERROR: Out of memory Vmem limit reached

打赏赞(2)分享

标签： 原创故障处理GreenPlum数据库初始化Failed to connect to template1Timeout expired connecting to template1

小麦苗

学习或考证，均可联系麦老师，请加微信db_bao或QQ646634621

• 下一篇 崖山YashanDB数据库巡检脚本
• 上一篇 GreenPlum在删除数据文件后如何恢复

您可能还喜欢...

• 0

  在Docker中快速体验CBDB数据库

  2024年7月8日

   由 小麦苗 · Published 2024年7月8日

   

  0    140    2
• 0

  【MOS】11gR2 installation failed with Error in CreateOUIProcess(): 13 : Permission denied (Doc ID 1671840.1)

  2021年7月14日

   由 小麦苗 · Published 2021年7月14日

  · 已更新 2021年7月14日  

  0    991    4
• 0

  IT行业疑难杂症终极解决之道

  2021年12月1日

   由 小麦苗 · Published 2021年12月1日 · Last modified 2024年10月30日

  · 已更新 2024年10月30日  

  0    1622    28