[pgpool-general: 1567] Re: Online Recovery failed with unknown reason
kong_mansatiansin at hotmail.com
Thu Apr 4 03:45:00 JST 2013
I agreed that the debug mode does not help at all. The problem could be due to various reasons. One gotcha I had was, despite a well-established password-less SSH setup, if you haven't made the hostname/IP recognized as a known host, SSH would prompt and pgpool_recovery simply gives out 'ERROR: pgpool_recovery failed' wihtout any additional message.
Try 'ssh se032c-94-31' and see if you get a prompt like the following. If so, simply answer yes to get the symbolic name on the ~/.ssh/known_hosts file and try your pgpool_recovery one more time.
I hope this leads you to something, if it does not directly address your issue.
The authenticity of host '10.89.94.31 (10.89.94.31)' can't be established.
RSA key fingerprint is ....
Are you sure you want to continue connecting (yes/no)?
> template1=# SELECT pgpool_recovery('basebackup.sh', 'se032c-94-31',
> ERROR: pgpool_recovery failed
> template1=# SELECT pgpool_recovery('basebackup.sh', '10.89.94.31',
> (1 row)
> If hostname is used, the command will failed, but IP works fine.
> I double check the hostname is pingable from localhost.
> [root at se032c-94-30 ~]# ping se032c-94-31
> PING se032c-94-31.cisco.com (10.89.94.31) 56(84) bytes of data.
> 64 bytes from se032c-94-31.abc.com (10.89.94.31): icmp_seq=1 ttl=64
> time=0.254 ms
> 64 bytes from se032c-94-31.abc.com (10.89.94.31): icmp_seq=2 ttl=64
> time=0.311 ms
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pgpool-general