View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000069 | Pgpool-II | Bug | public | 2013-08-28 00:43 | 2015-01-08 16:15 |
| Reporter | aliasdhacker | Assigned To | nagata | ||
| Priority | high | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | AMD64 | OS | RED HAT | OS Version | 5.7 |
| Summary | 0000069: Portal "X_#####" does not exist | ||||
| Description | 2013-08-02 14:55:50 LOG: pid 4882: pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 24651 statement: SELECT .... message: portal "C_20621" does not exist | ||||
| Steps To Reproduce | This error message is appearing in the logs randomly while under normal operating conditions. | ||||
| Tags | No tags attached. | ||||
|
|
Thanks for your reporting. Could you provide us the following information? - The version of your pgpool-II - The mode of pgpool-II (replication mode or master-slave mode? etc.) - pgpool.conf and more detailed log messages. - The steps to reproduce the problem. This is needed for our investigation. |
|
|
Sure, my client is in Japan and I have to go through some time zones and translators, but as soon as I get the information I will post it. Thanks for the response. |
|
|
The user is running PGPOOL 3.2.1 on Redhat 5.7 (64BIT) This issue says it is resolved in 3.2-stable, oct, 2012. But 3.2.1 is the Oct release and they are experiencing the issue. http://www.pgpool.net/mantisbt/view.php?id=19 More detailed log: 2013-08-02 11:48:33 LOG: pid 23630: Replication of node:1 is behind -880 bytes from the primary server (node:0) 2013-08-02 14:55:50 LOG: pid 23630: Replication of node:1 is behind -744 bytes from the primary server (node:0) 2013-08-02 14:55:50 LOG: pid 4882: pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 24651 statement: SELECT XX,XX,XX, XXXX, XXXXX,XX, XX FROM XXXXXXXX WHERE XXXXXXXXX = $1 AND XXXXXXX='1110' ORDER BY XX,XX message: portal "C_20621" does not exist 2013-08-02 22:03:15 LOG: pid 23630: Replication of node:1 is behind 14549648 bytes from the primary server (node:0) 2013-08-02 22:09:25 LOG: pid 23630: Replication of node:1 is behind 31949312 bytes from the primary server (node:0) 2013-08-02 22:12:25 LOG: pid 23630: Replication of node:1 is behind 83973792 bytes from the primary server (node:0) 2013-08-02 22:12:35 LOG: pid 23630: Replication of node:1 is behind 221729480 bytes from the primary server (node:0) 2013-08-02 22:14:45 LOG: pid 23630: Replication of node:1 is behind 187369512 bytes from the primary server (node:0) 2013-08-02 22:14:55 LOG: pid 23630: Replication of node:1 is behind 344643936 bytes from the primary server (node:0) 2013-08 Steps to recreate are simply running pgpool.. This error pops up when that statement occurs. This is the best I can provide at the moment. I am going to suggest they update to the latest 3.2 release. Any help will be greatly appreciated!!! |
|
|
I think, this bug was fixed in the following commit. Fix long standing bug "portal not found" error when replication delay authorTatsuo Ishii <ishii@postgresql.org> Mon, 10 Dec 2012 04:08:22 +0000 (13:08 +0900) http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=7256d6051d16ffecb6f1ae09e78abe91a22695a4 Many other bugs have been fixed in the latest version. I recommend to upgrade this. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-08-28 00:43 | aliasdhacker | New Issue | |
| 2013-08-28 10:44 | nagata | Note Added: 0000311 | |
| 2013-08-28 10:44 | nagata | Assigned To | => nagata |
| 2013-08-28 10:44 | nagata | Status | new => feedback |
| 2013-08-28 13:45 | aliasdhacker | Note Added: 0000312 | |
| 2013-08-28 13:45 | aliasdhacker | Status | feedback => assigned |
| 2013-09-10 17:34 | nagata | Status | assigned => feedback |
| 2013-09-18 04:28 | aliasdhacker | Note Added: 0000330 | |
| 2013-09-18 04:28 | aliasdhacker | Status | feedback => assigned |
| 2013-09-18 22:36 | nagata | Note Added: 0000332 | |
| 2013-09-18 22:37 | nagata | Status | assigned => feedback |
| 2015-01-08 16:15 | nagata | Status | feedback => closed |
| 2015-01-08 16:15 | nagata | Resolution | open => fixed |