Note that Debian 8 is very old. It runs systemd v215, which came out in 2014. So, from upstream's perspective, unless it's a well-known bug, the answer is probably "who knows? Use a more recent systemd."
I suggest filing a bug with Debian and asking them for help. Debian 8 is still supported for another 6 months, according to https://wiki.debian.org/LTS ... Although it's by a team of volunteers, so YMMV. - Dave On Wed, Dec 11, 2019 at 9:35 PM Md. Farhad Hasan Khan <[email protected]> wrote: > > Hi, > > We are observing high CPU utilization by systemd process. > > 100% CPU utilize by systemd process when no user is being logged in to the > server but CPU utilization became 0% while any user logged in to the server. > What cloud be possible reason behind this issue and solution? > > > > Log collected via login to the server via ssh or console: (0% CPU utilization) > > > > top -b -n 1 | grep systemd | grep 612 > 612 root 20 0 3386692 2.051g 4932 T 0.0 6.5 22029:26 systemd > > > > > > Log collected without login to the server : (100% CPU utilization) > > > > # ssh [email protected] top -b -n 1 | grep systemd | grep 612 > [email protected]'s password: > 612 root 20 0 3386692 2.051g 4932 S 789.2 6.5 22031:31 systemd > > > > > > Please find the server information: > > > > lsb_release -a > No LSB modules are available. > Distributor ID: Debian > Description: Debian GNU/Linux 8.11 (jessie) > Release: 8.11 > Codename: jessie > > uname -r > 3.16.0-6-amd64 > > > > Thanks & B’Rgds, > > Rony > > > > _______________________________________________ > systemd-devel mailing list > [email protected] > https://lists.freedesktop.org/mailman/listinfo/systemd-devel _______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
