Subject: Re: [vserver] vserver-stat error after upgrade
From: Herbert Poetzl <herbert@13thfloor.at>
Date: Tue, 3 May 2011 14:52:34 +0200

On Tue, May 03, 2011 at 12:21:27PM +0930, Mike O'Connor wrote:
> Hi Herbert

> Could not find any of cgroup files as mentioned at
> 'http://linux-vserver.org/util-vserver:Cgroups' so I just stopped and
> started the guests and it went away.

> There might have been an order issue as the newer init.d
> util-vserver scripts did not seem to work correctly so I
> overwrote them with the older ones which did work. 

playing mix and match with different versions is usually
the road to perdition ... unless you know exactly what
you are doing :)

> Maybe the did sort of work.

more likely it covered up some issues or provides only
partial support of the new(er) kernels now ... up-to-date
util-vserver should be fine with up-to-date kernels, if
not, please report a bug with more details ...

best,
Herbert

> Mike

> On 2/05/11 11:24 AM, Herbert Poetzl wrote:
>> On Sun, May 01, 2011 at 11:19:47PM +0930, Mike O'Connor wrote:
>>> Hi Guys
>>> I just upgraded to linux 2.6.36.4-vs2.3.0.36.39  and util-vserver
>>> 0.30.216-pre2955, I have two machine the same but one is giving an error
>>> for vserver-stat
>>> -- 
>>> root@nodeone:~# vserver-stat
>>> open(memory.usage_in_bytes): No such file or directory
>>> open(memory.usage_in_bytes): No such file or directory
>>> open(memory.usage_in_bytes): No such file or directory
>>> open(memory.usage_in_bytes): No such file or directory
>>> CTX   PROC    VSZ    RSS  userTIME   sysTIME    UPTIME NAME
>>> 8195    71   1.5G     0    0m00s00   0m00s00  56m14s18 xxxxx
>>> root@nodeone:~#
>>> --
>>> --
>>> root@nodetwo:/vservers# vserver-stat
>>> CTX   PROC    VSZ    RSS  userTIME   sysTIME    UPTIME NAME
>>> 8196    48  33.3G  44.7M   0m01s60   0m03s84  51m23s15 xxxxx
>>> root@nodetwo:/vservers#
>>> --
>>> Any ideas ?
>> looks like you configured for cgroup memory accounting/limits
>> but for whatever reason, the cgroup entry for context 8195 is
>> not there (so RSS cannot be read)

>> best,
>> Herbert

>>> Thanks
>>> Mike