On Tue, Dec 05, 2017 at 09:07:07PM +0100, Philipp Huebner wrote: > > I assume you have already tried rebooting ejabberd / the whole server?
Yes, helps temporarily. Also, after a while (~1h) it gets better by itself, only to become a cpu hog again. > Have you set the log level to debug (5)? > https://docs.ejabberd.im/admin/guide/troubleshooting/#log-files Not yet, I've been running at loglevel 4 by now. Set it to 5 now, waiting for the next occurence. > Other than that, please check dmesg and make sure it is not due to the > recently automatically enabled AppArmor. No, there isn't any trace of that. I only find a libapparmor1 as a dependency of a package. > > If one (or all) of the updated erlang-p1-* packages has caused this, the > solution is to update the ejabberd package, which I cannot do yet due to > #883017. When the new loglevel does not reveal anything, I'll check the dates when my erlang_p1* packages entered testing and try rolling back one version. Bye, Joerg
signature.asc
Description: PGP signature
