CEPH filesystem development
 help / color / mirror / Atom feed
From: Dan Mick <dan.mick@inktank.com>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: teuthology : ulimit: error
Date: Mon, 12 Aug 2013 19:53:36 -0700	[thread overview]
Message-ID: <52099FB0.1070301@inktank.com> (raw)
In-Reply-To: <5205FB01.5040905@dachary.org>

Ah, there's another we apply universally to our test systems, apparently:

'/etc/security/limits.d/ubuntu.conf'

ubuntu hard nofile 16384

and the tests run as user "ubuntu".  Line 4 of the script is the nofile 
setting.

On 08/10/2013 01:34 AM, Loic Dachary wrote:
>
>
> On 10/08/2013 07:35, Dan Mick wrote:
>> IIRC we had to adjust settings in /etc/security to allow ulimit adjustment of at least core:
>>
>> sed -i 's/^#\*.*soft.*core.*0/\*                soft    core unlimited/g' /etc/security/limits.conf
>>
>> or something like that.  That seems to apply to centos/fedora/redhat systems.
>
> Hi Dan,
>
> This is Ubuntu and it does work with sudo. It probably is something about how it's called rather than a system limit.
>
> Cheers
>
>>
>>
>> On 08/08/2013 02:52 PM, Loic Dachary wrote:
>>> Hi,
>>>
>>> Trying to use Ubuntu precise virtual machines as teuthology targets ( making sure they have 2GB of RAM because ceph-test-dbg will not even install with 1GB of RAM ;-) and installing the key with
>>>
>>> wget -q -O- 'https://ceph.com/git/?p=ceph.git;a=blob_plain;f=keys/release.asc' | sudo apt-key add -
>>>
>>> teuthology runs with
>>>
>>> ./virtualenv/bin/teuthology job.yaml
>>>
>>> where job.yaml is
>>>
>>> check-locks: false
>>> roles:
>>> - - mon.a
>>>     - mon.c
>>>     - osd.0
>>> - - mon.b
>>>     - osd.1
>>>     - client.0
>>> tasks:
>>> - install:
>>>      project: ceph
>>>      branch: wip-5510
>>> - ceph:
>>>      fs: ext4
>>> - workunit:
>>>       clients:
>>>         all:
>>>         - filestore/filestore.sh
>>> targets:
>>>      ubuntu@91.121.254.229: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDOSit20EyZ2AKCvk2tnMsdQ6LmVRutvBmZb0awV9Z2EduJa0fYPrReYRb9ZhGRq2PJe0zgpFPKr8s4gGay+tL0+dFkju5uyABqMGeITlJCifd+RhM0MCVllgIzekDwVb0n6ydTS8k7GVFyYv8ZC0TPgbfcDcEtSEgqJNRJ0o1Bh8swuTn+cipanNDRVK39tOqJdfptUxak+TD+5QY8CGFdXdEQYP7VsYJ+jQHw73O2xbuPgfv5Shbmt+qGWLToxFqKca3owMtkvFeONgYUdujgg9qr7Q9p0+HhCFCXB8v4N2I7NSbWNdpGqyJLdLqwJ70gEeNlOhm5F7IsXfVxTapB
>>>      ubuntu@91.121.254.237: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCXVzhedORtmEmCeZJ4Ssg8wfqpYyH9W/Aa+j6CvPHSAkzZ48zXqVBATxm6S8sIIqfKkz1hWpNssx6uUotbm8k/ZatMddsd932+Di136l/HUhp6O8iIFze56kjWpyDpRPw2MM0V+OKmsiHZDfMj9ATt6ChgXfRsm23MUlmnoFHvtfwvFBnvBjcZPN7qxMpFHDamZzACNvnis/OINJrud9VprOgjhZZ7mxcTbcVZaVgcTcnyC4b9d9PRrMG2aCv0BO1eb/qnlmSogQPfoKEORJcwaUcLgabww+Taa9hJSZ9l8yEQamj+XIgr6yzGKgCvlG4lTdHM2tQdpgATZvR7/pBz
>>>
>>> and produces the following output
>>>
>>> INFO:teuthology.orchestra.run.err:[91.121.254.229]: /home/ubuntu/cephtest/lo1308082328/adjust-ulimits: 4: ulimit: error setting limit (Operation not permitted)
>>>
>>> and the full output is at
>>>
>>> http://pastealacon.com/32957
>
> Refreshed with a longer timeout.
>
> http://pastealacon.com/32963
>>>
>>> as if
>>>
>>> /home/ubuntu/cephtest/lo1308082328/adjust-ulimits ceph-coverage /home/ubuntu/cephtest/lo1308082328/archive/coverage monmaptool --create --clobber --add a 91.121.254.229:6789 --add c 91.121.254.229:6790 --add b 91.121.254.237:6789 --print /home/ubuntu/cephtest/lo1308082328/monmap'
>>>
>>> was run without a leading sudo. I tried running sudo adjust-ulimits echo foo manually on the target and it works.
>>>
>>> I would very much appreciate a hint ;-)
>>>
>>> Cheers
>>>
>

  reply	other threads:[~2013-08-13  2:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08 21:52 teuthology : ulimit: error Loic Dachary
2013-08-10  5:35 ` Dan Mick
2013-08-10  8:34   ` Loic Dachary
2013-08-13  2:53     ` Dan Mick [this message]
2013-08-13 10:54       ` Loic Dachary

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52099FB0.1070301@inktank.com \
    --to=dan.mick@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=loic@dachary.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox