Occurs when log level is set to debug.

      In vmware.c module on line 3827 a string parameter is missing in the call to "zabbix_log" . This will case the "fatal_signal_handler" to be called.

      "zabbix_log" has a lock on the log_access mutex. The fatal_signal_handler also wants to log and is requesting the same mutex. Hence a deadlock occurs.

      To make things worse all other threads that want to log will end up in the same deadlock causing whole Zabbix server to hang.

      Advice is (besides fixing the bug) to rewrite the fatal signal handler so it does not depend on the log mutex to do its work.

            Unassigned Unassigned
            jasper.molenmaker Jasper Molenmaker
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: