Just for reference:
check_mk_agent caused the endlessly growing of SUnreclaim in
/proc/meminfo and similary vm_area_struct in slabtop if the typical
conditions are met in a Debian Buster with check-mk-agent:
- Debian 10 Buster
systemd241-7~deb10u1 amd64
Kernel 4.19.67-2, but with
On Fri, Jul 26, 2019 at 10:12:20PM +0300, Reco wrote:
> On Fri, Jul 26, 2019 at 08:55:19PM +0200, Matthias Böttcher wrote:
[...]
> > and additionally I stopped the socket for the Check_MK agent:
> >
> > sudo systemctl stop check_mk.socket
>
> I do not know this one. What's its purpose? Moni
On Fri, Jul 26, 2019 at 08:55:19PM +0200, Matthias Böttcher wrote:
> Reco :
> >
> > Hi.
> >
> > On Wed, Jul 24, 2019 at 06:54:42PM +0200, Matthias Böttcher wrote:
> > > OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
> > > 307534 304741 99%0,20K 16186 19 64744K v
Reco :
>
> Hi.
>
> On Wed, Jul 24, 2019 at 06:54:42PM +0200, Matthias Böttcher wrote:
> > OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
> > 307534 304741 99%0,20K 16186 19 64744K vm_area_struct
> > 14280 14274 99%3,69K 17858 57120K task_str
Shahryar Afifi :
>
> What happens when you run sync in terminal?
sync exits immediately and slabtop gives the same output like before sync.
Hi.
On Wed, Jul 24, 2019 at 06:54:42PM +0200, Matthias Böttcher wrote:
> OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
> 307534 304741 99%0,20K 16186 19 64744K vm_area_struct
> 14280 14274 99%3,69K 17858 57120K task_struct
> 178048 152224
Hi list,
my buster is using more and more memory until the oom-killer is
invoked. This occurs after two days of uptime, but no process is using
that memory. Slab seems suspicious to me.
Kernel: 4.19.37-5+deb10u1 (2019-07-19) x86_64
from /proc/meminfo after 8 hours uptime:
MemTotal:40411
7 matches
Mail list logo