Project

General

Profile

Anomalie #4761

Systemd en erreur sur les pm lors d'un reboot

Added by Christian P. Momon 2 months ago. Updated about 1 month ago.

Status:
Nouveau
Priority:
Élevée
Assignee:
-
Target version:
Start date:
09/30/2020
Due date:
% Done:

0%

Estimated time:

Description

Ce 30 septembre, durant la procédure de reboot pour maj noyal :

=(^-^)=root@maine:~# systemctl list-units
  UNIT                                                                                     LOAD   ACTIVE SUB       DESCRIPTION
● systemd-sysctl.service                                                                   loaded failed failed    Apply Kernel Variables

=(^-^)=root@maine:~# systemctl status systemd-sysctl.service
● systemd-sysctl.service - Apply Kernel Variables
   Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor preset: enabled)
  Drop-In: /etc/systemd/system/systemd-sysctl.service.d
           └─chapril-swappiness-post.conf
   Active: failed (Result: exit-code) since Wed 2020-09-30 01:38:03 CEST; 1min 31s ago
     Docs: man:systemd-sysctl.service(8)
           man:sysctl.d(5)
  Process: 388 ExecStart=/lib/systemd/systemd-sysctl (code=exited, status=0/SUCCESS)
  Process: 390 ExecStartPost=/usr/bin/find /sys/fs/cgroup -mindepth 2 -maxdepth 2 -name memory.swappiness -exec /bin/sh -c sysctl -n vm.swappiness > "{}" ; (code=exited, status=0/SUCCESS)
  Process: 393 ExecStartPost=/usr/bin/find /sys/fs/cgroup -mindepth 3 -maxdepth 3 -name memory.swappiness -exec /bin/sh -c sysctl -n vm.swappiness > "{}" ; (code=exited, status=0/SUCCESS)
  Process: 398 ExecStartPost=/usr/bin/find /sys/fs/cgroup -mindepth 4 -maxdepth 4 -name memory.swappiness -exec /bin/sh -c sysctl -n vm.swappiness > "{}" ; (code=exited, status=1/FAILURE)
 Main PID: 388 (code=exited, status=0/SUCCESS)

sept. 30 01:38:03 maine.chapril.org systemd[1]: Starting Apply Kernel Variables...
sept. 30 01:38:03 maine.chapril.org find[398]: /usr/bin/find: ‘/sys/fs/cgroup/memory/system.slice/systemd-tmpfiles-setup-dev.service’: Aucun fichier ou dossier de ce type
sept. 30 01:38:03 maine.chapril.org systemd[1]: systemd-sysctl.service: Control process exited, code=exited, status=1/FAILURE
sept. 30 01:38:03 maine.chapril.org systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
sept. 30 01:38:03 maine.chapril.org systemd[1]: Failed to start Apply Kernel Variables.

Pareil sur coon :

=(^-^)=root@coon:~# systemctl list-units
  UNIT                                                                                     LOAD   ACTIVE SUB       DESCRIPTION
● systemd-sysctl.service                                                                   loaded failed failed    Apply Kernel Variables

=(^-^)=root@coon:~# systemctl status systemd-sysctl.service
● systemd-sysctl.service - Apply Kernel Variables
   Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor preset: enabled)
  Drop-In: /etc/systemd/system/systemd-sysctl.service.d
           └─chapril-swappiness-post.conf
   Active: failed (Result: exit-code) since Wed 2020-09-30 01:49:27 CEST; 1min 33s ago
     Docs: man:systemd-sysctl.service(8)
           man:sysctl.d(5)
  Process: 354 ExecStart=/lib/systemd/systemd-sysctl (code=exited, status=0/SUCCESS)
  Process: 355 ExecStartPost=/usr/bin/find /sys/fs/cgroup -mindepth 2 -maxdepth 2 -name memory.swappiness -exec /bin/sh -c sysctl -n vm.swappiness > "{}" ; (code=exited, status=0/SUCCESS)
  Process: 360 ExecStartPost=/usr/bin/find /sys/fs/cgroup -mindepth 3 -maxdepth 3 -name memory.swappiness -exec /bin/sh -c sysctl -n vm.swappiness > "{}" ; (code=exited, status=0/SUCCESS)
  Process: 365 ExecStartPost=/usr/bin/find /sys/fs/cgroup -mindepth 4 -maxdepth 4 -name memory.swappiness -exec /bin/sh -c sysctl -n vm.swappiness > "{}" ; (code=exited, status=1/FAILURE)
 Main PID: 354 (code=exited, status=0/SUCCESS)

