Return-Path: X-Original-To: apmail-builds-archive@minotaur.apache.org Delivered-To: apmail-builds-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5791017574 for ; Mon, 6 Oct 2014 21:29:35 +0000 (UTC) Received: (qmail 10651 invoked by uid 500); 6 Oct 2014 21:29:34 -0000 Delivered-To: apmail-builds-archive@apache.org Received: (qmail 10584 invoked by uid 500); 6 Oct 2014 21:29:34 -0000 Mailing-List: contact builds-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: builds@apache.org Delivered-To: mailing list builds@apache.org Received: (qmail 10385 invoked by uid 99); 6 Oct 2014 21:29:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Oct 2014 21:29:34 +0000 Date: Mon, 6 Oct 2014 21:29:34 +0000 (UTC) From: "Andrew Bayer (JIRA)" To: builds@apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/BUILDS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160987#comment-14160987 ] Andrew Bayer commented on BUILDS-17: ------------------------------------ How so? ulimit -a spits out the right values, yes? cat /proc/pid/limits for the Jenkins slave process on one of the H* slaves gets this: {quote} root@asf905:~# cat /proc/5273/limits Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size 0 unlimited bytes Max resident set unlimited unlimited bytes Max processes 10240 10240 processes Max open files 60000 60000 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 386178 386178 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us {quote} > 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)