Availability trigger for Active Checks

[dreas]

Hi. Thanks for the response! Both are indeed not too satisfactory I guess I could add a trigger monitoring the write ability of the database and adding a dependency. However one can argue that nodata should not be triggered when there is a problem storing the data locally (cause there IS data .. it's just not stored).

[Andreas Bollhalder]

To get the locked state of the DB and depend on it would be a good idea. Unfortunatly, I don't have a solution for this.

Andreas

[Andreas Bollhalder]

I think the problem is the following:

The backup starts and the DB gets locked. Then a trapper would receive from the agent that the DB is locked, but can't update the DB, because it's locked. Therefore, the trigger for DB is locked would never comes to true and your dependencies on this trigger never works.

A possible solution could be to signal ZABBIX, before that the DB would be get locked. In a backup script, create for example a lock file. Then wait more time then the trigger of this lock file needs to get true. Make the backup and delete the lock file.

Andreas

[dreas]

Hmm true. I hadn't thought of that. How could I easily manage to trigger a trigger from my dump script before I start the dump?

[Andreas Bollhalder]

You also can setup an item for use with zabbix_sender. Use the zabbix_sender in the script to send a value which set the trigger to the needed state. I would still wait a short amount of time after using zabbix_sender to allow ZABBIX to process the value and change the trigger state.

Andreas

[dreas]

It seems the trigger state is instantly change. Will try this. Thanks for the suggestion!

[bbrendon]

I think we should stop using this thread. Its a cluster F*** of 4 different topics, which are not very related.

[bashman]

Example of agent.ping with nodata function:

http://www.zabbix.com/forum/showthread.php?p=59540