openSUSE Tumbleweed 64
I see some [FAILED] messages scrolling by when I boot, too fast for me to read. Are these logged in journalctl now? I looked in boot.log but they aren’t in there. Everything in boot.log says [OK]
Try
sudo grep -i failed /var/log/messages
I don’t have a /var/log/messages file… I guess because of systemd journal right?
Hi
Use the journal;
journalctl -b --no-pager |egrep "Failed|failed"
Ok I found them. I was expecting to find “[FAILED]” as shown during boot. But it isn’t in the journal like that. grep’ing failed works, thanks
Same output, except limited to current boot, and the Fs preceding ailed won’t be a highlighted color:
journalctl -b | grep ailed
Hi
I get extra stuff (det)ailed 
Aug 22 20:11:23 grover /usr/lib/gdm/gdm-x-session[1687]: (II) modeset(0): First detailed timing is preferred mode
Aug 22 20:11:23 grover /usr/lib/gdm/gdm-x-session[1687]: (II) modeset(0): Supported detailed timing:
Aug 22 20:11:23 grover /usr/lib/gdm/gdm-x-session[1687]: (II) modeset(0): Supported detailed timing:
Aug 22 20:11:23 grover /usr/lib/gdm/gdm-x-session[1687]: (II) modeset(0): Supported detailed timing:
Aug 22 20:11:23 grover /usr/lib/gdm/gdm-x-session[1687]: (II) modeset(0): Supported detailed timing:
Aug 22 20:11:23 grover /usr/lib/gdm/gdm-x-session[1687]: (II) modeset(0): Supported detailed timing:
Aug 22 20:11:23 grover /usr/lib/gdm/gdm-x-session[1687]: (II) modeset(0): Supported detailed timing:
I don’t have GDM, and got no detaileds.
# journalctl -b | grep -i failed
hn kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170303/psparse-516)
hn kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20170303/psparse-516)
hn systemd-sysv-generator[408]: stat() failed on /etc/init.d/lpd, ignoring: No such file or directory
hn systemd-vconsole-setup[608]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented
hn rpc.statd[1233]: Failed to create listener xprt (statd, 1, udp6)
hn rpc.statd[1233]: Failed to create listener xprt (statd, 1, tcp6)
(time/hostname redacted) eliminates any detaileds.
What about
grep -i ....
Priority based filtering:
erlangen:~ # journalctl --boot -2 **--priority err**
-- Logs begin at Wed 2019-07-31 16:03:01 CEST, end at Fri 2019-08-23 12:45:19 CEST. --
Aug 23 06:01:35 erlangen kernel: Couldn't get size: 0x800000000000000e
Aug 23 06:01:37 erlangen smartd[990]: Device: /dev/nvme0, number of Error Log entries increased from 1923 to 1924
Aug 23 06:01:37 erlangen systemd[1]: Failed to start WPA Supplicant daemon (interface wlan0).
Aug 23 06:03:38 erlangen systemd-networkd-wait-online[1143]: Event loop failed: Connection timed out
Aug 23 06:03:38 erlangen systemd[1]: Failed to start Wait for Network to be Configured.
Aug 23 06:16:33 erlangen kglobalaccel5[3206]: Failed to create wl_display (No such file or directory)
Aug 23 06:16:33 erlangen kglobalaccel5[3206]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Aug 23 06:16:33 erlangen systemd-logind[986]: Failed to start autovt@tty1.service: Transaction for getty@tty1.service/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
Aug 23 06:16:34 erlangen systemd-logind[986]: Failed to start autovt@tty1.service: Transaction for getty@tty1.service/start is destructive (sysinit.target has 'stop' job queued, but 'start' is included in transaction).
Aug 23 06:16:45 erlangen kernel: watchdog: watchdog0: watchdog did not stop!
erlangen:~ #
Although grepping typically works, it’s an unwieldy way to search the journal… The entire journal has to be read before the grep command can be applied.
You’ll get faster results if you query the journal directly using journalctl commands… And you can query for different levels of errors.
If you prefer not to read the journalctl MAN pages (who generally does?),
The following is a highly recommended, easy to read article describing how to search using journalctl commands…
After reading it and being more or less familiar with the content, I often return to this page and do a search on the page (CTL-F) to do a quick lookup for details.
TSU
The minus 2 (-2) here means two boots ago?
Hi
Last boot, not long at all… happens quicker that I can type it in… different strokes for different folks, which is a good thing
Thanks! I’m going to be doing similar, so much so I made a custom stylesheet to make it comfortable: http://fm.no-ip.com/Share/digitalocean.css
Exactly! journalctl is a big step forward. I used the long options for clarity. Actually I prefer journalctl -b -2 -p3.