Description:
Symptoms
========

The startup_abort_list contains the CONFIG_FILES token. The file users.conf is missing. The EMS Server fails to start complaining that a configuration file is missing (as expected), but then if the EMS Server is restarted, the startup succeeds.


Impact
======

Loss of Functionality
Users may not be able to connect to the server if the authorization is enabled


Workaround
==========

Check the EMS Server log file or console output after an unsuccessful startup. The server will print if files are missing, and in the case of users.conf and groups.conf will print that these files were created. The administrator should, before restarting the EMS Server, make sure that these empty files are replaced by the original missing files.
If the EMS Server is started from a script, the returned code should also be checked. By convention, a return code equal to zero means that there is no error. Any other value indicates a problem. If the script receives a non-zero return code when starting the EMS Server, it should not attempt to restart the server automatically.

Cause
=====

When startup_abort_list contains the CONFIG_FILES token, if one of the configuration file is not found, the EMS Server exits. However, in the case of users.conf and groups.conf, the EMS Server is incorrectly creating empty files before exiting. If the EMS Server is restarted without fixing that problem, empty users and/or groups files will be loaded. This can cause problems if users try to connect to the EMS Server with "authorization" enabled.


Resolution
=========

This is fixed in EMS 4.1.0.
Symptoms:

Cause:

The startup_abort_list does not always prevent the EMS Server from starting.