Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-20340

db.odbc.get key causing crashes of Zabbix server/proxy Oracle ODBC monitoring

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Proxy (P), Server (S)
    • None

      In some cases, db.odbc.get[] key causes crash of Zabbix server/proxy instance:

      Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x30]. Crashing ...
      Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x30]. Crashing ...
      Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x30]. Crashing ...
      Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x30]. Crashing ...
      Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x30]. Crashing ...
      Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x30]. Crashing ...
      Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x30]. Crashing ...
      

      From customer:

      DB admin disabled this item: Oracle: Get system metrics in our template (the one you also received from us before). And so far no crashes. Looks like there is some problem allocating memory in the area of odbc > transformation > json > regular expression processing. There is an attempt to access non existing memory.

      Currently we have those two items disabled since yesterday: Oracle: Get system metrics and Oracle: Get system metrics_i2. And we don’t see any crashes since then. The item Oracle: Get system metrics_i2 is a copy of the Oracle: Get system metrics hence both were disabled.

      Template attached, seems to be default 5.0 Oracle ODBC monitoring template.

            MVekslers Michael Veksler
            ksalins Karlis Salins
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: