Subject: Re: [vserver] vc_rlimit_stat(RLIMIT_AS): Invalid argument
From: Michael <michael.auckland@gmail.com>
Date: Thu, 2 Sep 2010 15:12:29 +1200
Thu, 2 Sep 2010 15:12:29 +1200
I had the same errors, so I've rebuild kernel with option:

CONFIG_VSERVER_LEGACY_MEM=y

errors now are gone.

On Wed, Sep 1, 2010 at 9:22 AM, Eric Schoeller <
eschoeller@users.sourceforge.net> wrote:

> I guess I should have mentioned that I'm not limiting resources on any
> vservers for this host. I have no rlimits config files. I haven't done
> anything with cgroups either.
>
> Eric
>
>
> ben@bristolwireless.net wrote:
>
>> Quoting "Eric Schoeller" <eschoeller@users.sourceforge.net>:
>>
>>  Good Morning,
>>>
>>> I recently upgraded to 2.6.35-vs2.3.0.36.31-beng and I'm now experiencing
>>> this problem:
>>>
>>> # vserver-stat
>>> vc_rlimit_stat(RLIMIT_AS): Invalid argument
>>> vc_rlimit_stat(RLIMIT_AS): Invalid argument
>>> vc_rlimit_stat(RLIMIT_AS): Invalid argument
>>> vc_rlimit_stat(RLIMIT_AS): Invalid argument
>>> vc_rlimit_stat(RLIMIT_AS): Invalid argument
>>> vc_rlimit_stat(RLIMIT_AS): Invalid argument
>>> CTX   PROC    VSZ    RSS  userTIME   sysTIME    UPTIME NAME
>>>
>>>
>>> I did not find a new util-vserver-basic-debian package on the psand.netrepository,
and I have a sinking suspicion that I need one.
>>>
>>> I found others with the same issue, but no real answers:
>>>
>>> http://paste.linux-vserver.org/16162
>>>
>>> http://forums.gentoo.org/viewtopic-p-6401816.html?sid=92654704c23f48fadc85910f73316370
>>>
>>> While reading the following excerpt from #vserver on irc.oftc.net (
>>> http://irc.13thfloor.at/LOG/2010-05/LOG_2010-05-27.txt) it looks like
>>> this issue cropped up because 'there is no AS limit in recent kernels'.
>>>
>>> Any ideas on this? Thanks!
>>>
>>> Eric Schoeller
>>>
>>>
>>>
>>>
>> Set limits using the cgroups system instead, remove your rlimits config
>> files. The cgroup memory limits should work fine with that kernel.
>>
>> Ta,
>> ==
>> From Ben Green
>>
>


-- 
--
Michael


I had the same errors, so I've rebuild kernel with option:

CONFIG VSERVER LEGACY MEM=y

errors now are gone.

On Wed, Sep 1, 2010 at 9:22 AM, Eric Schoeller <eschoeller@users.sourceforge.net> wrote:
I guess I should have mentioned that I'm not limiting resources on any vservers for this host. I have no rlimits config files. I haven't done anything with cgroups either.

Eric


ben@bristolwireless.net wrote:
Quoting "Eric Schoeller" <eschoeller@users.sourceforge.net>:

Good Morning,

I recently upgraded to 2.6.35-vs2.3.0.36.31-beng and I'm now experiencing this problem:

# vserver-stat
vc rlimit stat(RLIMIT AS): Invalid argument
vc rlimit stat(RLIMIT AS): Invalid argument
vc rlimit stat(RLIMIT AS): Invalid argument
vc rlimit stat(RLIMIT AS): Invalid argument
vc rlimit stat(RLIMIT AS): Invalid argument
vc rlimit stat(RLIMIT AS): Invalid argument
CTX   PROC    VSZ    RSS  userTIME   sysTIME    UPTIME NAME


I did not find a new util-vserver-basic-debian package on the psand.net repository, and I have a sinking suspicion that I need one.

I found others with the same issue, but no real answers:

http://paste.linux-vserver.org/16162
http://forums.gentoo.org/viewtopic-p-6401816.html?sid=92654704c23f48fadc85910f73316370

While reading the following excerpt from #vserver on irc.oftc.net (http://irc.13thfloor.at/LOG/2010-05/LOG 2010-05-27.txt) it looks like this issue cropped up because 'there is no AS limit in recent kernels'.

Any ideas on this? Thanks!

Eric Schoeller




Set limits using the cgroups system instead, remove your rlimits config files. The cgroup memory limits should work fine with that kernel.

Ta,
==
From Ben Green



--
--
Michael