View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000381 | Pgpool-II | Bug | public | 2018-03-02 22:57 | 2018-03-29 22:41 |
| Reporter | chg1995 | Assigned To | t-ishii | ||
| Priority | normal | Severity | block | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Platform | Linux | OS | Ubuntu | OS Version | 16.04 |
| Product Version | 3.7.2 | ||||
| Summary | 0000381: Problem when recovery attempts starting a fallen node | ||||
| Description | I have pgpool configured with two nodes and with load balance mode and replication mode on. I am trying the recovery command when a node is down. The recovery process is succesfully executed, but when it wants to start the node that is down, is always getting an error. This is the output of the recovery command: $ sudo -u postgres pcp_recovery_node -n 1 -h host1 -p 9898 -d -v DEBUG: recv: tos="m", len=8 DEBUG: recv: tos="r", len=21 DEBUG: send: tos="D", len=6 DEBUG: recv: tos="E", len=114 ERROR: node recovery failed, waiting connection closed in the other pgpools timeout DEBUG: send: tos="X", len=4 -------------------------- When it spends the timeout (established in 900 seconds) always returns this error. Logs of Postgres doesn't show errors. Do you know what can is going on? Ask for extra info if needed. Thank you very much in advance. | ||||
| Tags | No tags attached. | ||||
|
|
What is the exact Pgpool-II version? |
|
|
The version is 3.7.2 (amefuriboshi) |
|
|
I think I have found my problem. I was making the recovery with the Postgres service stopped in the failed node. Now with the Postgres Service actived, it could init the node recovered. Thank you very much. |
|
|
Today I wanted to recover a node failed, and I'm getting the same error of this report. |
|
|
The error message from pcp_recovery_node does not tell too much. Can you share: pgpool.conf Pgpool-II log PostgreSQL log |
|
|
Sorry for delay. I'm using the postgis extension in Postgres nodes and I realised that were different versions (postgis-2.2 vs postgis-2.3). I installed 2.3 version in both nodes and I don't issued the problem again. I think that is fixed. You can close the issue. Thank yo very much. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-03-02 22:57 | chg1995 | New Issue | |
| 2018-03-04 09:12 | t-ishii | Note Added: 0001947 | |
| 2018-03-05 16:25 | chg1995 | Note Added: 0001948 | |
| 2018-03-05 20:35 | chg1995 | Note Added: 0001949 | |
| 2018-03-06 18:50 | chg1995 | Note Added: 0001950 | |
| 2018-03-14 22:02 | t-ishii | Assigned To | => t-ishii |
| 2018-03-14 22:02 | t-ishii | Status | new => assigned |
| 2018-03-14 22:02 | t-ishii | Product Version | => 3.7.2 |
| 2018-03-14 22:05 | t-ishii | Note Added: 0001958 | |
| 2018-03-14 22:05 | t-ishii | Status | assigned => feedback |
| 2018-03-16 18:10 | chg1995 | Note Added: 0001969 | |
| 2018-03-16 18:10 | chg1995 | Status | feedback => assigned |
| 2018-03-29 22:41 | t-ishii | Status | assigned => closed |
