Cause
Memory corruption or bad code/build.
Proposed Solution
Procedure
- Verify that the server state is corrupt by entering the following commands on the Linux command line: server stop -Sf -s arbiter start -s arbiter server -c
If the output no longer shows Mode: Corrupt!, then the problem is fixed. Otherwise, proceed to Step 2.
- If the
arbiter file is OK or if the problem persists, go to the Avaya Support website at http://support.avaya.com to open a service request.
