IT Process Automation

Expand all | Collapse all

Unable to connect to remote SSH host. class com.sshtools.j2ssh.transport.TransportProtocolException

  • 1.  Unable to connect to remote SSH host. class com.sshtools.j2ssh.transport.TransportProtocolException

    Posted 02-06-2018 10:10 AM

    Hi Team,

    We are getting the below mentioned error while having SSH connection from last 5 hours.

     

    Unable to connect to the remote SSH host. class com.sshtools.j2ssh.transport.TransportProtocolException The connection did not complete

     

    The runbooks were executing fine from many months. Many times we have faced similar type of issue, when none of the runbook was able to perform SSH connection to the Unix/Linux based machines. At that time we have restarted the application and the problem got resolved.

     

    Now we are looking for some detail regarding this error and an permanent resolution to this. As hundreds of runbook are in production, failing which creating a lot of additional work and time loss in Production environment.

     

    Kindly let us know the possible solution to this issue.

     

     

    Thanks and Regards,

    Ankur Gupta



  • 2.  Re: Unable to connect to remote SSH host. class com.sshtools.j2ssh.transport.TransportProtocolException

    Broadcom Employee
    Posted 02-06-2018 10:37 AM

    Ankur,

    I would strongly recommend opening a support case so we can investigate this in more detail, but we can do some investigation here if you would prefer. 

     

    >What version of Process Automation are you using?

     

    >What Operators are you having a problem with?

     

    >Do other operators continue to work and this only impacts the SSH connection?

     

    >When this fails, the only requirement to 'fix' the problem is to restart the Process Automation server? 

     

    >Does this only impact 1 connection or do all SSH based connections from Process Automation start failing at the same time?

     

    >Has anything changed on the Linux server? 

         Any patches applied?

         Has the IP address changed?

         Any other changes at the Linux system?

     

    >Can you please set INFO level logging and provide the c2o.log file for our review.

           

    The following changes will take effect immediately without a restart of the Orchestrator Engine:


    1.  Browse to <PAM>\server\c2o\conf\ and backup the log4j.xml
    2.  Open the Log4j.xml in a text editor.
    3.  Change Threshold value for C2OFILE to INFO

    <appender name="C2OFILE" class="org.jboss.logging.appender.RollingFileAppender">
         <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
         <param name="File" value="${jboss.server.home.dir}/log/c2o.log"/>
         <param name="Threshold" value="INFO"/>
         <param name="Append" value="true"/>
         <param name="MaxFileSize" value="50000KB"/>
         <param name="MaxBackupIndex" value="3"/>

    4. Change ROOT priority value to INFO

       <!-- ======================= -->
       <!-- Setup the Root category -->
       <!-- ======================= -->

       <root>
    <priority value="INFO" />
    <appender-ref ref="FILE"/> 
    <appender-ref ref="CONSOLE"/> 
    <appender-ref ref="C2OFILE"/>   
       </root>

     

     

    Then cause, or wait for the failure to occur again and provide us with the logs.



  • 3.  Re: Unable to connect to remote SSH host. class com.sshtools.j2ssh.transport.TransportProtocolException

    Posted 02-07-2018 03:15 AM

    Hi Michael,

     

    Thank you for your reply.

    I had opened the support case in CA yesterday for this issue.

     

    Thanks & Regards,

    Ankur Gupta