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

High CPU / Faliure to Match REGEX

    XMLWordPrintable

Details

    • Problem report
    • Resolution: Fixed
    • Critical
    • 3.4.13rc1, 4.0.0beta1, 4.0 (plan)
    • 3.4.8
    • Agent (G), Proxy (P), Server (S)
    • Team C
    • Sprint 31, Sprint 32, Sprint 33, Sprint 34, Sprint 35, Sprint 36, Sprint 37, Sprint 38, Sprint 39, Sprint 40
    • 2

    Description

      Steps to reproduce:
      Create a hosttem with the following Macros:
      {$IP_NEIGHBOR1} value 201.16.1.34
      {$IP_NEIGHBOR2} value 201.16.1.35

      On this host create a item with the keys bellow:
      Item1

      snmptrap["(.|[[:space:]])*OSPF-TRAP-MIB::ospfNbrStateChange(.|[[:space:]])*OSPF-MIB::ospfNbrState.{$IP_NEIGHBOR1}.0(.|[[:space:]])*"]

      Item2

      snmptrap["(.|[[:space:]])*OSPF-TRAP-MIB::ospfNbrStateChange(.|[[:space:]])*OSPF-MIB::ospfNbrState.{$IP_NEIGHBOR2}.0(.|[[:space:]])*"]

      Send a trap like this:

      17:41:30 2018/04/10 ZBXTRAP 201.16.0.20
PDU INFO:
  notificationtype               TRAP
  version                        1
  receivedfrom                   UDP: [201.16.0.20]:59065->[201.16.8.5]:162
  errorstatus                    0
  messageid                      0
  community                      brfmgmt
  transactionid                  3358
  errorindex                     0
  requestid                      1915218045
VARBINDS:
  DISMAN-EVENT-MIB::sysUpTimeInstance type=67 value=Timeticks: (227107105) 26 days, 6:51:11.05
  SNMPv2-MIB::snmpTrapOID.0      type=6  value=OID: OSPF-TRAP-MIB::ospfNbrStateChange
  OSPF-MIB::ospfRouterId.0       type=64 value=IpAddress: 201.16.0.20
  OSPF-MIB::ospfNbrIpAddr.201.16.1.34.0 type=64 value=IpAddress: 201.16.1.34
  OSPF-MIB::ospfNbrAddressLessIndex.201.16.1.34.0 type=2  value=INTEGER: 0
  OSPF-MIB::ospfNbrRtrId.201.16.1.34.0 type=64 value=IpAddress: 201.16.0.6
  OSPF-MIB::ospfNbrState.201.16.1.34.0 type=2  value=INTEGER: 8
  SNMPv2-MIB::snmpTrapEnterprise.0 type=6  value=OID: JUNIPER-CHASSIS-DEFINES-MIB::jnxProductNameMX480

      Then the zabbix main trapper process shall spike to 100% cpu utilization.

      Attachments

        Issue Links

          causes

          Problem report - Problem report ZBX-15010 Regex in "log" item causes "cannot compile regular expression" error

          • Major - Major loss of function.
          • Closed

          Problem report - Problem report ZBX-15107 Incorrect error handling in compile_filename_regexp() if file name regexp does not compile in logrt[], logrt.count[] items

          • Major - Major loss of function.
          • Closed

          Problem report - Problem report ZBX-15318 Invalid regular expression in snmptrap[] Item

          • Major - Major loss of function.
          • Closed

          Problem report - Problem report ZBX-15178 If "output template" references captured groups which do not exist in regexp then item value can be unpredictable

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              yurii Jurijs Klopovskis
              klausps Klaus Schneider
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: