Zabbix server 6.0.4 Zabbix Agent 6.0.5 (Windows host)

Hello Evgeny,

Please confirm if you're using 6.0.6 or 6.0.5. Version 6.0.6 hasn't been released yet - only a RC (release candidate) is available.
The fact that you're getting the same error running zabbix_get on Zabbix server is absolutely expected, since it's an issue related to the monitored server and, thus, will only affect Zabbix agent behaviour (zabbix_get sends a request to Zabbix agent).

I understand that "Недостаточно системных ресурсов для завершения операции" means "Insufficient system resources to complete the operation". This is an error returned by Windows, not Zabbix. To help you troubleshoot this (and to help us identify if there's a bug in Zabbix agent), please let us know if you're using Zabbix agent or Zabbix agent 2 (and also confirm the version used).

Regards,
Eduardo

6.0.5 vervion one. Sorry, my bad.

I have new data. There is result of the command bellow on the problem host here:

zabbix_agentd.exe" -t vfs.fs.discovery

vfs.fs.discovery                              [s|[{"

":"C:","{#FSTYPE}":"NTFS","{#FSLABEL}":"","{#FSDRIVETYPE}":"fixed"},{"

":"E:","{#FSTYPE}":"UNKNOWN","{#FSLABEL}":"","{#FSDRIVETYPE}":"cdrom"}]]

I don't understand. You're saying that you can execute the command locally (by calling Zabbix agent directly), but not remotely (from Zabbix server/proxy)? If so, are you using an administrator user to to call Zabbix agent locally?

I wanna say that Zabbix server can't recieve list of the disks and get the error. I can recieve the list (using an administrator user) executing the command 'zabbix_agentd.exe" -t vfs.fs.discovery' on the problem host locally.

Are files on disk acessible to other users? Also: does this error occur when there's no disk in the drive?
 

I did an experiment. If I disable FDD in Device manager(Windows Server 2019 installed on the host) I won't recieve the error. It does not work on a host with Windows Server 2008. Ater that I ran the command on the host with Windows 2008.

zabbix_agentd.exe -t vfs.fs.discovery

Result:

vfs.fs.discovery  [s|[{"

":"E:","{#FSTYPE}":"UNKNOWN","{#FSLABEL}":"","{#FSDRIVETYPE}":"cdrom"}]]

After that I run another comman on zabbix server : sudo zabbix_get -s 192.168.1.198 -k "vfs.fs.discovery"

Result:

ZBX_NOTSUPPORTED: Cannot obtain a list of filesystems: [0x000005AA] Недостаточно системных ресурсов для завершения операции.

"Also: does this error occur when there's no disk in the drive?" I have no physical access to the hosts. I can't insert a floppy.

So you're saying that, even AFTER disabling the FDD in Windows 2008 you STILL get the error?

Yes, that is true

I see. Can you try temporarily disabling drive E: also, please, and report on the results? Does the Windows 2019 server also has a device identified as CDROM?

Well. I disabled CDROM on the Windows 2008 Server host and it works! I have no error anymore. The Windows 2019 server has no CDROM.

Could you please execute the following actions?

• Re-enable the CDROM in the Windows 2008 server
• Configure Zabbix agent to debug mode 5 and restart it
• Perform the query remotely from zabbix_server
• Send us the resulting logs
• Re-configure Zabbix agent to debug mode 3 and restart it (so it does not fill your disk)

Zabbix agent log:

135320:20220718:081435.580 Sending back [ZBX_NOTSUPPORTED: Cannot obtain a list of filesystems: [0x000005AA] Недостаточно системных ресурсов для завершения операции.]
 50996:20220718:081435.582 Sending back [51977928704]

Zabbix server log:
2049471:20220718:082010.847 Item [Win2019.test.local:vfs.fs.discovery] error: Cannot obtain a list of filesystems: [0x000005AA] Недостаточно системных ресурсов для завершения операции.
2049471:20220718:082010.847 End of get_value():NOTSUPPORTED
2049471:20220718:082010.847 In zbx_activate_item_interface() interfaceid:6837 itemid:445470 type:0
2049471:20220718:082010.847 End of zbx_activate_item_interface()
2049471:20220718:082010.847 In zbx_preprocess_item_value()
2049471:20220718:082010.847 End of zbx_preprocess_item_value()
2049471:20220718:082010.847 In zbx_ipc_socket_write()
2049471:20220718:082010.847 End of zbx_ipc_socket_write():SUCCEED

Do you have the same problem during your testing?

Was Zabbix agent using debuglevel=5 in this case?

Sure!

We need the lines before "sending back"... this line just shows that the error has already happened.

7820:20220721:080030.195 In collect_perfstat()
  7820:20220721:080030.227 End of collect_perfstat()
  7820:20220721:080031.228 In collect_perfstat()
  7820:20220721:080031.260 End of collect_perfstat()
  7820:20220721:080032.261 In collect_perfstat()
  7820:20220721:080032.292 End of collect_perfstat()
  7820:20220721:080033.293 In collect_perfstat()
  7820:20220721:080033.324 End of collect_perfstat()
  7828:20220721:080034.138 Requested [vm.memory.size[total]]
  7828:20220721:080034.139 Sending back [137437872128]
  7820:20220721:080034.325 In collect_perfstat()
  7820:20220721:080034.356 End of collect_perfstat()
  7828:20220721:080035.279 Requested [vfs.fs.discovery]
  7828:20220721:080035.280 Sending back [ZBX_NOTSUPPORTED: Cannot obtain a list of filesystems: [0x000005AA] Недостаточно системных ресурсов для завершения операции.]
  7832:20220721:080035.285 Requested [vm.memory.size[used]]
  7832:20220721:080035.286 Sending back [35503271936]