Subject: Re: [vserver] Exploding Load in v2.3
From: Herbert Poetzl <herbert@13thfloor.at>
Date: Wed, 20 Jan 2010 02:48:52 +0100

On Mon, Jan 18, 2010 at 10:35:38PM +0100, Cryptronic wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> Hello Nik,

> yes indeed i have 74 GB of RAM in that machine. VServers 50+.

> I use a shared partition with ext3 or ext4.

> remote syslog is not enabled yet, will do that in the next days. 
> And in syslog i could not find anything.

> In messages i found the following which must be appeared in between
> the load explosion, but not at the beginning:

> before:
> Jan 18 21:00:02 host kernel: [20304486.773634] vxW:
> [»landscape-sysin«,28639:#9113|9113|9113] did lookup hidden
> proc:ffff8812034377f8[#0,4026531914] »/proc/acpi«.

that looks fine, it's probably just some tool or script
trying to access acpi stuff (which is disabled inside
a guest) ... the name of the script seems to be something
like landscape-sysin...

> then:
> Jan 18 21:11:45 host kernel: [20304486.368940] apache2 invoked
> oom-killer: gfp_mask=0x0, order=0,
> oomkilladj=0                                                                     
                              
any memory limits on the guests?
what does /proc/virtual/<xid>/limit contain for the guests?

TIA,
Herbert

> Jan 18 21:11:45 host kernel: [20304486.368944] apache2 cpuset=/
> mems_allowed=0-1                                                                 
                                                                
> Jan 18 21:11:45 host kernel: [20304486.368947] Pid: 5090, comm:
> apache2 Not tainted 2.6.31.7-vs2.3.0.36.27
> #1                                                                               
                
> Jan 18 21:11:45 host kernel: [20304486.368949] Call
> Trace:                                                                           
                                                                            
> > At Kernel 2.6.29.6-vs2.3.0.36.14 this also happend. The hardware
> > is also not the thing, because this happens on different
> > architectures.

> > To get the server back online, you have to reset the hardware,
> > reboot and co not doing anything.

> > Best regards
> >>
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.14 (GNU/Linux)
> 
> iEYEARECAAYFAktU1CoACgkQOBdlVlcPuhxdwQCgyR4o0ZEYcfW5TUmlyxYrzzYz
> 25wAoJT6mReugXt1iYV/ud3VFtI/rYoF
> =TZyO
> -----END PGP SIGNATURE-----
>