On Thu, Dec 29, 2011 at 9:55 AM, Andreas Veithen <andreas.veit...@gmail.com> wrote: > On Wed, Dec 28, 2011 at 14:52, Niklas Gustavsson <nik...@protocol7.com> wrote: >> On Tue, Dec 27, 2011 at 12:37 PM, Andreas Veithen >> <andreas.veit...@gmail.com> wrote: >>> Did anybody ever find a solution for this? We are also seeing this >>> with our Axis2 and WS builds, but it seems to only affect ubuntu4 and >>> ubuntu5. After tying the builds to ubuntu1||ubuntu2||ubuntu3 they run >>> much more stable. >> >> I've cleaned up a lot of dead processes on ubuntu5, let's see if that >> help any. Will do the same on the other nodes when they are offline. >> >> /niklas > > Less than an hour after your mail, another build failed with the same > error on ubuntu5 again: > > https://builds.apache.org/job/sandesha2-1.6/108/
Seems like this might be fixed, I'll try an upgrade. https://issues.jenkins-ci.org/browse/JENKINS-8856 /niklas
