Monitor folder size

[jordibrand]

I've done the same thing on another server 2008 and a server 2012, it's working just fine. I think it's something on that specific server that's not working or incorrect. I get back to you in a few days.

Answer to question A:

[jordibrand]

Is it possible that the script takes to long to run? I can imagine if the folder size is very large, there's a timeout and you get no output. If so, how/where can I expand that time?

[simoon]

Check Timeout parameter in agent config.
Max value is 30.

[aib]

There are two ways to solve your problem with long running script.
1) Increase Timeout= to maximum number (30 sec) on both side (server side and client side) in config files and restart server and client.

Timeout=30

2) Change the way of collecting data.
- Change Item type from Zabbix agent to Trapper. It changes the way of collecting data from "querying" to "accept incoming"
- Create a local script on client side and make it starts regularly (cron or scheduler). Use zabbix_sender inside of script to send data from client to server

All information about zabbix_sender, script, etc can be collected on Zabbix Manual page or on this forum.

[jordibrand]

Everything is working fine now! I've increased the timeout on every server to 30 seconds, every item is working.
Thanks to everyone!!

[aib]

Well done!

[jordibrand]

Last question
I'm monitoring about 100 folders, 2 folders are giving an error in powershell:
Path of folder or files are too long. The file has to be less than 260 characters and the folder less than 248 characters.
Is there a workaround, or isn't it going to work at all with powershell?

[aib]

Last question
I'm monitoring about 100 folders, 2 folders are giving an error in powershell:
Path of folder or files are too long. The file has to be less than 260 characters and the folder less than 248 characters.
Is there a workaround, or isn't it going to work at all with powershell?

From top of my head - map long path to individual drive and check that drive for free space.

subst M: c:\users\geek\desktop

and then check folder.size[M:\]

[jordibrand]

It was that simpel Thanks!

[troffasky]

Inconsistent :-(

I am using the above Powershell one-liner on Windows 2008 and I've noticed holes in the data, but when I test it it's always fine. So I ran this:

# while sleep 30 ; do zabbix_get -s theserver -k folder.size[C:/temp/] ; done

and I get something like this:

59467878
59467878
59467878
59467878
ZBX_NOTSUPPORTED
ZBX_NOTSUPPORTED
ZBX_NOTSUPPORTED
59467878
59467878
59467878

Seems like it returns not supported for whatever reason and that probably causes it to be disabled [further enlarging the hole]. I am logging with level 3 and there is nothing in the log file of any interest.

Has anybody else seen similar behaviour?

[coreychristian]

troffasky,

It could be a timeout, or it could be returning an invalid data set. If you look in the zabbix server/proxy logs do you see any errors for your system and that metric?

[troffasky]

Yeah, the error is that it's not supported :-S

3354:20160411:144831.583 item [theserver:folder.size[c:/temp/]] became not supported: Not supported by Zabbix Agent
3353:20160411:151630.213 item [theserver:folder.size[c:/temp/]] became supported
3353:20160411:152031.550 item [theserver:folder.size[c:/temp/]] became not supported: Not supported by Zabbix Agent
3342:20160411:152627.994 item [theserver:folder.size[c:/temp/]] became supported

I am going to try turning logging up to 4 but it does produce a ludicrous quantity of information. Really there needs to be a logging level 3.5.

[coreychristian]

Yeah was hoping it would have more detail, what version of Zabbix Server are you running? Newer versions have a bit more detail in the logs/web ui usually.

That said it usually is either indicative of a timeout or invalid data being returned.

[angelhc]

A simple way to monitor folder size is create a item like this :

system.run[powershell -noprofile -command "(Get-ChildItem -r C:\log | Measure-Object -property length -sum |select sum).sum"]

No need to deploy on each server a new line on the configuration file.

Regards!

[troffasky]

Running 2.2. Will start testing whatever version of Zabbix comes with Ubuntu 16.04 shortly.

I didn't really get to the bottom of why the data wasn't always reported back. The issue only seems to occur one or so every 24h so it's not a massive deal.