View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002875 | SOGo | Backend General | public | 2014-08-03 10:01 | 2016-12-15 18:03 |
Reporter | bf-sogo | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | [Server] Linux | OS | Ubuntu | OS Version | 14.04 LTS |
Product Version | 2.2.7 | ||||
Summary | 0002875: SOGo core dumps signal 6 after running out of database connections | ||||
Description | SOGo 2.2.7 (WOWorkersCount 4) is connected to a Postgresql 9.3.4 unix socket. The Connection limit for postgres is 250. Browsing the calendar results in many database connections being spawned. Eventually SOGo stops displaying events in the calendar, the log shows sogod could not open additional conenctions to the database, received a signal 6 and dumped its core. Immediately after startup 5 sogod (4 workers) are running, 16 postgres sogodb processes are running. After logging in the user in monthly calendar view 71 postgres sogodb processes are running. The user has 9 calendars on display (2 owned, 7 shared owned by other users). Browsing back through the monthly calendar view adds 9 postgres sogodb processes per month. At some point (usually after >100 postgres sogodb processes are running) no more events are displayed, the log shows sogod has shut down. Increasing the number of workers does not seem to make a difference. | ||||
Steps To Reproduce | replicate setup, browse calendar | ||||
Additional Information | sogo.log excerpt before crash: | ||||
Tags | No tags attached. | ||||
If you can reproduce it easily (I can't), produce a stack trace: https://sogo.nu/nc/support/faq/article/how-do-i-debug-sogo.html |
|