[Bug 1797836] Re: [SRU] logwatch reports false kernel error warning

2019-08-13 Thread Andreas Hasenack
Thanks for the feedback @fomember! Could you please update the bug tags according to the instructions in comment #9? It would also be appreciated if you could be explicit about the package that you have been testing. An apt-cache policy output should be enough. -- You received this bug notificat

[Bug 1839527] Re: mysqld eats more than 16 GB of memory on startup

2019-08-13 Thread Andreas Hasenack
Since the LimitNOFILE=5000 isn't applied, the process gets whatever default the host has. In this case, Arch's kernel, since this is an LXC container. Aug 08 18:19:23 mysql57 bash[13131]: open files (-n) 1073741816 <--- see this? You probably have the same value on the host. I've seen another bug

[Bug 1839527] Re: mysqld eats more than 16 GB of memory on startup

2019-08-13 Thread Andreas Hasenack
I filed this bug upstream: https://bugs.mysql.com/bug.php?id=96525 ** Bug watch added: MySQL Bug System #96525 http://bugs.mysql.com/bug.php?id=96525 ** Also affects: mysql-server via http://bugs.mysql.com/bug.php?id=96525 Importance: Unknown Status: Unknown -- You received this

[Bug 1839527] Re: mysqld eats more than 16 GB of memory on startup

2019-08-13 Thread Andreas Hasenack
Still, something is happening in ubuntu where we still get the conservative 1024*1024 value, and we do have systemd 240 in eoan. I removed the 5000 setting from the mysql service file, issued daemon- reload, and I still get 1024*1024. In any case, by forcing a larger limit, I was able to reproduce