View Revisions: Issue #164

Summary 0000164: watchdog authentication failed
Revision 2016-01-30 10:48 by t-ishii
Description We took a report that pgpool-II failed in backend's failback with wachdog
from our customer. (environment: pgpool-II 3.4.1 / RHEL6.x / x86_64)
There are 4 pgpool-II nodes. An pgpool-II couldn't get information about
failback from other node.

The parameter "authkey" of 4 nodes are accorded, but the following
messages are outputted at that time.
  2015-12-08 18:40:50: pid 12345: LOG: failed sending watchdog response
  2015-12-08 18:40:50: pid 12345: DETAIL: watchdog authentication failed

I think a network malfunction or pgpool's runtime error caused this.

I wrote a patch that provides more log messages about authkey
hash calculation. It will help analyzing this phenomenon.
I tested it lightly (with gdb) on recent V3_4_STABLE snapshot.
Revision 2016-01-23 17:23 by t-ishii
Description
We took a report that pgpool-II failed in backend's failback with wachdog
from our customer. (environment: pgpool-II 3.4.1 / RHEL6.x / x86_64)
There are 4 pgpool-II nodes. An pgpool-II couldn't get information about
failback from other node.

The parameter "authkey" of 4 nodes are accorded, but the following
messages are outputted at that time.
  2015-12-08 18:40:50: pid 12345: LOG: failed sending watchdog response
  2015-12-08 18:40:50: pid 12345: DETAIL: watchdog authentication failed

I think a network malfunction or pgpool's runtime error caused this.

I wrote a patch that provides more log messages about authkey
hash calculation. It will help analyzing this phenomenon.
I tested it lightly (with gdb) on recent V3_4_STABLE snapshot.