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.