View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000164 | Pgpool-II | Bug | public | 2016-01-23 17:23 | 2016-02-01 17:11 |
| Reporter | harukat | Assigned To | nagata | ||
| Priority | normal | Severity | minor | Reproducibility | unable to reproduce |
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.4.0 | ||||
| Summary | 0000164: watchdog authentication failed | ||||
| 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. | ||||
| Tags | No tags attached. | ||||
|
|
|
|
|
Thank you for your reporting and providing the patch. I pushed this with some changes; - some fixes for warning messages - change log level from LOG to warning - add same changes for heartbeat packet handling http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=864c7d6fdafb644f28f8025d3a441f83ba53e64d I back-ported this to V3_3_STABLE and applied this to V3_5_STABLE and master, tool |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-01-23 17:23 | harukat | New Issue | |
| 2016-01-23 17:23 | harukat | File Added: V3_4_auth_key_error_check.patch | |
| 2016-01-30 10:48 | t-ishii | Assigned To | => nagata |
| 2016-01-30 10:48 | t-ishii | Status | new => assigned |
| 2016-01-30 10:48 | t-ishii | Description Updated | |
| 2016-02-01 17:10 | nagata | Note Added: 0000644 | |
| 2016-02-01 17:11 | nagata | Status | assigned => resolved |
| 2016-02-01 17:11 | nagata | Resolution | open => fixed |
