[pgpool-general: 3596] Re: Wathcdog issue
nagata at sraoss.co.jp
Tue Apr 7 16:04:51 JST 2015
On Tue, 7 Apr 2015 08:50:33 +0200
Mephysto <mephystoonhell at gmail.com> wrote:
> Hi there,
> I am trying for the first time to configure watchdog for pgpool-II 3.4.1.
> After doing some base settings in pgpool.conf, I tried to start pgpool, but
> I received some errore messages and watchdog are not working done. This is
> the log:
> 2015-04-05 18:32:35: pid 5094: DETAIL: ping data: PING localhost
> (127.0.0.1) 56(84) bytes of data.
> --- localhost ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 1999ms
> rtt min/avg/max/mdev = 0.014/0.030/0.041/0.012 ms
> 2015-04-05 18:32:35: pid 5094: LOG: failed to create watchdog sending
> 2015-04-05 18:32:35: pid 5094: DETAIL: connect() reports failure
> "Connection refused"
> 2015-04-05 18:32:35: pid 5094: HINT: You can safely ignore this while
> starting up.
> 2015-04-05 18:32:35: pid 5094: LOG: watchdog sending packet for nodes
> 2015-04-05 18:32:35: pid 5094: DETAIL: packet for "postgres-2:9000" is
> 2015-04-05 18:32:38: pid 5094: DEBUG: watchdog executing ping
> 2015-04-05 18:32:38: pid 5094: DETAIL: failed to ping "192.168.56.249"
> exit code: 1
> 2015-04-05 18:32:38: pid 5094: LOG: watchdog escalation
> 2015-04-05 18:32:38: pid 5094: DETAIL: escalating to master pgpool
> SIOCSIFADDR: Permission denied
> SIOCSIFFLAGS: Permission denied
> SIOCSIFNETMASK: Permission denied
> I'm using postgres user to run pgpool process, so I presume these errors
> due to postgres user permission. I would not use root to run pgpool
> process, so I ask you if exists a manner to run watchdog without using root
You can use setuid. This tutorial would be helpful. Alhough
this is using apache user instead of postgres user, the manner
is the almost the same.
> Best reegards.
Yugo Nagata <nagata at sraoss.co.jp>
More information about the pgpool-general