我正在尝试通过SSH将我的Jenkins主服务器连接到从属节点。我已经验证我能够在终端的主节点和从节点之间进行SSH。我已经为Jenkins提供了从节点的密钥和密码。我的主机密钥验证策略是Manually Trusted key verification Strategy. When I select
启动代理`,我看到以下错误。
[11/22/17 09:40:39] [SSH] Opening SSH connection to ec2-**-**-**-**.*********.compute.amazonaws.com:22.
[11/22/17 09:40:39] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed.
[11/22/17 09:40:39] [SSH] Authentication successful.
SSH connection reports a garbage before a command execution.
Check your .bashrc, .profile, and so on to make sure it is quiet.
The received junk text is as follows:
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
null
[11/22/17 09:40:39] Launch failed - cleaning up connection
[11/22/17 09:40:39] [SSH] Connection closed.
Jenkins登录主节点显示以下内容。
Nov 22, 2017 10:18:57 AM hudson.plugins.sshslaves.verifiers.TrileadVersionSupportManager getTrileadSupport
WARNING: Could not create Trilead support class. Using legacy Trilead features
java.lang.ClassNotFoundException: hudson.plugins.sshslaves.verifiers.JenkinsTrilead9VersionSupport
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:560)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at hudson.plugins.sshslaves.verifiers.TrileadVersionSupportManager.createVersion9Instance(TrileadVersionSupportManager.java:51)
at hudson.plugins.sshslaves.verifiers.TrileadVersionSupportManager.getTrileadSupport(TrileadVersionSupportManager.java:32)
at hudson.plugins.sshslaves.verifiers.SshHostKeyVerificationStrategy.getPreferredKeyAlgorithms(SshHostKeyVerificationStrategy.java:68)
at hudson.plugins.sshslaves.verifiers.ManuallyTrustedKeyVerificationStrategy.getPreferredKeyAlgorithms(ManuallyTrustedKeyVerificationStrategy.java:105)
at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:797)
at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:793)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[11/22/17 10:18:58] SSH Launch of DevOperations on ec2-**-**-**-**.*********.compute.amazonaws.com failed in 641 ms
这似乎是.bashrc
的问题,但我不知道在.bashrc
文件中要编辑什么以使其安静。
如何让SSH启动成功?
詹金斯:ver。 2.91主节点:Amazon Linux AMI发布2017.09
Slave Node:Ubuntu 14.04
答案 0 :(得分:0)
我找到了修复程序。在Slave框中,我必须编辑~/.bashrc
以删除设置颜色的位置:
magenta=$(tput setaf 4)
reset=$(tput sgr0)
删除此问题解决了问题