View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000273 | Pgpool-II | Bug | public | 2016-12-19 14:40 | 2017-08-29 09:43 |
| Reporter | bharattelange | Assigned To | pengbo | ||
| Priority | high | Severity | major | Reproducibility | have not tried |
| Status | closed | Resolution | open | ||
| Product Version | 3.5.4 | ||||
| Summary | 0000273: ERROR: unable to read data from frontend | ||||
| Description | Following are the environment details: Pgpool Version: 3.5.4 Postgresql Version: 9.5.2 We have multiple tomcat instances. When we run first instance, it connects to pgpool and successfully deploy the war file. but second instance didn't get deployed at all. Also, pgpool does not accepts any further connections. When we checked logs, following errors are seen: ERROR: unable to read data from frontend DETAIL: EOF encountered with frontend No errors is postgresql.log pgpool.conf: (Attaching the same) num_init_child = 80 max_pool = 6 max_connections = 500 in postgresql.conf | ||||
| Tags | No tags attached. | ||||
|
|
|
|
|
Upgraded pgpool to Version 3.6.0, but the errors still persists. Attaching the logs and conf herewith. |
|
|
We have made following changes in pgpool configuration and found that now it is observed that pgpool connections does not get stuck and pgpool allows to connect now. But the performance has been degraded and slowness is being observed. child_life_time = 10 child_max_connections = 0 connection_life_time = 10 client_idle_limit = 10 Following is the error observed in pgpool logs. 2017-01-13 15:03:57: pid 26132: ERROR: unable to read data 2017-01-13 15:03:57: pid 26132: DETAIL: child connection forced to terminate due to client_idle_limit:10 is reached 2017-01-13 15:03:57: pid 26132: LOCATION: pool_process_query.c:4671 2017-01-13 15:03:57: pid 26132: DEBUG: session context: unsetting query in progress. DONE 2017-01-13 15:03:57: pid 26132: LOCATION: pool_session_context.c:225 2017-01-13 15:03:57: pid 26132: DEBUG: called by pool_sent_message_destroy: sent message: address: 0x242fbf0 kind: P name: == 2017-01-13 15:03:57: pid 26132: LOCATION: pool_session_context.c:442 2017-01-13 15:03:57: pid 26132: DEBUG: checking if query context can be safely destroyed 2017-01-13 15:03:57: pid 26132: DETAIL: query context 0x2431fc0 is still used 2 times. query:"SET extra_float_digits = 3" 2017-01-13 15:03:57: pid 26132: LOCATION: pool_session_context.c:879 2017-01-13 15:03:57: pid 26132: DEBUG: called by pool_sent_message_destroy: sent message: address: 0x242fc88 kind: B name: == 2017-01-13 15:03:57: pid 26132: LOCATION: pool_session_context.c:442 2017-01-13 15:03:57: pid 26132: DEBUG: session context: unsetting query in progress. DONE 2017-01-13 15:03:57: pid 26132: LOCATION: pool_session_context.c:225 2017-01-13 15:03:57: pid 26132: DEBUG: pool_write: to backend: 0 kind:X 2017-01-13 15:03:57: pid 26132: LOCATION: pool_stream.c:436 2017-01-13 15:03:57: pid 26132: DEBUG: RESET ALL CONFIG VARIABLES 2017-01-13 15:03:57: pid 26132: LOCATION: pool_config_variables.c:3992 2017-01-13 15:03:57: pid 26608: ERROR: unable to read data 2017-01-13 15:03:57: pid 26608: DETAIL: child connection forced to terminate due to client_idle_limit:10 is reached 2017-01-13 15:03:57: pid 26608: LOCATION: pool_process_query.c:4671 2017-01-13 15:03:57: pid 26608: DEBUG: session context: unsetting query in progress. DONE 2017-01-13 15:03:57: pid 26608: LOCATION: pool_session_context.c:225 2017-01-13 15:03:57: pid 26608: DEBUG: called by pool_sent_message_destroy: sent message: address: 0x242fbf0 kind: P name: == 2017-01-13 15:03:57: pid 26608: LOCATION: pool_session_context.c:442 2017-01-13 15:03:57: pid 26608: DEBUG: checking if query context can be safely destroyed 2017-01-13 15:03:57: pid 26608: DETAIL: query context 0x2431fc0 is still used 2 times. query:"SET extra_float_digits = 3" 2017-01-13 15:03:57: pid 26608: LOCATION: pool_session_context.c:879 2017-01-13 15:03:57: pid 26608: DEBUG: called by pool_sent_message_destroy: sent message: address: 0x242fc88 kind: B name: == 2017-01-13 15:03:57: pid 26608: LOCATION: pool_session_context.c:442 2017-01-13 15:03:57: pid 26608: DEBUG: session context: unsetting query in progress. DONE 2017-01-13 15:03:57: pid 26608: LOCATION: pool_session_context.c:225 2017-01-13 15:03:57: pid 26608: DEBUG: pool_write: to backend: 0 kind:X 2017-01-13 15:03:57: pid 26608: LOCATION: pool_stream.c:436 2017-01-13 15:03:57: pid 26608: DEBUG: RESET ALL CONFIG VARIABLES 2017-01-13 15:03:57: pid 26608: LOCATION: pool_config_variables.c:3992 |
|
|
Could you try the latest version of Pgpool-II 3.5.8? http://www.pgpool.net/yum/rpms/3.5/redhat/rhel-7-x86_64/ |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-12-19 14:40 | bharattelange | New Issue | |
| 2016-12-19 14:40 | bharattelange | File Added: logs.zip | |
| 2016-12-20 09:35 | t-ishii | Assigned To | => pengbo |
| 2016-12-20 09:35 | t-ishii | Status | new => assigned |
| 2016-12-27 15:16 | bharattelange | File Added: pgpool.zip | |
| 2016-12-27 15:16 | bharattelange | Note Added: 0001265 | |
| 2017-01-13 19:33 | bharattelange | Note Added: 0001292 | |
| 2017-06-07 10:04 | pengbo | Note Added: 0001531 | |
| 2017-06-13 13:01 | pengbo | Status | assigned => feedback |
| 2017-08-29 09:43 | pengbo | Status | feedback => closed |
