Hallo, ich habe eine SLES 12 SP5 Maschine die gestern extrem lange zum Booten gebr= uacht hat: Jan 18 23:53:21 geneious systemd[1]: Startup finished in 3.310s (kernel) + = 2min 31.383s (initrd) + 9min 11.363s (userspace) =3D 11min 46.057s. Normalerseise dauert dies weniger als eine Minute, auf dem host l=C3=A4uft = eine kleine Postgres Datenbank, sonst nix. Nachdem der Bootvorgang abgeschlossen war konnte ich mich anmelden, und die= CPU hat fast 100% IO gemacht. Ich habe dann iotop installiert (was nat=C3=BCrlich auch Minuten gedauert h= at). Als die Installation fertig war war aber die IO-Last weg. Ein paar Sachen sind mir aufgefallen: Teilweise sind die Eintr=C3=A4ge nicht chronologisch: Jan 18 23:45:31 linux-8i1i systemd-journald[137]: Received SIGTERM from PID= 1 (systemd). Jan 18 23:45:31 linux-8i1i kernel: systemd: 19 output lines suppressed due = to ratelimiting Jan 18 23:45:31 linux-8i1i systemd-sysv-generator[543]: Overwriting existin= g symlink /run/systemd/generator.late/inputattach.service with real service= . Jan 18 23:45:31 linux-8i1i kernel: EXT4-fs (dm-1): re-mounted. Opts: acl,us= er_xattr Jan 18 23:45:31 linux-8i1i systemd-journald[549]: Journal started -- Subject: The journal has been started -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The system journal process has started up, opened the journal -- files for writing and is now ready to process requests. Jan 18 23:44:22 linux-8i1i systemd[1]: systemd 228 running in system mode. = (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP = +GCRYPT -GNUTLS +ACL +XZ -LZ4 +SECCOMP Jan 18 23:44:22 linux-8i1i systemd[1]: Detected virtualization kvm. Jan 18 23:44:22 linux-8i1i systemd[1]: Detected architecture x86-64. Jan 18 23:44:23 linux-8i1i systemd[1]: Set hostname to <linux-8i1i>. Jan 18 23:45:08 linux-8i1i systemd[1]: nss-lookup.target: Dependency Before= =3Dnss-lookup.target dropped Jan 18 23:45:20 linux-8i1i systemd[1]: Configuration file /opt/nsr/admin/ne= tworker.service is marked executable. Please remove executable permission b= its. Proceeding anyway. Jan 18 23:45:33 linux-8i1i systemd-tmpfiles[564]: [/usr/lib/tmpfiles.d/dirm= ngr.conf:1] Line references path below legacy directory /var/run/, updating= /var/run/dirmngr =E2=86=92 /run/dirmngr; pleas Jan 18 23:45:36 linux-8i1i systemd-sysctl[572]: Couldn't write '0' to 'dev/= cdrom/autoclose', ignoring: No such file or directory Wie kann das sein ? Ich dachte beim Booten werden Dienste gestartet. Wieso werden dann im Journal so viele runtergefahren ? -- Subject: Unit user@0.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit user@0.service has begun shutting down. Jan 19 02:45:01 geneious systemd[3485]: Stopped target Default. -- Subject: Unit UNIT has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit UNIT has finished shutting down. Jan 19 02:45:01 geneious systemd[3485]: Stopped target Basic System. -- Subject: Unit UNIT has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit UNIT has finished shutting down. Jan 19 02:45:01 geneious systemd[3485]: Stopped target Timers. -- Subject: Unit UNIT has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit UNIT has finished shutting down. Jan 19 02:45:01 geneious systemd[3485]: Stopped target Sockets. -- Subject: Unit UNIT has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit UNIT has finished shutting down. Jan 19 02:45:01 geneious systemd[3485]: Stopped target Paths. -- Subject: Unit UNIT has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit UNIT has finished shutting down. Jan 19 02:45:01 geneious systemd[3485]: Reached target Shutdown. -- Subject: Unit UNIT has finished start-up Danke. Bernd --=20 Bernd Lentes=20 Head of Systemadministration=20 Institute for Metabolism and Cell Death (MCD)=20 Building 25 - office 122=20 HelmholtzZentrum M=C3=BCnchen=20 bernd.lentes@helmholtz-muenchen.de=20 phone: +49 89 3187 1241=20 phone: +49 89 3187 3827=20 fax: +49 89 3187 2294=20 http://www.helmholtz-muenchen.de/mcd Helmholtz Zentrum München Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Aufsichtsratsvorsitzende: MinDir.in Prof. Dr. Veronika von Messling Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Kerstin Guenther Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671
----- On Jan 19, 2021, at 11:46 AM, Bernd Lentes bernd.lentes@helmholtz-muenchen.de wrote:
Hallo,
ich habe eine SLES 12 SP5 Maschine die gestern extrem lange zum Booten gebr= uacht hat: Jan 18 23:53:21 geneious systemd[1]: Startup finished in 3.310s (kernel) + = 2min 31.383s (initrd) + 9min 11.363s (userspace) =3D 11min 46.057s. Normalerseise dauert dies weniger als eine Minute, auf dem host l=C3=A4uft = eine kleine Postgres Datenbank, sonst nix.
Nachdem der Bootvorgang abgeschlossen war konnte ich mich anmelden, und die= CPU hat fast 100% IO gemacht. Ich habe dann iotop installiert (was nat=C3=BCrlich auch Minuten gedauert h= at). Als die Installation fertig war war aber die IO-Last weg.
Ein paar Sachen sind mir aufgefallen: Teilweise sind die Eintr=C3=A4ge nicht chronologisch: Jan 18 23:45:31 linux-8i1i systemd-journald[137]: Received SIGTERM from PID= 1 (systemd). Jan 18 23:45:31 linux-8i1i kernel: systemd: 19 output lines suppressed due = to ratelimiting Jan 18 23:45:31 linux-8i1i systemd-sysv-generator[543]: Overwriting existin= g symlink /run/systemd/generator.late/inputattach.service with real service= . Jan 18 23:45:31 linux-8i1i kernel: EXT4-fs (dm-1): re-mounted. Opts: acl,us= er_xattr Jan 18 23:45:31 linux-8i1i systemd-journald[549]: Journal started -- Subject: The journal has been started -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The system journal process has started up, opened the journal -- files for writing and is now ready to process requests. Jan 18 23:44:22 linux-8i1i systemd[1]: systemd 228 running in system mode. = (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP = +GCRYPT -GNUTLS +ACL +XZ -LZ4 +SECCOMP Jan 18 23:44:22 linux-8i1i systemd[1]: Detected virtualization kvm. Jan 18 23:44:22 linux-8i1i systemd[1]: Detected architecture x86-64. Jan 18 23:44:23 linux-8i1i systemd[1]: Set hostname to <linux-8i1i>. Jan 18 23:45:08 linux-8i1i systemd[1]: nss-lookup.target: Dependency Before= =3Dnss-lookup.target dropped Jan 18 23:45:20 linux-8i1i systemd[1]: Configuration file /opt/nsr/admin/ne= tworker.service is marked executable. Please remove executable permission b= its. Proceeding anyway. Jan 18 23:45:33 linux-8i1i systemd-tmpfiles[564]: [/usr/lib/tmpfiles.d/dirm= ngr.conf:1] Line references path below legacy directory /var/run/, updating= /var/run/dirmngr =E2=86=92 /run/dirmngr; pleas Jan 18 23:45:36 linux-8i1i systemd-sysctl[572]: Couldn't write '0' to 'dev/= cdrom/autoclose', ignoring: No such file or directory
Wie kann das sein ?
Ich dachte beim Booten werden Dienste gestartet. Wieso werden dann im Journal so viele runtergefahren ?
-- Subject: Unit user@0.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit user@0.service has begun shutting down. Jan 19 02:45:01 geneious systemd[3485]: Stopped target Default. -- Subject: Unit UNIT has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit UNIT has finished shutting down. Jan 19 02:45:01 geneious systemd[3485]: Stopped target Basic System. -- Subject: Unit UNIT has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit UNIT has finished shutting down. Jan 19 02:45:01 geneious systemd[3485]: Stopped target Timers. -- Subject: Unit UNIT has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit UNIT has finished shutting down. Jan 19 02:45:01 geneious systemd[3485]: Stopped target Sockets. -- Subject: Unit UNIT has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit UNIT has finished shutting down. Jan 19 02:45:01 geneious systemd[3485]: Stopped target Paths. -- Subject: Unit UNIT has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit UNIT has finished shutting down. Jan 19 02:45:01 geneious systemd[3485]: Reached target Shutdown. -- Subject: Unit UNIT has finished start-up
Danke.
Bernd
Hier ist das Journal vom Booten: https://nc-mcd.helmholtz-muenchen.de/nextcloud/s/y4yq5WWyetienMH Bernd Helmholtz Zentrum München Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Aufsichtsratsvorsitzende: MinDir.in Prof. Dr. Veronika von Messling Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Kerstin Guenther Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671
participants (1)
-
Lentes, Bernd