[pgpool-general: 5746] Re: FATAL: failed to create INET domain socket DETAIL: getaddrinfo() failed: Name or service not known

Giancarlo Celli giancarlocelli at gmail.com
Sat Sep 23 17:15:20 JST 2017


I solved this problem by setting listen_address to '*'.

Previously I entered the correct IPs (eno1 and eno2's Nodes IPs and
Virtual IP) in the listen_address list of IPs.

Why doesn't work?



2017-09-22 18:09 GMT+02:00 Giancarlo Celli <giancarlocelli at gmail.com>:

> Hello everyone,
> I have 2 streaming replication servers on which I've installed pgpool-II.
> Postgresql in running on port 5433 and pgpool on port 5432.
>
> Servers are connected by a cross cable to the eno2 interface, but eno1 is a public interface.
>
> The configuration is as follows:
> Server1: eno1: x.y.z.11 eno2: 192.168.0.11 Server2: eno1: x.y.z.12 eno2:
> 192.168.0.12 Virtual IP: x.y.z.10
>
> (x.y.z. is just for example)
> I'm sending my pgpool.conf in attachment.
>
> pgpool does not start and in pgpool.log I can see the following output:
>
> 2017-09-22 17:44:02: pid 3512: LOG: waiting for watchdog to initialize
> 2017-09-22 17:44:02: pid 3513: LOG: setting the local watchdog node name to
> "x.y.z.12:5432 Linux produzione2" 2017-09-22 17:44:02: pid 3513: LOG:
> watchdog cluster is configured with 1 remote nodes 2017-09-22 17:44:02: pid
> 3513: LOG: watchdog remote node:0 on x.y.z.11:9000 2017-09-22 17:44:02: pid
> 3513: LOG: interface monitoring is disabled in watchdog 2017-09-22
> 17:44:02: pid 3513: LOG: watchdog node state changed from [DEAD] to
> [LOADING] 2017-09-22 17:44:07: pid 3513: LOG: watchdog node state changed
> from [LOADING] to [JOINING] 2017-09-22 17:44:11: pid 3513: LOG: watchdog
> node state changed from [JOINING] to [INITIALIZING] 2017-09-22 17:44:12:
> pid 3513: LOG: I am the only alive node in the watchdog cluster 2017-09-22
> 17:44:12: pid 3513: HINT: skiping stand for coordinator state 2017-09-22
> 17:44:12: pid 3513: LOG: watchdog node state changed from [INITIALIZING] to
> [MASTER] 2017-09-22 17:44:12: pid 3513: LOG: I am announcing my self as
> master/coordinator watchdog node 2017-09-22 17:44:16: pid 3513: LOG: I am
> the cluster leader node 2017-09-22 17:44:16: pid 3513: DETAIL: our declare
> coordinator message is accepted by all nodes 2017-09-22 17:44:16: pid 3513:
> LOG: setting the local node "x.y.z.12:5432 Linux produzione2" as watchdog
> cluster master 2017-09-22 17:44:16: pid 3513: LOG: I am the cluster leader
> node. Starting escalation process 2017-09-22 17:44:16: pid 3512: LOG:
> watchdog process is initialized 2017-09-22 17:44:16: pid 3513: LOG:
> escalation process started with PID:3522 2017-09-22 17:44:16: pid 3513:
> LOG: new IPC connection received 2017-09-22 17:44:16: pid 3522: LOG:
> watchdog: escalation started 2017-09-22 17:44:16: pid 3513: LOG: new IPC
> connection received 2017-09-22 17:44:16: pid 3523: LOG: 2 watchdog nodes
> are configured for lifecheck 2017-09-22 17:44:16: pid 3523: LOG: watchdog
> nodes ID:0 Name:"x.y.z.12:5432 Linux produzione2" 2017-09-22 17:44:16:
> pid 3523: DETAIL: Host:"x.y.z.12" WD Port:9000 pgpool-II port:5432
> 2017-09-22 17:44:16: pid 3523: LOG: watchdog nodes ID:1 Name:"Not_Set"
> 2017-09-22 17:44:16: pid 3523: DETAIL: Host:"x.y.z.11" WD Port:9000
> pgpool-II port:5432 2017-09-22 17:44:16: pid 3523: LOG: watchdog lifecheck
> trusted server "8.8.8.8" added for the availability check 2017-09-22
> 17:44:16: pid 3523: LOG: watchdog lifecheck trusted server "8.8.4.4" added
> for the availability check *2017-09-22 17:44:16: pid 3512: FATAL: failed
> to create INET domain socket 2017-09-22 17:44:16: pid 3512: DETAIL:
> getaddrinfo() failed: Name or service not known* 2017-09-22 17:44:16: pid
> 3513: LOG: Watchdog is shutting down 2017-09-22 17:44:16: pid 3513: LOG:
> waiting for escalation process to exit before starting de-escalation
> 2017-09-22 17:44:17: pid 3513: LOG: waiting for escalation process to exit
> before starting de-escalation 2017-09-22 17:44:18: pid 3513: LOG: waiting
> for escalation process to exit before starting de-escalation 2017-09-22
> 17:44:19: pid 3513: LOG: waiting for escalation process to exit before
> starting de-escalation 2017-09-22 17:44:20: pid 3513: LOG: waiting for
> escalation process to exit before starting de-escalation 2017-09-22
> 17:44:20: pid 3522: LOG: successfully acquired the delegate IP:"x.y.z.10"
> 2017-09-22 17:44:20: pid 3522: DETAIL: 'if_up_cmd' returned with success
> 2017-09-22 17:44:20: pid 3513: LOG: escalation process does not exited in
> time 2017-09-22 17:44:20: pid 3513: DETAIL: starting the de-escalation
> anyway 2017-09-22 17:44:20: pid 3529: LOG: watchdog: de-escalation started
> 2017-09-22 17:44:20: pid 3529: LOG: successfully released the delegate IP:"
> x.y.z.10" 2017-09-22 17:44:20: pid 3529: DETAIL: 'if_down_cmd' returned
> with success
>
> Can you help me???
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170923/0623020b/attachment.html>


More information about the pgpool-general mailing list