BSA: secure is empty, proceeding ahead with the default secure settings 

Version 11
    Share This:

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


    PRODUCT:

    BladeLogic Server Automation Suite


    COMPONENT:

    BladeLogic Agent and NSH


    APPLIES TO:

    BSA BladeLogic Server Automation Suite



    PROBLEM:

    When attempting to connect to a BSA Target Server, the following message is observed in the rscd log on the target system:

    Windows:

    (Not_Available):(Not_Available): C:\Windows/rsc/secure is empty, proceeding ahead with the default secure settings
      


    Linux  
    (Not_available): (Not_available): /etc/rsc/secure is empty, proceeding ahead with the default secure settings
      


    This will likely be accompanied by the following: 
       
    (Not_available): (Not_available): TLS setup failed for agent: Protocol mismatch. Check that client and server "secure" files match. Exiting and terminating connection.
      

      

     


    CAUSE:

    empty secure file


    SOLUTION:

    Check the contents of the secure file on target server for the rscd line.  If not present, you will see this message and the rscd service will listen on 5750/tcp instead of the expected 4750/tcp.  The default settings in the file should be:
     

    rscd:port=4750:protocol=5:tls_mode=encryption_only:encryption=tls
      


      

     


    Article Number:

    000123692


    Article Type:

    Solutions to a Product Problem



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