greenplum的主机名更改导致无法启动问题解决
2024-05-13 02:46:43
查看报错日志
[gpadmin@mydb_master ~]$ cat /home/gpadmin/gpAdminLogs/gpstart_20210224.log
20210224:18:27:05:007350 gpstart:mydb_master:gpadmin-[INFO]:-----------------------------------------------------
20210224:18:27:05:007350 gpstart:mydb_master:gpadmin-[INFO]:- Successful segment starts = 0
20210224:18:27:05:007350 gpstart:mydb_master:gpadmin-[WARNING]:-Failed segment starts = 1 <<<<<<<<
20210224:18:27:05:007350 gpstart:mydb_master:gpadmin-[INFO]:- Skipped segment starts (segments are marked down in configuration) = 0
20210224:18:27:05:007350 gpstart:mydb_master:gpadmin-[INFO]:-----------------------------------------------------
20210224:18:27:05:007350 gpstart:mydb_master:gpadmin-[INFO]:-Successfully started 0 of 1 segment instances <<<<<<<<
20210224:18:27:05:007350 gpstart:mydb_master:gpadmin-[INFO]:-----------------------------------------------------
20210224:18:27:05:007350 gpstart:mydb_master:gpadmin-[WARNING]:-Segment instance startup failures reported
20210224:18:27:05:007350 gpstart:mydb_master:gpadmin-[WARNING]:-Failed start 1 of 1 segment instances <<<<<<<<
20210224:18:27:05:007350 gpstart:mydb_master:gpadmin-[WARNING]:-Review /home/gpadmin/gpAdminLogs/gpstart_20210224.log
20210224:18:27:05:007350 gpstart:mydb_master:gpadmin-[INFO]:-----------------------------------------------------
20210224:18:27:05:007350 gpstart:mydb_master:gpadmin-[INFO]:-Commencing parallel segment instance shutdown, please wait...
20210224:18:27:05:007350 gpstart:mydb_master:gpadmin-[ERROR]:-gpstart error: Do not have enough valid segments to start the array.
20210224:18:29:07:002358 gpstart:mydb_master:gpadmin-[INFO]:-Starting gpstart with args:
20210224:18:29:07:002358 gpstart:mydb_master:gpadmin-[INFO]:-Gathering information and validating the environment...
20210224:18:29:07:002358 gpstart:mydb_master:gpadmin-[INFO]:-Greenplum Binary Version: 'postgres (Greenplum Database) 6.10.0 build commit:cced3a78d1a0650ba21205438955d2df06644bc8'
20210224:18:29:07:002358 gpstart:mydb_master:gpadmin-[INFO]:-Greenplum Catalog Version: '301908232'
20210224:18:29:07:002358 gpstart:mydb_master:gpadmin-[INFO]:-Starting Master instance in admin mode
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:-Obtaining Segment details from master...
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:-Setting new master era
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:-Master Started...
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:-Shutting down master
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:---------------------------
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:-Master instance parameters
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:---------------------------
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:-Database = template1
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:-Master Port = 5432
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:-Master directory = /data/gpdata/gpmaster/gpseg-1
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:-Timeout = 600 seconds
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:-Master standby = Off
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:---------------------------------------
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:-Segment instances that will be started
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:---------------------------------------
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:- Host Datadir Port
20210224:18:29:08:002358 gpstart:mydb_master:gpadmin-[INFO]:- mydb1 /data/gpdata/gpdatap1/gpseg0 40000
20210224:18:29:15:002358 gpstart:mydb_master:gpadmin-[WARNING]:-Ping to host: 'mydb1' FAILED
20210224:18:29:15:002358 gpstart:mydb_master:gpadmin-[WARNING]:-Ping to host: 'mydb1' FAILED
20210224:18:29:15:002358 gpstart:mydb_master:gpadmin-[WARNING]:-Skipping startup of segdb on mydb1 directory /data/gpdata/gpdatap1/gpseg0 Ping Failed <<<<<<
20210224:18:29:15:002358 gpstart:mydb_master:gpadmin-[ERROR]:-No segment started for content: 0.
20210224:18:29:15:002358 gpstart:mydb_master:gpadmin-[INFO]:-dumping success segments: []
20210224:18:29:15:002358 gpstart:mydb_master:gpadmin-[INFO]:-----------------------------------------------------
20210224:18:29:15:002358 gpstart:mydb_master:gpadmin-[INFO]:-DBID:2 FAILED host:'mydb1' datadir:'/data/gpdata/gpdatap1/gpseg0' with reason:'Failed to Ping on host: mydb1'
20210224:18:29:15:002358 gpstart:mydb_master:gpadmin-[INFO]:-----------------------------------------------------
分析问题
我的master节点名称是 mydb_master，一个segment节点是 mydb_segment1，但是启动的时候，日志中 ping 的主机名却是 mydb1，说明gp内部的节点配置出了问题；
解决问题
- 以管理员模式启动数据库；
[gpadmin@mydb_master etc]$ gpstart -m
- 登陆管理数据库；
- 查看节点配置文件；
- 更改系统表模式为可以修改；
- 更新hostname和address；
- 更改系统表模式为不能修改；
- 退出；
[gpadmin@mydb_master etc]$ PGOPTIONS="-c gp_session_role=utility" psql -d postgres
postgres=# select * from gp_segment_configuration;dbid | content | role | preferred_role | mode | status | port | hostname | address | datadir
------+---------+------+----------------+------+--------+-------+---------------+---------+-------------------------------1 | -1 | p | p | n | u | 5432 | mydb_master | mydb | /data/gpdata/gpmaster/gpseg-12 | 0 | p | p | n | u | 40000 | mydb_segment1 | mydb1 | /data/gpdata/gpdatap1/gpseg0
(2 rows)
postgres=# set allow_system_table_mods='true';
SET
postgres=# update gp_segment_configuration set hostname = 'mydb_master',address = 'mydb_master' where dbid = 1;
UPDATE 1
postgres=# update gp_segment_configuration set hostname = 'mydb_segment1',address = 'mydb_segment1' where dbid = 2;
UPDATE 1
postgres=# set allow_system_table_mods='false';
SET
postgres=# \q
重启数据库
[gpadmin@mydb_master etc]$ gpstop
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:-Starting gpstop with args:
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:-Gathering information and validating the environment...
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:-Obtaining Segment details from master...
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:-Greenplum Version: 'postgres (Greenplum Database) 6.10.0 build commit:cced3a78d1a0650ba21205438955d2df06644bc8'
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:---------------------------------------------
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:-Master instance parameters
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:---------------------------------------------
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:- Master Greenplum instance process active PID = 7521
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:- Database = template1
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:- Master port = 5432
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:- Master directory = /data/gpdata/gpmaster/gpseg-1
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:- Shutdown mode = smart
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:- Timeout = 120
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:- Shutdown Master standby host = Off
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:---------------------------------------------
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:-Segment instances that will be shutdown:
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:---------------------------------------------
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:- Host Datadir Port Status
20210224:18:53:10:007825 gpstop:mydb_master:gpadmin-[INFO]:- mydb_segment1 /data/gpdata/gpdatap1/gpseg0 40000 uContinue with Greenplum instance shutdown Yy|Nn (default=N):
> y
20210224:18:53:11:007825 gpstop:mydb_master:gpadmin-[INFO]:-Commencing Master instance shutdown with mode='smart'
20210224:18:53:11:007825 gpstop:mydb_master:gpadmin-[INFO]:-Master segment instance directory=/data/gpdata/gpmaster/gpseg-1
20210224:18:53:11:007825 gpstop:mydb_master:gpadmin-[INFO]:-Stopping master segment and waiting for user connections to finish ...
server shutting down
20210224:18:53:12:007825 gpstop:mydb_master:gpadmin-[INFO]:-Attempting forceful termination of any leftover master process
20210224:18:53:12:007825 gpstop:mydb_master:gpadmin-[INFO]:-Terminating processes for segment /data/gpdata/gpmaster/gpseg-1
20210224:18:53:12:007825 gpstop:mydb_master:gpadmin-[INFO]:-No standby master host configured
20210224:18:53:12:007825 gpstop:mydb_master:gpadmin-[INFO]:-Targeting dbid [2] for shutdown
20210224:18:53:12:007825 gpstop:mydb_master:gpadmin-[INFO]:-Commencing parallel segment instance shutdown, please wait...
20210224:18:53:12:007825 gpstop:mydb_master:gpadmin-[INFO]:-0.00% of jobs completed
20210224:18:53:13:007825 gpstop:mydb_master:gpadmin-[INFO]:-100.00% of jobs completed
20210224:18:53:13:007825 gpstop:mydb_master:gpadmin-[INFO]:-----------------------------------------------------
20210224:18:53:13:007825 gpstop:mydb_master:gpadmin-[INFO]:- Segments stopped successfully = 1
20210224:18:53:13:007825 gpstop:mydb_master:gpadmin-[INFO]:- Segments with errors during stop = 0
20210224:18:53:13:007825 gpstop:mydb_master:gpadmin-[INFO]:-----------------------------------------------------
20210224:18:53:13:007825 gpstop:mydb_master:gpadmin-[INFO]:-Successfully shutdown 1 of 1 segment instances
20210224:18:53:13:007825 gpstop:mydb_master:gpadmin-[INFO]:-Database successfully shutdown with no errors reported
20210224:18:53:13:007825 gpstop:mydb_master:gpadmin-[INFO]:-Cleaning up leftover gpmmon process
20210224:18:53:13:007825 gpstop:mydb_master:gpadmin-[INFO]:-No leftover gpmmon process found
20210224:18:53:13:007825 gpstop:mydb_master:gpadmin-[INFO]:-Cleaning up leftover gpsmon processes
20210224:18:53:13:007825 gpstop:mydb_master:gpadmin-[INFO]:-No leftover gpsmon processes on some hosts. not attempting forceful termination on these hosts
20210224:18:53:13:007825 gpstop:mydb_master:gpadmin-[INFO]:-Cleaning up leftover shared memory
[gpadmin@mydb_master etc]$ gpstart
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Starting gpstart with args:
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Gathering information and validating the environment...
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Greenplum Binary Version: 'postgres (Greenplum Database) 6.10.0 build commit:cced3a78d1a0650ba21205438955d2df06644bc8'
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Greenplum Catalog Version: '301908232'
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Starting Master instance in admin mode
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Obtaining Segment details from master...
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Setting new master era
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Master Started...
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Shutting down master
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:---------------------------
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Master instance parameters
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:---------------------------
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Database = template1
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Master Port = 5432
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Master directory = /data/gpdata/gpmaster/gpseg-1
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Timeout = 600 seconds
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Master standby = Off
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:---------------------------------------
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:-Segment instances that will be started
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:---------------------------------------
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:- Host Datadir Port
20210224:18:53:17:007928 gpstart:mydb_master:gpadmin-[INFO]:- mydb_segment1 /data/gpdata/gpdatap1/gpseg0 40000Continue with Greenplum instance startup Yy|Nn (default=N):
> y
20210224:18:53:20:007928 gpstart:mydb_master:gpadmin-[INFO]:-Commencing parallel segment instance startup, please wait...
20210224:18:53:21:007928 gpstart:mydb_master:gpadmin-[INFO]:-Process results...
20210224:18:53:21:007928 gpstart:mydb_master:gpadmin-[INFO]:-----------------------------------------------------
20210224:18:53:21:007928 gpstart:mydb_master:gpadmin-[INFO]:- Successful segment starts = 1
20210224:18:53:21:007928 gpstart:mydb_master:gpadmin-[INFO]:- Failed segment starts = 0
20210224:18:53:21:007928 gpstart:mydb_master:gpadmin-[INFO]:- Skipped segment starts (segments are marked down in configuration) = 0
20210224:18:53:21:007928 gpstart:mydb_master:gpadmin-[INFO]:-----------------------------------------------------
20210224:18:53:21:007928 gpstart:mydb_master:gpadmin-[INFO]:-Successfully started 1 of 1 segment instances
20210224:18:53:21:007928 gpstart:mydb_master:gpadmin-[INFO]:-----------------------------------------------------
20210224:18:53:21:007928 gpstart:mydb_master:gpadmin-[INFO]:-Starting Master instance mydb_master directory /data/gpdata/gpmaster/gpseg-1
20210224:18:53:21:007928 gpstart:mydb_master:gpadmin-[INFO]:-Command pg_ctl reports Master mydb_master instance active
20210224:18:53:21:007928 gpstart:mydb_master:gpadmin-[INFO]:-Connecting to dbname='template1' connect_timeout=15
20210224:18:53:21:007928 gpstart:mydb_master:gpadmin-[INFO]:-No standby master configured. skipping...
20210224:18:53:21:007928 gpstart:mydb_master:gpadmin-[INFO]:-Database successfully started
参考文章
Deepgreen/Greenplum删除节点步骤
greenplum的主机名更改导致无法启动问题解决相关推荐
- 更改主机名后mysql无法启动_主机名变更导致MySql启动失败
问题描述 mySql 启动时,报错ERROR! The server quit without updating PID file (/usr/local/var/mysql/bogon.pid) 解 ...
- 因主机名更改造成oracle控制台登录错误：ora-12545，ora-12541
http://blog.csdn.net/rookie_one/archive/2006/11/30/1421781.aspx 昨天临下班因嫌自己的计算机名太丑,就改成了别的.(当初装系统的时候太匆忙 ...
- 在 RHEL or CentOS 7、8 中更改主机名的 4 种方法
要检查主机名,请打开终端并在 CentOS 7/8 中键入 hostname 或 hostnamectl 命令.默认情况下,主机名是 localhost.localdomain.要更改主机名,您可以按 ...
- 修改linux终端中的程序名字,在Ubuntu/Debian/Arch Linux/Fedora/OpenSUSE下更改主机名的方法...
本文教你如何更改Linux计算机主机名(hostname),即在Ubuntu/Debian/Arch Linux/Fedora/OpenSUSE操作系统下更改主机名的方法. 前言 像Linux.BSD ...
- 解决由于DNS解析导致Emacs启动巨慢的问题
小白是Emacs的忠实用户,在CentOS服务器上也要自己编译安装一个Emacs供自己使用.由于使用了很多Emacs的插件,每次启动那是很缓慢的,几乎是5s左右才打开一个文件(让大家误以为服务器配置很 ...
- 域名中主机名是第几个_CentOS7系统如何修改主机名
请关注本头条号,每天坚持更新原创干货技术文章. 如需学习视频,请在微信搜索公众号"智传网优"直接开始自助视频学习 1. 前言 本文将讲解CentOS7系统如何修改主机名. 本教程将 ...
- 关于电脑主机名更改，oracle登录不了的问题
因更改了主机名字而无法连接数据库: ORACLE数据库如果安装后再更改电脑主机名,会导致主机名不同而无法连接数据库,此时就需要更改listener文件中的主机名 路径: Oracle的安装路径-pro ...
- centos nmtui 使用_CentOS7如何修改主机名
1. 前言 本文将讲解CentOS7系统如何修改主机名. 本教程将指导您如何在CentOS 7系统上修改主机名. 默认情况下主机名会在安装CentOS7操作系统时被设置,或者在启动虚拟机时动态分配给实 ...
- docker容器和宿主机的主机名映射失败
一.为什么将 Oracle 部署在 docker容器中 我们首先通过 docker 安装了 oracle11g 版本的 Oracle 数据库--不要问我为什么通过 docker 安装数据库,正确做法或 ...
最新文章
- 跟风Google Brain，Facebook AI研究机构启动见习项目
- Error: Network is unreachable. Reason: couldn‘t connect to server localhost:27017（连接mongodb数据库失败）
- Spring靴子战争包装
- 无线网络共享到CM3计算板调试时 connect: Network is unreachable
- 避免流量高峰期CDN问题的10个方法
- 详解4种微服务框架接入Istio方案
- Linux之scsi网络存储
- comsol 裂隙 耦合_使用COMSOL建立多重连续介质渗流模型
- ubunut16.04 更新python3.6
- Warez 组织的64K 3D动画下载
- Mujoco制作模拟视频
- cygwin安装gcc/g++
- 计算机学院java男默女泪,最新网络用语学习笔记，看了后，男默女泪
- windows 下配置 Nginx 常见问题
- 这是一篇有温度的NLP秋招面经
- 【C语言】C语言实现中文字符(句号，感叹号，问号)的十进制数值
- 数据分析的价值是什么？
- Python中比较好用的PDF模块——发票金额提取
- Jmeter操作数据库详解
- web期末大作业：基于html+css+js制作 学校班级网页制作----校园运动会 4页