Expected actions not triggered following an event

In situations where a large number of events are generated and where an action or actions that are expected to be triggered on the master are not triggered, then most probably not all events arrived on the server. There are a number of steps you can perform to collect the necessary information customer support requires to assist you in solving the problem.

Collecting required information:

  1. Set the keyword LogEvents = YES in the following files on the server and client. By default, the value assigned to this keyword is NO.
    On the client
    On Windows operating systems
    <TWA_home>/EIF/monmaneif.templ
    <TWA_home>/ssm/eif/tecad_snmp_eeif.templ
    On UNIX operating systems
    <TWA_DATA_DIR>/EIF/monmaneif.templ
    <TWA_DATA_DIR>/EDWA/ssm/eif/tecad_snmp_eeif.templ
    On the server
    On Windows operating systems
    <TWA_home>TWS\stdlist\appserver\engineServer\temp\TWS\EIFListener/eif.templ
    On UNIX operating systems
    <TWA_DATA_DIR>/stdlist/appserver/engineServer/temp/TWS/EIFListener/eif.templ
  2. On the client, stop and start monman by submitting the respective command.
    Stop
    conman stopmon
    Start
    conman startmon
  3. On the server, stop and start the event processor submitting the respective command.
    Stop
    conman stopevtproc
    Start
    conman startevtproc
  4. All generated events are logged in a file. By default, this file is stored in the path /EIF. Collect these logs and send them to customer support. Because this log file can become quite large very quickly, there are ways to filter the events that get logged in the file.
    On the server, set the LogEventsFilter keyword using a regular expression to filter events written on the server. By default, the value of this keyword is ".*" and therefore all events are logged. For example, if you are aware that problems originate from a specific client, then you can specify the CPU name of the client in the value of the LogEventsFilter keyword to limit the events logged to the file to this specific client as follows:
    LogEventsFilter=.*<cpu_name>#MONMAN.*