Feb 15 15:39:53 host-131 NetworkManager[2818]: <info>  [1708000793.1962] device (enp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 15 15:39:53 host-131 NetworkManager[2818]: <info>  [1708000793.1968] device (enp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Feb 15 15:39:53 host-131 NetworkManager[2818]: <info>  [1708000793.1970] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Feb 15 15:39:53 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:39:53 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:39:53 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:39:53 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:39:53 host-131 lightdm[3006]: pam_tcb(lightdm:auth): Authentication passed for test from (uid=0)
Feb 15 15:39:53 host-131 lightdm[3006]: gkr-pam: unable to locate daemon control file
Feb 15 15:39:53 host-131 lightdm[3006]: gkr-pam: stashed password to try later in open session
Feb 15 15:39:53 host-131 systemd[1]: systemd-rfkill.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit systemd-rfkill.service has successfully entered the 'dead' state.
Feb 15 15:39:53 host-131 systemd[1]: Stopping Session 1 of User _ldm...
-- Subject: A stop job for unit session-1.scope has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit session-1.scope has begun execution.
-- 
-- The job identifier is 1231.
Feb 15 15:39:53 host-131 systemd[1]: session-1.scope: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit session-1.scope has successfully entered the 'dead' state.
Feb 15 15:39:53 host-131 systemd[1]: Stopped Session 1 of User _ldm.
-- Subject: A stop job for unit session-1.scope has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit session-1.scope has finished.
-- 
-- The job identifier is 1231 and the job result is done.
Feb 15 15:39:53 host-131 systemd-logind[2726]: Removed session 1.
-- Subject: Session 1 has been terminated
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: sd-login(3)
-- 
-- A session with the ID 1 has been terminated.
Feb 15 15:39:53 host-131 lightdm[3006]: pam_tcb(lightdm:session): Session opened for test by (uid=0)
Feb 15 15:39:53 host-131 systemd[1]: Created slice User Slice of UID 500.
-- Subject: A start job for unit user-500.slice has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit user-500.slice has finished successfully.
-- 
-- The job identifier is 1336.
Feb 15 15:39:53 host-131 systemd[1]: Starting User Runtime Directory /run/user/500...
-- Subject: A start job for unit user-runtime-dir@500.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit user-runtime-dir@500.service has begun execution.
-- 
-- The job identifier is 1335.
Feb 15 15:39:53 host-131 systemd-logind[2726]: New session 3 of user test.
-- Subject: A new session 3 has been created for user test
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: sd-login(3)
-- 
-- A new session with the ID 3 has been created for the user test.
-- 
-- The leading process of the session is 3006.
Feb 15 15:39:53 host-131 systemd[1]: Finished User Runtime Directory /run/user/500.
-- Subject: A start job for unit user-runtime-dir@500.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit user-runtime-dir@500.service has finished successfully.
-- 
-- The job identifier is 1335.
Feb 15 15:39:53 host-131 systemd[1]: Starting User Manager for UID 500...
-- Subject: A start job for unit user@500.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit user@500.service has begun execution.
-- 
-- The job identifier is 1232.
Feb 15 15:39:53 host-131 (systemd)[3019]: pam_tcb(systemd-user:session): Session opened for test by (uid=0)
Feb 15 15:39:54 host-131 systemd-xdg-autostart-generator[3025]: /home/test/.config/autostart/gnome-keyring-gpg.desktop:1: Assignment outside of section. Ignoring.
Feb 15 15:39:54 host-131 systemd-xdg-autostart-generator[3025]: /home/test/.config/autostart/gnome-keyring-ssh.desktop:1: Assignment outside of section. Ignoring.
Feb 15 15:39:54 host-131 systemd-xdg-autostart-generator[3025]: /home/test/.config/autostart/mate-keyring-ssh.desktop:1: Assignment outside of section. Ignoring.
Feb 15 15:39:54 host-131 systemd[3019]: Queued start job for default target Main User Target.
Feb 15 15:39:54 host-131 systemd[3019]: Created slice User Application Slice.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 8.
Feb 15 15:39:54 host-131 systemd[3019]: Created slice User Core Session Slice.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 21.
Feb 15 15:39:54 host-131 systemd[3019]: Started Daily Cleanup of User's Temporary Directories.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 11.
Feb 15 15:39:54 host-131 systemd[3019]: Reached target Paths.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 5.
Feb 15 15:39:54 host-131 systemd[3019]: Reached target Timers.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 10.
Feb 15 15:39:54 host-131 systemd[3019]: Starting D-Bus User Message Bus Socket...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 14.
Feb 15 15:39:54 host-131 systemd[3019]: Listening on GnuPG network certificate management daemon.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 18.
Feb 15 15:39:54 host-131 systemd[3019]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 16.
Feb 15 15:39:54 host-131 systemd[3019]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 13.
Feb 15 15:39:54 host-131 systemd[3019]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 19.
Feb 15 15:39:54 host-131 systemd[3019]: Listening on GnuPG cryptographic agent and passphrase cache.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 15.
Feb 15 15:39:54 host-131 systemd[3019]: Listening on Sound System.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 17.
Feb 15 15:39:54 host-131 systemd[3019]: Starting Create User's Volatile Files and Directories...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 7.
Feb 15 15:39:54 host-131 systemd[3019]: Listening on D-Bus User Message Bus Socket.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 14.
Feb 15 15:39:54 host-131 systemd[3019]: Reached target Sockets.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 12.
Feb 15 15:39:54 host-131 systemd[3019]: Finished Create User's Volatile Files and Directories.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 7.
Feb 15 15:39:54 host-131 systemd[3019]: Reached target Basic System.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 4.
Feb 15 15:39:54 host-131 systemd[1]: Started User Manager for UID 500.
-- Subject: A start job for unit user@500.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit user@500.service has finished successfully.
-- 
-- The job identifier is 1232.
Feb 15 15:39:54 host-131 systemd[1]: Started Session 3 of User test.
-- Subject: A start job for unit session-3.scope has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit session-3.scope has finished successfully.
-- 
-- The job identifier is 1338.
Feb 15 15:39:54 host-131 systemd[3019]: Starting Sound Service...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 20.
Feb 15 15:39:54 host-131 systemd[3019]: Starting D-Bus User Message Bus...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 23.
Feb 15 15:39:54 host-131 lightdm[3006]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Feb 15 15:39:54 host-131 systemd[3019]: Started D-Bus User Message Bus.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 23.
Feb 15 15:39:54 host-131 systemd[3019]: Started Sound Service.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 20.
Feb 15 15:39:54 host-131 systemd[3019]: Reached target Main User Target.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 3.
Feb 15 15:39:54 host-131 systemd[3019]: Startup finished in 366ms.
-- Subject: User manager start-up is now complete
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The user manager instance for user 500 has been started. All services queued
-- for starting have been started. Note that other services might still be starting
-- up or be started at any later time.
-- 
-- Startup of the manager took 366588 microseconds.
Feb 15 15:39:54 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=500 pid=3036 comm="/usr/bin/mate-session")
Feb 15 15:39:54 host-131 systemd[3019]: Starting Virtual filesystem service...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 41.
Feb 15 15:39:54 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.gtk.vfs.Daemon'
Feb 15 15:39:54 host-131 systemd[3019]: Started Virtual filesystem service.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 41.
Feb 15 15:39:54 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.5' (uid=500 pid=3036 comm="/usr/bin/mate-session")
Feb 15 15:39:54 host-131 systemd[3019]: Starting Accessibility services bus...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 58.
Feb 15 15:39:54 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.a11y.Bus'
Feb 15 15:39:54 host-131 systemd[3019]: Started Accessibility services bus.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 58.
Feb 15 15:39:54 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.3' (uid=500 pid=3036 comm="/usr/bin/mate-session")
Feb 15 15:39:54 host-131 systemd[3019]: Starting User preferences database...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 75.
Feb 15 15:39:54 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'ca.desrt.dconf'
Feb 15 15:39:54 host-131 systemd[3019]: Started User preferences database.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 75.
Feb 15 15:39:54 host-131 mate-session[3036]: WARNING: Could not parse desktop file /home/test/.config/autostart/gnome-keyring-gpg.desktop: Файл ключей не начинается с группы
Feb 15 15:39:54 host-131 mate-session[3036]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x56184574a2f0 finalized while still in-construction
Feb 15 15:39:54 host-131 mate-session[3036]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is invalid). Please use GInitable instead.
Feb 15 15:39:54 host-131 mate-session[3036]: WARNING: could not read /home/test/.config/autostart/gnome-keyring-gpg.desktop
Feb 15 15:39:54 host-131 mate-session[3036]: WARNING: Could not parse desktop file /home/test/.config/autostart/gnome-keyring-ssh.desktop: Файл ключей не начинается с группы
Feb 15 15:39:54 host-131 mate-session[3036]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x56184574a3b0 finalized while still in-construction
Feb 15 15:39:54 host-131 mate-session[3036]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is invalid). Please use GInitable instead.
Feb 15 15:39:54 host-131 mate-session[3036]: WARNING: could not read /home/test/.config/autostart/gnome-keyring-ssh.desktop
Feb 15 15:39:54 host-131 mate-session[3036]: WARNING: Could not parse desktop file /home/test/.config/autostart/mate-keyring-ssh.desktop: Файл ключей не начинается с группы
Feb 15 15:39:54 host-131 mate-session[3036]: GLib-GObject-CRITICAL: object GsmAutostartApp 0x56184574a470 finalized while still in-construction
Feb 15 15:39:54 host-131 mate-session[3036]: GLib-GObject-CRITICAL: Custom constructor for class GsmAutostartApp returned NULL (which is invalid). Please use GInitable instead.
Feb 15 15:39:54 host-131 mate-session[3036]: WARNING: could not read /home/test/.config/autostart/mate-keyring-ssh.desktop
Feb 15 15:39:54 host-131 mate-session[3036]: WARNING: Unable to find provider '' of required component 'dock'
Feb 15 15:39:54 host-131 at-spi-bus-launcher[3146]: dbus-daemon[3146]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=500 pid=3036 comm="/usr/bin/mate-session")
Feb 15 15:39:54 host-131 at-spi-bus-launcher[3146]: dbus-daemon[3146]: Successfully activated service 'org.a11y.atspi.Registry'
Feb 15 15:39:54 host-131 at-spi-bus-launcher[3166]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Feb 15 15:39:54 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.12' (uid=500 pid=3164 comm="/usr/libexec/mate-settings-daemon")
Feb 15 15:39:54 host-131 systemd[3019]: Starting Virtual filesystem service - disk device monitor...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 92.
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Feb 15 15:39:55 host-131 systemd[3019]: Started Virtual filesystem service - disk device monitor.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 92.
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.12' (uid=500 pid=3164 comm="/usr/libexec/mate-settings-daemon")
Feb 15 15:39:55 host-131 systemd[3019]: Starting Virtual filesystem service - digital camera monitor...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 109.
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Feb 15 15:39:55 host-131 systemd[3019]: Started Virtual filesystem service - digital camera monitor.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 109.
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.12' (uid=500 pid=3164 comm="/usr/libexec/mate-settings-daemon")
Feb 15 15:39:55 host-131 systemd[3019]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 126.
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating service name='org.gnome.OnlineAccounts' requested by ':1.18' (uid=500 pid=3207 comm="/usr/libexec/gvfs/gvfs-goa-volume-monitor")
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating service name='org.mate.panel.applet.MateMenuAppletFactory' requested by ':1.15' (uid=500 pid=3185 comm="mate-panel")
Feb 15 15:39:55 host-131 gnome-keyring-daemon[3033]: The Secret Service was already initialized
Feb 15 15:39:55 host-131 dbus-daemon[2716]: [system] Activating service name='org.mate.SettingsDaemon.DateTimeMechanism' requested by ':1.70' (uid=500 pid=3185 comm="mate-panel") (using servicehelper)
Feb 15 15:39:55 host-131 systemd[1]: Started PC/SC Smart Card Daemon.
-- Subject: A start job for unit pcscd.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit pcscd.service has finished successfully.
-- 
-- The job identifier is 1445.
Feb 15 15:39:55 host-131 spice-vdagent[3228]: vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 does not exist, exiting
Feb 15 15:39:55 host-131 gnome-keyring-daemon[3033]: The PKCS#11 component was already initialized
Feb 15 15:39:55 host-131 dbus-daemon[2716]: [system] Successfully activated service 'org.mate.SettingsDaemon.DateTimeMechanism'
Feb 15 15:39:55 host-131 avahi-daemon[2713]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fe80::8eec:4bff:fe46:d888.
Feb 15 15:39:55 host-131 avahi-daemon[2713]: New relevant interface enp2s0.IPv6 for mDNS.
Feb 15 15:39:55 host-131 avahi-daemon[2713]: Registering new address record for fe80::8eec:4bff:fe46:d888 on enp2s0.*.
Feb 15 15:39:55 host-131 goa-daemon[3212]: goa-daemon version 3.40.1 starting
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating service name='org.gnome.Identity' requested by ':1.23' (uid=500 pid=3212 comm="/usr/libexec/goa-daemon")
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.gnome.OnlineAccounts'
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Feb 15 15:39:55 host-131 systemd[3019]: Started Virtual filesystem service - GNOME Online Accounts monitor.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 126.
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.gnome.Identity'
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.12' (uid=500 pid=3164 comm="/usr/libexec/mate-settings-daemon")
Feb 15 15:39:55 host-131 goa-identity-se[3280]: GoaKerberosIdentityManager: Using polling for change notification for credential cache type 'KEYRING'
Feb 15 15:39:55 host-131 systemd[3019]: Starting Virtual filesystem service - Apple File Conduit monitor...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 143.
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Feb 15 15:39:55 host-131 systemd[3019]: Started Virtual filesystem service - Apple File Conduit monitor.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 143.
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.12' (uid=500 pid=3164 comm="/usr/libexec/mate-settings-daemon")
Feb 15 15:39:55 host-131 systemd[3019]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 160.
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Feb 15 15:39:55 host-131 systemd[3019]: Started Virtual filesystem service - Media Transfer Protocol monitor.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 160.
Feb 15 15:39:55 host-131 polkitd[2718]: Registered Authentication Agent for unix-session:3 (system bus name :1.80 [/usr/libexec/polkit-mate-authentication-agent-1], object path /org/mate/PolicyKit1/AuthenticationAgent, locale ru_RU.UTF-8)
Feb 15 15:39:55 host-131 NetworkManager[2818]: <info>  [1708000795.4045] dhcp4 (enp2s0): state changed new lease, address=10.88.128.131
Feb 15 15:39:55 host-131 NetworkManager[2818]: <info>  [1708000795.4049] policy: set 'System enp2s0' (enp2s0) as default for IPv4 routing and DNS
Feb 15 15:39:55 host-131 NetworkManager[2818]: <info>  [1708000795.4113] dns-mgr: Writing DNS information to /sbin/resolvconf
Feb 15 15:39:55 host-131 avahi-daemon[2713]: Joining mDNS multicast group on interface enp2s0.IPv4 with address 10.88.128.131.
Feb 15 15:39:55 host-131 avahi-daemon[2713]: New relevant interface enp2s0.IPv4 for mDNS.
Feb 15 15:39:55 host-131 avahi-daemon[2713]: Registering new address record for 10.88.128.131 on enp2s0.IPv4.
Feb 15 15:39:55 host-131 NetworkManager[2818]: <info>  [1708000795.5097] device (enp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Feb 15 15:39:55 host-131 chronyd[2797]: Source 10.88.7.1 online
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.mate.panel.applet.MateMenuAppletFactory'
Feb 15 15:39:55 host-131 dbus-daemon[2716]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.84' (uid=0 pid=3400 comm="/usr/bin/pkcon quit")
Feb 15 15:39:55 host-131 systemd[1]: Starting PackageKit Daemon...
-- Subject: A start job for unit packagekit.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit packagekit.service has begun execution.
-- 
-- The job identifier is 1549.
Feb 15 15:39:55 host-131 PackageKit[3405]: daemon start
Feb 15 15:39:55 host-131 NetworkManager[2818]: <info>  [1708000795.5707] agent-manager: agent[90f8db085f51ac15,:1.82/org.freedesktop.nm-applet/500]: agent registered
Feb 15 15:39:55 host-131 kernel: EXT4-fs (sdb4): warning: mounting unchecked fs, running e2fsck is recommended
Feb 15 15:39:55 host-131 kernel: EXT4-fs (sdb4): mounted filesystem without journal. Quota mode: none.
Feb 15 15:39:55 host-131 udisksd[2727]: Mounted /dev/sdb4 at /run/media/test/alt-live-storage on behalf of uid 500
Feb 15 15:39:55 host-131 org.mate.panel.applet.MateMenuAppletFactory[3214]: /usr/lib/mate-menu/mate-menu.py:564: DeprecationWarning: MatePanelApplet.Applet.set_background_widget is deprecated
Feb 15 15:39:55 host-131 org.mate.panel.applet.MateMenuAppletFactory[3214]:   self.applet.set_background_widget( self.applet )
Feb 15 15:39:55 host-131 dbus-daemon[2716]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb 15 15:39:55 host-131 systemd[1]: Started PackageKit Daemon.
-- Subject: A start job for unit packagekit.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit packagekit.service has finished successfully.
-- 
-- The job identifier is 1549.
Feb 15 15:39:55 host-131 PackageKit[3405]: daemon quit
Feb 15 15:39:55 host-131 NetworkManager[2818]: <info>  [1708000795.6357] device (enp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Feb 15 15:39:55 host-131 NetworkManager[2818]: <info>  [1708000795.6359] device (enp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Feb 15 15:39:55 host-131 NetworkManager[2818]: <info>  [1708000795.6363] manager: NetworkManager state is now CONNECTED_SITE
Feb 15 15:39:55 host-131 systemd[1]: packagekit.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit packagekit.service has successfully entered the 'dead' state.
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating service name='org.freedesktop.Notifications' requested by ':1.26' (uid=500 pid=3250 comm="nm-applet")
Feb 15 15:39:55 host-131 NetworkManager[2818]: <info>  [1708000795.6428] device (enp2s0): Activation: successful, device activated.
Feb 15 15:39:55 host-131 NetworkManager[2818]: <info>  [1708000795.6434] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.41' (uid=500 pid=3241 comm="blueberry-obex-agent                             ")
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.freedesktop.Notifications'
Feb 15 15:39:55 host-131 systemd[3019]: Starting Bluetooth OBEX service...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 184.
Feb 15 15:39:55 host-131 obexd[3455]: OBEX daemon 5.69
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.bluez.obex'
Feb 15 15:39:55 host-131 systemd[3019]: Started Bluetooth OBEX service.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 184.
Feb 15 15:39:55 host-131 systemd[1]: Stopping NTP client/server...
-- Subject: A stop job for unit chronyd.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit chronyd.service has begun execution.
-- 
-- The job identifier is 1667.
Feb 15 15:39:55 host-131 chronyd[2797]: chronyd exiting
Feb 15 15:39:55 host-131 systemd[1]: chronyd.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit chronyd.service has successfully entered the 'dead' state.
Feb 15 15:39:55 host-131 systemd[1]: Stopped NTP client/server.
-- Subject: A stop job for unit chronyd.service has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit chronyd.service has finished.
-- 
-- The job identifier is 1667 and the job result is done.
Feb 15 15:39:55 host-131 systemd[1]: Starting NTP client/server...
-- Subject: A start job for unit chronyd.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit chronyd.service has begun execution.
-- 
-- The job identifier is 1667.
Feb 15 15:39:55 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:39:55 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:39:55 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:39:55 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:39:55 host-131 chronyd[3483]: chronyd version 4.5 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
Feb 15 15:39:55 host-131 chronyd[3483]: Frequency -4.354 +/- 3.516 ppm read from /var/lib/chrony/drift
Feb 15 15:39:55 host-131 systemd[1]: Started NTP client/server.
-- Subject: A start job for unit chronyd.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit chronyd.service has finished successfully.
-- 
-- The job identifier is 1667.
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating service name='org.mate.ScreenSaver' requested by ':1.40' (uid=500 pid=3424 comm="/usr/libexec/mate-notification-daemon")
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.mate.ScreenSaver'
Feb 15 15:39:55 host-131 mate-screensave[3496]: хранитель экрана уже запущен в этом сеансе
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.19' (uid=500 pid=3203 comm="/usr/bin/caja")
Feb 15 15:39:55 host-131 systemd[3019]: Starting Virtual filesystem metadata service...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 201.
Feb 15 15:39:55 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.gtk.vfs.Metadata'
Feb 15 15:39:55 host-131 systemd[3019]: Started Virtual filesystem metadata service.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 201.
Feb 15 15:39:56 host-131 org.mate.panel.applet.MateMenuAppletFactory[3214]: /usr/lib/mate-menu/mate-menu.py:309: DeprecationWarning: Gtk.StyleContext.get_background_color is deprecated
Feb 15 15:39:56 host-131 org.mate.panel.applet.MateMenuAppletFactory[3214]:   bgColor = context.get_background_color( context.get_state() )
Feb 15 15:39:56 host-131 org.mate.panel.applet.MateMenuAppletFactory[3214]: /usr/lib/mate-menu/mate-menu.py:310: DeprecationWarning: Gtk.StyleContext.get_border_color is deprecated
Feb 15 15:39:56 host-131 org.mate.panel.applet.MateMenuAppletFactory[3214]:   borderColor = context.get_border_color( context.get_state() )
Feb 15 15:39:56 host-131 org.mate.panel.applet.MateMenuAppletFactory[3214]: /usr/lib/mate-menu/mate-menu.py:335: DeprecationWarning: Gtk.Widget.override_background_color is deprecated
Feb 15 15:39:56 host-131 org.mate.panel.applet.MateMenuAppletFactory[3214]:   item.override_background_color( context.get_state(), color )
Feb 15 15:39:56 host-131 NetworkManager[2818]: <info>  [1708000796.1511] manager: startup complete
Feb 15 15:39:56 host-131 systemd[1]: Finished Network Manager Wait Online.
-- Subject: A start job for unit NetworkManager-wait-online.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit NetworkManager-wait-online.service has finished successfully.
-- 
-- The job identifier is 115.
Feb 15 15:39:56 host-131 systemd[1]: Reached target Network is Online.
-- Subject: A start job for unit network-online.target has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit network-online.target has finished successfully.
-- 
-- The job identifier is 114.
Feb 15 15:39:56 host-131 systemd[1]: Started Make remote CUPS printers available locally.
-- Subject: A start job for unit cups-browsed.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit cups-browsed.service has finished successfully.
-- 
-- The job identifier is 126.
Feb 15 15:39:56 host-131 systemd[1]: Starting Samba NMB Daemon...
-- Subject: A start job for unit nmb.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit nmb.service has begun execution.
-- 
-- The job identifier is 113.
Feb 15 15:39:56 host-131 nmbd[3514]: [2024/02/15 15:39:56.274845,  0] ../../source3/nmbd/nmbd.c:901(main)
Feb 15 15:39:56 host-131 nmbd[3514]:   nmbd version 4.17.12 started.
Feb 15 15:39:56 host-131 nmbd[3514]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
Feb 15 15:39:56 host-131 systemd[1]: Started Samba NMB Daemon.
-- Subject: A start job for unit nmb.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit nmb.service has finished successfully.
-- 
-- The job identifier is 113.
Feb 15 15:39:56 host-131 systemd[1]: Starting Samba SMB Daemon...
-- Subject: A start job for unit smb.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit smb.service has begun execution.
-- 
-- The job identifier is 125.
Feb 15 15:39:56 host-131 smbd[3517]: [2024/02/15 15:39:56.344715,  0] ../../source3/smbd/server.c:1741(main)
Feb 15 15:39:56 host-131 smbd[3517]:   smbd version 4.17.12 started.
Feb 15 15:39:56 host-131 smbd[3517]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
Feb 15 15:39:56 host-131 nmbd[3514]: [2024/02/15 15:39:56.356735,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Feb 15 15:39:56 host-131 nmbd[3514]:   query_name_response: Multiple (2) responses received for a query on subnet 10.88.128.131 for name SAMBA<1d>.
Feb 15 15:39:56 host-131 nmbd[3514]:   This response was from IP 10.88.128.94, reporting an IP address of 10.88.128.94.
Feb 15 15:39:56 host-131 systemd[1]: Started Samba SMB Daemon.
-- Subject: A start job for unit smb.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit smb.service has finished successfully.
-- 
-- The job identifier is 125.
Feb 15 15:39:56 host-131 systemd[1]: Reached target Multi-User System.
-- Subject: A start job for unit multi-user.target has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit multi-user.target has finished successfully.
-- 
-- The job identifier is 2.
Feb 15 15:39:56 host-131 systemd[1]: Reached target Graphical Interface.
-- Subject: A start job for unit graphical.target has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit graphical.target has finished successfully.
-- 
-- The job identifier is 1.
Feb 15 15:39:56 host-131 systemd[1]: Starting Record Runlevel Change in UTMP...
-- Subject: A start job for unit systemd-update-utmp-runlevel.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit systemd-update-utmp-runlevel.service has begun execution.
-- 
-- The job identifier is 131.
Feb 15 15:39:56 host-131 systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit systemd-update-utmp-runlevel.service has successfully entered the 'dead' state.
Feb 15 15:39:56 host-131 systemd[1]: Finished Record Runlevel Change in UTMP.
-- Subject: A start job for unit systemd-update-utmp-runlevel.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit systemd-update-utmp-runlevel.service has finished successfully.
-- 
-- The job identifier is 131.
Feb 15 15:39:56 host-131 systemd[1]: Startup finished in 10.818s (firmware) + 10.953s (loader) + 6.729s (kernel) + 8.526s (userspace) = 37.027s.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- All system services necessary queued for starting at boot have been
-- started. Note that this does not mean that the machine is now idle as services
-- might still be busy with completing start-up.
-- 
-- Kernel start-up required 6729091 microseconds.
-- 
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- 
-- Userspace start-up required 8526134 microseconds.
Feb 15 15:39:56 host-131 avahi-daemon[2713]: Leaving mDNS multicast group on interface enp2s0.IPv6 with address fe80::8eec:4bff:fe46:d888.
Feb 15 15:39:56 host-131 avahi-daemon[2713]: Joining mDNS multicast group on interface enp2s0.IPv6 with address 2a0c:88c0:2:811:8eec:4bff:fe46:d888.
Feb 15 15:39:56 host-131 avahi-daemon[2713]: Registering new address record for 2a0c:88c0:2:811:8eec:4bff:fe46:d888 on enp2s0.*.
Feb 15 15:39:56 host-131 avahi-daemon[2713]: Withdrawing address record for fe80::8eec:4bff:fe46:d888 on enp2s0.
Feb 15 15:39:58 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:39:58 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:39:58 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:39:58 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:39:58 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:39:58 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:39:58 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:39:58 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:39:59 host-131 systemd[1]: Starting Load/Save RF Kill Switch Status...
-- Subject: A start job for unit systemd-rfkill.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit systemd-rfkill.service has begun execution.
-- 
-- The job identifier is 1772.
Feb 15 15:39:59 host-131 systemd[2944]: Reached target Bluetooth.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 82.
Feb 15 15:39:59 host-131 systemd[3019]: Reached target Bluetooth.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 218.
Feb 15 15:39:59 host-131 systemd[1]: Reached target Bluetooth Support.
-- Subject: A start job for unit bluetooth.target has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit bluetooth.target has finished successfully.
-- 
-- The job identifier is 1780.
Feb 15 15:39:59 host-131 systemd[1]: Started Load/Save RF Kill Switch Status.
-- Subject: A start job for unit systemd-rfkill.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit systemd-rfkill.service has finished successfully.
-- 
-- The job identifier is 1772.
Feb 15 15:39:59 host-131 kernel: Bluetooth: MGMT ver 1.22
Feb 15 15:39:59 host-131 kernel: NET: Registered PF_ALG protocol family
Feb 15 15:39:59 host-131 kernel: Bluetooth: RFCOMM TTY layer initialized
Feb 15 15:39:59 host-131 kernel: Bluetooth: RFCOMM socket layer initialized
Feb 15 15:39:59 host-131 kernel: Bluetooth: RFCOMM ver 1.11
Feb 15 15:39:59 host-131 pulseaudio[3028]: Could not find org.bluez.BatteryProviderManager1.RegisterBatteryProvider(), is bluetoothd started with experimental features enabled (-E flag)?
Feb 15 15:39:59 host-131 bluetoothd[2979]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSink/aptx_hd
Feb 15 15:39:59 host-131 bluetoothd[2979]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSource/aptx_hd
Feb 15 15:39:59 host-131 bluetoothd[2979]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSink/aptx
Feb 15 15:39:59 host-131 bluetoothd[2979]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSource/aptx
Feb 15 15:39:59 host-131 bluetoothd[2979]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSink/sbc
Feb 15 15:39:59 host-131 bluetoothd[2979]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSource/sbc
Feb 15 15:39:59 host-131 bluetoothd[2979]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Feb 15 15:39:59 host-131 bluetoothd[2979]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Feb 15 15:39:59 host-131 bluetoothd[2979]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Feb 15 15:39:59 host-131 bluetoothd[2979]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Feb 15 15:39:59 host-131 bluetoothd[2979]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Feb 15 15:39:59 host-131 bluetoothd[2979]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Feb 15 15:40:00 host-131 chronyd[3483]: Selected source 194.190.168.1 (pool.ntp.org)
Feb 15 15:40:01 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:40:01 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:01 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000081/0000e000
Feb 15 15:40:01 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:01 host-131 kernel: r8169 0000:03:00.0:    [ 7] BadDLLP               
Feb 15 15:40:01 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:01 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:01 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:01 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:03 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:03 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:03 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:03 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:03 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:03 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:03 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:04 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:04 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:04 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:04 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:04 host-131 systemd[1]: Stopping User Manager for UID 487...
-- Subject: A stop job for unit user@487.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit user@487.service has begun execution.
-- 
-- The job identifier is 1885.
Feb 15 15:40:04 host-131 systemd[2944]: Stopped target Bluetooth.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 108 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Stopped target Main User Target.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 106 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Stopping Accessibility services bus...
-- Subject: A stop job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has begun execution.
-- 
-- The job identifier is 90.
Feb 15 15:40:04 host-131 gvfsd[2973]: A connection to the bus can't be made
Feb 15 15:40:04 host-131 systemd[2944]: Stopping D-Bus User Message Bus...
-- Subject: A stop job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has begun execution.
-- 
-- The job identifier is 102.
Feb 15 15:40:04 host-131 systemd[2944]: Stopping Virtual filesystem service...
-- Subject: A stop job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has begun execution.
-- 
-- The job identifier is 88.
Feb 15 15:40:04 host-131 systemd[2944]: Stopped Accessibility services bus.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 90 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Stopped D-Bus User Message Bus.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 102 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Stopped Virtual filesystem service.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 88 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Removed slice User Core Session Slice.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 109 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Stopped target Basic System.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 105 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Stopped target Paths.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 110 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Stopped target Sockets.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 111 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Stopped target Timers.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 104 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Stopped Daily Cleanup of User's Temporary Directories.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 112 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Closed D-Bus User Message Bus Socket.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 101 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Closed GnuPG network certificate management daemon.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 103 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 97 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 98 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Closed GnuPG cryptographic agent (ssh-agent emulation).
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 89 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Closed GnuPG cryptographic agent and passphrase cache.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 91 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Closed Sound System.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 99 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Stopped Create User's Volatile Files and Directories.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 93 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Removed slice User Application Slice.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit UNIT has finished.
-- 
-- The job identifier is 95 and the job result is done.
Feb 15 15:40:04 host-131 systemd[2944]: Reached target Shutdown.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 86.
Feb 15 15:40:04 host-131 systemd[2944]: Finished Exit the Session.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 85.
Feb 15 15:40:04 host-131 systemd[2944]: Reached target Exit the Session.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 84.
Feb 15 15:40:04 host-131 systemd[1]: user@487.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit user@487.service has successfully entered the 'dead' state.
Feb 15 15:40:04 host-131 systemd[1]: Stopped User Manager for UID 487.
-- Subject: A stop job for unit user@487.service has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit user@487.service has finished.
-- 
-- The job identifier is 1885 and the job result is done.
Feb 15 15:40:04 host-131 systemd[1]: Stopping User Runtime Directory /run/user/487...
-- Subject: A stop job for unit user-runtime-dir@487.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit user-runtime-dir@487.service has begun execution.
-- 
-- The job identifier is 1886.
Feb 15 15:40:04 host-131 systemd[1]: run-user-487.mount: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit run-user-487.mount has successfully entered the 'dead' state.
Feb 15 15:40:04 host-131 systemd[1]: user-runtime-dir@487.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit user-runtime-dir@487.service has successfully entered the 'dead' state.
Feb 15 15:40:04 host-131 systemd[1]: Stopped User Runtime Directory /run/user/487.
-- Subject: A stop job for unit user-runtime-dir@487.service has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit user-runtime-dir@487.service has finished.
-- 
-- The job identifier is 1886 and the job result is done.
Feb 15 15:40:04 host-131 systemd[1]: Removed slice User Slice of UID 487.
-- Subject: A stop job for unit user-487.slice has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A stop job for unit user-487.slice has finished.
-- 
-- The job identifier is 1887 and the job result is done.
Feb 15 15:40:04 host-131 systemd[1]: user-487.slice: Consumed 1.473s CPU time.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit user-487.slice completed and consumed the indicated resources.
Feb 15 15:40:04 host-131 systemd[1]: systemd-rfkill.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit systemd-rfkill.service has successfully entered the 'dead' state.
Feb 15 15:40:05 host-131 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.
Feb 15 15:40:07 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:40:07 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Feb 15 15:40:07 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00001001/0000e000
Feb 15 15:40:07 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:07 host-131 kernel: r8169 0000:03:00.0:    [12] Timeout               
Feb 15 15:40:10 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:10 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:10 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:10 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:10 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:10 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:10 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:10 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:13 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:13 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:13 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:13 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:15 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:15 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:15 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:15 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:15 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:15 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:15 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:15 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:16 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:16 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:16 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:16 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:18 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:18 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:18 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:18 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:18 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:40:18 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Feb 15 15:40:18 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00001081/0000e000
Feb 15 15:40:18 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:18 host-131 kernel: r8169 0000:03:00.0:    [ 7] BadDLLP               
Feb 15 15:40:18 host-131 kernel: r8169 0000:03:00.0:    [12] Timeout               
Feb 15 15:40:19 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:19 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:19 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:19 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:21 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:21 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:21 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:21 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:21 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:21 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:21 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:21 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:22 host-131 org.mate.panel.applet.MateMenuAppletFactory[3214]: /usr/lib/mate-menu/mate-menu.py:398: DeprecationWarning: Gtk.Window.set_opacity is deprecated
Feb 15 15:40:22 host-131 org.mate.panel.applet.MateMenuAppletFactory[3214]:   self.window.set_opacity(1.0)
Feb 15 15:40:22 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:22 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:22 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:22 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:24 host-131 org.mate.panel.applet.MateMenuAppletFactory[3593]: ATTENTION: default value of option mesa_glthread overridden by environment.
Feb 15 15:40:24 host-131 org.mate.panel.applet.MateMenuAppletFactory[3593]: ATTENTION: default value of option mesa_glthread overridden by environment.
Feb 15 15:40:24 host-131 org.mate.panel.applet.MateMenuAppletFactory[3593]: ATTENTION: default value of option mesa_glthread overridden by environment.
Feb 15 15:40:24 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:24 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:24 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:24 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:24 host-131 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit systemd-hostnamed.service has successfully entered the 'dead' state.
Feb 15 15:40:32 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:32 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:32 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:32 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:32 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:32 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:32 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:32 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:33 host-131 org.mate.panel.applet.MateMenuAppletFactory[3593]: ATTENTION: default value of option mesa_glthread overridden by environment.
Feb 15 15:40:34 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:34 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:34 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:34 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:35 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:35 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:35 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:35 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:36 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:40:36 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Feb 15 15:40:36 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00001081/0000e000
Feb 15 15:40:36 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:36 host-131 kernel: r8169 0000:03:00.0:    [ 7] BadDLLP               
Feb 15 15:40:36 host-131 kernel: r8169 0000:03:00.0:    [12] Timeout               
Feb 15 15:40:37 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:37 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:37 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:37 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:38 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:38 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:38 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:38 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:40 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:40 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:40 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:40 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:44 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:44 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:44 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:44 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:44 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:44 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:44 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:44 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:48 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:48 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:48 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:48 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:50 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:40:50 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Feb 15 15:40:50 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00001081/0000e000
Feb 15 15:40:50 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:50 host-131 kernel: r8169 0000:03:00.0:    [ 7] BadDLLP               
Feb 15 15:40:50 host-131 kernel: r8169 0000:03:00.0:    [12] Timeout               
Feb 15 15:40:56 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:56 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:56 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:56 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:57 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:57 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:57 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:57 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:40:59 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:40:59 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:40:59 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:40:59 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:01 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Activating service name='org.freedesktop.Notifications' requested by ':1.44' (uid=500 pid=3233 comm="apt-indicator --autostarted")
Feb 15 15:41:01 host-131 dbus-daemon[3030]: [session uid=500 pid=3030] Successfully activated service 'org.freedesktop.Notifications'
Feb 15 15:41:07 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:07 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:07 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:07 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:09 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:09 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:09 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:09 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:09 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:09 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:09 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:09 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:12 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:12 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:12 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:12 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:12 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:12 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:12 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:12 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:13 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:13 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:13 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:13 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:13 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:13 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:13 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:13 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:14 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:14 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:14 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:14 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:15 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:15 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:15 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:15 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:16 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:16 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:16 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:16 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:19 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:41:19 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:19 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:19 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:22 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:22 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:22 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:22 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:24 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:24 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:24 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:24 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:28 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:41:28 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Feb 15 15:41:28 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00001001/0000e000
Feb 15 15:41:28 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:28 host-131 kernel: r8169 0000:03:00.0:    [12] Timeout               
Feb 15 15:41:28 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:28 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:28 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:28 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:29 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:29 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:29 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:29 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:30 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:41:30 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:30 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:30 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:31 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:31 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:31 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:31 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:32 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:32 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:32 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:32 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:36 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:41:36 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:36 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:36 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:36 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:36 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:36 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:36 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:38 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:41:38 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:38 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:38 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:46 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:46 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:46 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:46 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:50 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:50 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:50 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:50 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:52 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:52 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:52 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:52 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:41:59 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:41:59 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:41:59 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:41:59 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:42:02 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:42:02 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:42:02 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:42:02 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:42:03 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:42:03 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:42:03 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:42:03 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:42:05 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:42:05 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:42:05 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:42:05 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:42:11 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:42:11 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:42:11 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:42:11 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:42:15 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:42:15 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:42:15 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:42:15 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:42:15 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:42:15 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:42:15 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:42:15 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:42:24 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:42:24 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:42:24 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:42:24 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:42:25 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:42:25 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:42:25 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:42:25 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:42:28 host-131 su[4237]: pam_tcb(su:auth): Authentication passed for root from test(uid=500)
Feb 15 15:42:28 host-131 su[4237]: pam_tcb(su:session): Session opened for root by test(uid=500)
Feb 15 15:42:32 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:42:32 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:42:32 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:42:32 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:42:37 host-131 systemd[1]: Reloading.
Feb 15 15:42:37 host-131 systemd-sysv-generator[4302]: SysV service '/etc/rc.d/init.d/clock' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Feb 15 15:42:37 host-131 systemd-sysv-generator[4302]: SysV service '/etc/rc.d/init.d/pppoe' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Feb 15 15:42:37 host-131 systemd-sysv-generator[4302]: SysV service '/etc/rc.d/init.d/cryptdisks.functions' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Feb 15 15:42:37 host-131 systemd[1]: /lib/systemd/system/pcscd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/pcscd/pcscd.comm → /run/pcscd/pcscd.comm; please update the unit file accordingly.
Feb 15 15:42:37 host-131 systemd[1]: /lib/systemd/system/cups.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/cups/cups.sock → /run/cups/cups.sock; please update the unit file accordingly.
Feb 15 15:42:37 host-131 systemd[1]: Reloading.
Feb 15 15:42:37 host-131 systemd-sysv-generator[4318]: SysV service '/etc/rc.d/init.d/clock' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Feb 15 15:42:37 host-131 systemd-sysv-generator[4318]: SysV service '/etc/rc.d/init.d/pppoe' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Feb 15 15:42:37 host-131 systemd-sysv-generator[4318]: SysV service '/etc/rc.d/init.d/cryptdisks.functions' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Feb 15 15:42:37 host-131 systemd[1]: /lib/systemd/system/pcscd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/pcscd/pcscd.comm → /run/pcscd/pcscd.comm; please update the unit file accordingly.
Feb 15 15:42:37 host-131 systemd[1]: /lib/systemd/system/cups.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/cups/cups.sock → /run/cups/cups.sock; please update the unit file accordingly.
Feb 15 15:42:37 host-131 systemd[1]: Starting OpenSSH server daemon...
-- Subject: A start job for unit sshd.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit sshd.service has begun execution.
-- 
-- The job identifier is 2096.
Feb 15 15:42:37 host-131 systemd[1]: Started OpenSSH server daemon.
-- Subject: A start job for unit sshd.service has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit sshd.service has finished successfully.
-- 
-- The job identifier is 2096.
Feb 15 15:42:37 host-131 sshd[4325]: Server listening on 0.0.0.0 port 22.
Feb 15 15:42:37 host-131 sshd[4325]: Server listening on :: port 22.
Feb 15 15:42:47 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:42:47 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:42:47 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:42:47 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:42:48 host-131 sshd[4327]: pam_tcb(sshd:auth): Authentication failed for test from (uid=0)
Feb 15 15:42:49 host-131 sshd[4327]: Failed password for test from 10.88.144.188 port 57954 ssh2
Feb 15 15:42:50 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:42:50 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:42:50 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:42:50 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:42:51 host-131 sshd[4327]: pam_tcb(sshd:auth): Authentication failed for test from (uid=0)
Feb 15 15:42:51 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:42:51 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:42:51 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:42:51 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:42:53 host-131 sshd[4327]: Failed password for test from 10.88.144.188 port 57954 ssh2
Feb 15 15:42:59 host-131 sshd[4327]: pam_tcb(sshd:auth): Authentication passed for test from (uid=0)
Feb 15 15:42:59 host-131 sshd[4327]: Accepted password for test from 10.88.144.188 port 57954 ssh2
Feb 15 15:42:59 host-131 sshd[4327]: pam_tcb(sshd:session): Session opened for test by (uid=0)
Feb 15 15:42:59 host-131 systemd-logind[2726]: New session 5 of user test.
-- Subject: A new session 5 has been created for user test
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: sd-login(3)
-- 
-- A new session with the ID 5 has been created for the user test.
-- 
-- The leading process of the session is 4327.
Feb 15 15:42:59 host-131 systemd[1]: Started Session 5 of User test.
-- Subject: A start job for unit session-5.scope has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit session-5.scope has finished successfully.
-- 
-- The job identifier is 2199.
Feb 15 15:43:02 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:43:02 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:43:02 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:43:02 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:43:03 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:43:03 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:43:03 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:43:03 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:43:10 host-131 sshd[4375]: pam_tcb(sshd:auth): Authentication passed for test from (uid=0)
Feb 15 15:43:10 host-131 sshd[4375]: Accepted password for test from 10.88.144.188 port 43216 ssh2
Feb 15 15:43:10 host-131 sshd[4375]: pam_tcb(sshd:session): Session opened for test by (uid=0)
Feb 15 15:43:10 host-131 systemd-logind[2726]: New session 6 of user test.
-- Subject: A new session 6 has been created for user test
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: sd-login(3)
-- 
-- A new session with the ID 6 has been created for the user test.
-- 
-- The leading process of the session is 4375.
Feb 15 15:43:10 host-131 systemd[1]: Started Session 6 of User test.
-- Subject: A start job for unit session-6.scope has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit session-6.scope has finished successfully.
-- 
-- The job identifier is 2306.
Feb 15 15:43:13 host-131 su[4418]: pam_tcb(su:auth): Authentication passed for root from test(uid=500)
Feb 15 15:43:13 host-131 su[4418]: pam_tcb(su:session): Session opened for root by test(uid=500)
Feb 15 15:43:16 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:43:16 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:43:16 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:43:16 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:43:25 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:43:25 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:43:25 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:43:25 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:43:28 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:43:28 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:43:28 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:43:28 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:43:33 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:43:33 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Feb 15 15:43:33 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00001001/0000e000
Feb 15 15:43:33 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:43:33 host-131 kernel: r8169 0000:03:00.0:    [12] Timeout               
Feb 15 15:43:36 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:43:36 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:43:36 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:43:36 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:43:39 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:43:39 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:43:39 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:43:39 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:43:47 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:43:47 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:43:47 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:43:47 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:43:51 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:43:51 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:43:51 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:43:51 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:43:54 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:43:54 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:43:54 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:43:54 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:43:56 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:43:56 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:43:56 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:43:56 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:43:57 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:43:57 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:43:57 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:43:57 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:44:01 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:44:01 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:44:01 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:44:01 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:44:07 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:44:07 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:44:07 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:44:07 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:44:09 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:44:09 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:44:09 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:44:09 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:44:24 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:44:24 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:44:24 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:44:24 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:44:26 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:44:26 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:44:26 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:44:26 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:44:36 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:44:36 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:44:36 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:44:36 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:44:36 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:44:36 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:44:36 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:44:36 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:44:40 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:44:40 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:44:40 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:44:40 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:44:47 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:44:47 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:44:47 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:44:47 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:44:49 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:44:49 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:44:49 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:44:49 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:11 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:11 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:11 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:11 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:14 host-131 systemd[3019]: Created slice User Background Tasks Slice.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 221.
Feb 15 15:45:14 host-131 systemd[3019]: Starting Cleanup of User's Temporary Files and Directories...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has begun execution.
-- 
-- The job identifier is 220.
Feb 15 15:45:14 host-131 systemd[3019]: Finished Cleanup of User's Temporary Files and Directories.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit UNIT has finished successfully.
-- 
-- The job identifier is 220.
Feb 15 15:45:15 host-131 nmbd[3514]: [2024/02/15 15:45:15.164687,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Feb 15 15:45:15 host-131 nmbd[3514]:   query_name_response: Multiple (2) responses received for a query on subnet 10.88.128.131 for name SAMBA<1d>.
Feb 15 15:45:15 host-131 nmbd[3514]:   This response was from IP 10.88.128.94, reporting an IP address of 10.88.128.94.
Feb 15 15:45:15 host-131 nmbd[3514]: [2024/02/15 15:45:15.164945,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Feb 15 15:45:15 host-131 nmbd[3514]:   query_name_response: Multiple (3) responses received for a query on subnet 10.88.128.131 for name SAMBA<1d>.
Feb 15 15:45:15 host-131 nmbd[3514]:   This response was from IP 10.88.128.94, reporting an IP address of 10.88.128.94.
Feb 15 15:45:15 host-131 nmbd[3514]: [2024/02/15 15:45:15.165111,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Feb 15 15:45:15 host-131 nmbd[3514]:   query_name_response: Multiple (4) responses received for a query on subnet 10.88.128.131 for name SAMBA<1d>.
Feb 15 15:45:15 host-131 nmbd[3514]:   This response was from IP 10.88.128.94, reporting an IP address of 10.88.128.94.
Feb 15 15:45:15 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:15 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:15 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:15 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:20 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:20 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:20 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:20 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:22 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:45:22 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Feb 15 15:45:22 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00001001/0000e000
Feb 15 15:45:22 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:22 host-131 kernel: r8169 0000:03:00.0:    [12] Timeout               
Feb 15 15:45:22 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:22 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:22 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:22 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:23 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:23 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:23 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:23 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:24 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:24 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:24 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:24 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:27 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:27 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:27 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:27 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:30 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:30 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:30 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:30 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:31 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:31 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:31 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:31 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:35 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:35 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:35 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:35 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:36 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:45:36 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:36 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:36 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:36 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:45:36 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Feb 15 15:45:36 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00001001/0000e000
Feb 15 15:45:36 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:36 host-131 kernel: r8169 0000:03:00.0:    [12] Timeout               
Feb 15 15:45:36 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:36 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:36 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:36 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:44 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:45:44 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Feb 15 15:45:44 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00001001/0000e000
Feb 15 15:45:44 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:44 host-131 kernel: r8169 0000:03:00.0:    [12] Timeout               
Feb 15 15:45:45 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:45 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:45 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:45 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:47 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:47 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:47 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:47 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:49 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:49 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:49 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:49 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:45:51 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:45:51 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:45:51 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:45:51 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:05 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:05 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:05 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:05 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:07 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:07 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:07 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:07 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:11 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:11 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:11 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:11 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:12 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:46:12 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:12 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:12 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:14 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:14 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:14 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:14 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:18 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:18 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:18 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:18 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:19 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:19 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:19 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:19 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:21 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:21 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:21 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:21 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:22 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:22 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:22 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:22 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:22 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:22 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:22 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:22 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:23 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:23 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:23 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:23 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:27 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:27 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:27 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:27 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:27 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:46:27 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:27 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:27 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:28 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:28 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:28 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:28 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:28 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:28 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:28 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:28 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:28 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:28 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:28 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:28 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:32 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:46:32 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Feb 15 15:46:32 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00001001/0000e000
Feb 15 15:46:32 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:32 host-131 kernel: r8169 0000:03:00.0:    [12] Timeout               
Feb 15 15:46:33 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:33 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:33 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:33 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:33 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:33 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:33 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:33 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:34 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:34 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:34 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:34 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:34 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:46:34 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Feb 15 15:46:34 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00001081/0000e000
Feb 15 15:46:34 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:34 host-131 kernel: r8169 0000:03:00.0:    [ 7] BadDLLP               
Feb 15 15:46:34 host-131 kernel: r8169 0000:03:00.0:    [12] Timeout               
Feb 15 15:46:34 host-131 kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:03:00.0
Feb 15 15:46:34 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Feb 15 15:46:34 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00001001/0000e000
Feb 15 15:46:34 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:34 host-131 kernel: r8169 0000:03:00.0:    [12] Timeout               
Feb 15 15:46:35 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:35 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:35 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:35 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:42 host-131 NetworkManager[2818]: <info>  [1708001202.1501] device (wlp4s0): set-hw-addr: set MAC address to 46:35:73:40:DD:CA (scanning)
Feb 15 15:46:42 host-131 NetworkManager[2818]: <info>  [1708001202.1639] device (wlp4s0): supplicant interface state: disconnected -> interface_disabled
Feb 15 15:46:42 host-131 NetworkManager[2818]: <info>  [1708001202.1640] device (p2p-dev-wlp4s0): supplicant management interface state: disconnected -> interface_disabled
Feb 15 15:46:42 host-131 NetworkManager[2818]: <info>  [1708001202.1704] device (wlp4s0): supplicant interface state: interface_disabled -> inactive
Feb 15 15:46:42 host-131 NetworkManager[2818]: <info>  [1708001202.1705] device (p2p-dev-wlp4s0): supplicant management interface state: interface_disabled -> inactive
Feb 15 15:46:44 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:44 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:44 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:44 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:47 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:47 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:47 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:47 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:47 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:47 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:47 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:47 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:54 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:54 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:54 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:54 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:55 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:55 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:55 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:55 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:55 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:55 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:55 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:55 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:46:56 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:46:56 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:46:56 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:46:56 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:47:01 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:47:01 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:47:01 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:47:01 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:47:02 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:47:02 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:47:02 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:47:02 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:47:03 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:47:03 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:47:03 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:47:03 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:47:09 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:47:09 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:47:09 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:47:09 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:47:10 host-131 su[4541]: pam_tcb(su:auth): Authentication passed for root from test(uid=500)
Feb 15 15:47:10 host-131 su[4541]: pam_tcb(su:session): Session opened for root by test(uid=500)
Feb 15 15:47:12 host-131 apt-get[4540]: python-modules-json-2.7.18-alt10 p10+309289.100.3.1 1668015444 installed
Feb 15 15:47:12 host-131 apt-get[4540]: python-modules-distutils-2.7.18-alt10 p10+309289.100.3.1 1668015444 installed
Feb 15 15:47:12 host-131 apt-get[4540]: python-module-six-1.15.0-alt2 sisyphus+270533.5100.6.1 1619685463 installed
Feb 15 15:47:12 host-131 apt-get[4540]: python-module-libxml2-1:2.9.12-alt1.p10.1 p10+314068.100.3.1 1675354348 installed
Feb 15 15:47:13 host-131 apt-get[4540]: sos-3.5-alt9.1 sisyphus+277446.100.1.1 1625565385 installed
Feb 15 15:47:13 host-131 apt-get[4540]: lsscsi-0.32-alt1 sisyphus+279452.100.1.1 1626546413 installed
Feb 15 15:47:13 host-131 apt-get[4540]: acpica-20201113-alt1 sisyphus+278518.100.1.1 1626108552 installed
Feb 15 15:47:14 host-131 systemd[1]: Reloading.
Feb 15 15:47:14 host-131 systemd-sysv-generator[4794]: SysV service '/etc/rc.d/init.d/clock' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Feb 15 15:47:14 host-131 systemd-sysv-generator[4794]: SysV service '/etc/rc.d/init.d/pppoe' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Feb 15 15:47:14 host-131 systemd-sysv-generator[4794]: SysV service '/etc/rc.d/init.d/cryptdisks.functions' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
Feb 15 15:47:14 host-131 systemd[1]: /lib/systemd/system/pcscd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/pcscd/pcscd.comm → /run/pcscd/pcscd.comm; please update the unit file accordingly.
Feb 15 15:47:14 host-131 systemd[1]: /lib/systemd/system/cups.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/cups/cups.sock → /run/cups/cups.sock; please update the unit file accordingly.
Feb 15 15:47:14 host-131 systemd[1]: Queuing reload/restart jobs for marked units…
Feb 15 15:47:15 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:47:15 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:47:15 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:47:15 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:47:19 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:47:19 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:47:19 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:47:19 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:47:19 host-131 kernel: r8169 0000:03:00.0: invalid VPD tag 0xff (size 0) at offset 0; assume missing optional EEPROM
Feb 15 15:47:20 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:47:20 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:47:20 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:47:20 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:47:25 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:47:25 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:47:25 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:47:25 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
Feb 15 15:47:28 host-131 systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 6819 (df)
Feb 15 15:47:28 host-131 systemd[1]: Mounting Arbitrary Executable File Formats File System...
-- Subject: A start job for unit proc-sys-fs-binfmt_misc.mount has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit proc-sys-fs-binfmt_misc.mount has begun execution.
-- 
-- The job identifier is 2517.
Feb 15 15:47:28 host-131 systemd[1]: Mounted Arbitrary Executable File Formats File System.
-- Subject: A start job for unit proc-sys-fs-binfmt_misc.mount has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit proc-sys-fs-binfmt_misc.mount has finished successfully.
-- 
-- The job identifier is 2517.
Feb 15 15:47:29 host-131 kernel: WARNING! power/level is deprecated; use power/control instead
Feb 15 15:47:31 host-131 crontab[6922]: (root) LIST (root)
Feb 15 15:47:31 host-131 kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:03:00.0
Feb 15 15:47:31 host-131 kernel: r8169 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Feb 15 15:47:31 host-131 kernel: r8169 0000:03:00.0:   device [10ec:8125] error status/mask=00000001/0000e000
Feb 15 15:47:31 host-131 kernel: r8169 0000:03:00.0:    [ 0] RxErr                 
