Ad Widget

**zabbixfk** · 05-06-2019, 20:21

Can someone reply to this.... after upgrade, for every trigger we are seeing too many number of emails ( though configured is two).
This upgrade seems broken....

Thanks,

**zabbixfk** · 06-06-2019, 10:04

Can you someone help me figure out what's wrong with the upgrade here... if this is the case i can't depend on zabbix anymore !!!!, just a upgrade and it broke actions....

Thanks,

**vso** · 06-06-2019, 17:39

Please post some information about triggers that fired and action

**zabbixfk** · 06-06-2019, 19:48

Thanks for replying @vso.
I have already added trigger details, here it is once again.
Trigger,

Code:

Name : Low memory on {HOST.NAME}
Severity Warning
Expression : [B](({DC-Windows-Servers:vm.memory.size[free].last(180)} * 100 ) / {DC-Windows-Servers:vm.memory.size.last(180)} )<5[/B]
OK event generation : Expression [B](selected auto after upgrading from 3.0, this field wasn't there earlier)[/B]
PROBLEM event generation mode : single [B](selected auto after upgrading from 3.0, this field wasn't there earlier)[/B]
OK event closes : All problems [B](selected auto after upgrading from 3.0, this field wasn't there earlier)[/B]
Tags  : none
Allow manual close : unchecked [B](selected blank/unchecked after upgrading from 3.0, this field wasn't there earlier)[/B]
URL : none
Description : If the Free memory is below 5%
Enabled : Selected.
Dependencies : None

Actions :

Code:

[B][I]Action Tab consists[/I][/B]
Name : Low Memory On Windows Server :{HOST.NAME}
Conditions : Label A , Name Trigger equals [I]DC-Windows-Servers: Low memory on DC-Windows-Servers [/I]
New condition : Blank

Operations  :
Default operation step duration : 1m (Don't know what's this, this wasn't there on 3.0)
Default subject : {EVENT.NAME}
Default message :  
                        HostName : {HOST.NAME}
                        IP : {HOST.IP}
                        Status : {TRIGGER.STATUS}  

                       1. {ITEM.NAME1}  - {ITEM.VALUE1}
                       2. {ITEM.NAME2}  - {ITEM.VALUE2}  

                       Note: this is a system generated email. Please do not reply to this email.  

Pause operations for suppressed problems : Unchecked [B](auto populated after upgrading from 3.0, this field wasn't there earlier)[/B]

Operations :
                   Steps - 1, Details : [B]Send message to user groups: [/B]Email_DL_Compute, Email_DL_NOC via Email , Start in: Immediately , Duration : Default.  

[I][B]Recovery Operations tab consists : [/B][/I][B](auto populated after upgrading from 3.0, this field wasn't there earlier)[/B]
Default subject : {TRIGGER.STATUS}: {EVENT.NAME}
Default message :
                              Trigger: {EVENT.NAME}
                              Trigger status: {TRIGGER.STATUS}
                              Trigger severity: {TRIGGER.SEVERITY}
                              Trigger URL: {TRIGGER.URL}  
                              Item values:
                                        1. {ITEM.NAME1} ({HOST.NAME1}:{ITEM.KEY1}): {ITEM.VALUE1}
                                        2. {ITEM.NAME2} ({HOST.NAME2}:{ITEM.KEY2}): {ITEM.VALUE2}
                                        3. {ITEM.NAME3} ({HOST.NAME3}:{ITEM.KEY3}): {ITEM.VALUE3}  

Operations : Blank  

[I][B]Update Operations Tab consists: [/B][/I][B](auto populated after upgrading from 3.0, this field wasn't there earlier)[/B]
Default subject : Acknowledged: {EVENT.NAME}
Default message : {USER.FULLNAME} acknowledged problem at {ACK.DATE} {ACK.TIME} with the following message: {ACK.MESSAGE}  Current problem status is {EVENT.STATUS}
Operations : Blank.

Email_DL_Compute consists one user with groups access to Servers group, where this template is tied to those groups hosts.
Email_DL_NOC consists one user with groups access to most of the groups in system.

SO in 3.0, whenever theres this trigger fired, it creates PROBLEM event and email goes to two groups i.e two users ( each group with one user). And same case with OK event ( email sent to two groups). Each event has only two emails - that is what its suppose to do.
But in 4.0, several actions happening, i.e several emails going for these two groups with different actions body ( different as in i have lot of other actions in system and their body is getting sent), basically for this action about 33 emails sent.

Another issue: Earlier ( in 3.0), we could see when clicked on Monitoring - trigger - all the events for that trigger, but now only one tab called problems, and i am not able to see older problems, i tried all the combinations on the filters with this hostname which has low memory issue, or selecting this server hostgroup or resetting all the filters but its not displaying anything.

I have about 7K devices with more than 600 triggers and for each trigger or most of the combinations of triggers there's email action. I have disabled actions for now as emails flooding ,
I am just stuck with this upgrade. I really need some help.

Any pointers are greatly helpful.

Thanks

**vso** · 06-06-2019, 22:05

Action can fire multiple times only if condition is met, it is best to make sure that there are only one trigger that meet following condition:
Name Trigger equals DC-Windows-Servers: Low memory on DC-Windows-Servers

You can also add another condition and limiting to desired host

**zabbixfk** · 07-06-2019, 07:35

Thanks for the reply @vso.
Yes, i understand. But, there's only one trigger for all the windows hosts i.e via template.
I just don't understand, something which is working fine in 3.0, i.e sending only two emails, is sending now 30+ emails. In the first thread if you see, i have also added sample actions, there, it is sending with more fields, and some linkUtilisation action body ( this definitely from different trigger. Not from DC-Windows-Servers, but from anther action).

And let me tell you, this is not only happening to one particular template, for all the actions i am seeing multiple emails !!!!!! So definitely nothing to with this action or template - something wrong at code level.

Here are the screenshots of the action and other configs, but it seems i am no logner able to locate that problem anymore, in the problems page its not getting displayed now.

Is this something to do with this bug?

Thanks

**vso** · 07-06-2019, 08:04

Please open action and provide screenshot what are the unknown values ?

**zabbixfk** · 07-06-2019, 09:32

Thanks for the reply @vso.
Whatever is coming n UNKOWN is from different action not from this and that is what i am saying cross action mails and multiple mails for single action.
Here is the screenshot for the action.

**zabbixfk** · 07-06-2019, 10:18

See, i enabled actions, and i am seeing the number of emails going up and up rising...
Some cross actions happening here... i don't know how and why is this problem. I had to disable all the aciton in order to minimise the issue.
Please help.

**zabbixfk** · 08-06-2019, 05:51

If you see closely, one of the trigger - Low memory - for example, in addition to matching its own body, its matching most of the other action bodies and applying action on it. i.e sending email. You can refer last thread sceenshots.

Looks like its either this bug or some other bug. Basically, when i enable all the actions, every event will match with most of the actions and sending emails. Action / Email body is getting filled with random action body. I am able to reproduce this with what i have. If you want, i can provide my trigger and action dumps or any other details required , but, this is something very bad for a LTS release. All i did was upgrading from 3.0 to 4.0 i.e upgrade by running zabbix_server after compiling 4.0 version - yes i do compile, doesn't rely on rpms - i have been doing this since 2.0.x versions. - it did upgrade the database and started monitoring too - though i haven't enabled all the devices for monitoring - for testing i enabled some and i am encountering this error.

Can someone from zabbix team look into this? Or any others - any pointers are greatly helpful.

Thanks

**vso** · 08-06-2019, 13:20

It would be best to localize issue and leave one action enabled, are you saying that adding trigger condition in action results in action being fired for all other triggers ?

**zabbixfk** · 10-06-2019, 04:11

- When i have only one action enabled, i.e example low memory , i am getting only two emails - which is what that action defined and its working as expected.
Now, when i start enabling all the actions, ( have about 250+) for different triggers , each action which is fired is sending more than 30 emails. i.e
- most of the email body is not from desired action.
- It seems its pulling action body from some other actions defined.
- For example, for low memory acton, its pulling body from linkUtilisation action and values are filled as UNKNOWN.
- All the emails received as part of this have heading/body on the email says low memory.
- This is not only happening for low memory but also for all other triggers, if you look at my screenshots, triggers such as , zabbix process more than 75% busy, DHCP scope issues etc also firing more than 30 emails. And this is unaccepted as these actions have only two address configured to send emails.

And i can't keep only one action enabled, i have to enable all the actions while rolling out for production.

Really stuck on this upgrade part, need some inputs/help. Thanks in advance.

**zabbixfk** · 10-06-2019, 10:49

*bump* - can someone from zbx team or others look at this? Since this is happening to a LTS build, i feel this is quite serious issue.

**vso** · 10-06-2019, 16:31

If you think that there is a bug then it’s better to create a bug report, currently it’s unclear how to reproduce the issue.

Please note that actions only fire after trigger is fired, what possibly is happening is that trigger fires and then multiple actions get executed for that trigger because action conditions match, is that the case ? Are those 30 mails actually 30 different actions ?

Ad Widget

Multiple cross emails from actions upgrade from 3.0 to 4.0.7 : broken

Multiple cross emails from actions upgrade from 3.0 to 4.0.7 : broken

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment