Ubuntu

Do you get this for all PROBLEM events? If not, is there anything special about those PROBLEM events? For instance, could it be that trigger already became OK while you were acknowledging it?

Hello. No I had only 3 problems several days ago . Two problems I closed. I changed settings devices and problems were true in real. Then I fixed settings and events disappeared.

Only one problem is true now.

So you have one trigger in PROBLEM state right now? If you try to acknowledge it, does it complain about event not being in the PROBLEM state as in "2.jpg"? If so, could you please post a screenshot of that trigger in "Monitoring" -> "Triggers" with "Events" = "Show all (7 days)" and "Show details" checked?

So you have one trigger in PROBLEM state right now? YES
If you try to acknowledge it, does it complain about event not being in the PROBLEM state as in "2.jpg"? YES

4.jpg

It seems that your trigger is in PROBLEM state, but has no PROBLEM events - only OK events.

Thus, the error message is correct and expected, but there is now a different question - how can a PROBLEM trigger have only OK events?

maybe if the problem event is old enough for the housekeeper to have removed it ?

But then OK events should be even older, shouldn't they?

yes, unless they were generated in one of those weird/wrong ways out of sequence (ZBX-9432 etc)

Vitaly, do you often get such out of sequence events in your installation?

I'm not sure that I undestand you.

There were two problems.
This is first problem. How can you see this problem lives 12 days.There are lastest data's values on picture 5.jpg

Can helps for solving issue. Scenario how to get message as in 2.jpg, if trigger is in PROBLEM state
1. Create trigger, set "PROBLEM event generation mode" to Multiple
2. Make trigger in problem state and generate 3 problem events
3. Change trigger "PROBLEM event generation mode" to Single
4. Manual close 2 last problem events
5. Go to Monitoring->Triggers
6. Open acknowledgement form of the required trigger, enter comment and submit
Result: trigger in problem state, but message "Cannot acknowledge problem: event is not in PROBLEM state. "

Hello.

Yesterday I turned off that trigger and changed trigger to Multiple and I enabled that trigger

Then I turned off that trigger and changed trigger to Single and I enabled that trigger.

Now trigger is working OK.

(1) No translation strings changed

iivs CLOSED

RESOLVED in development branch svn://svn.zabbix.com/branches/dev/ZBX-11359

(2) Please, return the checkbox and link to acknowledgements in trigger list, like we discussed.

gunarspujats RESOLVED in r63914

iivs CLOSED

(3) In order for main checkbox in list views to work, we use automatic form detection using $form->getName(). This is intentional, so we don't have to keep track of the name when we decide to change it. Now the name in tr_status.php is hardcoded. That's not good. I would suggest to rever the main code refactoring for the form and keep it as a simple bug fix.

gunarspujats RESOLVED in r63977

iivs CLOSED

(4) Annoying naming in variables:

$ack_checkbox
$ackColumn

gunarspujats RESOLVED in r63976

iivs CLOSED

TESTED

Fixed in:

• pre-3.2.2rc1 r63998
• pre-3.3.0 (trunk) r63998

(5) "Undefined index" error on Monitoring->Triggers page with selected "Show details"

Undefined index: recovery_expression [ in tr_status.php:285]

gunarspujats RESOLVED in r63998

iivs CLOSED

(6) The same message "Cannot acknowledge problem: event is not in PROBLEM state. " on page Monitoring->Overview

gunarspujats RESOLVED in r64023

natalja.zabbix still left in Monitoring→Screens (with Host group issues, Host issues, System status and Triggers overview elements) and Monitoring→Dashboard (Last 20 issues and System status widgets)

gunarspujats RESOLVED in r64091

natalja.zabbix ui tested

gunarspujats Discussed with sasha, moved to ZBX-11538

CLOSED