Pivotal Greenplum Database (GPDB)
gprecoverseg command fails, turning on the verbose mode "gprecoverseg -v" shows the following error:
20150812:16:33:19:018897 gprecoverseg:00213SG1LGRE01:gpadmin-[DEBUG]:-[worker0] finished cmd: Get segment status cmdStr='ssh -o 'StrictHostKeyChecking no' 00213SG1LGRE05 ". /usr/local/greenplum-db/./greenplum_path.sh; $GPHOME/bin/gp_primarymirror -h 00213SG1LGRE05 -p 40003"' had result: cmd had rc=1 completed=True halted=False stdout='' stderr='DO NOT PROCEED UNLESS YOU ARE AN AUTHORISED USER This is a private computer facility protected by a security system. Access to, and use of, this system is restricted to genuine account users. Activity and use of this network is strictly monitored to secure effective operation and for other lawful business purposes. Communications using these systems will also be monitored and may be recorded to secure the effective operation and for other lawful business purposes. Unauthorised access or attempts to alter, destroy or damage data, programs or equipment could result in criminal prosecution. stroy or damage data, programs or equipment could result in criminal prosecution. mode: PrimarySegment segmentState: Ready dataState: InChangeTracking faultType: NotInitialized mode: PrimarySegment segmentState: Ready dataState: InChangeTracking faultType: NotInitialized '
This is caused due to ssh banner prompt of server i.e the banner that displayed on the screen when a user connects to the server.
Please do the following on all segment hosts:
- "vi" the /etc/ssh/sshd_config file and look for the banner in question and then comment it out.
- service sshd restart
- retry gprecoverseg