Wrong disk size info on alerts

[danomanno]

Hello,

I have three zabbix 1.4.4 environments with about the same setup in each. The problem that I am having is that the disk space alerts that I get are incorrect for one of the environments. Here is my disk space trigger that is the same for each env:

{hostname:vfs.fs.size[/,free].last(0)}<10G

Here is my action for this trigger (actually it's a generic action for all triggers):

{HOSTNAME} - {DATE} {TIME} - {IPADDRESS}
{ITEM.NAME}: {{HOSTNAME}:{TRIGGER.KEY}.last(0)}


The disk space item is also the same for all three env. Here's what I get when the trigger goes off for the correct env:

Subject: dev - Base Disk Space Low: Warning ON
dev - 2008.08.07 00:12:51 - xxx.xxx.xxx.xxx
Free disk space on /: 10.00 GB


Here is the alert I get for the incorrect env:

Subject: stage - Base Disk Space Low: Warning ON
stage - 2008.07.23 02:21:09 - xxx.xxx.xxx.xxx
Free disk space on /: 2.00 GB

Another:

Subject: stage - Base Disk Space Low: Warning OFF
stage - 2008.07.22 00:00:09 - xxx.xxx.xxx.xxx
Free disk space on /: 261.77 MB

The alert action show correct information for all other triggers except the disk space trigger.

I can't seem to figure out where this error is coming from. The graphs/screens show the correct space readings. It's just the alerts that are messed up. Is there anywhere that I should look for extra config options?

Would it be best to just remove the disk space items and re-add them?

Thanks!

[danomanno]

Well, I think I was able to fix it... I changed the 10G label to 10000M and now I am getting correct readings. Weird.....

[danomanno]

Ok, so I haven't been able to fix this in two of my environments. One environment is working fine. I checked all settings between the three and they are all the same.

The only place that the data is incorrect is in the email alert/action. All other info such as "Latest data" and the graphs show correct information.

Why does only {TRIGGER.KEY}.last(0) in my action show the wrong data for disk space?

Where does this value come from? Why is this value in all other parts of zabbix correct except for the action?

[danomanno]

After doing some testing, it's not the action that is incorrect. The wrong value is getting passed to the action.

Where does the action get it's data from? Is there anywhere that I could look within zabbix to track down the incorrect data?

[danomanno]

OK, I answered my own question now.... Somehow, the 1.4.4 source code was hosed. I downloaded 1.4.6 and re-compiled. It is working correctly now.