Greenplum初始化数据库时出现gpadmin-[ERROR]:-gpstart error: Do not have enough valid segments to start the arr

启动初始化greenplum数据库报错信息如下所示

[gpadmin@mdw gpAdminLogs]$ gpstart
20181018:01:09:27:043309 gpstart:mdw:gpadmin-[INFO]:-Starting gpstart with args:
20181018:01:09:27:043309 gpstart:mdw:gpadmin-[INFO]:-Gathering information and validating the environment...
20181018:01:09:27:043309 gpstart:mdw:gpadmin-[INFO]:-Greenplum Binary Version: 'postgres (Greenplum Database) 5.11.0 build commit:6f447c24554134df0c1d473e63e0124e7ee6de6b'
20181018:01:09:27:043309 gpstart:mdw:gpadmin-[INFO]:-Greenplum Catalog Version: '301705051'
20181018:01:09:27:043309 gpstart:mdw:gpadmin-[INFO]:-Starting Master instance in admin mode
20181018:01:09:28:043309 gpstart:mdw:gpadmin-[INFO]:-Obtaining Greenplum Master catalog information
20181018:01:09:28:043309 gpstart:mdw:gpadmin-[INFO]:-Obtaining Segment details from master...
20181018:01:09:28:043309 gpstart:mdw:gpadmin-[INFO]:-Setting new master era
20181018:01:09:28:043309 gpstart:mdw:gpadmin-[INFO]:-Master Started...
20181018:01:09:28:043309 gpstart:mdw:gpadmin-[INFO]:-Shutting down master
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:---------------------------
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:-Master instance parameters
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:---------------------------
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:-Database                 = template1
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:-Master Port              = 5432
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:-Master directory         = /home/gpadmin/masterdata/gpseg-1
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:-Timeout                  = 600 seconds
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:-Master standby           = Off
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:---------------------------------------
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:-Segment instances that will be started
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:---------------------------------------
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:-   Host   Datadir                             Port
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:-   mdw    /home/gpadmin/segmentdata1/gpseg0   33000
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:-   mdw    /home/gpadmin/segmentdata2/gpseg1   33001
20181018:01:09:30:043309 gpstart:mdw:gpadmin-[INFO]:-   mdw    /home/gpadmin/segmentdata3/gpseg2   33002Continue with Greenplum instance startup Yy|Nn (default=N):
> y
20181018:01:09:32:043309 gpstart:mdw:gpadmin-[INFO]:-Commencing parallel segment instance startup, please wait...
.
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-Process results...
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[ERROR]:-No segment started for content: 0.
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-dumping success segments: []
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-----------------------------------------------------
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-DBID:2  FAILED  host:'mdw' datadir:'/home/gpadmin/segmentdata1/gpseg0' with reason:'cmd had rc=255 completed=True halted=Falsestdout=''stderr='/etc/ssh/ssh_config: line 69: Bad configuration option: clientaliveinterval
/etc/ssh/ssh_config: line 70: Bad configuration option: clientalivecountmax
/etc/ssh/ssh_config: terminating, 2 bad configuration options
''
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-DBID:3  FAILED  host:'mdw' datadir:'/home/gpadmin/segmentdata2/gpseg1' with reason:'cmd had rc=255 completed=True halted=Falsestdout=''stderr='/etc/ssh/ssh_config: line 69: Bad configuration option: clientaliveinterval
/etc/ssh/ssh_config: line 70: Bad configuration option: clientalivecountmax
/etc/ssh/ssh_config: terminating, 2 bad configuration options
''
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-DBID:4  FAILED  host:'mdw' datadir:'/home/gpadmin/segmentdata3/gpseg2' with reason:'cmd had rc=255 completed=True halted=Falsestdout=''stderr='/etc/ssh/ssh_config: line 69: Bad configuration option: clientaliveinterval
/etc/ssh/ssh_config: line 70: Bad configuration option: clientalivecountmax
/etc/ssh/ssh_config: terminating, 2 bad configuration options
''
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-----------------------------------------------------20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-----------------------------------------------------
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-   Successful segment starts                                            = 0
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[WARNING]:-Failed segment starts                                                = 3   <<<<<<<<
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-   Skipped segment starts (segments are marked down in configuration)   = 0
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-----------------------------------------------------
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-Successfully started 0 of 3 segment instances <<<<<<<<
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-----------------------------------------------------
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[WARNING]:-Segment instance startup failures reported
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[WARNING]:-Failed start 3 of 3 segment instances <<<<<<<<
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[WARNING]:-Review /home/gpadmin/gpAdminLogs/gpstart_20181018.log
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-----------------------------------------------------
20181018:01:09:33:043309 gpstart:mdw:gpadmin-[INFO]:-Commencing parallel segment instance shutdown, please wait...
.
20181018:01:09:34:043309 gpstart:mdw:gpadmin-[ERROR]:-gpstart error: Do not have enough valid segments to start the array.

