Thanks for looking into this. I am sorry that it's always our machine that causes trouble :(
Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Niklas Gustavsson [mailto:nik...@protocol7.com] > Sent: Wednesday, June 01, 2011 3:49 PM > To: builds@apache.org > Subject: Re: Lucene Jenkins node down and does not start itsself > > Hi > > Jenkins seems to be confused about the Lucene slave. I'll try to restart > Jenkins (I'm doing some upgrades anyways) which will hopefully solve this. > > /niklas > > On Wed, Jun 1, 2011 at 3:35 PM, Uwe Schindler <u...@thetaphi.de> wrote: > > Hi, > > > > The Jenkins node on luzene.zones is down and Jenkins itself is not > > able to restart it: https://builds.apache.org/computer/lucene/ > > The log is empty (https://builds.apache.org/computer/lucene/log) or I > > cannot see it. I have no chance to look into it, as my Hudson account > > is too restricted. It would be nice if somebody from the Jenkins team > > could look into it. > > > > The slave.jar process is not running on lucene.zones and manually > > starting it does not work, it says: > > > > WARNING: Are you running slave agent from an interactive console? > > If so, you are probably using it incorrectly. > > See > > http://wiki.jenkins-ci.org/display/JENKINS/Launching+slave.jar+from+fr > > om+con > > sole > > <===[HUDSON REMOTING > > > CAPACITY]===>rO0ABXNyABpodWRzb24ucmVtb3RpbmcuQ2FwYWJpbGl0eQ > AAAAAAAAABA > > gABSgA > > EbWFza3hwAAAAAAAAAAY=’VT102 > > ^C > > > > Thanks! > > Uwe > > > > ----- > > Uwe Schindler > > H.-H.-Meier-Allee 63, D-28213 Bremen > > http://www.thetaphi.de > > eMail: u...@thetaphi.de > > > > > > > >
