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

[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?


> So it seems to be related to the kind of output what the script
> returns.. I’m now unsure if it’s really a Debian/Systemd bug.
> 
>  
> 
> If someone tries to reproduce this here is the script
> https://pastebin.com/ySdNu57A.  To enable the encryption create a file
> /etc/check_mk/encryption.cfg with the content:


Unfortunately I have no idea what Check MK is and how I'm supposed to
use the above script so I fear that script won't help me much unless you
give me some guidance how to setup the environment where I can
execute/run the script and reproduce the issue.




-- 
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/20190912/07d91f51/attachment.sig>