{TRIGGER.STATUS} gives opposite result in Zabbix 1.3.5

[jvalkiunas]

After much digging and forum searching I'm at a loss using a svn checkout of Zabbix 1.3.5 (as of April, 4th).

Everything is working splendidly except for my Trigger.Status shows the opposite result of the Trigger state.

ie:
manually shutdown of an SMTP server causes:
-Trigger: net.tcp.service[smtp].last(0)=0
Status = TRUE
-Action: Type = Email
Subject = Email (SMTP) server is down on {HOSTNAME}: OFF
- Monitoring/Overview and Monitoring/Triggers correctly show the host and status as down/red. Data = Down(0)

Turning the SMTP server back on causes:
-Trigger: net.tcp.service[smtp].last(0)=0
Status = FALSE
-Action: Type = Email
Subject = Email (SMTP) server is down on {HOSTNAME}: ON
- Monitoring/Overview and Monitoring/Triggers correctly show the host and status as up/green. Data = Up(1)

My second Zabbix server running 1.1.3 does not have this problem and functions correctly.

Value mappings are:
Service state 1 ⇒ Up, 0 ⇒ Down
Host status 0 ⇒ Up, 2 ⇒ Unreachable


How can I flip the TRIGGER.STATUS so tjhat it corresonds to trigger state? Any ideas of what could have gone wrong?

[dash]

http://www.zabbix.com/forum/showthread.php?t=5679