Jenkins 2.7.4 已安装在 RedHat 服务器中,Linux 从服务器通过选择“通过在主服务器上执行命令启动代理”选项进行配置。我们创建了一个 Shell 脚本,它在 Jenkins 2.7.4 版本中运行良好。
现在我们将 Jenkins 升级到 2.121.1。现在相同的脚本抛出一个错误
<===[JENKINS REMOTING CAPACITY]===>Exception in thread "main" java.io.StreamCorruptedException: invalid stream header: 099EACED at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:808) at java.io.ObjectInputStream.(ObjectInputStream.java:301) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.ChannelBuilder.makeTransport(ChannelBuilder.java:478) at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:433) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:354) at hudson.remoting.Launcher.main(Launcher.java:743) at hudson.remoting.Launcher.runWithStdinStdout(Launcher.java:691) at hudson.remoting.Launcher.run(Launcher.java:373) at hudson.remoting.Launcher.main(Launcher.java:283) ERROR: Connection terminated ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.io.IOException: Unexpected EOF at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:99) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) ERROR: Process terminated with exit code 1 java.io.IOException: Unexpected EOF at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:99) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to rtt-ci-euhrhd0036vdeas at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.Request.call(Request.java:202) at hudson.remoting.Channel.call(Channel.java:954) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:549) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:416) at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:153) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:288) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) 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: hudson.remoting.RequestAbortedException at hudson.remoting.Request.abort(Request.java:340) at hudson.remoting.Channel.terminate(Channel.java:1038) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:96)
如果我在 Manage Jenkins -> Configure Security 中禁用 SSHD 端口,那么我就可以启动我的 slave。但是在我的脚本中,我将使用 Jenkins-cli.jar 触发一项工作,将二进制文件从主服务器复制到从服务器。
java -jar jenkins-cli.jar -s http://localhost:8080 --ssh -user username -i ~/.ssh/id_rsa build RTT/RTT-CI-Tools/RTT-CI-Tools-Distribute -s -p SLAVE_REGEX=从机名称
我收到一条消息
"WARNING: No header 'X-SSH-Endpoint' returned by Jenkins"
并且构建没有被触发。我还尝试在 jenkins-cli.jar 命令中将 -ssh 替换为 -http,
java -jar jenkins-cli.jar -s http://localhost:8080 -http -auth username:60b3450a883a2519592af84cdcd0d224 build $CI_JOB -s -p SLAVE_REGEX=$SLAVEHOST
它触发作业。再次无法启动从机,
<===[JENKINS REMOTING CAPACITY]===>Exception in thread "main" java.io.StreamCorruptedException: invalid stream header: 099FACED at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:808) at java.io.ObjectInputStream.(ObjectInputStream.java:301) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.ChannelBuilder.makeTransport(ChannelBuilder.java:478) at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:433) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:354) at hudson.remoting.Launcher.main(Launcher.java:743) at hudson.remoting.Launcher.runWithStdinStdout(Launcher.java:691) at hudson.remoting.Launcher.run(Launcher.java:373) at hudson.remoting.Launcher.main(Launcher.java:283) usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec] [-D [bind_address:]port] [-e escape_char] [-F configfile] [-i identity_file] [-L [bind_address:]port:host:hostport] [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port] [-R [bind_address:]port:host:hostport] [-S ctl_path] [-W host:port] [-w local_tun[:remote_tun]] [user@]hostname [command] ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins ERROR: Connection terminated java.io.IOException: Unexpected EOF
如何解决这个问题
最佳答案
未改变的标准输入,未改变的标准输出
我相信您脚本中的某些内容正在篡改标准输入。
您的脚本应该将完整的、未更改的 stdin 流传递给 Jenkins 代理进程。
通用解决方案
OP 建立 Jenkins session 的命令与我的不同,但无论如何,您应该将启动脚本分为 3 个主要部分:
设置:这部分没有篡改标准输入或标准输出。
建立 Jenkins session : java -jar jenkins-cli.jar ...
Tear down:这部分没有篡改标准输入或标准输出。
#!/bin/bash
function set_up {
# your set-up code here
}
function tear_down {
# your tear-down code here
}
function main {
# set-up (no stdin, no stdout)
set_up "$@" < /dev/null > /dev/null || exit $?
# establish Jenkins session
java -jar jenkins-cli.jar -blah -blah -blah
# tear-down (no stdin, no stdout)
tear_down "$@" < /dev/null > /dev/null || exit $?
}
main "$@"
但是……为什么?
启动脚本的工作是在主控和构建代理之间建立一个未被篡改的通信 channel (通过标准输入和标准输出)。
+------------+
"Hello Agent" | |
_ _ ----+ +----
v Hello Agent ->
----+ +----
| |
| | "Hello Master"
----+ +---- _ _
<- Hello Master v
----+ +----
| |
+------------+
launch
script
如果此通信 channel 被篡改,Jenkins 将无法工作。
+------------+
"Hello Agent" | |
_ _ ----+ +-----------
v Hel PLZ SEND HELP!! t ->
----+ +-----------
| |
| |
----+ +---- | |
^
----+ +----
| |
+------------+
launch
script
某些 Unix 命令可能会“吞噬”您的启动脚本的标准输入,如果您不将任何内容传送到该命令,因此会“破坏”通信 channel 。考虑以下脚本。
#!/bin/bash
function keep_stdin_intact {
printf 'I do not consume any stdin, ' >&2
echo 'and I do not alter the original stdout.' >&2
}
function swallow_stdin {
echo 'I swallow stdin. Did you see any hexdump below?' >&2
read yn # read consumed some stdin
}
echo 'yes' | { keep_stdin_intact; cat -; } | xxd
echo 'yes' | { swallow_stdin; cat -; } | xxd
echo "no you can't now :P" | { swallow_stdin < /dev/null; cat -; } | xxd
第一个
yes
被管道输出并被十六进制转储,因为keep_stdin_intact
没有篡改 stdin,在本例中为“yes”流。第二个
yes
没有了,因为swallow_stdin
消耗了它,所以cat
没有什么可以 cat 和xdd
没有什么可读的。通过将
/dev/null
管道传输到吞噬标准输入的命令,我们保护了我们自己的标准输入。
ssh 怎么了?
ssh
是吞噬您的标准输入的邪恶命令之一。
假设您想在运行 agent.jar
之前删除构建代理上的一些文件。如果没有样板,您可能会想写:
ssh $OPTIONS "$remote" 'sudo rm -rf /var/log/nginx/*'
ssh $OPTIONS "$remote" 'cd $HOME && java -jar agent.jar'
^ 但这是错误的!第一个 ssh
命令将吞下您的标准输入,而 Jenkins session 将没有任何可读取的内容。
第一个 ssh
必须“静音”。传递 /dev/null
作为它的标准输入。
ssh $OPTIONS "$remote" 'sudo rm -rf /var/log/nginx/*' < /dev/null
ssh $OPTIONS "$remote" 'cd $HOME && java -jar agent.jar'
关于linux - Jenkins Slave 问题 - 无效的流 header : 099EACED,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/51104429/