Troubleshooting the httpd daemon process

Last Updated : Dec 07, 2012 |

The MPP uses the Apache Web server for performing operations. The Apache Web server is identified on the system and controlled by the httpd daemon process process. Therefore, if you suspect problems with the Apache Web server, check the status of the httpd daemon process.

Note:

These strategies assume that you have checked the Avaya Experience Portal system status on the <System name> Details tab of the System Monitor page.

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

  • The EPM indicates that the operational state of the MPP is Not Responding or Unknown.

  • When you log in to the Media Server Service Menu, the browser window displays an error message that the page cannot be displayed, the server cannot be found, or there is a DNS error.

  • An improper system shutdown left a locked process file.

  • The MPP key and/or certificate is corrupted.

If none of these solutions help to identify and resolve the problem, contact your Avaya technical support representative for assistance.

Proposed Solution 1: Restarting the httpd daemon process

Procedure

  1. Log on to the MPP server as a root user.
  2. At the Linux command line prompt, check the status of the httpd daemon process by entering the /sbin/service httpd status command.
  3. If the httpd daemon process is not running, start it by entering the /sbin/service httpd start command.
  4. If the httpd daemon process is running, stop it and then restart it:
    1. Stop the httpd daemon process by entering the /sbin/service httpd stop command.

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

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

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

  5. 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/httpd command.
    2. Start the service again by entering the /sbin/service httpd start command.

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

  6. Let the service run for several minutes, and then check the status by entering the /sbin/service httpd status command.

    If the service is:

Proposed Solution 2: Examining the httpd daemon process MPP log files

Procedure

  1. In an ASCII editor, open the following log files:

    • /var/log/error_log

    • /var/log/httpd/ws_error_log

  2. Search both log files for the following error messages:

    • >Unable to configure RSA server private key

    • >SSL Library Error: 185073780 error:0B080074:x509

    • certificate routines:X509_check_private_key:key values

    • mismatch

  3. If you find these errors in either log file, reinstall the MPP software to create a new certificate on the MPP.

    When you reconnect the MPP and the EPM, these errors should be resolved.

  4. If you do not find these errors in either log file, see Proposed Solution 3: Examining the httpd daemon process log files.

Proposed Solution 3: Examining the httpd daemon process log files

Procedure

  1. Log into Linux on the EPM server.
  2. In an ASCII editor, open the EPM log file /opt/Avaya/ExperiencePortal/VPMS/logs/avaya.vpms.log.
  3. Search for error messages relating to the httpd daemon process.
  4. If you do not find any messages relating to the problem, In an ASCII edit, open the log file $CATALINA_HOME/logs/catalina.out.
  5. Search for error messages relating to the httpd daemon process.
  6. If you do not find any messages relating to the problem, contact Avaya technical support.