I fixed the config. The Jail is also running again.

Uwe

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de


> -----Original Message-----
> From: Steve Rowe [mailto:sar...@gmail.com]
> Sent: Saturday, June 07, 2014 1:48 AM
> To: dev@lucene.apache.org
> Subject: Re: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #640: POMs out of
> sync
> 
> More info from gmcdonald on #asfinfra:
> 
> 6:48:33 PM <sarowe> JanIV: do you know who's responsible for the lucene
> (and other) zones?
> 7:40:20 PM <gmcdonald> sarowe1: its a jail on a downed host, known issue,
> will look at it
>                         in the morning if noone else gets there first
> 7:40:45 PM <sarowe1> thanks gmcdonald
> 7:40:54 PM <gmcdonald> np
> 
> On Jun 6, 2014, at 6:48 PM, Steve Rowe <sar...@gmail.com> wrote:
> 
> > abayer = Andrew Bayer
> >
> > I chatted with JanIV = Jan Iversen, and abayer on #asfinfra today about the
> issue - here’s a transcript:
> >
> > 5:58:06 PM <sarowe> Hi, I'm trying to ssh into lucene.zones.apache.org but
> it times out
> >                    - is this known/expected?
> > 5:59:01 PM <sarowe> (I do see a bunch of red zones alerts on
> status.apache.org - maybe
> >                    ssh://hudson-fbsd.zones?)
> > 6:17:28 PM <sarowe> Hello? anybody there who can tell me about the
> lucene jenkins build
> >                    slave outage?  I see at least one lucene job's 
> > configuration was
> >                    altered today to have it run on ubuntu in addition to 
> > lucene.
> > 6:18:10 PM <sarowe> there's no way it will run there without
> > modifications, btw
> > 6:22:24 PM <janIV> sarowe: the "bunch" you see right now is because our
> staff is
> >                   fighting hard with upgrades to overcome a security issue.
> > 6:22:44 PM <janIV> sarowe: I recommend you check it again tomorrow.
> > 6:23:49 PM <janIV> sarowe: abayer is working hard on getting the jenkins
> master to work
> >                   effeciently, maybe thats the cause of the change.
> > 6:24:33 PM <abayer> sarowe, janIV - that was me, testing to see if it'd run
> alright
> >                    elsewhere.
> > 6:24:39 PM <sarowe> JanIV: makes sense, it was abayer who changed the
> > lucene job configs
> > 6:24:41 PM <abayer> My bad.
> > 6:25:08 PM <abayer> Is there a doc somewhere on what's needed for the
> lucene build env?
> >                    If so, I'll try to make sure that future general slaves 
> > can handle
> >                    it...
> > 6:25:13 PM <sarowe> abayer: lucene's jobs are tied to local config on
> > the lucene slave
> > 6:25:37 PM <sarowe> abayer: the guy who maintains that (Uwe Schindler)
> doesn't seem to
> >                    be online ATM
> > 6:25:44 PM <janIV> abayer: not your bad ! you need to test to make things
> better, thats
> >                   quite ok. but maybe tell the affected people.
> > 6:26:36 PM <abayer> sarowe: Ok, I'll email him later - I'd chatted a bit 
> > with
> Mark
> >                    Miller about it internally here at Cloudera and he 
> > didn't think
> >                    there was anything specific to the slave, but no biggie 
> > - I just
> >                    got sad seeing so many queued up jobs.
> > 6:26:57 PM <sarowe> abayer: just to be sure: lucene heavily uses the
> dedicated lucene
> >                    slave - it's going to remain available, isn't it?
> > 6:27:26 PM <abayer> sarowe: I hope so! I'm not planning to get rid of it,
> and, well, I
> >                    can't get rid of it.
> > 6:27:46 PM <abayer> Nor would I want to - I just want to complement
> it/supplement it/
> >                    get a better box for it/etc.
> > 6:28:20 PM <sarowe> that'd be great - lucene could use more machine
> resources for its
> >                    jobs, for sure
> > 6:29:44 PM <janIV> abayer: I hope all your changes are documented in
> some form, not
> >                   the tests, but the outcome.
> > 6:29:49 PM <abayer> In any case, my apologies for the misconfig, and yeah,
> not sure who
> >                    you need to talk to about lucene.zones - it's been down 
> > since
> >                    yesterday, I think, but I don't know who's involved in 
> > getting it up.
> > 6:29:55 PM <abayer> janIV: Gradually, yes.
> > 6:30:20 PM <abayer> I've got an evernote note chock full of crap that I'll
> pull together
> >                    into something coherent once I feel like we're really at 
> > a steady
> >                    state - next week most likely.
> > 6:30:23 PM <sarowe> abayer, sure, no problem, thanks for the info
> > 6:31:12 PM <janIV> abayer: make a "jenkins" file in trunk/docs then we can
> all share it.
> >                   you have commit karma there.
> > 6:31:17 PM <abayer> yarp yarp
> >
> >
> > On Jun 6, 2014, at 6:11 PM, Chris Hostetter <hossman_luc...@fucit.org>
> wrote:
> >
> >>
> >> All sorts of wonkiness here...
> >>
> >> #1) the job got run on "ubuntu6" instead of on our lucene zone (which
> >> is why ivy wasn't found)
> >>
> >> #2) the lucene zone machine appears to be down
> >>
> >> #3) the reason the job got run on ubuntu6 seems to be because "abayer"
> >> edited the job config to saw it could run on either one...
> >>
> >> https://builds.apache.org/job/Lucene-Solr-Maven-4.x/jobConfigHistory/
> >> showDiffFiles?timestamp1=2014-05-09_16-37-34&timestamp2=2014-06-
> 06_21
> >> -44-58
> >>
> >> (Note: that diff URL will only work if you have jenkins web auth to
> >> login)
> >>
> >> No idea who "abayer" is (is that someone on infra?) or why he's
> >> editing the job config.
> >>
> >>
> >>
> >> : Date: Fri, 6 Jun 2014 21:47:33 +0000 (UTC)
> >> : From: Apache Jenkins Server <jenk...@builds.apache.org>
> >> : Reply-To: dev@lucene.apache.org
> >> : To: dev@lucene.apache.org
> >> : Subject: [JENKINS-MAVEN] Lucene-Solr-Maven-4.x #640: POMs out of
> >> sync
> >> :
> >> : Build: https://builds.apache.org/job/Lucene-Solr-Maven-4.x/640/
> >> :
> >> : No tests ran.
> >> :
> >> : Build Log:
> >> : [...truncated 9684 lines...]
> >> : BUILD FAILED
> >> : /home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-
> 4.x/build.xml:483: The following error occurred while executing this line:
> >> : /home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-
> 4.x/build.xml:104: The following error occurred while executing this line:
> >> : /home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-
> 4.x/lucene/build.xml:194: The following error occurred while executing this
> line:
> >> : /home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-
> 4.x/lucene/common-build.xml:401: The following error occurred while
> executing this line:
> >> :
> >> /home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-
> 4.x/lucene/co
> >> mmon-build.xml:438: Ivy is not available
> >> :
> >> : Total time: 6 seconds
> >> : Build step 'Invoke Ant' marked build as failure
> >> : Recording test results
> >> : Email was triggered for: Failure
> >> : Sending email for trigger: Failure
> >> :
> >> :
> >> :
> >>
> >> -Hoss
> >> http://www.lucidworks.com/
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For
> >> additional commands, e-mail: dev-h...@lucene.apache.org
> >>
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional
> commands, e-mail: dev-h...@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to