Eclipse Community Forums: Hudson » Command execution failure

Help

Home

Home » Archived » Hudson » Command execution failure(Hudson/Jenkis 3.0.1)

Show: Today's Messages :: Show Polls :: Message Navigator

Command execution failure [message #1061482]

Fri, 31 May 2013 20:54

Alex Pineda

Messages: 3
Registered: May 2013

Junior Member

I installed Hudson on my Oracle Enterprise Linux 6 machine in "native". I'm running Hudson server and I have attached one slave to the system. I'm able to run my Hudson job, but after the last command in the "shell" page, I get the following error. It does not matter what the last command is. It always gives this error.

"FATAL: command execution failed
hudson.util.IOException2: Failed to join the process
at hudson.Proc$RemoteProc.join(Proc.java:362)
at hudson.Launcher$ProcStarter.join(Launcher.java:273)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:79)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:54)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:34)
at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:646)
at hudson.model.Build$RunnerImpl.build(Build.java:181)
at hudson.model.Build$RunnerImpl.doRun(Build.java:136)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:434)
at hudson.model.Run.run(Run.java:1390)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:40)
at hudson.model.ResourceController.execute(ResourceController.java:82)
at hudson.model.Executor.run(Executor.java:137)
Caused by: java.util.concurrent.ExecutionException: java.lang.NoSuchMethodError: hudson.remoting.Channel.flushPipe()V
at hudson.remoting.Channel$2.adapt(Channel.java:677)
at hudson.remoting.Channel$2.adapt(Channel.java:672)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:48)
at hudson.Proc$RemoteProc.join(Proc.java:353)
... 12 more
Caused by: java.lang.NoSuchMethodError: hudson.remoting.Channel.flushPipe()V
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:838)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:796)
at hudson.remoting.UserRequest.perform(UserRequest.java:114)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Sending e-mails to: alex.pineda@oracle.com
[DEBUG] Skipping watched dependency update for build: alex-core-bat #10 due to result: FAILURE
Finished: FAILURE

Can someone shed some light on why this is happening? It doesn't appear to be harmful, but I have not fully investigated.

Report message to a moderator

Re: Command execution failure [message #1061699 is a reply to message #1061482]

Mon, 03 June 2013 14:18

Winston Prakash

Messages: 534
Registered: August 2011
Location: Fremont, CA USA

Senior Member

You have a older slave.jar in the slave machine and the master Hudson is a newer version.

Winston Prakash
Eclipse Hudson team

Report message to a moderator

Re: Command execution failure [message #1061770 is a reply to message #1061699]

Mon, 03 June 2013 21:12

Alex Pineda

Messages: 3
Registered: May 2013

Junior Member

Thanks for the follow up. Your suggestion resolved the error. Be aware that I'm updating our existing Hudson Server and I will need to update all our Hudson slaves (50+) as you indicated. Good thing to know now and I can include this task to our "Update/Upgrade" plan.

Report message to a moderator

Previous Topic:	Hudson CI Setup Guide - Request for review
Next Topic:	(Solved) Hudson ignoring http.proxyHost / http.ProxyPort

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Apr 20 15:20:58 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter