Data is not being collected

[max.ch.88]

Try it on the ms windows server
zabbix_agentd -t vfs.dir.size[c:/exchange]

[1berto]

The error message you posted indicated that The agent is having a problema to access a file (the file is being used by another process), the agent don't need access to files to get CPU items, but it can getting stucked because of another item.
Also the filename in the message seems strange (slashes and backslashes mixed). Try to know which item is using this file and correct it or disable all other items and see if the item you want come back...

[MichaelF]

"Try to know which item is using this file and correct it or disable all other items and see if the item you want come back... " - yes, that's it - thank you very much for the suggestion!!! All items started working right after disabling Directory size item! ...but I do need this item - why does it works only once and then stops? I tried it even for the empty folders - the same result ((

[max.ch.88]

Well, I created the same item. Zabbix 3.4.14 on CentOS Linux release 7.5.1804 (Core), Agent 3.4.6 on Windows Server 2012 R2.
The item works. In both mode - active and passive.

https://www.zabbix.com/documentation/3.4/manual/config/items/itemtypes/zabbix_agent

Only directories with at least read permission for zabbix user are calculated.

With large directories or slow drives this item may time out due to the Timeout setting in agent and server/proxyconfiguration files. Increase the timeout values as necessary.

Examples:
⇒ vfs.dir.size[/tmp,log] - calculates size of all files in /tmp which contain 'log'
⇒ vfs.dir.size[/tmp,log,^.+\.old$] - calculates size of all files in /tmp which contain 'log', excluding files containing '.old'

The file size limit depends on large file support.

Note that in Zabbix 3.4.0-3.4.6 any symlink or hard link on Windows is interpreted as regular file or directory. Since 3.4.7, any symlink is skipped and hard links are taken into account only once.

Supported since Zabbix 3.4.0.

[MichaelF]

"Only directories with at least read permission for zabbix user are calculated." - how can I add the read permission (as well as any other) for a zabbix user which is a local Linux/Freebsd account to a folder on Windows server? I thought that in Windows it is the Zabbix Service account which should have at least read permission to a folder being monitored. Anyway, this item did work when it was first configured but stopped a bit later (and it caused all other items to stop functioning too) - this looks weird to me...
P.S. My server OS is Windows Server 2019

[max.ch.88]

You need to change the units of item to B. What is the status of the item - enable or not supported?

[MichaelF]

You need to change the units of item to B. - that didn't help.
What is the status of the item - enable or not supported? - enabled.

[max.ch.88]

What is the result of execute
zabbix_agentd -t vfs.dir.size[c:\exchange]
?

[max.ch.88]

Hi, MichaelF
I've installed ws2019 v1809 build 17763.1, with zabbix-agent 3.4.6. It's working fine.
May be to disable firewall and reinstall the zabbix-agent. Or to reinstall OS.
It seems some fault inside of this server.

[MichaelF]

Hi max.ch.88,
"zabbix_agentd -t vfs.dir.size[c:\exchange]" = No such file or directory.
"Or to reinstall OS." - mmm, so tough measures out of a single item?
I've installed zabbix agent to another Windows Server 2019 (with Exchange 2019) - the result is the same (for any folder!), but vfs.dir.size does work perfect for my own Windows 10 box so this problem arises only on my WinServers 2019. I don't know what can be the cause of this but I know there's no fault inside these servers - at least that I'm aware of. Anyway thank you and all others very much who helped me to figure out why the data was not being retrieved from my hosts.

[max.ch.88]

"... the result is the same (for any folder!)" Are you sure? Could you create a new folder and repeat the command zabbix_agentd -t vfs.dir.size[.... ?

[MichaelF]

"... the result is the same (for any folder!)" Are you sure? Could you create a new folder and repeat the command zabbix_agentd -t vfs.dir.size[.... ?" - I wouldn't have written it if I had not tried it many times This command does not work for ANY folder (including the newly-created folders containing no files at all) for my both Windows Server 2019 machines.