Я обнаружил системный сбой, используя команду `last`. Как мне решить его причину?
Здесь last Команда говорит мне (правильно), что у меня произошел сбой в 18:58 плюс 01:07 (20:05):
$ last
michael :0 :0 Mon Apr 8 20:10 still logged in
reboot system boot 4.18.20-041820-g Mon Apr 8 20:09 still running
reboot system boot 4.18.20-041820-g Mon Apr 8 20:06 - 20:08 (00:01)
michael :0 :0 Mon Apr 8 18:58 - crash (01:07)
reboot system boot 4.18.20-041820-g Mon Apr 8 18:58 - 20:08 (01:10)
reboot system boot 4.18.20-041820-g Mon Apr 8 01:02 - 01:04 (00:01)
michael :0 :0 Sun Apr 7 00:25 - crash (1+01:36)
reboot system boot 4.18.20-041820-g Sun Apr 7 00:25 - 01:04 (1+01:38)
reboot system boot 4.18.20-041820-g Sun Apr 7 00:24 - 00:24 (00:00)
michael :0 :0 Tue Apr 2 23:32 - crash (4+00:51)
reboot system boot 4.18.20-041820-g Tue Apr 2 23:32 - 00:24 (4+00:52)
wtmp begins Tue Apr 2 23:32:29 2019
Тем не менее, я просмотрел различные журналы и не нашел ничего полезного, используя journalctl:
$ journalctl -b -2 -e
Apr 08 19:17:01 michael-desktop CRON[8096]: pam_unix(cron:session): session closed for user root
Apr 08 19:25:01 michael-desktop CRON[8302]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 08 19:25:02 michael-desktop CRON[8303]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 08 19:25:02 michael-desktop CRON[8302]: pam_unix(cron:session): session closed for user root
Apr 08 19:27:39 michael-desktop systemd-resolved[958]: Grace period over, resuming full feature set (UDP+EDNS0) for DNS server fe80::7e7d:3dff:fe2e:35a9%3.
Apr 08 19:29:08 michael-desktop systemd-resolved[958]: Using degraded feature set (UDP) for DNS server fe80::7e7d:3dff:fe2e:35a9%3.
Apr 08 19:32:45 michael-desktop systemd-resolved[958]: Grace period over, resuming full feature set (UDP+EDNS0) for DNS server 192.168.0.1.
Apr 08 19:33:09 michael-desktop systemd-resolved[958]: Using degraded feature set (UDP) for DNS server 192.168.0.1.
Apr 08 19:35:01 michael-desktop CRON[8524]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 08 19:35:01 michael-desktop CRON[8525]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 08 19:35:01 michael-desktop CRON[8524]: pam_unix(cron:session): session closed for user root
Apr 08 19:36:46 michael-desktop dbus-daemon[3522]: [session uid=1000 pid=3522] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.137' (uid=1000 pid=8
Apr 08 19:36:46 michael-desktop systemd[3458]: Starting GNOME Terminal Server...
Apr 08 19:36:46 michael-desktop dbus-daemon[3522]: [session uid=1000 pid=3522] Successfully activated service 'org.gnome.Terminal'
Apr 08 19:36:46 michael-desktop systemd[3458]: Started GNOME Terminal Server.
Apr 08 19:37:05 michael-desktop gnome-shell[3767]: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
Apr 08 19:37:28 michael-desktop org.gnome.Shell.desktop[3767]: [4488:4576:0408/193728.310678:ERROR:latency_info.cc(147)] Surface::TakeLatencyInfoFromFrame, LatencyInfo vector size 102 is too big.
Apr 08 19:41:43 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 19:42:26 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 19:42:49 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 19:44:19 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 19:45:01 michael-desktop CRON[10665]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 08 19:45:01 michael-desktop CRON[10666]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 08 19:45:01 michael-desktop CRON[10665]: pam_unix(cron:session): session closed for user root
Apr 08 19:45:37 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 19:45:47 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 19:46:34 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 19:46:45 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 19:47:39 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 19:47:58 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 19:48:11 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 19:48:15 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 19:48:31 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 19:55:01 michael-desktop CRON[12067]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 08 19:55:01 michael-desktop CRON[12068]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 08 19:55:01 michael-desktop CRON[12067]: pam_unix(cron:session): session closed for user root
Apr 08 19:58:14 michael-desktop canonical-livepatch[1887]: Client.Check
Apr 08 19:58:14 michael-desktop canonical-livepatch[1887]: cannot get current kernel version: fork/exec /uname: no such file or directory
Apr 08 19:58:14 michael-desktop canonical-livepatch[1887]: error in livepatch check state: check-failed
Apr 08 19:58:14 michael-desktop canonical-livepatch[1887]: Checking with livepatch service.
Apr 08 19:58:16 michael-desktop canonical-livepatch[1887]: updating last-check
Apr 08 19:58:16 michael-desktop canonical-livepatch[1887]: touched last check
Apr 08 19:58:16 michael-desktop canonical-livepatch[1887]: No updates available at this time.
Apr 08 19:58:16 michael-desktop canonical-livepatch[1887]: No payload available.
Apr 08 20:04:39 michael-desktop gnome-shell[3767]: pushModal: invocation of begin_modal failed
Apr 08 20:05:01 michael-desktop CRON[12989]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 08 20:05:01 michael-desktop CRON[12990]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 08 20:05:01 michael-desktop CRON[12989]: pam_unix(cron:session): session closed for user root
Есть ли другие полезные команды, которые я могу использовать? Есть ли что-нибудь, что last может автоматически сделать, так как он правильно обнаружил сбой. Если он нашел сбой в /var/log/wtmpКак я могу посмотреть на этот файл для деталей?