[pgpool-general: 4929] Re: Pgpool and IP bonding

[Muhammad Usama]

Hi

>From the pgpool-II logs you shared apparently the pgpool-II startup failure
is because of watchdog fails to bind to the TCP address(most probably
because of the port number is already in use), but unfortunately because of
a bug the error message of bind failure was not printing the correct reason
for failure. I have committed the fix for the error reporting problem in
master and pgpool-II 3.5 branches.

http://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=c9b1f71765ca7a51efea51b6275165a8df659e71

Can try building from source code and share the logs when the problem
occurs.

Regards
Muhammad Usama

On Mon, Aug 15, 2016 at 5:19 PM, Avi Weinberg <AviW at gilat.com> wrote:

>
>
> Hi all,
>
>
>
> From time to time pgpool will not stop / start and only restarting the
> network (service network restart) will help it come up.  As you can see
> from the tail of this mail we have IP bonding.  Does pgpool have problem
> with IP
>
> Bonding?
>
>
>
> Thanks!
>
>
>
>
>
> 2016-08-15 13:04:07: pid 32074: LOG:  watchdog remote node:0 on
> 172.18.255.42:9000
>
> 2016-08-15 13:04:07: pid 32074: LOG:  interface monitoring is disabled in
> watchdog
>
> 2016-08-15 13:04:09: pid 29367: LOG:  forked new pcp worker, pid=32088
> socket=6
>
> 2016-08-15 13:04:09: pid 29367: LOG:  PCP process with pid: 32088 exit
> with SUCCESS.
>
> 2016-08-15 13:04:09: pid 29367: LOG:  PCP process with pid: 32088 exits
> with status 0
>
> 2016-08-15 13:04:09: pid 29367: LOG:  forked new pcp worker, pid=32094
> socket=6
>
> 2016-08-15 13:04:09: pid 29367: LOG:  PCP process with pid: 32094 exit
> with SUCCESS.
>
> 2016-08-15 13:04:09: pid 29367: LOG:  PCP process with pid: 32094 exits
> with status 0
>
> 2016-08-15 13:04:12: pid 29367: LOG:  forked new pcp worker, pid=32106
> socket=6
>
> 2016-08-15 13:04:12: pid 29367: LOG:  PCP process with pid: 32106 exit
> with SUCCESS.
>
> 2016-08-15 13:04:12: pid 29367: LOG:  PCP process with pid: 32106 exits
> with status 0
>
> 2016-08-15 13:04:15: pid 29367: LOG:  forked new pcp worker, pid=32192
> socket=6
>
> 2016-08-15 13:04:15: pid 29367: LOG:  PCP process with pid: 32192 exit
> with SUCCESS.
>
> 2016-08-15 13:04:15: pid 29367: LOG:  PCP process with pid: 32192 exits
> with status 0
>
> 2016-08-15 13:05:07: pid 32318: LOG:  waiting for watchdog to initialize
>
> 2016-08-15 13:05:07: pid 32320: LOG:  setting the local watchdog node name
> to "Linux_postgres_server1_9999"
>
> 2016-08-15 13:05:07: pid 32320: LOG:  watchdog cluster configured with 1
> remote nodes
>
> 2016-08-15 13:05:07: pid 32320: LOG:  watchdog remote node:0 on
> 172.18.255.42:9000
>
> 2016-08-15 13:05:07: pid 32320: LOG:  interface monitoring is disabled in
> watchdog
>
> 2016-08-15 13:05:07: pid 32320: FATAL:  failed to create watchdog receive
> socket
>
> 2016-08-15 13:05:07: pid 32320: DETAIL:  bind on ":" failed with reason:
> "Success"
>
> 2016-08-15 13:05:07: pid 32318: LOG:  watchdog child process with pid:
> 32320 exits with status 768
>
> 2016-08-15 13:05:07: pid 32318: FATAL:  watchdog child process exit with
> fatal error. exiting pgpool-II
>
> 2016-08-15 13:05:07: pid 32321: LOG:  setting the local watchdog node name
> to "Linux_postgres_server1_9999"
>
> 2016-08-15 13:05:07: pid 32321: LOG:  watchdog cluster configured with 1
> remote nodes
>
> 2016-08-15 13:05:07: pid 32321: LOG:  watchdog remote node:0 on
> 172.18.255.42:9000
>
> 2016-08-15 13:05:07: pid 32321: LOG:  interface monitoring is disabled in
> watchdog
>
> 2016-08-15 13:05:09: pid 29367: LOG:  forked new pcp worker, pid=32335
> socket=6
>
> 2016-08-15 13:05:09: pid 29367: LOG:  PCP process with pid: 32335 exit
> with SUCCESS.
>
> 2016-08-15 13:05:09: pid 29367: LOG:  PCP process with pid: 32335 exits
> with status 0
>
> 2016-08-15 13:05:09: pid 29367: LOG:  forked new pcp worker, pid=32341
> socket=6
>
> 2016-08-15 13:05:09: pid 29367: LOG:  PCP process with pid: 32341 exit
> with SUCCESS.
>
> 2016-08-15 13:05:09: pid 29367: LOG:  PCP process with pid: 32341 exits
> with status 0
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Shutting down interface bond1.18:                          [  OK  ]
>
> Shutting down interface bond0:                             [  OK  ]
>
> Shutting down interface bond1:                             [  OK  ]
>
> Shutting down loopback interface:                          [  OK  ]
>
> Bringing up loopback interface:                            [  OK  ]
>
> Bringing up interface bond0:  Determining if ip address 172.19.255.41 is
> already in use for device bond0...
>
>                                                            [  OK  ]
>
> Bringing up interface bond1:                               [  OK  ]
>
> Bringing up interface bond1.18:  Determining if ip address 172.18.255.41
> is already in use for device bond1.18...
>
>                                                            [  OK  ]
>
> [root at postgres_server1 data]# service pgpool start
>
> Starting pgpool service:                                   [  OK  ]
>
>
>
>
>
>
> IMPORTANT - This email and any attachments is intended for the above named
> addressee(s), and may contain information which is confidential or
> privileged. If you are not the intended recipient, please inform the sender
> immediately and delete this email: you should not copy or use this e-mail
> for any purpose nor disclose its contents to any person.
>
> _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20160818/d68fc880/attachment-0001.html>