No subject


Sun Nov 18 18:09:07 JST 2012


Apr  1 16:14:52 se032c-94-30 pgpool[2456]: starting recovering node 1
Apr  1 16:14:52 se032c-94-30 pgpool[2456]: starting recovery command:
"SELECT pgpool_recovery('basebackup.sh', 'se032c-94-31',
'/opt/postgres/9.2/data')"
Apr  1 16:14:52 se032c-94-30 postgres[3096]: [2-1]
[unknown]postgres3096ERROR:  pgpool_recovery failed
Apr  1 16:14:52 se032c-94-30 postgres[3096]: [2-2]
[unknown]postgres3096STATEMENT:  SELECT pgpool_recovery('basebackup.sh',
'se032c-94-31', '/opt/postgres/9.2/data')

The exact same script used on both node, so why one work but not the others.
And from the log, I have no idea why it fails, setting debug=[1,2,3] does
not help on troubleshooting.

I then went to manually execute the pgpool_recovery statement, i see the
following:

template1=# SELECT pgpool_recovery('basebackup.sh', 'se032c-94-31',
'/opt/postgres/9.2/data');
ERROR:  pgpool_recovery failed
template1=# SELECT pgpool_recovery('basebackup.sh', '10.89.94.31',
'/opt/postgres/9.2/data');
 pgpool_recovery
-----------------
 t
(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

Please help!

Thanks~
Ning

--047d7b6d9940fdf89504d9534abd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Hi folks,<br><br></div>I have a setup of two nod=
es with Streaming Replication, pgpool running on both nodes monitoring each=
 other backends. Everything is working fine,=A0 failover work and oneline r=
ecovery work like a charm. <br>
<br></div><div>Here is the problem, while server0 failover to server1, and =
server1 recover server0 had no problem; however, when i failover back, serv=
er1 failover to server0, server0 is not able to recover server1.<br><br>
</div><div>From the log on Primary:<br>Apr=A0 1 16:14:52 se032c-94-30 pgpoo=
l[2456]: starting recovering node 1<br>Apr=A0 1 16:14:52 se032c-94-30 pgpoo=
l[2456]: starting recovery command: &quot;SELECT pgpool_recovery(&#39;baseb=
ackup.sh&#39;, &#39;se032c-94-31&#39;, &#39;/opt/postgres/9.2/data&#39;)&qu=
ot;<br>
Apr=A0 1 16:14:52 se032c-94-30 postgres[3096]: [2-1] [unknown]postgres3096E=
RROR:=A0 pgpool_recovery failed<br>Apr=A0 1 16:14:52 se032c-94-30 postgres[=
3096]: [2-2] [unknown]postgres3096STATEMENT:=A0 SELECT pgpool_recovery(&#39=
;basebackup.sh&#39;, &#39;se032c-94-31&#39;, &#39;/opt/postgres/9.2/data&#3=
9;)<br>
<br></div><div>The exact same script used on both node, so why one work but=
 not the others.<br></div><div>And from the log, I have no idea why it fail=
s, setting debug=3D[1,2,3] does not help on troubleshooting.<br><br></div>
<div>I then went to manually execute the pgpool_recovery statement, i see t=
he following:<br><br>template1=3D# SELECT pgpool_recovery(&#39;basebackup.s=
h&#39;, &#39;se032c-94-31&#39;, &#39;/opt/postgres/9.2/data&#39;);<br>ERROR=
:=A0 pgpool_recovery failed<br>
template1=3D# SELECT pgpool_recovery(&#39;basebackup.sh&#39;, &#39;10.89.94=
.31&#39;, &#39;/opt/postgres/9.2/data&#39;);<br>=A0pgpool_recovery<br>-----=
------------<br>=A0t<br>(1 row)<br><br><br></div><div>If hostname is used, =
the command will failed, but IP works fine.<br>
<br></div><div>I double check the hostname is pingable from localhost.<br><=
br>[root at se032c-94-30 ~]# ping se032c-94-31<br>PING <a href=3D"http://se032=
c-94-31.cisco.com">se032c-94-31.cisco.com</a> (10.89.94.31) 56(84) bytes of=
 data.<br>
64 bytes from <a href=3D"http://se032c-94-31.abc.com">se032c-94-31.abc.com<=
/a> (10.89.94.31): icmp_seq=3D1 ttl=3D64 time=3D0.254 ms<br>64 bytes from <=
a href=3D"http://se032c-94-31.abc.com">se032c-94-31.abc.com</a> (10.89.94.3=
1): icmp_seq=3D2 ttl=3D64 time=3D0.311 ms<br>
<br></div><div>Please help!<br><br>Thanks~<br>Ning<br></div></div>

--047d7b6d9940fdf89504d9534abd--


More information about the pgpool-general mailing list