Configuration Errors

When an EMS server is started, the fault tolerance mechanism is triggered by the presence of a URL in the "secondary_listens" node of a primary tibemsd, or by that of a URL in the "primary_listens" node of a secondary tibemsd.

Once fault tolerance is triggered, the EMS server generates an error if it finds that the "ft_active" Boolean was not set for any URL in its peer’s node. If CONFIG_ERRORS is present in the startup_abort_list parameter, the tibemsd aborts startup. Otherwise, the tibemsd cancels fault tolerance and starts without checking its peer. This results in a file lock error for the EMS server that is started second.