Need help...

[darkwolf29a]

I'm trying to figure out a way to get a true list of :

100*last("AIX-SNMP-hrStorageDescr6")/last("AIX-SNMP-hrStorageSize6") and what they attach to. I want to create actual triggers for these issues. Right now, it appears that Zabbix is, simply, using one tigger, for /, and alerting based on that.


Also, it seems to be alerting incorrectly on it, as the file system never truly goes above about 5%.

Any help here?

[darkwolf29a]

Further information on this:

Used: 1039380
Size: 1048576

If you do the math, that comes out to be 99% free. Yes, it's a small file system. But, it's never used much in production and it's the same size there. This is an exact copy, block for block, of the production file system. It only gets copied once a day to this server, but it alearts all day.

Not sure why, but I am open to suggestions.

[darkwolf29a]

Ok, I now understand, I think, why I'm getting these alerts. I have more than one hrStorageSize6, for example.

I have found another way of doing this same alerting, using {Template_AIX:vfs.fs.size[/,pfree].last(0)}<10 for example.

So, my question now becomes if this will work with my ancient version of Zabbix, 1.8 Appliance.

I know, we should really upgrade, but now is not the time. We are in the middle of various upgrades, so.. yeah... time is not my friend right now.

Thanks for any suggestions.

[darkwolf29a]

So, if I stop and restart the zabbix services, will that force Zabbbix to reset that number to 1 and start rebuilding that set of temporary variables?

Right now, we have a bunch of these variables that are wrong. In fact, they are alerting on incorrect values. When the temporary value was first set it was fine, but since that filesystem has been unmounted and things mounted before it. So, now the numbers that attach to what file system are all messed and I am getting false alerts.

I am really digging in to this, so any thoughts will be utilitized.