View Issue Details

IDProjectCategoryView StatusLast Update
0000402pgpool-HABugpublic2018-06-04 13:28
ReporterParkbyunggyu Assigned To 
PriorityhighSeveritycrashReproducibilityrandom
Status closedResolutionopen 
PlatformX86_64OSCentOSOS Version7.3
Summary0000402: write on backend 0 failed with error :"Success"
DescriptionHi,
I am currently experiencing problems using pg-pool II 3.6.5.
Database is using PostgreSQL version 9.6.5
And I'm using H/A streaming replication mode Master - Slave structure.
The following warning occasionally occurs , and the connection is temporarily unavailable.
When I check other similar issues(issue_ID=0000395), the answer is called Bug.
But I can not confirm the solution to the bug, so I issue a new issue.
I write pg-pool err and upload OS log , postgresql.log
Please help me,..

================================================================================================

2018-04-18 15:58:02: pid 3307: FATAL: unable to read data from DB node 0
2018-04-18 15:58:02: pid 3307: DETAIL: EOF encountered with backend
2018-04-18 15:58:02: pid 3307: WARNING: write on backend 0 failed with error :"Success"
2018-04-18 15:58:02: pid 3307: DETAIL: while trying to write data from offset: 0 wlen: 5
2018-04-18 15:58:02: pid 10737: LOG: child process with pid: 3307 exits with status 256
2018-04-18 15:58:02: pid 10737: LOG: fork a new child process with pid: 5895
2018-04-18 15:58:02: pid 3308: FATAL: unable to read data from DB node 0
2018-04-18 15:58:02: pid 3308: DETAIL: EOF encountered with backend
2018-04-18 15:58:02: pid 3308: WARNING: write on backend 0 failed with error :"Success"
2018-04-18 15:58:02: pid 3308: DETAIL: while trying to write data from offset: 0 wlen: 5
2018-04-18 15:58:02: pid 10737: LOG: child process with pid: 3308 exits with status 256
2018-04-18 15:58:02: pid 10737: LOG: fork a new child process with pid: 5896
2018-04-18 15:58:02: pid 3315: FATAL: unable to read data from DB node 0
2018-04-18 15:58:02: pid 3315: DETAIL: EOF encountered with backend
2018-04-18 15:58:02: pid 3315: WARNING: write on backend 0 failed with error :"Success"
2018-04-18 15:58:02: pid 3315: DETAIL: while trying to write data from offset: 0 wlen: 5
2018-04-18 15:58:02: pid 3315: WARNING: write on backend 1 failed with error :"Success"
2018-04-18 15:58:02: pid 3315: DETAIL: while trying to write data from offset: 0 wlen: 5
2018-04-18 15:58:02: pid 10737: LOG: child process with pid: 3315 exits with status 256
2018-04-18 15:58:02: pid 10737: LOG: fork a new child process with pid: 5897
2018-04-18 15:58:02: pid 3321: FATAL: unable to read data from DB node 0
2018-04-18 15:58:02: pid 3321: DETAIL: EOF encountered with backend
2018-04-18 15:58:02: pid 3321: WARNING: write on backend 0 failed with error :"Success"
2018-04-18 15:58:02: pid 3321: DETAIL: while trying to write data from offset: 0 wlen: 5
2018-04-18 15:58:02: pid 10737: LOG: child process with pid: 3321 exits with status 256
2018-04-18 15:58:02: pid 10737: LOG: fork a new child process with pid: 5898
2018-04-18 15:58:02: pid 3324: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3324: DETAIL: EOF encountered with frontend
2018-04-18 15:58:02: pid 3329: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3329: DETAIL: EOF encountered with frontend
2018-04-18 15:58:02: pid 3331: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3331: DETAIL: EOF encountered with frontend
2018-04-18 15:58:02: pid 3334: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3334: DETAIL: EOF encountered with frontend
2018-04-18 15:58:02: pid 3333: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3333: DETAIL: EOF encountered with frontend
2018-04-18 15:58:02: pid 3339: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3339: DETAIL: EOF encountered with frontend
2018-04-18 15:58:02: pid 3337: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3337: DETAIL: EOF encountered with frontend
2018-04-18 15:58:02: pid 3341: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3341: DETAIL: EOF encountered with frontend
2018-04-18 15:58:02: pid 3342: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3342: DETAIL: EOF encountered with frontend
2018-04-18 15:58:02: pid 3373: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3373: DETAIL: EOF encountered with frontend
2018-04-18 15:58:02: pid 3486: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3486: DETAIL: EOF encountered with frontend
2018-04-18 15:58:02: pid 3527: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3527: DETAIL: EOF encountered with frontend
2018-04-18 15:58:02: pid 3559: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3559: DETAIL: EOF encountered with frontend
2018-04-18 15:58:02: pid 3562: ERROR: unable to read data from frontend
2018-04-18 15:58:02: pid 3562: DETAIL: EOF encountered with frontend

=============================================================================

