* Michael Biebl <bi...@debian.org> [191004 21:51]: > 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?
JFTR, I see this problem with no encryption enabled. > > 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. Generally, just running this as a socket activated unit should show the problem I guess. FTR, here are the involved unit files: /etc/systemd/system/check_mk@.service # systemd service definition file [Unit] Description=Check_MK [Service] ExecStart=/usr/bin/check_mk_agent KillMode=process User=root Group=root StandardInput=socket /etc/systemd/system/check_mk.socket: # systemd socket definition file [Unit] Description=Check_MK Agent Socket [Socket] ListenStream=6556 Accept=true [Install] WantedBy=sockets.target Michael, if you catch me on IRC (and are interested), I have a machine showing this problem that you could inspect... Cheers, Chris
