Veam job is still running trigers

[ZegalPL]

i have problem with "veam job is still running" triggers wich never get marked as OK in my zabbix, data collection seems to be ok, zabbix is receiving data, i have increased timeout setting in abbix agents on veeam servers, but to no avail.

could someone please guide me to how fix it?

BR, Piotr

EDIT: i'm using Veeam 9 and zabbix 3.0

[schzffr]

Hi,

Same problem here, thanks for your help

[xenadmin]

What does the simple graph for the item protoype "Running status for job named {#JOBNAME}" say? The Trigger is based on an average numerical value for 24h. There must be a hint there I would guess.

Before I would check the trigger, I would check the data it depends on.

I personally have disabled that Trigger, I don't think that it gives us any value.

[J0HAN85]

@xenadmin "The Trigger is based on an average numerical value for 24h." You're sure? My trigger looks only at the last value; {Template Veeam Backup:vbr["RunningJob"].last(0)}>{$VEEAM_MAX_RUNNING_JOB} Works fine for me. Of course you should have the macro "{$VEEAM_MAX_RUNNING_JOB}". I've set it to 10.

[xenadmin]

Yes I'm sure. You mixed up the triggers.

@sachazufferey Is talking about "VEEAM job {#JOBNAME} is still RUNNING" @J0HAN85 are talking about: "Too many running VEEAM jobs"

Both depend on different item keys and thereby different Triggers.

[schzffr]

All others triggers work fine, except the "STILL RUNNING" one...

Le 5 juil. 2017 4:47 PM, "Marco Hofmann" notifications@github.com a écrit :

Yes I'm sure. You mixed up the triggers.

@sachazufferey https://github.com/sachazufferey Is talking about "VEEAM job {#JOBNAME} is still RUNNING" @J0HAN85 https://github.com/j0han85 are talking about: "Too many running VEEAM jobs"

Both depend on different item keys and thereby different Triggers.

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/jjmartres/Zabbix/issues/113#issuecomment-313125647, or mute the thread https://github.com/notifications/unsubscribe-auth/AchlUCW2JkGOdRphphIXoMeHAxgoKC8gks5sK6ISgaJpZM4I9jXw .

[xenadmin]

@sachazufferey You didn't answer my question.

Before you blame the trigger, you have to check the data of the corresponding item key. In this case the item prototype: "Running status for job named {#JOBNAME} /// vbr[RunStatus,{#JOBID}]"

Maybe the item key Logs "1" all the time, and therefore the Trigger Expression is always true? Then you would have to find the reason why there is always a "1".

There is rarely a failure with Triggers, as they just evaluate the raw data of the items.

[J0HAN85]

@xenadmin whoops.. you're right, I mixed them up... But then again, if the trigger is based on average value over 24h, and the jobs runs every day it would always keep the trigger alive. Although I'm not using the trigger mine looks like; {Template Veeam Backup:vbr[RunStatus,{#JOBID}].avg(3600)}>0

[schzffr]

@xenadmin I don't blame it, I just want to understand it...

@J0HAN85 I will give it a try, thanks for the tips

[xenadmin]

@sachazufferey So did you check the item?