|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
This error suddenly popped up in our Debian environment, running Jenkins ver. 1.565.3.
The problem only appears for the SSH agent. We use the same key for launching the slave itself, so it is odd that this error appears only when running SSH agent on the slave.
At the time the error appeared, the slave was running Oracle Java 8, but we downgraded to 7 without seeing any changes in behavior.
What worked for us as a workaround was to remove the passphrase from the SSH key.
I cannot explain what triggered the problem, but we do not have a strictly controlled environment. Debian system upgrades roll in automatically, and developers are free to upgrade plugins in Jenkins as they please. The slave was relaunched due to some network problems around the same time which could explain the timing.