ZBX-7698.patch
strace.log
|
Duplicate |
[ZBX-7698] Zabbix does not close PostgreSQL connection socket when DB is not available Created: 2014 Jan 24 Updated: 2017 May 30 Resolved: 2014 Feb 05 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | 2.0.11rc1, 2.2.2 |
| Fix Version/s: | 2.0.11rc2, 2.2.2rc3, 2.3.0 |
| Type: | Incident report | Priority: | Major |
| Reporter: | Alexey Pustovalov | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
ZBX-7698.patch
strace.log
|
||||
| Issue Links: |
|
||||
| Description |
|
When Zabbix server can not connect to PostgreSQL it tries to execute DBExecute function, DBExecute function tries to call DBConnect again. |
| Comments |
| Comment by Alexey Pustovalov [ 2014 Jan 24 ] |
|
Also we need use low level calls to DB instead of DBExecute. Bug fix patch is attached. |
| Comment by Alexander Vladishev [ 2014 Feb 05 ] |
|
Fixed in the development branch svn://svn.zabbix.com/branches/dev/ZBX-7698 |
| Comment by Andris Zeila [ 2014 Feb 06 ] |
|
Successfully tested |
| Comment by Alexander Vladishev [ 2014 Feb 06 ] |
|
Fixed in pre-2.0.11 r42381, pre-2.2.2 r42385 and pre-2.3.0 (trunk) r42386. |