Good morning,
I've recently upgraded our Zabbix installation to 6.0 LTS.
I wanted to take advantage of the official zabbix smart monitoring plugin on some Windows 10 Hosts.
On them I've got:
On systems with just nvme disks, everything works fantastically.
On systems with SATA drives, I noticed that discovery times out, and system CPU usage spiking heavily.
On further inspection, it looks like the Zabbix agent was opening a bunch of instances of smartctl.exe and rapidly closing, with increasing numbers of this making the system sluggish.
I increased DebugLevel to 5 to see what was happening and it looks like zabbix is looping through device types that seem to not be supported by smartmontools on windows:
It does this for 3ware, areca and cciss types, looping forever until I stop the agent.
I can't seem to find a way to disable checking for these device types, or anything I can configure to get around this. Does anyone have any insight?
I did find a forum post in the Russian forums that could be the same issue, but not 100% sure: https://www.zabbix.com/forum/in-russ...plugin-windows
I've recently upgraded our Zabbix installation to 6.0 LTS.
I wanted to take advantage of the official zabbix smart monitoring plugin on some Windows 10 Hosts.
On them I've got:
- Zabbix Agent 2 v6.0.5
- smartmontools 7.3
- smartctl in the PATH environment variable
On systems with just nvme disks, everything works fantastically.
On systems with SATA drives, I noticed that discovery times out, and system CPU usage spiking heavily.
On further inspection, it looks like the Zabbix agent was opening a bunch of instances of smartctl.exe and rapidly closing, with increasing numbers of this making the system sluggish.
I increased DebugLevel to 5 to see what was happening and it looks like zabbix is looping through device types that seem to not be supported by smartmontools on windows:
Code:
2022/06/17 10:05:41.280692 [Smart] command smartctl -a /dev/sda -d 3ware,1 -j smartctl raw response: {
"json_format_version": [
1,
0
],
"smartctl": {
"version": [
7,
3
],
"svn_revision": "5338",
"platform_info": "x86_64-w64-mingw32-w10-21H2",
"build_info": "(sf-7.3-1)",
"argv": [
"smartctl",
"-a",
"/dev/sda",
"-d",
"3ware,1",
"-j"
],
"messages": [
{
"string": "/dev/sda: Unknown device type '3ware,1'",
"severity": "error"
},
{
"string": "=======> VALID ARGUMENTS ARE: ata, scsi[+TYPE], nvme[,NSID], sat[,auto][,N][+TYPE], usbcypress[,X], usbjmicron[,p][,x][,N], usbprolific, usbsunplus, sntasmedia, sntjmicron[,NSID], sntrealtek, intelliprop,N[+TYPE], jmb39x[-q],N[,sLBA][,force][+TYPE], jms56x,N[,sLBA][,force][+TYPE], aacraid,H,L,ID, areca,N[/E], auto, test <=======",
"severity": "error"
}
],
"exit_status": 1
},
"local_time": {
"time_t": 1655417141,
"asctime": "Fri Jun 17 10:05:41 2022 NZST"
}
}
I can't seem to find a way to disable checking for these device types, or anything I can configure to get around this. Does anyone have any insight?
I did find a forum post in the Russian forums that could be the same issue, but not 100% sure: https://www.zabbix.com/forum/in-russ...plugin-windows
Comment