日韩性视频-久久久蜜桃-www中文字幕-在线中文字幕av-亚洲欧美一区二区三区四区-撸久久-香蕉视频一区-久久无码精品丰满人妻-国产高潮av-激情福利社-日韩av网址大全-国产精品久久999-日本五十路在线-性欧美在线-久久99精品波多结衣一区-男女午夜免费视频-黑人极品ⅴideos精品欧美棵-人人妻人人澡人人爽精品欧美一区-日韩一区在线看-欧美a级在线免费观看

歡迎訪問 生活随笔!

生活随笔

當前位置: 首頁 > 编程资源 > 编程问答 >内容正文

编程问答

Launch failed - cleaning up connection

發布時間:2024/9/27 编程问答 27 豆豆
生活随笔 收集整理的這篇文章主要介紹了 Launch failed - cleaning up connection 小編覺得挺不錯的,現在分享給大家,幫大家做個參考.

Jenkins遠程連接ssh(Linux系統)失敗

關鍵信息:
Warning: no key algorithms provided; JENKINS-42959 disabled

Warning: no key algorithms provided; JENKINS-42959 disabled SSHLauncher{host='192.168.45.145', port=22, credentialsId='61eab5fd-5c3f-4bc7-a794-f87136cbff5c', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.KnownHostsFileKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true} [05/20/19 16:20:01] [SSH] Opening SSH connection to 192.168.45.145:22. [05/20/19 16:20:01] [SSH] WARNING: No entry currently exists in the Known Hosts file for this host. Connections will be denied until this new host and its associated key is added to the Known Hosts file. Key exchange was not finished, connection is closed. java.io.IOException: There was a problem while connecting to 192.168.45.145:22at com.trilead.ssh2.Connection.connect(Connection.java:758)at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1175)at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:846)at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:833)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.io.IOException: Key exchange was not finished, connection is closed.at com.trilead.ssh2.transport.KexManager.getOrWaitForConnectionInfo(KexManager.java:95)at com.trilead.ssh2.transport.TransportManager.getConnectionInfo(TransportManager.java:237)at com.trilead.ssh2.Connection.connect(Connection.java:710)... 7 more Caused by: java.io.IOException: The server hostkey was not accepted by the verifier callbackat com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:548)at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:790)at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:502)... 1 more 連接時失敗是啥情況啊 [08/06/18 17:52:52] [SSH]打開SSH連接到10.18.6.30:22。 C:\ Windows \ system32 \ config \ systemprofile \ .ssh \ known_hosts [SSH]在C:\ Windows \ system32 \ config \ systemprofile \ .ssh \ known_hosts中找不到已知的主機文件。請確保在此路徑中創建一個并且Jenkins可以讀取它。 密鑰交換未完成,連接已關閉。 java.io.IOException:連接到10.18.6.30:22時出現問題 在com.trilead.ssh2.Connection.connect(Connection.java:834) 在hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1324) 在hudson.plugins.sshslaves.SSHLauncher $ 2.call(SSHLauncher.java:831) 在hudson.plugins.sshslaves.SSHLauncher $ 2.call(SSHLauncher.java:820) 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) 在java.lang.Thread.run(未知來源) 引起:java.io.IOException:密鑰交換未完成,連接已關閉。 在com.trilead.ssh2.transport.KexManager.getOrWaitForConnectionInfo(KexManager.java:95) 在com.trilead.ssh2.transport.TransportManager.getConnectionInfo(TransportManager.java:237) 在com.trilead.ssh2.Connection.connect(Connection.java:786) ......還有7個 引起:java.io.IOException:驗證程序回調未接受服務器hostkey 在com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:548) 在com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:790) 在com.trilead.ssh2.transport.TransportManager $ 1.run(TransportManager.java:502) ......還有1個 [08/06/18 17:52:53]發射失敗 - 清理連接 [08/06/18 17:52:53] [SSH]連接關閉。

解決方案01:配置節點 - 啟動方式時,選擇非驗證驗證策略


在【 Host Key Verification Strategy】-選擇【Non verifying Verification Strategy】 -【點擊Save】即可!!!

翻譯版本:
在【主機密鑰驗證策略】-選擇【非驗證策略】-【點擊保存】即可!!!

解決方案02:配置節點 - 啟動方式時,選擇非驗證驗證策略

配置節點時,將主機密鑰驗證策略選項勾選為非驗證驗證策略。如果還報其他的錯誤,檢查一下配置的Linux的用戶名密碼時否正確

總結

以上是生活随笔為你收集整理的Launch failed - cleaning up connection的全部內容,希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯,歡迎將生活随笔推薦給好友。