I filed https://issues.apache.org/jira/browse/INFRA-14628 which is probably
related to this since the exception message says "Too many open files".

2017-07-19 17:01 GMT+02:00 Mike Drob <md...@apache.org>:

> Have the changes resulted in any noticeable improvements? Is there a JIRA
> interested folks can follow along on?
>
> On Tue, Jul 18, 2017 at 6:40 PM, Chris Lambertus <c...@apache.org> wrote:
>
> > We’re trying a suggested downgrade of the credentials binding plugin
> which
> > may be related to this. No guarantees, though. I will be restarting again
> > tonight at 0100 UTC 19 July.
> >
> > -Chris
> >
> >
> >
> >
> > > On Jul 18, 2017, at 9:00 AM, Chris Lambertus <c...@apache.org> wrote:
> > >
> > > This appears to be a bug in one of the new versions of either jenkins
> or
> > a plugin. We are still looking into the issue. The limit was raised
> > yesterday by a factor of 4.
> > >
> > >
> > >
> > >
> > >> On Jul 18, 2017, at 4:08 AM, Geoff Macartney <
> > geoff.macart...@cloudsoft.io> wrote:
> > >>
> > >> We're seeing them in Apache Brooklyn builds too, e.g.
> > >> https://builds.apache.org/job/brooklyn-server-master/664.
> > >>
> > >> regards
> > >> Geoff
> > >>
> > >>
> > >>
> > >> On Tue, 18 Jul 2017 at 12:03 Ismael Juma <ism...@juma.me.uk> wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> Thanks for the heads up. Was this done? We are still seeing "too many
> > open
> > >>> files" issues in Kafka builds. One example of many:
> > >>>
> > >>> https://builds.apache.org/job/kafka-trunk-jdk7/
> > lastCompletedBuild/console
> > >>>
> > >>> Ismael
> > >>>
> > >>> On Mon, Jul 17, 2017 at 2:53 PM, Chris Lambertus <c...@apache.org>
> > wrote:
> > >>>
> > >>>>
> > >>>> Jenkins will be restarted at midnight tonight UTC to address
> problems
> > >>>> related to ‘too many open files’ and to attempt to correct a problem
> > with
> > >>>> some windows agents. I will be stopping new builds so that the queue
> > can
> > >>>> empty over the next 2 hours.
> > >>>>
> > >>>> -Chris
> > >>>>
> > >>>>
> > >>>
> > >
> >
> >
>



-- 
Dominik Psenner

Reply via email to