Bug#940021: systemd: socket activation leads to OOM situation due to slices not getting cleaned up

[Michael Biebl]

Am 13.09.19 um 00:53 schrieb Michael Biebl:
> Am 12.09.19 um 14:29 schrieb Michael Biebl:
>> Am 11.09.19 um 15:54 schrieb Julian Hübenthal:
>>> Just discovered something that may help to debug:
>>>
>>>  
>>>
>>> It does not happen with a simple “Hello World” bash script instead of
>>> the Check MK Agent.
>>>
>>> It does not happen when the Encryption of the Check MK Agent is disabled.
>>>
>>> It happens when the Encryption of Check MK is enabled, which should be
>>> AES 128/256 output.
>>
>>
>> I wonder if the MK agent does some tricks like locking the memory when
>> encryption is on and then does not properly release its resources?
> 
> Just to ask the obvious: The slice(s) themselves are empty, i.e. the
> check-mk agent process has exited (successfully)?
> 
> What's the status of such a service that is not cleaned up?
> Taking your first email that would be
> systemctl status check_mk at 10-10.28.5.6:6556-10.28.5.1:42844.service
> 
> I'd be interested in the output of
> 
> find /sys/fs/cgroup/system.slice/system-check_mk.slice/ as well
> 
> 

As well as systemctl status system-check_mk.slice




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190913/3bedf7dc/attachment.sig>