Hi, On 1/22/18 1:58 PM, Elias wrote: > Hello all, > > I have a single Proxmox node running multiple virtual machines and lxc > containers. > Since the two(?) last updates, shortly after a reboot (<12h) the system > will start to spawn a few dozens systemd-journald processes, the load > will rise above 150 on a 4core/4threads cpu (while all vms/containers > run smoothly). Furthermore, dmesg gets spammed with the log shown below > - after a while, the webinterface + sshd will become unresponsible. > > Is this a known problem or is there a mitigation strategy available? >
Not that I'm currently aware off. Anything interesting in `dmesg` output? > Proxmox is on version 5.1-42/724a6cb3 (running kernel: 4.13.13-5-pve). > I mean it could be a kernel update related problem. Can you try to boot in a older one? E.g., one with version 4.13-32 (or ABI 4.13.13-2-pve). > Thanks, > Elias > > > [68423.721417] systemd[1]: Starting Journal Service... > [68430.428008] systemd[1]: Started Session 66 of user root. > [68513.966147] systemd[1]: systemd-journald.service: Start operation > timed out. Terminating. > [68604.214629] systemd[1]: systemd-journald.service: State > 'stop-final-sigterm' timed out. Killing. > [68604.215344] systemd[1]: systemd-journald.service: Killing process > 1990 (systemd-journal) with signal SIGKILL. > [68604.215960] systemd[1]: systemd-journald.service: Killing process 468 > (systemd-journal) with signal SIGKILL. > [68604.216436] systemd[1]: systemd-journald.service: Killing process 470 > (systemd-journal) with signal SIGKILL. > [68604.216869] systemd[1]: systemd-journald.service: Killing process 795 > (systemd-journal) with signal SIGKILL. > [68604.217463] systemd[1]: systemd-journald.service: Killing process 825 > (systemd-journal) with signal SIGKILL. > [68604.217972] systemd[1]: systemd-journald.service: Killing process > 1272 (systemd-journal) with signal SIGKILL. > [68604.218417] systemd[1]: systemd-journald.service: Killing process > 1369 (systemd-journal) with signal SIGKILL. > [68604.218833] systemd[1]: systemd-journald.service: Killing process > 1591 (systemd-journal) with signal SIGKILL. > [68604.219230] systemd[1]: systemd-journald.service: Killing process > 1874 (systemd-journal) with signal SIGKILL. > [68634.577947] systemd[1]: Started Session 67 of user root. > [68694.463116] systemd[1]: systemd-journald.service: Processes still > around after final SIGKILL. Entering failed mode. > [68694.463704] systemd[1]: Failed to start Journal Service. > [68694.464224] systemd[1]: systemd-journald.service: Unit entered failed > state. > [68694.464660] systemd[1]: systemd-journald.service: Failed with result > 'timeout'. > [68694.465536] systemd[1]: systemd-journald.service: Service has no > hold-off time, scheduling restart. > [68694.466070] systemd[1]: Stopped Journal Service. > [68694.467034] systemd[1]: Starting Journal Service... > _______________________________________________ pve-user mailing list [email protected] https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
