Maintenance mode

Maintenance mode is an Eclipse Amlen server state that allows a system administrator to complete a number of tasks. In maintenance mode, a system administrator can clean the server store, stop and start the server, and change the server state from Maintenance to Running.

There are several reasons that the Eclipse Amlen server state changes to maintenance mode:
  • There is a configuration error. For example:
    • High Availability might be configured with the wrong IP address for the local replication NIC.
    • The LDAP Bind DN password might be changed on the LDAP server, and therefore the Eclipse Amlen server cannot connect.
    • A certificate might be invalid or corrupted.
  • The system administrator sets the server state to Maintenance by using REST Administration APIs, or by using the Amlen WebUI. For more information changing the server state, see Changing the server state.
  • The store is corrupted and unrecoverable, or there are insufficient system resources to start the store. When any of these issues occur, the Eclipse Amlen server automatically changes the server state to Maintenance.
  • A pair of Eclipse Amlen servers in a high availability (HA) pair is incorrectly configured for cluster membership. One server in the HA pair might be configured for cluster membership but the other server in the HA pair might not be configured for cluster membership. For more information about configuring HA on cluster members, see Configuring HA.

To diagnose why the server is in maintenance mode, check the status of the server, and check the log files for possible causes. After you resolve the issue, you can change the server state from Maintenance. For more information about checking the status of the server and changing the server state, see Changing the server state.

If the store is corrupted and unrecoverable, or if there are insufficient system resources to start the store, you might need to clean the store. Cleaning the store deletes all persistent data, including messages, subscriptions, and client states. Do not clean the store unless you want to delete all persistent data on the system. For more information about cleaning the store, see Cleaning the store.

As an alternative to cleaning the store, consider setting the "TolerateRecoveryInconsistencies": object to true by using an Eclipse Amlen REST API POST method. Setting "TolerateRecoveryInconsistencies": true, and then restarting the server, allows Eclipse Amlen to continue and try to recover as much data as possible if it encounters problems with persisted data during restart. Any data that cannot be reconstructed correctly is deleted; this setting results in partial, possibly complete, data loss. Cleaning the store, however, always deletes all persistent data. For more information about setting "TolerateRecoveryInconsistencies": true, see Set TolerateRecoveryInconsistencies.