sept. 30 01:49:27 coon.chapril.org find[365]: /usr/bin/find: ‘/sys/fs/cgroup/memory/system.slice/lvm2-monitor.service’: Aucun fichier ou dossier de ce type
sept. 30 01:49:27 coon.chapril.org systemd[1]: systemd-sysctl.service: Control process exited, code=exited, status=1/FAILURE
sept. 30 01:49:27 coon.chapril.org systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
sept. 30 01:49:27 coon.chapril.org systemd[1]: Failed to start Apply Kernel Variables.

À chaque fois, un simple systemctl restart systemd-sysctl.service a débloqué la situation.

Questions :
- cela vient-il de la nature pm des machines ?
- que faire pour éviter le problème à nouveau ?

History

#1

Updated by François Poulain about 1 month ago

Visiblement c'est aussi sur les VM.

=(^-^)=root@allo:~# systemctl status systemd-sysctl
● systemd-sysctl.service - Apply Kernel Variables
   Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor preset: enabled)
  Drop-In: /etc/systemd/system/systemd-sysctl.service.d
           └─chapril-swappiness-post.conf
   Active: failed (Result: exit-code) since Tue 2020-10-20 00:11:34 CEST; 13h ago
     Docs: man:systemd-sysctl.service(8)
           man:sysctl.d(5)
  Process: 279 ExecStart=/lib/systemd/systemd-sysctl (code=exited, status=0/SUCCESS)
  Process: 284 ExecStartPost=/usr/bin/find /sys/fs/cgroup -mindepth 2 -maxdepth 2 -name memory.swappiness -exec /bin/sh -c sysctl -n vm.swappiness > "{}" ; (code=exited, status=0/SUCCESS)
  Process: 288 ExecStartPost=/usr/bin/find /sys/fs/cgroup -mindepth 3 -maxdepth 3 -name memory.swappiness -exec /bin/sh -c sysctl -n vm.swappiness > "{}" ; (code=exited, status=0/SUCCESS)
  Process: 293 ExecStartPost=/usr/bin/find /sys/fs/cgroup -mindepth 4 -maxdepth 4 -name memory.swappiness -exec /bin/sh -c sysctl -n vm.swappiness > "{}" ; (code=exited, status=0/SUCCESS)
  Process: 316 ExecStartPost=/usr/bin/find /sys/fs/cgroup -mindepth 5 -maxdepth 5 -name memory.swappiness -exec /bin/sh -c sysctl -n vm.swappiness > "{}" ; (code=exited, status=0/SUCCESS)
  Process: 317 ExecStartPost=/usr/bin/find /sys/fs/cgroup -name memory.swappiness -exec /bin/sh -c sysctl -n vm.swappiness > "{}" ; (code=exited, status=1/FAILURE)
 Main PID: 279 (code=exited, status=0/SUCCESS)

oct. 20 00:11:33 allo.cluster.chapril.org systemd[1]: Starting Apply Kernel Variables...
oct. 20 00:11:34 allo.cluster.chapril.org find[317]: /usr/bin/find: ‘/sys/fs/cgroup/memory/system.slice/keyboard-setup.service’: Aucun fichier ou dossier de ce type
oct. 20 00:11:34 allo.cluster.chapril.org systemd[1]: systemd-sysctl.service: Control process exited, code=exited, status=1/FAILURE
oct. 20 00:11:34 allo.cluster.chapril.org systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
oct. 20 00:11:34 allo.cluster.chapril.org systemd[1]: Failed to start Apply Kernel Variables.
#2

Updated by Christian P. Momon about 1 month ago

  • Priority changed from Normale to Élevée

Super bien vu. Comme pas d'alerte sur le status dans Icinga, je pensais naïvement que tout allait bien et que ça ne concernait que les pm…

cpm@ocmstar (15:16:02) ~/Dossiers/April/Chapril/Adminsys 20 > ./do.sh "systemctl status |head -3 | grep State | egrep -i '(degraded|running)'" 
===== bastion =====
    State: degraded
===== lamp =====
    State: degraded
===== libreoffice =====
    State: degraded
===== allo =====
    State: degraded
===== icinga2.chapril.org =====
    State: degraded

Also available in: Atom PDF