|
|
pgpool log01.PNG (95,056 bytes) Architecture.PNG (116,173 bytes) |
|
|
------ ERROR: unable to read data from frontend DETAIL: EOF encountered with frontend ------ This error may occur because the application doesn't close the connection to pgpool. Does your application use connection pooling to keep the connections open to pgpool? In this case, you may need to specify the parameter "client_idle_limit" to setting a timeout to disconnect a client if it remains idle since the last query. For example, client_idle_limit = 60; https://www.pgpool.net/docs/latest/en/html/runtime-config-connection-pooling.html#GUC-CLIENT-IDLE-LIMIT |
|
|
Hi Pengbo, Does your application use connection pooling to keep the connections open to pgpool? --> Yes, our app is using connection pooling. I specified the parameter "client_idle_limit" in pgpool-II. After several weeks, we got the attached logs and our app could not access DB through pgpool-II. Could you please help us? Thank you very much! |
|
|
I've attached logs picture! pgpool3.PNG (70,605 bytes) |
|
|
Hi Pengbo, Can you help me regarding above issue? Thank you very much! |
|
|
Sorry for late response. > I specified the parameter "client_idle_limit" in pgpool-II. > After several weeks, we got the attached logs and our app could not access DB through pgpool-II. Could you please help us? I would confirm pgpool and postgresql status, could you share the following information? (1) When your application could not access DB through pgpool, could you show me the process status of pgpool and progress? Please share the result of the following command. ---------------------- ps -ef | grep pgpool ps -ef | grep postgres ---------------------- (2) Connect to DB and run the following query. ---------------------- select * from pg_stat_activity where backend_type = 'client backend'; ---------------------- |
|
|
Hi hai.nguyentien Has your issue been resolved？ If yes, could you describe how you resolved it？ Thanks Gary |
- Anonymous
