ExportXMLWordPrintable

    • 1

      After upgrading/installing Zabbix Agent 2 8.0.0rc1, the agent starts successfully but crashes approximately two seconds later with a Go panic in the MQTT plugin configuration code.

      The agent does not need to process an MQTT item first; the crash occurs during Agent 2 startup/configuration.

      Result

      Starting Zabbix Agent 2 (8.0.0rc1)
      Oct 01 17:11:22 zbx zabbix_agent2[2101851]: Zabbix Agent2 hostname: [TTN,log item]
      Oct 01 17:11:22 zbx zabbix_agent2[2101851]: Press Ctrl+C to exit.
      Oct 01 17:11:24 zbx zabbix_agent2[2101851]: panic: runtime error: invalid memory address or nil pointer dereference
      Oct 01 17:11:24 zbx zabbix_agent2[2101851]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x78 pc=0x861a03]
      Oct 01 17:11:24 zbx zabbix_agent2[2101851]: goroutine 37 [running]:
      Oct 01 17:11:24 zbx zabbix_agent2[2101851]: golang.zabbix.com/agent2/plugins/mqtt.(*Plugin).Configure(0x1685de0, 0xc0001120d8, {0x0?, 0x0?})
      Oct 01 17:11:24 zbx zabbix_agent2[2101851]:         /tmp/build-rhel-9-x86_64.69z8XI1L/buildroot/BUILD/zabbix-8.0.0rc1/src/go/plugins/mqtt/config.go:62 +0x143
      Oct 01 17:11:24 zbx zabbix_agent2[2101851]: golang.zabbix.com/agent2/internal/agent/scheduler.(*configuratorTask).perform.func1()
      Oct 01 17:11:24 zbx zabbix_agent2[2101851]:         /tmp/build-rhel-9-x86_64.69z8XI1L/buildroot/BUILD/zabbix-8.0.0rc1/src/go/internal/agent/scheduler/task.go:598 +0xfe
      Oct 01 17:11:24 zbx zabbix_agent2[2101851]: created by golang.zabbix.com/agent2/internal/agent/scheduler.(*configuratorTask).perform in goroutine 9
      Oct 01 17:11:24 zbx zabbix_agent2[2101851]:         /tmp/build-rhel-9-x86_64.69z8XI1L/buildroot/BUILD/zabbix-8.0.0rc1/src/go/internal/agent/scheduler/task.go:596 +0xcc
      Oct 01 17:11:24 zbx systemd[1]: zabbix-agent2.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
      

      *Expected result
      *
      Agent 2 should start normally.

      If the MQTT configuration is invalid or incomplete, Agent 2 should report a configuration error instead of terminating with a Go panic / segmentation violation.

        1. screenshot-1.png
          110 kB
          Brian van Baekel

            Assignee:
            Oskars Pucka
            Reporter:
            Brian van Baekel
            Team INT
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - Not Specified
                Not Specified
                Logged:
                Time Spent - 6.5h
                6.5h