[jira] [Work started] (BUILDS-17) ulimit set too low on some jenkins build hosts

["Giridharan Kesavan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BUILDS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on BUILDS-17 started by Giridharan Kesavan.
------------------------------------------------
> 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)