Check Apache Configuration for the Back Office - Fluid Topics - 3.1

Install Fluid Topics on a Single Server

Product
Fluid Topics
FT_Version
3.1
Platform
Debian
Category
Technical Notes
language
English

A tool is available to check if Apache has been properly configured on the Back Office server.

This tool is available in the antidot-troubleshooting-tools package.

Run the following command (does not require any specific user permissions):

/usr/local/afs7/Fluid-Topics/python/bin/bo_health_check

This command:

  1. Sends a request to the Back Office to make sure it is reachable.
  2. Sends a request containing an encoded slash to make sure that the "AllowEncodedSlashes" parameter is properly activated.

  • If the command returns the following result:

    04:59:46 INFO: Sending normal request
    04:59:46 INFO: Normal request succesfull, BO is reachable
    04:59:46 INFO: Sending encoded request
    04:59:46 INFO: Encoded Request Succesfull, AllowEncodedSlashes is ON

    the Back Office is reachable AND AllowEncodedSlashes has been properly activated.

  • If the command returns the following result:

    04:59:46 ERROR: Error 503: Is BO server started? If you are using RHEL, make sure SELinux is disabled

    the Back Office is not reachable. Make sure that the BO server is started by running the following command:

    As root user

    /etc/init.d/bo_server status

  • If the command returns the following result:

    AFS v7 BO Web Services server not running.

    run the following command:

    As root user

    /etc/init.d/bo_server start

  • If the command returns the following result:

    04:59:46 INFO: Sending normal request
    04:59:46 INFO: Normal request succesfull, BO is reachable
    04:59:46 INFO: Sending encoded request
    04:59:46 WARNING: Error 404: AllowEncodedSlashes is not On
    04:59:46 WARNING: You need to add "AllowEncodedSlashes On" to the vhost file controlling http://localhost

    the Back Office is reachable BUT AllowEncodedSlashes has not been properly activated. Ensure that you followed all Apache Virtual Host Configuration steps.