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

vmware collector remains after zabbix main process was stopped

    XMLWordPrintable

Details

    • Problem report
    • Status: Closed
    • Critical
    • Resolution: Duplicate
    • 2.2.22
    • 4.0 (plan)
    • Proxy (P), Server (S)
    • Team A
    • Sprint 38
    • 2

    Description

      Steps to reproduce:

      1. service zabbix-server start

      (Running for 10 minutes~ with vmware collectors)

      2. service zabbix-server stop

      15224:20170326:010015.427 Got signal [signal:15(SIGTERM),sender_pid:19729,sender_uid:0,reason:0]. Exiting ...
      15224:20170326:010017.428 syncing history data...
      15224:20170326:010017.458 syncing history data done
      15224:20170326:010017.458 syncing trends data...
      15224:20170326:010017.774 syncing trends data done
      15224:20170326:010017.774 Zabbix Server stopped. Zabbix 3.0.4 (revision 61185).
      

      3. Try to start again zabbix-server but failed.

      listener failed: zbx_tcp_listen() fatal error: unable to serve on any address [[-]:10051
      

      because 1 vmware collector child process remaining here.

      # ps -ef |grep zabbix_server
      root 12465 5864 0 14:34 pts/0 00:00:00 grep zabbix_server
      zabbix 15437 1 0 Mar26 ? 00:00:06 /usr/sbin/zabbix_server: vmware collector #4 [updated 0, removed 0 VMware services
      in 0.000004 sec, querying VMware services]
      

      You can kill this child process <PID> directly, but It will happens sometimes.

      Attachments

        Issue Links

          Activity

            People

              vso Vladislavs Sokurenko
              JKKim Kim Jongkwon
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: