View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000657 | Pgpool-II | Bug | public | 2020-10-31 10:16 | 2020-11-25 21:06 |
| Reporter | Nilsson | Assigned To | t-ishii | ||
| Priority | high | Severity | major | Reproducibility | random |
| Status | resolved | Resolution | open | ||
| OS | Centos 8 | ||||
| Product Version | 4.1.4 | ||||
| Fixed in Version | 4.1.5 | ||||
| Summary | 0000657: Sporadic "Sorry, to many clients already" | ||||
| Description | I have written more information about this issue on stackoverflow. But paste the maim text here also. For more files and info please see this link: https://stackoverflow.com/questions/64615097/pgpool-ii-sorry-too-many-clients-already Issue: Every now and then there is an error from the pgpool cluster: Sorry, too many clients already. Usually when connecting with psql, but sometimes this also happens from entity framework. My initial thought was that this was because the databases had to many clients connected, but running pg_stat_activity just seconds after the error shows that there are way less connections (around 50), then the 150 max_connections in psql config. I could not find any errors at all in psql logs in the "log" folder in psql data directory. But in the pgpool.log file there are an error entry: Oct 30 16:34:19 sql1 pgpool[4062984]: [109497-1] 2020-10-30 16:34:19: pid 4062984: ERROR: Sorry, too many clients already pgpool has num_init_children = 32 and max_pool = 4 so I do not really see where the problem might be coming from. | ||||
| Tags | No tags attached. | ||||
|
|
There is a similar report: https://www.pgpool.net/mantisbt/view.php?id=656 The problem happens when a query is canceled. If it applied to this too, you can try a patch attached to 0000656. If not, please let us know how to reproduce the problem. |
|
|
First of all, thank you very much for your resonse. Impressive responsetime, it is very much appreciated. I have checked the other report and this might actually be the same problem. (My application still works after one or many of these errors occurred though. But I guess the counter goes down in other ways.) I do not really know how to apply the patch and think I will wait for november 19 for the official update. |
|
|
I have upgraded now to 4.1.5. So far everything seems to work ok. I think though I cannot by certainty say that this issue is resolved until around 2 months from now, since it took quite some time until the last problem occurred. So close this issue for now and if, which I do not think, the error comes back I open a new issue instead. |
|
|
Ok, I will close this issue for now. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-10-31 10:16 | Nilsson | New Issue | |
| 2020-11-01 08:06 | t-ishii | Note Added: 0003594 | |
| 2020-11-01 08:06 | t-ishii | Assigned To | => t-ishii |
| 2020-11-01 08:06 | t-ishii | Status | new => feedback |
| 2020-11-02 22:06 | Nilsson | Note Added: 0003595 | |
| 2020-11-02 22:06 | Nilsson | Status | feedback => assigned |
| 2020-11-25 20:33 | Nilsson | Note Added: 0003612 | |
| 2020-11-25 21:05 | t-ishii | Fixed in Version | => 4.1.5 |
| 2020-11-25 21:05 | t-ishii | Note Added: 0003613 | |
| 2020-11-25 21:06 | t-ishii | Status | assigned => resolved |
