<div dir="ltr"><div><div><div><div><div>Hi All,<br></div>After upgrade to pgPool-II 3.2.3 and I tested my failover/ failback setup, and start / stop pgpool mutlip times, I see one of the pgpool goes in to an unrecoverable state.<br>
<br>Mar 1 10:45:25 server1 pgpool[3007]: received smart shutdown request<br>Mar 1 10:45:25 server1 pgpool[3007]: watchdog_pid: 3010<br>Mar 1 10:45:31 server1 pgpool[3338]: wd_chk_sticky: ifup[/sbin/ip] doesn't have sticky bit<br>
Mar 1 10:45:31 server1 pgpool[3339]: bind(:) failed. reason: Success<br>Mar 1 10:45:31 server1 pgpool[3339]: unlink(/tmp/.s.PGSQL.9898) failed: No such file or directory<br><br><br></div>netstat shows the following:<br>
[root@server1 ~]# netstat -na |egrep "9898|9999"<br>tcp 0 0 <a href="http://0.0.0.0:9898">0.0.0.0:9898</a> 0.0.0.0:* LISTEN <br>tcp 0 0 <a href="http://0.0.0.0:9999">0.0.0.0:9999</a> 0.0.0.0:* LISTEN <br>
tcp 0 0 <a href="http://172.16.6.154:46650">172.16.6.154:46650</a> <a href="http://172.16.6.153:9999">172.16.6.153:9999</a> TIME_WAIT <br>tcp 9 0 <a href="http://172.16.6.154:9999">172.16.6.154:9999</a> <a href="http://172.16.6.153:51868">172.16.6.153:51868</a> CLOSE_WAIT <br>
tcp 9 0 <a href="http://172.16.6.154:9999">172.16.6.154:9999</a> <a href="http://172.16.6.153:51906">172.16.6.153:51906</a> CLOSE_WAIT <br>tcp 0 0 <a href="http://172.16.6.154:9999">172.16.6.154:9999</a> <a href="http://172.16.6.154:50624">172.16.6.154:50624</a> TIME_WAIT <br>
tcp 9 0 <a href="http://172.16.6.154:9999">172.16.6.154:9999</a> <a href="http://172.16.6.153:51946">172.16.6.153:51946</a> CLOSE_WAIT <br>unix 2 [ ACC ] STREAM LISTENING 18698 /tmp/.s.PGSQL.9898<br>
unix 2 [ ACC ] STREAM LISTENING 18685 /tmp/.s.PGSQL.9999<br><br></div>Is this a known issue?<br><br></div>I will have to reboot the server in order to start pgpool back online.<br><br></div>My cluster has two servers (server0 & server1) which each of them are running pgpool, and postgreSQL with streaming Replication setup.<br>
<br>Thanks~<br>Ning<br></div>