Enable persistent storage for the systemd journal loghttps://gist.github.com/JPvRiel/b7c185833da32631fa6ce65b40836887
All journal logs:
sudo journalctl
Logs from previous boot only (where -1 means the current boot log minus one, replace with -2, -3, as needed):
sudo journalctl -b -1
Makes sense to me. Will take me a while to find right one but that is what I needed.
Will get back if I find issues.
Regards.
My trying to sort out my network manager configuration left me unable to boot for a long time. I left the system in the stalled situation and changed to my Debian machine to be able to keep in touch. When I returned the boot had completed so I thought I would check what was happening. I received the following results:-
alastair@ibmserv2:~> sudo systemd-analyze critical-chain
[sudo] password for root:
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
└─display-manager.service @22.877s +2.777s
└─systemd-user-sessions.service @22.758s +115ms
└─network.target @14.962s
└─NetworkManager.service @14.499s +462ms
└─network-pre.target @14.497s
└─firewalld.service @7.213s +7.283s
└─polkit.service @4.563s +2.648s
└─basic.target @4.545s
└─tmp.mount @14.985s +8ms
└─dev-sda3.device @6.222s
alastair@ibmserv2:~> sudo systemd-analyze blame
12.659s postfix.service
7.936s btrfsmaintenance-refresh.service
7.283s firewalld.service
7.207s NetworkManager-wait-online.service
4.456s smartd.service
3.399s initrd-switch-root.service
2.777s display-manager.service
2.666s avahi-daemon.service
2.648s polkit.service
2.211s plymouth-quit-wait.service
1.913s dracut-initqueue.service
1.766s apparmor.service
1.724s udisks2.service
1.580s nscd.service
1.399s rsyslog.service
1.333s rpcbind.service
1.077s systemd-udevd.service
1.037s ModemManager.service
1.013s user@1000.service
863ms mcelog.service
808ms kbdsettings.service
734ms upower.service
711ms issue-generator.service
710ms sound-extra.service
602ms systemd-logind.service
574ms home-alastair-Nas_Multimedia_NFS.mount
496ms systemd-journald.service
463ms multimedia.mount
462ms NetworkManager.service
362ms home.mount
330ms systemd-udev-trigger.service
317ms sysroot.mount
311ms systemd-tmpfiles-clean.service
251ms systemd-sysctl.service
242ms initrd-parse-etc.service
218ms plymouth-switch-root.service
217ms auditd.service
204ms systemd-tmpfiles-setup.service
191ms systemd-tmpfiles-setup-dev.service
187ms systemd-random-seed.service
176ms systemd-journal-flush.service
151ms systemd-modules-load.service
148ms klog.service
137ms systemd-remount-fs.service
132ms systemd-update-utmp.service
131ms user-runtime-dir@1000.service
119ms plymouth-read-write.service
118ms rtkit-daemon.service
117ms boot-efi.mount
115ms systemd-user-sessions.service
81ms dev-disk-by\x2duuid-46f191b6\x2d7472\x2d49c0\x2dbd98\x2d75824020d947.swap
79ms iscsi.service
71ms dracut-cmdline.service
44ms \x2esnapshots.mount
41ms boot-grub2-i386\x2dpc.mount
38ms plymouth-start.service
32ms dracut-pre-udev.service
28ms dev-hugepages.mount
27ms dev-mqueue.mount
26ms initrd-cleanup.service
26ms systemd-fsck-root.service
25ms boot-grub2-x86_64\x2defi.mount
24ms var.mount
24ms sys-kernel-debug.mount
23ms dracut-shutdown.service
23ms sys-kernel-tracing.mount
22ms kmod-static-nodes.service
20ms opt.mount
19ms root.mount
19ms systemd-vconsole-setup.service
17ms srv.mount
10ms initrd-udevadm-cleanup-db.service
8ms usr-local.mount
8ms tmp.mount
7ms sys-fs-fuse-connections.mount
Nothing too outrageous here but this I do not understand:-
alastair@ibmserv2:~> sudo journalctl -b -1
[sudo] password for root:
Specifying boot ID or boot offset has no effect, no persistent journal was found.
alastair@ibmserv2:~>
Have I used the wrong command. A typo I cannot see?
Running simply
sudo journalctl
gives me too much to post!
What does the following report?
ls -la /var/log/journal
Also share
cat /etc/systemd/journald.conf
Review the following guide
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha-journalctl.html#sec-journalctl-persistent
The services times don’t explain the delay at all. 8 minutes is a lot. Have you checked the hardware connections (disks, ram)?
A few more commands:
systemd-analyze
sudo journalctl -b -p 0..4
sudo journalctl -b --grep timeout
sudo journalctl -b --grep timed
Also, does the journal cover these 8 minutes? You might find a gap there that can provide some explanation.
The small i3-4130 assembled in 2014 has:
erlangen:~ # systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @3.094s
└─display-manager.service @1.925s +1.167s
└─apache2.service @1.744s +177ms
└─time-sync.target @1.733s
└─chronyd.service @1.480s +252ms
└─network.target @1.479s
└─systemd-networkd.service @837ms +642ms
└─systemd-udevd.service @363ms +472ms
└─systemd-tmpfiles-setup-dev.service @320ms +18ms
└─kmod-static-nodes.service @294ms +9ms
└─systemd-journald.socket
└─system.slice
└─-.slice
erlangen:~ #
1.307s dracut-initqueue.service
1.167s display-manager.service
1.031s postfix.service
994ms udisks2.service
822ms systemd-logind.service
642ms systemd-networkd.service
476ms upower.service
472ms systemd-udevd.service
431ms initrd-switch-root.service
397ms kbdsettings.service
373ms systemd-journald.service
252ms chronyd.service
178ms initrd-parse-etc.service
178ms user@1000.service
177ms apache2.service
149ms user@1001.service
145ms systemd-journal-flush.service
141ms issue-generator.service
128ms systemd-udev-trigger.service
You definitely may improve your setup.