Looks like Infra has figured it out. From Chris Lambertus on builds.apache.org
this morning:
> Looks like this was primarily due to the switch to systemd startup in ubuntu
> 16.04 and the need to update DefaultLimitNOFILE in /etc/systemd/system.conf
> (grr) to affect processes started via syst
An update from Chris Lambertus on bui...@apache.org mailing list, about 2 hours
ago:
> 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.
--
Steve
www.lucidworks.com
> On
On the bui...@apache.org mailing list last night, on thread “jenkins emergency
restart notice”, Chris Lambertus 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
This is the 2nd one of these I've seen in 2 days (different jobs) but
it seems to resolve itself on the next run.
Steve Rowe, do you have any insight into what we can do to avoid it?
I'll be happy to ask INFRA if not.
On Tue, Jul 18, 2017 at 7:32 AM, Apache Jenkins Server
wrote:
> Build: https:/
Build: https://builds.apache.org/job/Solr-reference-guide-7.x/156/
Log:
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H19 (git-websites) in workspace
/home/jenkins/jenkins-slave/workspace/Solr-reference-guide-7.x
> git rev-parse --is-inside-work-tree #
