1 2 Previous Next 24 Replies Latest reply: Apr 20, 2012 9:20 AM by Siddu Angadi RSS

Problem with RSCD

Oscar Avila González

Hi All.

 

I have a problem with an RSCD Agent, When I try to get the agent information appears the next message:

 

SOFCBAO01% agentinfo SOFCBAO01

 

SSL_connect2

 

SSL_connect

 

Can't access host "SOFCBAO01": Error in TLS protocol

 

 

When I try to run the getlic command appears the next message:

 

SOFCBAO01% getlic SOFCBAO01

 

Error accessing host SOFCBAO01: Error in TLS protocol

 

Do someone knows what happen to the RSCD?

 

can someone help me?

 

Thank you.

  • 1. Problem with RSCD
    Oscar Avila González

    In the rscd.log files appears:

     

    privilege mapping: BladeLogicRSCD

    03/22/12 18:07:16.309 INFO     rscd -  SOFCBAO01 4016 SYSTEM (???): ???: Adding account right "SeBatchLogonRight" to user BladeLogicRSCD@SOFCBAO01 for user privilege mapping

    03/22/12 18:07:16.357 INFO     rscd -  SOFCBAO01 4016 SYSTEM (???): ???: Adding account right "SeDenyInteractiveLogonRight" to user BladeLogicRSCD@SOFCBAO01 for user privilege mapping

    03/22/12 18:08:10.530 ERROR    rscd -  141.32.3.72 4420 SYSTEM (???): ???: new_connection: SSL finish error.

    03/22/12 18:08:18.232 ERROR    rscd -  141.32.3.72 3616 SYSTEM (???): ???: new_connection: SSL finish error.

    03/22/12 18:17:14.348 WARN     rscd -  SOFCBAO01 1264 SYSTEM (???): ???: Main: Wait Timeout. Starting AgentHouseKeeping.

    03/22/12 18:22:14.828 ERROR    rscd -  141.32.3.70 4548 SYSTEM (???): ???: new_connection: SSL finish error.

    03/22/12 18:27:14.227 WARN     rscd -  SOFCBAO01 1264 SYSTEM (???): ???: Main: Wait Timeout. Starting AgentHouseKeeping.

    03/22/12 18:37:14.310 WARN     rscd -  SOFCBAO01 1264 SYSTEM (???): ???: Main: Wait Timeout. Starting AgentHouseKeeping.

    03/22/12 18:46:13.937 ERROR    rscd -  141.32.3.70 2604 SYSTEM (???): ???: new_connection: SSL finish error.

    03/22/12 18:47:14.619 WARN     rscd -  SOFCBAO01 1264 SYSTEM (???): ???: Main: Wait Timeout. Starting AgentHouseKeeping.

    03/22/12 18:52:34.135 ERROR    rscd -  141.32.3.70 4756 SYSTEM (???): ???: new_connection: SSL finish error.

    03/22/12 18:53:09.365 ERROR    rscd -  141.32.3.70 4264 SYSTEM (???): ???: new_connection: SSL finish error.

    03/22/12 18:54:01.839 ERROR    rscd -  141.32.3.70 4408 SYSTEM (???): ???: new_connection: SSL finish error.

    03/22/12 18:56:55.969 ERROR    rscd -  141.32.3.70 2164 SYSTEM (???): ???: new_connection: SSL finish error.

    03/22/12 18:57:14.924 WARN     rscd -  SOFCBAO01 1264 SYSTEM (???): ???: Main: Wait Timeout. Starting AgentHouseKeeping.

  • 2. Problem with RSCD
    Shirish Katariya

    Hey Hi....

     

                    Did you performed installation of RSCD successfully??  And is your Box is reachable in the network or not?? May be due to this problem the You are getting the error of "TimeOut" in RSCD Log file. and how did you checking the agentinfo for your particular box?? (were you followed exact steps?)

     

    Just go into CMD prompt from your App server, and write the below mention command.::

     

    "agentinfo Server_IP"

     

    It will either give you exact agentinfo for your particular server or it will returns a notification of "Connection TimeOut" (If the box is not reachable).

     

    OR

     

    Open your BladeLogic GUI and go into folder view, brows the Servers, select respective server for whom you wants to get the agent info. Do Right click on that server and select the option " Run Custom Commands" from context menu. it will pop-up a new window, from which select Agent Information and click on OK. you will get the agent information for that server.

     

    If you still have any doubt then please share here......

     

    Thanks & Regards,

    Shirish Katariya.

  • 3. Problem with RSCD
    Oscar Avila González

    Hi.

     

    The RSCD Agent was working correct some months ago, but last week I used the "agentinfo" command and the next message appears:

     

    SOFCBAO01% agentinfo SOFCBAO01


    SSL_connect2


    SSL_connect


    Can't access host "SOFCBAO01": Error in TLS protocol

     

    I try to corrected the error and I reinstalled the RSCD.

     

    The agent was instaled successfully but the error is appears again.

     

    When I used the Console, I can´t work with this server, I have 50 servers more and only one of them has the problem.

     

    Thank you.

  • 4. Problem with RSCD
    Joe Piotrowski

    Can you compare the contents of the .../rsc/secure file from the problem server against a working server. Do you see a difference?

  • 5. Problem with RSCD
    Oscar Avila González

    Yes.

     

    The contents of the secure file is identical in all of the servers.

     

    Thanks Joe.

  • 6. Problem with RSCD
    Oscar Avila González

    Hi.

     

    I Found this Article:

     

    Knowledge Article

    SSL_connect errors when accessing Agent

     

    Knowledge Article ID:KA312612
    Version:2.0
    Status:Published
    Published date:07/20/2011
    Updated:07/20/2011

     

    Problem

    SSL_connect SSL_connect2

    SSL finish error

    Solution

    This error can be caused by an empty <WINDIR>\rsc\certificate.pem or /usr/lib/rsc/certificate.pem left behind by a previous install

    1. Stop RSCD Agent

    2. Delete certificate.pem

    3. Start Agent

    4. Valid certificate is created automatically

     

    (https://kb.bmc.com/infocenter/index?page=content&id=KA312612&actp=search&viewlocale=en_US&searchid=1332784788767)

     

     

    But in the server where have the issue, there isn´t the \rsc\certificate.pem file. Someone knows if this file can be copy from another server? or what is the reason to the file is not creating?

     

    Thanks.

  • 8. Problem with RSCD
    Joe Piotrowski

    Here is the error and solution if you don't have access to that post:

     

    When I try to verify some servers in the BL OM console, I get the following error:
    "Error in TLS protocol: <servername>"

    I have tried the following two procedures to rectify this problem with no success:
    1. Restart the BL agent;
    2. Execute the command: "secadmin -m rscd -p 5 -T encryption_only" and then select option 6 (TLS) and then restart the BL agent.

    I am still unable to verify the server and still get the "Error in TLS protocol" pop-up error message.What else can I check/do to fix this problem?

     

    Solution:
    Some further investigation by a colleague (Saurabh) found that the certificate.pem file in /usr/lib/rsc was empty on the machine exhibiting the problem. We then took the contents of certificate.pem from a working machine and recreated certificate.pem on the non-working machine. We then re-ran the 'secadmin' command and restarted the rscd agent and the problem is no longer there now.

  • 9. Problem with RSCD
    Oscar Avila González

    Hi Joe.

     

    I tried the solution that you sending me, but the issue is continued.

     

    thanks for your help.

  • 10. Problem with RSCD
    Joe Piotrowski

    What is the OS of this server? Another poster said it was a firewall issue on theirs. Stopping iptables as a test worked for them.

  • 11. Problem with RSCD
    Oscar Avila González

    The SO is Windows Server 2008 R2 Enterprise.

     

    The firewall can be cause that the Certificate.pem file is not creating?

  • 12. Problem with RSCD
    Joe Piotrowski

    They did not provide details unfortunately. My assumption would be they didn't configure port 4750 properly in some regard.

     

    You might want to open a ticket on this, if you haven't already, while you see if anyone else can help on here. I've run out of ideas, sorry. =)

  • 13. Problem with RSCD
    Oscar Avila González

    Joe.

     

    Thank you very much for your help.

     

    Regards.

  • 14. Problem with RSCD
    Joe Piotrowski

    Found this reference in an old 7.4.3 document. Not sure if it helps much. But it describes the reason for the "SSL finish error" message in the log.

     

    122 <module>: SSL finish error.

     

    Error Fatal

     

    The RSCD agent had a problem closing a client connection.

     

    Examine the RSCD agent log for further errors. Assure the client is not prematurely closing the connection during connection close.

1 2 Previous Next