If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to REGISTER before you can post. To start viewing messages, select the forum that you want to visit from the selection below.
Ad Widget
Collapse
Problem: MSSQL: Failed to fetch info data (or no data for 30m)
I do it and odbc.ini look that, but still i have te "information"
Also, delete driver path from odbc.ini
Driver above it is correct (commented out) and its name is referencing to odbcinst.ini
Example
odbc.ini:
[MSSQLServer]
Driver = this is my driver
and odbcinst.ini:
[this is my driver]
Driver = /opt..<path to driver>
On top of it check permissions is zabbix can execute odbc commands on the driver.
And make sure your have StartODBCPollers at least set to 1 in for zabbix (or ZBX_STARTODBCPOLLERS=1 if in docker as environment vars). Its disabled by default
ok i checked my test env this is how my odbc.ini looks like
[DSN]
Driver = ODBC Driver 18 for SQL Server
DSN = DSN
Server = TCP:<ip_address>, 1433
Port = 1433
TrustServerCertificate = yes
Encrypt = false
odbcinst.ini:
[ODBC Driver 18 for SQL Server]
Description=Microsoft ODBC Driver 18 for SQL Server
Driver=/opt/microsoft/msodbcsql18/lib64/libmsodbcsql-18.1.so.1.1
UsageCount=999
regarding permissions check this file path (change to yours) not odbc.ini file permission:
/opt/microsoft/msodbcsql18/lib64/libmsodbcsql-18.1.so.1.1
also not sure if this is supposed to be installed on web container. I don't use it from zabbix server just from proxy. In proxy we have only 2x containers : main proxy and db. And I have installed it on main proxy "engine" but for the server .... I'm not sure.
When using on frontend create new item "database monitor" fill usr/psw even manually
and try simple select - does it work at all?
Also check logs on SQL itself to see if it "trying" at least to connect - if it reaching but failed login - then user permission. If there is nothing .. then to be honest i don't know.
When I look in item default created by mssql template i see this error
that means it cannot find DSN entry. or driver attached to it. so maybe it has to be installed on docker where zabbix is not web container. but I never did on server - I always used proxy to query SQL
Comment