View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000458 | Pgpool-II | General | public | 2019-01-26 01:52 | 2019-02-27 07:41 |
| Reporter | adityakamana | Assigned To | t-ishii | ||
| Priority | high | Severity | major | Reproducibility | N/A |
| Status | resolved | Resolution | open | ||
| Product Version | 4.0.2 | ||||
| Target Version | 4.0.3 | ||||
| Summary | 0000458: Pgpool generates lot of core dump files | ||||
| Description | I have installed pgpool 4.0.2 on Centos 6 with one master and one standby host. After starting pgpool, I see a lot of core dump files being generated. | ||||
| Steps To Reproduce | Start pgpool. | ||||
| Additional Information | Attached core dump output (17513.log) and pgpool.conf | ||||
| Tags | No tags attached. | ||||
|
|
|
|
|
Core dump output |
|
|
trying to attach again. |
|
|
Is it possible to a provide stack trace using gdb? |
|
|
Can you tell me how to generate a stack trace using gdb? |
|
|
I managed to generate some trace: (gdb) bt #0 0x00007ffff6c8d207 in raise () from /usr/lib64/libc.so.6 0000001 0x00007ffff6c8e8f8 in abort () from /usr/lib64/libc.so.6 0000002 0x00007ffff6ccfd27 in __libc_message () from /usr/lib64/libc.so.6 0000003 0x00007ffff6cd8489 in _int_free () from /usr/lib64/libc.so.6 0000004 0x000000000044d42a in pattern_compare (str=str@entry=0x7c77d8 "", type=type@entry=0, param_name=<optimized out>, param_name@entry=0x4ac49b "black_query_pattern_list") at utils/pool_select_walker.c:270 0000005 0x000000000044823f in pool_where_to_send (query_context=0x7c39c8, query=0x7c77d8 "", node=0x7c4810) at context/pool_query_context.c:418 0000006 0x000000000043c234 in Parse (frontend=frontend@entry=0x7ba028, backend=backend@entry=0x7ffff7fc7210, len=4, contents=contents@entry=0x7c19b8 "") at protocol/pool_proto_modules.c:1141 0000007 0x000000000043cf89 in ProcessFrontendResponse (frontend=frontend@entry=0x7ba028, backend=backend@entry=0x7ffff7fc7210) at protocol/pool_proto_modules.c:2503 0000008 0x000000000042fb39 in read_packets_and_process (frontend=frontend@entry=0x7ba028, backend=backend@entry=0x7ffff7fc7210, reset_request=reset_request@entry=0, state=state@entry=0x7fffffff1264, num_fields=num_fields@entry=0x7fffffff1262, cont=cont@entry=0x7fffffff126c "\001") at protocol/pool_process_query.c:4905 0000009 0x000000000043062b in pool_process_query (frontend=0x7ba028, backend=0x7ffff7fc7210, reset_request=reset_request@entry=0) at protocol/pool_process_query.c:285 0000010 0x000000000042af99 in do_child (fds=fds@entry=0x7b5c70) at protocol/child.c:388 0000011 0x0000000000407be5 in fork_a_child (fds=0x7b5c70, id=28) at main/pgpool_main.c:659 0000012 0x000000000040e8c9 in PgpoolMain (discard_status=discard_status@entry=0 '\000', clear_memcache_oidmaps=clear_memcache_oidmaps@entry=0 '\000') at main/pgpool_main.c:378 0000013 0x00000000004062ca in main (argc=<optimized out>, argv=<optimized out>) at main/main.c:349 |
|
|
Did you figure out anything from the dump? |
|
|
Yes, I think there's a bug with Pgpool-II, which is only revealed when input query is empty. I have already pushed the fix into all supported branches. For 4.0 stable branch, here is the commit. https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f7427e21121f115715fb23ae5aa6225675fa53ba |
|
|
How do I apply this patch to my existing installation? Do I have to reinstall pgpool? |
|
|
Yes, you need to reinstall pgpool. You can download full source code from "snapshot" link. Or you could wait till next minor release is out (see the release schedule: https://pgpool.net/mediawiki/index.php/Roadmap). |
|
|
I have installed the patch and dont see any core dump files now. I will let pgpool run for a couple more days and see. Thank you t-ishii. |
|
|
You are welcome. Looking forward to hearing from you the result. |
|
|
Can we mark this is as resolved? |
|
|
Yes please. The issue was resolved. Thank you so much for you quick help on this. |
|
|
Thanks. Issue resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-01-26 01:52 | adityakamana | New Issue | |
| 2019-01-26 01:52 | adityakamana | File Added: pgpool.conf | |
| 2019-01-26 02:22 | adityakamana | Note Added: 0002330 | |
| 2019-01-26 02:23 | adityakamana | File Added: 17513.zip | |
| 2019-01-26 02:23 | adityakamana | Note Added: 0002331 | |
| 2019-01-26 16:30 | t-ishii | Note Added: 0002332 | |
| 2019-01-27 02:12 | adityakamana | Note Added: 0002333 | |
| 2019-01-27 02:52 | adityakamana | Note Added: 0002334 | |
| 2019-01-28 23:53 | adityakamana | Note Added: 0002347 | |
| 2019-01-29 15:57 | t-ishii | Assigned To | => t-ishii |
| 2019-01-29 15:57 | t-ishii | Status | new => assigned |
| 2019-01-29 17:42 | t-ishii | Note Added: 0002352 | |
| 2019-01-29 17:42 | t-ishii | Target Version | => 4.0.3 |
| 2019-01-29 17:43 | t-ishii | Status | assigned => feedback |
| 2019-01-29 17:44 | t-ishii | Note Edited: 0002352 | |
| 2019-01-31 04:23 | adityakamana | Note Added: 0002357 | |
| 2019-01-31 04:23 | adityakamana | Status | feedback => assigned |
| 2019-02-04 08:57 | t-ishii | Note Added: 0002364 | |
| 2019-02-04 08:58 | t-ishii | Status | assigned => feedback |
| 2019-02-04 14:04 | t-ishii | Note Edited: 0002364 | |
| 2019-02-06 01:36 | adityakamana | Note Added: 0002370 | |
| 2019-02-06 01:36 | adityakamana | Status | feedback => assigned |
| 2019-02-06 08:14 | t-ishii | Note Added: 0002372 | |
| 2019-02-06 08:15 | t-ishii | Status | assigned => feedback |
| 2019-02-24 20:19 | t-ishii | Note Added: 0002401 | |
| 2019-02-27 00:57 | adityakamana | Note Added: 0002407 | |
| 2019-02-27 00:57 | adityakamana | Status | feedback => assigned |
| 2019-02-27 07:40 | t-ishii | Note Added: 0002408 | |
| 2019-02-27 07:41 | t-ishii | Status | assigned => resolved |
