当前位置: 首页 > 知识库问答 >
问题:

升级Jenkins后,无法启动通过SSH连接的从节点

钮才哲
2023-03-14
[02/28/14 14:20:02] [SSH] Checking java version of java
Couldn't figure out the Java version of java
bash: java: command not found

[02/28/14 14:20:02] [SSH] Checking java version of /usr/bin/java
Couldn't figure out the Java version of /usr/bin/java
bash: /usr/bin/java: No such file or directory

[02/28/14 14:20:02] [SSH] Checking java version of /usr/java/default/bin/java
Couldn't figure out the Java version of /usr/java/default/bin/java
bash: /usr/java/default/bin/java: No such file or directory

[02/28/14 14:20:02] [SSH] Checking java version of /usr/java/latest/bin/java
Couldn't figure out the Java version of /usr/java/latest/bin/java
bash: /usr/java/latest/bin/java: No such file or directory

[02/28/14 14:20:02] [SSH] Checking java version of /usr/local/bin/java
Couldn't figure out the Java version of /usr/local/bin/java
bash: /usr/local/bin/java: No such file or directory

[02/28/14 14:20:02] [SSH] Checking java version of /usr/local/java/bin/java
Couldn't figure out the Java version of /usr/local/java/bin/java
bash: /usr/local/java/bin/java: No such file or directory

[02/28/14 14:20:02] [SSH] Checking java version of         /users/mdspadm/tools/hudson_tmp/jdk/bin/java
Couldn't figure out the Java version of /users/mdspadm/tools/hudson_tmp/jdk/bin/java
bash: /users/mdspadm/tools/hudson_tmp/jdk/bin/java: No such file or directory

[02/28/14 14:20:03] [SSH] Checking java version of     /users/apache/tools/hudson/usr/lib/jvm/jre-1.5.0-ibm//bin/java
[02/28/14 14:20:03] [SSH] /users/apache/tools/hudson/usr/lib/jvm/jre-1.5.0-ibm//bin/java -version returned 1.5.0.
[02/28/14 14:20:03] [SSH] Starting sftp client.
[02/28/14 14:20:03] [SSH] Copying latest slave.jar...
[02/28/14 14:20:04] [SSH] Copied 346,845 bytes.
Expanded the channel window size to 4MB
[02/28/14 14:20:04] [SSH] Starting slave process: cd "/users/mdspadm/tools/hudson_tmp"   && /users/apache/tools/hudson/usr/lib/jvm/jre-1.5.0-ibm//bin/java  -jar slave.jar
<===[JENKINS REMOTING CAPACITY]===>channel started
java.io.IOException: Remote call on tunnel_mspvq330 failed
at hudson.remoting.Channel.call(Channel.java:731)
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:449)
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:345)
at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:812)
at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:598)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassFormatError: Failed to load 

参考文献:http://jenkins-ci.org/content/good-bye-java6

共有1个答案

仲鸿风
2023-03-14

如果您已经从一个非常老的版本升级了Jenkins,我建议您更新Java,

还有其他问题,可能是Java bin路径的System/Envronment变量丢失或不正确?

Java在最新的更新中还引入了新的安全特性,所以要注意可能需要的任何额外身份验证。

 类似资料:
  • Jenkins master运行在Amazon实例上,从机设置在专用的Soyoustart机器上。工作正常,直到需要重做从属设置:重新安装OS,安装Java,向从属authorized_keys添加masters key,并删除/再次添加masters known_hosts中的从属。为从机设置新的凭据,并在Jenkins master中配置节点,但它无法连接到从机。 设置是相同的,并且一直在与其

  • 我在Unix系统(OEL)上安装了一个Jenkins master。我配置了两个通过SSH启动的Unix从机(也是OEL)。从属程序永远不会启动,主程序的GUI中也不会报告错误(根本没有输出,只是一个旋转的球): 我在文件中看到的唯一警告是: 主服务器上的JDK版本是: 从服务器上的Java版本: 看起来Jenkins没有启动任何SSH连接。 将Jenkins升级到1.607版本后,在尝试启动从机

  • 我用这个命令升级了open ssh:sudo apt-get升级openssh-server 我重新启动了服务器,之后,我无法连接到任何数据库(Wordpress数据库,you'll数据库,phpmyadmin数据库) 对于WordPress我得到:错误建立数据库连接 对于yourls,我得到:数据库配置不正确,或无法连接到数据库 对于phpmyadmin我得到:mysqli_real_conne

  • 我在周末将笔记本电脑从Kubuntu 12.04升级到12.10,一切看起来都很好,直到我重新开始工作。 笔记本电脑是一台通过php5 fpm运行Nginx和php的webdev机器,但现在看来php5 fpm不会启动。当我运行/etc/init时。d/php5 fpm重启我刚收到一条消息说失败。我在syslog或/var/log/fpm php中没有收到任何消息。www.log提供有关正在发生的

  • 我读过一些文章,其中他们建议使用手动密钥,我在上面也这样做了,但身份验证仍然失败。我错过了什么?

  • 我已经使用ELS 1.4.1在Windows 7版本x64上成功安装了Elasticsearch。升级到Kibana 4 RTM后,需要ELS 1.4.4。 为了执行升级,我执行了以下步骤: 下载ELS 1.4.4 启动服务后,它会在几秒钟内停止。记录如下: (请注意,这是为了开发目的) 如果从命令提示符下运行elasticsearch,会出现以下错误: