TrueSight Orchestration peer installed in containers does not run on the correct port

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight Orchestration Platform


    APPLIES TO:

    TrueSight Orchestration Platform 8.2.xx



    PROBLEM:

    A new BMC TrueSight Orchestration (TSO) peer installed as a Docker image does not start on the correct port. According to the logs the peer starts without error, but Grid Manager is available on an incorrect port. For example, a peer installed on port 38080 would normally publish Grid Manager at this URL:
     

      
    Instead, it publishes Grid Manager on a different port: 
       
      https://server.bmc.com:   30000/baocdp 
      
      

     


    CAUSE:

    Recent versions of Docker use a newer version of Traefik that does not accept configurations for older versions. TSO only has an older configuration, so it cannot start the load balancer component that would let it publish to the correct port.


    SOLUTION:

    Use the new port to access Grid Manager. This port is fully-functional and does not impact peer performance. All other ports, including the communications port, work as expected.

    BMC is targeting a solution for BMC TrueSight Orchestration Platform 8.3.


    Article Number:

    000175236


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles