|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Currently testing with the following sshd options:
TCPKeepAlive yes
ClientAliveInterval 30
ClientAliveCountMax 100
The sshd logging on disconnects is now a bit different.
The "Timeout, client not responding." isn't happening anymore.
However, the session is still closed:
Feb 4 08:33:45 ip-10-4-40-213 sshd[2195]: pam_unix(sshd:session): session closed for user ec2-user
This could meen that the problem isn't in the ssh connection disappearing, but that somehow the slave process is terminated or the master terminates the connection.
I tried bringing the number of executors down to 1, didn't help.
Now we're testing with a bigger EC2 instance (C3XLarge instead of C3Large) and with a larger Java heap for the slave process (-Xmx2048M).