2018-06-01 11:13:46: pid 13796: LOG: new connection received
2018-06-01 11:13:46: pid 13796: DETAIL: connecting host=XXX.XXX.XXX.8 port=XXXX
2018-06-01 11:13:46: pid 13796: LOG: new connection received
2018-06-01 11:13:46: pid 13796: DETAIL: connecting host=XXX.XXX.XXX.XXX port=XXXX
2018-06-01 11:13:46: pid 10737: LOG: fork a new child process with pid: 13797
2018-06-01 11:13:46: pid 13797: LOG: new connection received
2018-06-01 11:13:46: pid 13797: DETAIL: connecting host=XXX.XXX.XXX.XXX port=XXXX
2018-06-01 11:13:48: pid 7433: FATAL: unable to read data from DB node 0
2018-06-01 11:13:48: pid 7433: DETAIL: EOF encountered with backend
2018-06-01 11:13:48: pid 7433: WARNING: write on backend 0 failed with error :"Success"
2018-06-01 11:13:48: pid 7433: DETAIL: while trying to write data from offset: 0 wlen: 5
2018-06-01 11:13:48: pid 10737: LOG: child process with pid: 7433 exits with status 256
2018-06-01 11:13:48: pid 10737: LOG: fork a new child process with pid: 13800
2018-06-01 11:13:48: pid 13800: LOG: new connection received
2018-06-01 11:13:48: pid 13800: DETAIL: connecting host=XXX.XXX.XXX.XXX port=XXXX
2018-06-01 11:13:48: pid 10902: FATAL: unable to read data from DB node 0
2018-06-01 11:13:48: pid 10902: DETAIL: EOF encountered with backend
2018-06-01 11:13:48: pid 10902: WARNING: write on backend 0 failed with error :"Success"
2018-06-01 11:13:48: pid 10902: DETAIL: while trying to write data from offset: 0 wlen: 5
2018-06-01 11:13:48: pid 10737: LOG: child process with pid: 10902 exits with status 256
2018-06-01 11:13:48: pid 10737: LOG: fork a new child process with pid: 13802
2018-06-01 11:13:48: pid 13802: LOG: new connection received
2018-06-01 11:13:48: pid 13802: DETAIL: connecting host=XXX.XXX.XXX.XXX port=XXXX
2018-06-01 11:13:49: pid 4042: FATAL: unable to read data from DB node 0
2018-06-01 11:13:49: pid 4042: DETAIL: EOF encountered with backend
2018-06-01 11:13:49: pid 4042: WARNING: write on backend 0 failed with error :"Success"
2018-06-01 11:13:49: pid 4042: DETAIL: while trying to write data from offset: 0 wlen: 5
2018-06-01 11:13:49: pid 10737: LOG: child process with pid: 4042 exits with status 256
2018-06-01 11:13:49: pid 10737: LOG: fork a new child process with pid: 13805
2018-06-01 11:13:49: pid 13805: LOG: new connection received
2018-06-01 11:13:49: pid 13805: DETAIL: connecting host=XXX.XXX.XXX.XXX port=XXXX
2018-06-01 11:13:51: pid 9303: FATAL: unable to read data from DB node 0
2018-06-01 11:13:51: pid 9303: DETAIL: EOF encountered with backend
2018-06-01 11:13:51: pid 9303: WARNING: write on backend 0 failed with error :"Success"
2018-06-01 11:13:51: pid 9303: DETAIL: while trying to write data from offset: 0 wlen: 5
2018-06-01 11:13:51: pid 10737: LOG: child process with pid: 9303 exits with status 256
2018-06-01 11:13:51: pid 10737: LOG: fork a new child process with pid: 13808
2018-06-01 11:13:51: pid 13808: LOG: new connection received
2018-06-01 11:13:51: pid 13808: DETAIL: connecting host=XXX.XXX.XXX.XXX port=XXXX
2018-06-01 11:13:52: pid 9318: FATAL: unable to read data from DB node 0
2018-06-01 11:13:52: pid 9318: DETAIL: EOF encountered with backend
2018-06-01 11:13:52: pid 9318: WARNING: write on backend 0 failed with error :"Success"
2018-06-01 11:13:52: pid 9318: DETAIL: while trying to write data from offset: 0 wlen: 5
2018-06-01 11:13:52: pid 10737: LOG: child process with pid: 9318 exits with status 256
2018-06-01 11:13:52: pid 10737: LOG: fork a new child process with pid: 13811
2018-06-01 11:13:52: pid 13811: LOG: new connection received
2018-06-01 11:13:52: pid 13811: DETAIL: connecting host=XXX.XXX.XXX.XXX port=XXXX
2018-06-01 11:13:54: pid 25112: FATAL: unable to read data from DB node 0
2018-06-01 11:13:54: pid 25112: DETAIL: EOF encountered with backend
2018-06-01 11:13:54: pid 25112: WARNING: write on backend 0 failed with error :"Success"
2018-06-01 11:13:54: pid 25112: DETAIL: while trying to write data from offset: 0 wlen: 5

=============================================================================
Tagspgpool

Activities

Parkbyunggyu

2018-06-04 11:34

reporter  

messages_1.txt (36,765 bytes)   
messages_1.txt (36,765 bytes)   

pengbo

2018-06-04 13:15

developer   ~0002040

It seems to be just a Pgpool-II issue, not a pgpool-HA issue.
pgpool-HA is the RA (Resource Agent) script of Pgpool-II for Pacemaker cluster.

Could you close this one and make a new issue for Pgpool-II?

Parkbyunggyu

2018-06-04 13:22

reporter   ~0002041

sorry, how to close issue?.. i can't see anything for close issue

pengbo

2018-06-04 13:28

developer   ~0002042

I will close this one to move it to a Pgpool-II project.

Issue History

Date Modified Username Field Change
2018-06-04 11:34 Parkbyunggyu New Issue
2018-06-04 11:34 Parkbyunggyu File Added: postgresql-2018-04-18_000000_1.log
2018-06-04 11:34 Parkbyunggyu File Added: messages_1.txt
2018-06-04 11:34 Parkbyunggyu Tag Attached: pgpool
2018-06-04 13:15 pengbo Note Added: 0002040
2018-06-04 13:22 Parkbyunggyu Note Added: 0002041
2018-06-04 13:28 pengbo Status new => closed
2018-06-04 13:28 pengbo Note Added: 0002042