-
Problem report
-
Resolution: Fixed
-
Trivial
-
None
-
None
-
1
Currently Agent 2 handles loadable plugin child processes with a universal listener (created by a syscall) to all child process signals, meaning that the listener will also catch signals unrelated to loadable plugins (like smart plugin smartctl invocations and command invocations). This means that for no-loadable plugin child processes there may be two listeners for the processes signals, creating a conflict and uncertanti - which listener will catch the signal first.
Fix this by adding singular handling to each loadable plugins process with `cmd.Run()`, `cmd.Wait(), and/or `cmd.Start()`. Remove the universal child process signal listeners.
- part of
-
ZBXNEXT-9081 Disks on a HBA are not discovered by zabbix
- Closed