[pgpool-general: 6721] Re: Can't restart pgpool on SLAVE node (that is primary postgres server)
ishii at sraoss.co.jp
Tue Sep 24 07:38:51 JST 2019
> I had to kill the pgpool process to change the master on the other
> node. I also removed the pgpool.pid.
> Now this is the situation:
> NODE A:
> - Master pgpool ON
> - Standby postgres ON
> NODE B:
> - Slave pgpool DOWN
> - Primary postgres ON
> My problem is that if I try to restart pgpool on NODE B (SLAVE
> pgpool), it not works.
> In the log I see that initially it starts up correctly, but then the
> following error appears and pgpool goes down again:
> FATAL: failed to bind a socket: "/tmp/.s.PGSQL.5432"
> DETAIL: bind socket failed with error: "Address already in use"
> LOG: Watchdog is shutting down
How did you kill pgpool on node B? If it's something like kill -9 or
something rude way then pgpool sockt would remain. In this case you
need to manually remove pgpool socket (I am assuming it's
> I cannot stop postgres because it is primary server.
> What can I do for start pgpool on SLAVE pgpool?
SRA OSS, Inc. Japan
More information about the pgpool-general