odbc installation for low level discovery with proxy

[andrea.g.els]

I'm reading about low level discovery with ODBC, and I need to do LLD on one host monitored through a proxy (No direct monitor , different DC )
Where i must install the ODBC package ? On the proxy or on the mysql host ?

checked

https://www.zabbix.com/documentation/3.4/manual/config/items/itemtypes/odbc_checks

and

https://www.zabbix.com/documentation/3.4/manual/discovery/low_level_discovery/sql_queries

but doesn't shed light

[LenR]

I'm pretty sure on the proxy

[Hernandes Martins]

Yes, the best practices on the proxy.

[andrea.g.els]

ok , done and tested with isql from the proxy :

[root@proxy zabbix]# sudo -u  zabbix  isql -v DSN
+---------------------------------------+
| Connected!                            |
|                                       |
| sql-statement                         |
| help [tablename]                      |
| quit                                  |
|                                       |
+---------------------------------------+

created the template , and assigned to the host (which is managed by the proxy).

From the server's log I can find those entries :

  6695:20180814:105715.947 item "dbhost:db.odbc.discovery[discovery,DSN]" became not supported: Cannot connect to ODBC DSN:[SQL_ERROR]:[HY000][2003][[unixODBC][MySQL][ODBC 5.2(w) Driver]Can't connect to MySQL server on '10.14.100.30' (13)]|

any clue?
there is something else needed to put the proxy in charge for the discovery , except the "managed by proxy" in the client ?

[andrea.g.els]

additional note : despite having interval set to 30s for this rule , I've seen this message only once

[Hernandes Martins]

Hi,

look (13) = permision denied

run test

# isql DSN user password

or

# query | isql DSN user password


Follow the examples

https://www.zabbix.com/documentation/3.4/manual/config/items/itemtypes/odbc_checks

Search commands isql with queries.

Regards

[andrea.g.els]

Hello Hernandes,
the permission denied hint (also if not 100% accurate) ringed a bell.


It was a selinux missing permission on the proxy host

zabbix_server.log:  6695:20180814:105715.947 item "HOST:db.odbc.discovery[DISCOVERY,DSN]" became not supported: Cannot connect to ODBC DSN:[SQL_ERROR]:[HY000][2003][[unixODBC][MySQL][ODBC 5.2(w) Driver]Can't connect to MySQL server on 'IP' (13)]|
zabbix_server.log:  6698:20180814:132513.848 discovery rule "HOST:db.odbc.discovery[DISCOVERY,DSN]" became supported

ausearch -c 'zabbix_proxy' --raw | audit2allow -M my-zabbixproxy
semodule -i my-zabbixproxy.pp
setsebool -P zabbix_can_network 1

fixed the issue


It's still unclear to me why the discovery run after 2 hrs and half instead of 30 seconds as configured

[Hernandes Martins]

Wow

Great job!!!

[DmitryL]

Keep in mind that proxy gets fresh configuration from the server only once an hour by default.