[ZBX-23520] MSSQL ODBC monitoring - SQL Timeout error [258], Login timeout expired, Unable to complete login process due to delay in prelogin response Created: 2023 Oct 09  Updated: 2024 Nov 19  Resolved: 2024 Oct 03

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 6.0.22, 6.4.7, 7.0.0alpha6
Fix Version/s: 6.0.35rc1, 7.0.5rc1, 7.2.0alpha1

Type: Problem report Priority: Major
Reporter: Łukasz Assignee: Aleksandr Kotsegubov
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Team: Team INT
Story Points: 1

 Description   

Steps to reproduce:

  1. In place by default from time to time
  2. Monitored via ODBC SQL gets timeouts restored in the next 30-60 seconds
  3. Most probably increasing the timeout value will help to get rid of this issue
  4. Maybe additional improvements like ability to provide frequent queries might be helpful too. 

 

Result:
600701:20231009:045104.498 item "SQL1:mssql.db.log_flush_waits_sec.rate["SomeDatabase"]" became not supported: Cannot connect to ODBC DSN: [SQL_ERROR]:[HYT00][0][[unixODBC][Microsoft][ODBC Driver 17 for SQL Server]Login timeout expired]|[08001][258][[unixODBC][Microsoft][ODBC Driver 17 for SQL Server]TCP Provider: Timeout error [258]. ]|[08001][258][[unixODBC][Microsoft][ODBC Driver 17 for SQL Server]Unable to complete login process due to delay in prelogin response]

Expected:

Increase default SQL timeout parameters:



 Comments   
Comment by Aleksandr Kotsegubov [ 2024 Sep 30 ]

Available in:

Comment by Marianna Zvaigzne [ 2024 Oct 01 ]

Documentation updated:

Generated at Thu May 01 08:11:17 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.