报错信息指示到/etc/ssh/ssh_config,错误字段为clientaliveinterval和clientalivecountmax，网上很多信息都是将这两个字段的信息改小，实际不用，只需要将这两个字段直接注释掉即可，同样在/etc/ssh/sshd_config文件中这两个字段同样也是被注释掉的。

Greenplum初始化数据库时出现gpadmin-[ERROR]:-gpstart error: Do not have enough valid segments to start the arr相关推荐

关于初始化数据库时报错及解决办法（常见故障整理）
在初始化数据库时使用如下命令: [root@localhost mysql]# bin/mysqld \ --initialize-insecure \ --user=mysql \ --basedi ...
初始化MySQL时可能遇到的问题
之前自己第一次初始化数据库时一切顺利,基本过程也已经记录在这里. 然而今天换了个环境重新配置数据库的时候,出现了许许多多的问题.趁自己还记得,简单做一下记录. 1 Install时出错在输入指令 m ...
如何在Mysql的Docker容器启动时初始化数据库
1.前言 Docker在开发中使用的越来越多了,最近搞了一个Spring Boot应用,为了方便部署将Mysql也放在Docker中运行.那么怎么初始化 SQL脚本以及数据呢? 我这里有两个传统方案. ...
docker mysql数据库初始化_如何在Mysql的Docker容器启动时初始化数据库
1.前言 Docker在开发中使用的越来越多了,最近搞了一个Spring Boot应用,为了方便部署将Mysql也放在Docker中运行.那么怎么初始化 SQL脚本以及数据呢? 我这里有两个传统方案. ...
Java初始化VM时出错怎么办_异常 - 虚拟机初始化错误 - Error occurred during initialization of VM...
1 环境配置信息 1.1 服务器配置信息服务器是物理机, 配置信息如下: CPU型号 CPU个数 CPU核数 CPU线程数内存 Intel(R) Xeon(R) CPU E5-2630 v4 @ ...
安装MySQL8，安装时初始化数据库失败
大概过程下载解压到你想要安装的目录例如我这次是直接在C盘下.C:\mysql-8.0.17-winx64 配置环境变量,把C:\mysql-8.0.17-winx64\bin加到PATH环境变量里后 ...
64位win7下，plsql连接64位数据库时提示initialization error，已解决
问题描述:plsql链接数据库时提示initialization error,(本机系统是windows7 64位,远程数据库所在系统为windows server 2008 64位) 解决方案: 一 ...
SSM Mybatis将新增数据写入数据库时出现的500状态码：Error updating database.的可能...
关于maven下ssm整合的项目推荐这篇博客:https://www.cnblogs.com/yiye/p/5969157.html 今日在ssm下的将新增数据写回数据库时遇到不少的问题,现作记录如 ...
MCI播放mp3文件error：初始化mci时发生问题
今天使用MCI写一个音乐播放器雏形的时候,使用的是mp3文件,在打开第一个文件时候还没有问题,但是在换了一个mp3文件之后,发现打开文件失败了,使用mciGetErrorString函数得到其错误为: ...

Greenplum初始化数据库时出现gpadmin-[ERROR]:-gpstart error: Do not have enough valid segments to start the arr

Greenplum初始化数据库时出现gpadmin-[ERROR]:-gpstart error: Do not have enough valid segments to start the arr相关推荐

最新文章

热门文章