Techtip : Why are my custom actions not executed by systemedge .

Document created by DirkBleyenberg Employee on Oct 31, 2014
Version 1Show Document
  • View in full screen mode

Problem :

 

I have defined some actions to be executed when my self monitor entry is triggered , but these actions are not executed .    

 

Solution :

 

By default the agent does not execute any actions .

This has to be enabled in the sysedge.cf file  when using manual configuration .

find the following section in the sysedge.cf

 

################################################################################

# This entry instructs the agent NOT to invoke actions.

# Any monitor can configure an action, which will always be invoked concurrent

# to the sending of any trap (including notReady traps).

# Attention: Per default actions are running as system respectively root user.

#

# Syntax:

#    no_actions

################################################################################

template no_actions

no_actions

 

Comment out the no_actions and restart the agent .

 

When using Virtual assurance for infrastructure you have to enable this on the  sysedge policy .Untitled1.png

 

and deploy the update policy to the agent .

 

 


Attachments

    Outcomes