|
Backtrace for easier searching:
|
|
It seems that you also use Oracle as the Zabbix backend database. Does it crash on every ODBC check or from time to time? Did it ever work for you before with a previous version of Zabbix? What Oracle libraries do you have installed on the system?
|
|
Seems like unixODBC was linked with /home/swcomun/herrtux/aaresmi/mon-zabbix/tools/unixODBC/lib/libodbcinst.so.2.0.0 but calls functions from /app/oracle/product/11.2.0/client_1/lib/libsqora.so.11.1 and crashes because of incompatible binary interfaces.
|
|
@Aleksandrs. This is the first time that I try ODBC check. And fails every time. I worked with 2.4 version of zabbix but i didn't use unixODBC. The Oracle libraries used are 11.2.0
@Glebs, I compiled unixODBC 2.3.4 from sources and the instaled client in my server is 11.2.0. Do you mean that unixODBC is not compatible with 11.2.0 Oracle libraries? I'm see that the libodbcinst.so.1 libraries at Oracle path has this ldd:
linux-vdso.so.1 => (0x00007fff84246000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f6339a03000)
libm.so.6 => /lib64/libm.so.6 (0x00007f633977e000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f6339561000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f6339348000)
libclntsh.so.11.1 => /app/oracle/product/11.2.0/client_1/lib/libclntsh.so.11.1 (0x00007f6336d1c000)
libodbcinst.so.1 => not found
libc.so.6 => /lib64/libc.so.6 (0x00007f6336988000)
/lib64/ld-linux-x86-64.so.2 (0x00007f6339dd8000)
libnnz11.so => /app/oracle/product/11.2.0/client_1/lib/libnnz11.so (0x00007f63365bf000)
libaio.so.1 => /lib64/libaio.so.1 (0x00007f63363be000)
when unixODBC 2.3.4 generate the libodbcinst.so.2.0.0
|
|
I haven't investigated your issue properly, but from the first glance it seems like the root cause is that both Zabbix and ODBC connector library depend on Oracle DB client library. Since Zabbix and ODBC connector (probably as a dependency for unixODBC) are built separately, generally speaking, same symbols (i.e. function calls) may resolve (at linking time) to different potentially incompatible implementations. System loader will resolve these symbols (at runtime) using either of libraries used at linking time (and consider its work done). But these leaves half of function calls with potentially incompatible implementation which leads to crashes.
From the backtrace I see that ODBC check is being processed, but functions from libsqora.so are being called. Instead of calling functions from libsqora.so for direct Zabbix connections to Oracle DB and calling functions from libodbcinst.so when connection is via unixODBC layer. Unfortunately, it is not a straightforward fix.
|
|
Dear aaresmi, there was a change of SQLLEN size from 4 to 8 bytes for 64 bit platforms between unixODBC versions 2.2.14 and 2.3.x, hence different major versions of the library (libodbc.so.1 and libodbc.so.2). As they say, this can affect drivers compiled with old definition of SQLLEN type. And you can use slencheck utility to find out what size of SQLLEN your ODBC driver adopts. Can you try this?
|
|
I had the same issue and as you pointed, as you suggest I remove installed unixODBC 2.3 of Base repo of CentOS 7 and manually install 2.2.14 from base repo of CentOS 6. Also I use the Oracle client 11.2.0.4 that is the recommended for unixODBC 2.2.14.
Additional, I added the enviroment variables to the systemd script of zabbix-server, because, systemd units don't take enviroments from the system. This was checking the EnviromentFile variable of the script
[root@zabbix ~]# cat /usr/lib/systemd/system/zabbix-server.service
[Unit]
Description=Zabbix Server
After=syslog.target
After=network.target
[Service]
Environment="CONFFILE=/etc/zabbix/zabbix_server.conf"
EnvironmentFile=-/etc/sysconfig/zabbix-server
Type=forking
Restart=on-failure
PIDFile=/run/zabbix/zabbix_server.pid
KillMode=control-group
ExecStart=/usr/sbin/zabbix_server -c $CONFFILE
ExecStop=/bin/kill -SIGTERM $MAINPID
RestartSec=10s
[Install]
WantedBy=multi-user.target
And later adding to the file that is called:
[root@zabbix ~]# cat /etc/sysconfig/zabbix-server
ORACLE_HOME=/usr/lib/oracle/11.2/client64
LD_LIBRARY_PATH=/usr/lib/oracle/11.2/client64/lib:/usr/lib64:/usr/lib:$LD_LIBRARY_PATH
TNS_ADMIN=/usr/lib/oracle/11.2/client64/network/admin
PATH=$PATH:$ORACLE_HOME/bin
You can check this by findind the main pid of zabbix-server and runnning:
[root@zabbix ~]# strings -a /proc/24415/environ
LANG=en_US.UTF-8
PATH=$PATH:$ORACLE_HOME/bin
CONFFILE=/etc/zabbix/zabbix_server.conf
ORACLE_HOME=/usr/lib/oracle/11.2/client64
LD_LIBRARY_PATH=/usr/lib/oracle/11.2/client64/lib:/usr/lib64:/usr/lib:$LD_LIBRARY_PATH
TNS_ADMIN=/usr/lib/oracle/11.2/client64/network/admin
Using zabbix 3, CentOS 7, Postgres and Nginx.
|
|
Dear aaresmi, do you have any updates?
|
|
Sorry for the long delay. With the instructions added by kanibal (thx a lot) all worked with zabbix 3.2.5 and Oracle client 11.2.0.4.
I think that is needed to add to the documentation that the correct installation versions of the UnixOBDC and Oracle client are 2.2.14 and 11.2.0.4 respectively.
thx
|
|
A similar issue was reported in ZBX-16223 and a solution was eventually found.
|
Generated at Tue Apr 01 05:57:03 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.
dump.zabbix_server.gz