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

Too many process using zabbix with oracle RAC 11 as Backend and too many cursors never closed

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Fixed
    • Icon: Critical Critical
    • 2.2.1rc1, 2.3.0
    • 2.0.2
    • Frontend (F), Server (S)

      Zabbix with configuration for a large environment have too many problems with oracle in backend. One over all is the connections (1 for process?????) and too many session opened and never closed.

      zabbix_server.conf (for the connections):

      StartPingers=10
      StartPollers=350
      StartTrappers=5
      StartDiscoverers=1
      StartDBSyncers=20
      StartJavaPollers=10
      StartPollersUnreachable=10

      Connections from Apache are maximum 20 (from the httpd.conf, we must use prefork and not worker):

      <IfModule prefork.c>
      StartServers 1
      MinSpareServers 2
      MaxSpareServers 2
      ServerLimit 10
      MaxClients 10
      MaxRequestsPerChild 1000
      </IfModule>

      When zabbix start (fronted and server) we have 420 (minimum ) connection (in oracle "process") to database (most of this are marked as INACTIVE) and 4000 cursors that grow to 8000 and more ... We have a big RAC system and zabbix, for now, is the most used resource process for oracle ...

      For me (using backend oracle) the important thinks are:

      • CLOSE CURSORS (reason because i have opened the bug req!)
      • USE OF "CONNECTION POOL APPROACH" to better manage the connections effectively required (so process are never too much)

            Unassigned Unassigned
            yayo yayo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: