Дата и время публикации:
Дата и время модификации:
Как получить критические сообщения об ошибках
Выпоняется c помощью dmesg, как показано в дампе 1.
Дамп 1
sudo dmesg -l err
[ 0.591749] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0.SWUS], AE_NOT_FOUND (20190509/dswload2-160)
[ 0.591755] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-221)
[ 0.591758] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0.SWUS.SWDS], AE_NOT_FOUND (20190509/dswload2-160)
[ 0.591761] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-221)
[ 1.295744] pci 0000:00:00.2: AMD-Vi: Unable to write to IOMMU perf counter.
[ 3.229453] tpm_crb MSFT0101:00: can't request region for resource [mem 0xbd4df000-0xbd4e2fff]
[ 3.270939] sp5100-tco sp5100-tco: Watchdog hardware is disabled
[ 3.677973] nouveau 0000:01:00.0: DRM: failed to create kernel channel, -22
[ 3.987666] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:1! type 0 expected 3
[ 3.987779] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
[ 3.987886] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3
либо через journalctl, которая выводит все возможные зарегистрированные в журнале сообщения с использованием опции '-p', как показано в дампе 2
Дамп 2
sudo journalctl -p emerg..debug -b
-- Logs begin at Sun 2019-10-20 04:46:52 UTC, end at Sun 2019-10-20 06:21:29 UTC. --
окт 20 04:46:52 home2 kernel: Linux version 5.2.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-23)) #1 SMP Debian 5.2.17>
окт 20 04:46:52 home2 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.2.0-3-amd64 root=UUID=58726747-0009-4e5e-a09d-76a799171ca0 ro quiet idle=nomwait
окт 20 04:46:52 home2 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
окт 20 04:46:52 home2 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
окт 20 04:46:52 home2 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
окт 20 04:46:52 home2 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
окт 20 04:46:52 home2 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
окт 20 04:46:52 home2 kernel: BIOS-provided physical RAM map:
окт 20 04:46:52 home2 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
окт 20 04:46:52 home2 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
окт 20 04:46:52 home2 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009e01fff] usable
окт 20 04:46:52 home2 kernel: BIOS-e820: [mem 0x0000000009e02000-0x0000000009ffffff] reserved
окт 20 04:46:52 home2 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
. . .
окт 20 05:15:52 home2 systemd[1]: Started User Manager for UID 1000.
окт 20 05:15:52 home2 systemd[1]: Started Session 13 of user user.
окт 20 05:16:42 home2 sshd[1635]: Connection closed by 192.168.2.50 port 46628 [preauth]
окт 20 05:16:52 home2 sshd[1637]: Accepted password for user from 192.168.2.50 port 46630 ssh2
окт 20 05:16:52 home2 sshd[1637]: pam_unix(sshd:session): session opened for user user by (uid=0)
окт 20 05:16:52 home2 systemd-logind[607]: New session 15 of user user.
окт 20 05:16:52 home2 systemd[1]: Started Session 15 of user user.
окт 20 05:18:47 home2 sudo[1651]: user : unable to resolve host home2
окт 20 05:18:47 home2 sudo[1651]: user : problem with defaults entries ; TTY=pts/1 ; PWD=/home/user ; USER=root ;
ввод опции -p с emerg..debug указывает journalctl выводить все зарегистрированные сообщения помеченные согласно принятой маркировки уровня приоритетности в Syslog от emerg, alert, crit, err, warning, notice, info, debug
Таким образом, использование journalctl взамен dmesg получить более объективную картину всех бедствий происшедших в системе.
Можно так же оперативно, как и в случае dmesg -f, считывать записи из журнала аудита, если поблочный вывод journalctl через опцию '-b' заменить на '-f', пример показан в дампе 3
Дамп 3
sudo journalctl -p emerg..debug -f
...
окт 26 07:18:07 home2 sshd[779]: Accepted password for admin from 192.168.2.50 port 43074 ssh2
окт 26 07:18:07 home2 sshd[779]: pam_unix(sshd:session): session opened for user admin by (uid=0)
окт 26 07:18:07 home2 systemd[1]: Created slice User Slice of UID 1001.
окт 26 07:18:07 home2 systemd[1]: Starting User Runtime Directory /run/user/1001...
окт 26 07:18:07 home2 systemd-logind[607]: New session 8 of user admin.
окт 26 07:18:07 home2 systemd[1]: Started User Runtime Directory /run/user/1001.
окт 26 07:18:07 home2 systemd[1]: Starting User Manager for UID 1001...
окт 26 07:18:07 home2 systemd[782]: pam_unix(systemd-user:session): session opened for user admin by (uid=0)
окт 26 07:18:07 home2 systemd[1]: Started User Manager for UID 1001.
окт 26 07:18:07 home2 systemd[1]: Started Session 8 of user admin.
Библиография
3.1 how to use journalctl to view and manipulate systemd logs