[ZBX-24254] Database monitoring with ODBC has insufficient settings for timeout Created: 2024 Mar 21 Updated: 2025 Apr 11 |
|
| Status: | Open |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Taiki Fujiwara | Assignee: | Alexey Pustovalov |
| Resolution: | Unresolved | Votes: | 4 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Zabbix server Zabbix proxy Host |
||
| Description |
|
Database monitoring with ODBC sets only SQL_LOGIN_TIMEOUT as its timeout setting, so there is no timeout for any other processes except login. MySQL and PostgreSQL ODBC driver does not support SQL_ATTR_CONNECTION_TIMEOUT is noted in the following issue. https://support.zabbix.com/browse/ZBX-6797 So, I think it is need to add timeout handling to ODBC connection process on Zabbix side.
I have not confirmed that it is related to this, but after restarting the target host for MSSQL monitoring, the logs of the process are no longer output after the following log (DebugLevel=4) and cannot be monitored after that. In zbx_odbc_connect() dsn:'test' user:'test' I suspect that the problem may have been caused by the timeout settings.
Steps to reproduce:
Result: Cannot be monitored, but there is no error. Expected: |
| Comments |
| Comment by Smirnov Dmitriy [ 2024 Apr 02 ] |
|
Oracle monitoring also suffers from this. Database performance issues block the poller and it is never released. |
| Comment by Taiki Fujiwara [ 2025 Apr 11 ] |
|
Is there a plan to fix this problem? |