CODEWITHSUNDEEP
jenkins
user655145
user655145

Reputation:

Jenkins complains with "Couldn't clean up oid" at the end of a build

I'm playing around with Jenkins (version 1.650) and have successfully set up a job that builds a Maven based Java project. However, at the end of most builds, I get a warning, that clean up failed. The build still succeeds.

[WARNING] Couldn't clean up oid=3 from null
    hudson.remoting.ChannelClosedException: channel is already closed
    at hudson.remoting.Channel.send(Channel.java:578)
    at hudson.remoting.RemoteInvocationHandler$PhantomReferenceImpl.cleanup(RemoteInvocationHandler.java:360)
    at hudson.remoting.RemoteInvocationHandler$PhantomReferenceImpl.access$700(RemoteInvocationHandler.java:319)
    at hudson.remoting.RemoteInvocationHandler$Unexporter.run(RemoteInvocationHandler.java:420)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
    at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException
    at hudson.remoting.Channel.close(Channel.java:1163)
    at hudson.remoting.Channel.close(Channel.java:1138)
    at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1079)
    at hudson.remoting.Channel$1.handle(Channel.java:501)
    at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)

As I only now Jenkins as a enduser I don't exactly know what's going on at that point. I've been looking around but can't find any useful hints that point me to a solution. I only have a master node setup, no slaves involved, so I don't understand how the remoting comes into play here.

I'm running Jenkins on a Vagrant managed VM with Ubuntu 14.04. My job pulls in a project from Bitbucket using a ssh connection. But that's all probably not too important in this context.

Any hints will be greatly appreciated, thanks in advance!

Upvotes: 8

Views: 3091

Answers (2)

Albert Bos
Albert Bos

Reputation: 2062

Not sure if you still have this issue. I had this issue when I performed maven task from the <plugin /> part.

For me it is resolved when I enable process plugins during pom parsing at the build-attempt options. Hope it helps.

Upvotes: 1

Rop
Rop

Reputation: 3409

To summarize:

It's just a warning --- you can ignore it.

Then it will go away after a while :)

Upvotes: 2

Related Questions