Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Date: Wed, 1 Oct 2014 22:29:35 +0000 (UTC)
From: "Michi Mutsuzaki (JIRA)" <jira@apache.org>
To: builds@apache.org
Message-ID: <JIRA.12738848.1409764796000.170271.1412202575614@Atlassian.JIRA>
In-Reply-To: <JIRA.12738848.1409764796000@Atlassian.JIRA>
References: <JIRA.12738848.1409764796000@Atlassian.JIRA>
 <JIRA.12738848.1409764796514@arcas>
Subject: [jira] [Commented] (BUILDS-17) ulimit set too low on some jenkins
 build hosts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/BUILDS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14155671#comment-14155671 ] 

Michi Mutsuzaki commented on BUILDS-17:
---------------------------------------

Here are some links that look relevant to the issue:

http://blog.mindfab.net/2013/12/changing-ulimits-for-jenkins-daemons.html
http://serverfault.com/questions/436138/ulimit-not-reflected-for-jenkins-slave

> ulimit set too low on some jenkins build hosts
> ----------------------------------------------
>
>                 Key: BUILDS-17
>                 URL: https://issues.apache.org/jira/browse/BUILDS-17
>             Project: Infra Build Platform
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Patrick Hunt
>            Assignee: Giridharan Kesavan
>            Priority: Blocker
>
> Our precommit job is failing, this started just after the recent major upgrades to the jenkins infra (was fine prior to that):
> https://builds.apache.org/view/S-Z/view/ZooKeeper/job/PreCommit-ZOOKEEPER-Build/2303/
> The test is still failing with the same error (too many open
> files) and afaict the ulimit is still just set to 4k. I'm printing the
> ulimit info at the start of the job, here it is:
> core file size          (blocks, -c) 0
> data seg size           (kbytes, -d) unlimited
> scheduling priority             (-e) 0
> file size               (blocks, -f) unlimited
> pending signals                 (-i) 386177
> max locked memory       (kbytes, -l) 64
> max memory size         (kbytes, -m) unlimited
> open files                      (-n) 4096
> pipe size            (512 bytes, -p) 8
> POSIX message queues     (bytes, -q) 819200
> real-time priority              (-r) 0
> stack size              (kbytes, -s) 8192
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) 386177
> Please increase the ulimit to a significantly larger value (perhaps you can set it to what it was set to prior to the upgrade?)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)