In TSCO the "Gateway Servers" page takes several minutes to open and console ends up on 500-Internal-server-error

Version 2
    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 Capacity Optimization


    COMPONENT:

    Capacity Optimization


    APPLIES TO:

    TrueSight Capacity Optimization 10.7.01



    QUESTION:

    When accessing Application server console on Administration>Gateway Manager, the "Gateway Servers" page takes several minutes to open, but does show the new gateway server. The link on the new server name ends up with a timeout and 500 error.


    ANSWER:

    Some tests we may execute to make sure there is a normal communication (no network issues) is to execute these commands from the Application Server:

    Network connection tests

    (1)  curl  --data @getConsoleOS.xml http://localhost:10129 

    The content of file getConsoleOS.xml as follows:  
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:GeneralManager">
    <soapenv:Header/>
    <soapenv:Body>
    <urn:getConsoleOS
    <version xsi:type="xsd:string"></version>
    </urn:getConsoleOS>
    </soapenv:Body>
    </soapenv:Envelope>


    (2)  curl  --data @listfinishedMR.xml http://localhost:10129 

    The content of file listfinishedMR.xml as follows:  
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:GeneralManager">
    <soapenv:Header/>
    <soapenv:Body>
    <urn:listAllFinishedManagerRuns <version xsi:type="xsd:string">
    </version></urn:listAllFinishedManagerRuns>
    </soapenv:Body>
    </soapenv:Envelope>


    (3) Repeat steps 1 and 2 from the Application server in order to test correct communication between both components 

    curl  --data @listfinishedMR.xml http://[GWS_hostname]:10129 
    curl  --data @getConsoleOS.xml http://[GWS_hostname]:10129 

    (4) telnet GWS_hostname 10129  


    File validation in Application Server

    One thing to consider if there are no communication issues (and timeout causing 500-internal-server-error to happen) is to check if these directories contain a valid file that has to be unique on that directory, if there are more than one file, it increases the possibility in the console to fail. So, a good way to check whether or not the configuration is correct in the Application Server as follows: 

    (1) ls -l  $CPITBASE/repository/GeneralManager/ 

    The output of the command above should return a single xml file GM_hostname.xml, if there are two or more xml files, you may proceed to delete the incorrect one (most likely the oldest file) or make sure any other files in the repository folder should not have same console ids.  . 

    (2) Check the file /opt/bmc/BCO/web/tomcat/webapps/GeneralManager/WEB-INF/gmconsolemgmt.xml. 

    This file should look similar to GM_hostname.xml, make sure that console IDs look the same in both files, so both files should be sync. 

     more /opt/bmc/BCO/web/tomcat/webapps/GeneralManager/WEB-INF/gmconsolemgmt.xml 
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?> 
    <consoleList> 
        <console> 
            <console-name>hostname_GWS1</console-name> 
            <port-no>10129</port-no> 
            <console-id>2</console-id> 
            <mode>0</mode> 
            <sd-port>10128</sd-port> 
        </console> 
        <console> 
            <console-name>hostname_GWS2</console-name> 
            <port-no>10129</port-no> 
            <console-id>4</console-id> 
            <mode>0</mode> 
            <sd-port>10128</sd-port> 
        </console> 
    </consoleList> 


      

     


    Article Number:

    000155821


    Article Type:

    FAQ/Procedural



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