Zabbix has intermittent (by way of upstream MySQL bugs getting fixed and reappearing) difficulties with ODBC items crashing Zabbix servers and proxies, by way of dynamic linking issues within the ODBC connector libraries.

Zabbix could fix this by having the ODBC poller relegate ODBC queries out to a subprocess that doesn't link against libmysql (or hardly anything else). This would be a very simple and straightforward (if not ideal, from an efficiency standpoint) solution that would armor the Zabbix server and proxy architecture against future issues like these.

This might look like using a pipe to feed requests in, and then receiving the results back when they're available. It doesn't even need an asynchronous alerting / are-the-results-ready-yet behavior outside of a heartbeat, I suspect, as the ODBC poller processes are only expected to be working one query at a time.

Again, this would permanently fix ZBX-7665, as well as prevent Zabbix server and proxy crashes that stem from issues from ODBC libraries.

Related to ZBX-7665 and ZBX-10654 (which I include because it shows the sporadic nature of ZBX-7665's impact).