The MPP uses the mpp daemon process to start and control the various processes that enable the MPP to function as it should. If this process does not start, stops working, or experiences other problems, the MPP does not respond as it should. Therefore, if you are having problems with the MPP and you have confirmed that the httpd daemon process is running correctly as described in Troubleshooting the httpd daemon process, the next step is to check the status of the mpp daemon process.

Problems with the mpp daemon process can manifest in the following ways:

  • An improper system shutdown left a locked process file.

  • A conflict exists with permissions for the mppsysmgr directory or log file.

Proposed Solution 1: Restarting the mpp daemon process

Procedure

  1. At the Linux command line prompt, check the status of the mpp daemon process by entering the /sbin/service mpp status command.
  2. If the systems responds with a message that the service is not running, start it by entering the /sbin/service mpp start command.
  3. If the service is running, stop and then restart it:
    1. Stop the mpp daemon process by entering the /sbin/service mpp stop command.

      The system should respond with a message that ends with [OK] to indicate that the service has stopped.

    2. Restart the mpp daemon process by entering the /sbin/service mpp start command.

      The system should respond with a message that ends with[OK] to indicate that the mppsysmgr daemon has started.

  4. If the system responds with a message stating that the service cannot be started because there are locked files:
    1. Delete the lock file by entering the rm /var/lock/subsys/mppsysmgr command.
    2. Try to start the service again by entering the /sbin/service mpp start command.

    If the service still does not start, see Proposed Solution 2: Examining the mpp daemon process log files.

  5. Let the service run for several minutes, and then check the status again by entering the /sbin/service mpp status command.

    If the service status is not running, or if the problems reoccur, see Proposed Solution 2: Examining the mpp daemon process log files.

Proposed Solution 2: Examining the mpp daemon process log files

Procedure

  1. In an ASCII editor, examine the $AVAYA_MPP_HOME/logs/process/SysMgr/logfile.log log file.
  2. If you find relevant error messages in the file, perform the troubleshooting procedures described for that error message.
  3. If you cannot find any relevant error messages or if the troubleshooting procedures do not resolve the problems, see Proposed Solution 3: Checking for core files.

Proposed Solution 3: Checking for core files

Procedure

  1. Log into Linux on the MPP server.
  2. Navigate to the $AVAYA_MPP_HOME/logs/core directory and check to see if there are any mppsysmgr* core files in that directory.
  3. If the directory contains core files, delete the $AVAYA_MPP_HOME/logs/process/SysMgr/ directory.

    This solution resolves problems with permissions on the log file or directory.

  4. Reboot the MPP server.
  5. If you do not find any core files, or if deleting the files does not solve the problem, contact Avaya technical support.