Enabling Logging for SSH2 Library

If the SSH2 connection fails with no useful information in the PPM logs, you can route the logs of the SSH library to a dedicated file and set its logging level to a more verbose setting by adding the following text in your logging.conf file. You can change the red parts as you demand.

# SSH2 logging. 
log4j.logger.com.kintana.core.net.ssh.apache=DEBUG, SSH2_LOG 

# SSH2_LOG has a dedicated log file to easily pinpoint any error during SSH2 connection. 
log4j.appender.SSH2_LOG=org.apache.log4j.RollingFileAppender 
log4j.appender.SSH2_LOG.File=${jboss.server.home.dir}/log/ssh2_SSH2_LOG.txt 
log4j.appender.SSH2_LOG.Append=true 
log4j.appender.SSH2_LOG.MaxFileSize=250KB 
log4j.appender.SSH2_LOG.MaxBackupIndex=20 
log4j.appender.SSH2_LOG.layout=org.apache.log4j.PatternLayout 
log4j.appender.SSH2_LOG.layout.ConversionPattern=%x:%t:%c:%d{yyyy/MM/dd-HH:mm:ss.SSS z}: %m%n