● np0000001290 State: degraded Units: 470 loaded (incl. loaded aliases) Jobs: 0 queued Failed: 6 units Since: Fri 2026-05-22 15:45:37 UTC; 46min ago systemd: 255.4-1ubuntu8.12 Tainted: cgroupsv1 CGroup: / ├─init.scope │ └─1 /sbin/init nofb ├─storpool.slice │ └─storpool-common.slice │ ├─storpool_beacon.service │ │ ├─ 7970 /usr/bin/perl /usr/sbin/storpool_beacon -- │ │ └─19896 /usr/sbin/storpool_beacon.bin -l -p /run/storpool_beacon.bin.pid "" -n 1 -t 60 -a b2p2.b -e 2 -W 6 │ ├─storpool_block.service │ │ ├─ 7971 /usr/bin/perl /usr/sbin/storpool_block -- │ │ └─19881 /usr/sbin/storpool_block.bin -l -p /run/storpool_block.bin.pid -b 0 -i 1 -a b2p2.b -N -W 6 │ ├─storpool_nvmed.service │ │ ├─7926 /usr/bin/perl /usr/sbin/storpool_nvmed │ │ └─7948 /usr/sbin/storpool_nvmed.bin -l -p /run/storpool_nvmed.bin.pid -W 6 │ └─storpool_server.service │ ├─ 7993 /usr/bin/perl /usr/sbin/storpool_server -- │ └─19873 /usr/sbin/storpool_server.bin -l -p /run/storpool_server.bin.pid -b 0 -C 512 -N -i 1 -a b2p2.b -W 6 ├─system.slice │ ├─ModemManager.service │ │ └─5010 /usr/sbin/ModemManager │ ├─chrony.service │ │ ├─4986 /usr/sbin/chronyd -F 1 │ │ └─4996 /usr/sbin/chronyd -F 1 │ ├─cron.service │ │ └─4930 /usr/sbin/cron -f -P │ ├─dbus.service │ │ └─4868 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only │ ├─lldpd.service │ │ ├─4872 "lldpd: monitor. " │ │ └─4891 "lldpd: connected to a9." │ ├─multipathd.service │ │ └─7266 /sbin/multipathd -d -s │ ├─networkd-dispatcher.service │ │ └─4874 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers │ ├─polkit.service │ │ └─4877 /usr/lib/polkit-1/polkitd --no-debug │ ├─rsyslog.service │ │ └─4966 /usr/sbin/rsyslogd -n -iNONE │ ├─ssh.service │ │ └─5168 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups" │ ├─storpool_controller.service │ │ ├─7972 /usr/bin/perl /usr/sbin/storpool_controller │ │ └─8089 /usr/sbin/storpool_controller.bin -l -p /run/storpool_controller.bin.pid -i 1 -A 192.168.10.5 -W 6 │ ├─storpool_dre.service │ │ └─19827 /opt/storpool/python3/bin/python3 /usr/lib/storpool/storpool_dre │ ├─storpool_qos.service │ │ └─7992 /opt/storpool/python3/bin/python3 /usr/lib/storpool/storpool_qos daemon │ ├─storpool_volumecare.service │ │ └─20317 /opt/storpool/python3/bin/python3 /usr/lib/storpool/storpool_volumecare.py │ ├─system-getty.slice │ │ └─getty@tty1.service │ │ └─5000 /sbin/agetty -o "-p -- \\u" --noclear - linux │ ├─system-serial\x2dgetty.slice │ │ └─serial-getty@ttyS0.service │ │ └─4972 /sbin/agetty -o "-p -- \\u" --keep-baud 115200,57600,38400,9600 - vt220 │ ├─systemd-journald.service │ │ └─497 /usr/lib/systemd/systemd-journald │ ├─systemd-logind.service │ │ └─4889 /usr/lib/systemd/systemd-logind │ ├─systemd-networkd.service │ │ └─1179 /usr/lib/systemd/systemd-networkd │ ├─systemd-resolved.service │ │ └─1138 /usr/lib/systemd/systemd-resolved │ ├─systemd-udevd.service │ │ └─udev │ │ └─590 /usr/lib/systemd/systemd-udevd │ ├─udisks2.service │ │ └─4892 /usr/libexec/udisks2/udisksd │ └─unbound.service │ └─4951 /usr/sbin/unbound -d -p └─user.slice └─user-1000.slice ├─session-5.scope │ └─8569 /usr/bin/python3 ├─session-67.scope │ ├─20085 "sshd: ubuntu [priv]" │ ├─20144 "sshd: ubuntu@notty" │ ├─20659 /bin/sh -c "sudo -H -S -n -u root /bin/sh -c 'echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3' && sleep 0" │ ├─20660 sudo -H -S -n -u root /bin/sh -c "echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3" │ ├─20661 /bin/sh -c "echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3" │ ├─20662 /usr/bin/python3 │ ├─20665 /bin/bash -c "sudo iptables-save > /home/ubuntu/iptables.txt\n\n# NOTE(sfernand): Run 'df' with a 60s timeout to prevent hangs from\n# stale NFS mounts.\ntimeout -s 9 60s df -h > /home/ubuntu/df.txt || true\n# If 'df' times out, the mount output helps debug which NFS share\n# is unresponsive.\nmount > /home/ubuntu/mount.txt\n\nfor py_ver in 2 3; do\n if [[ \`which python\${py_ver}\` ]]; then\n python\${py_ver} -m pip freeze > /home/ubuntu/pip\${py_ver}-freeze.txt\n fi\ndone\n\nif [ \`command -v dpkg\` ]; then\n dpkg -l> /home/ubuntu/dpkg-l.txt\nfi\nif [ \`command -v rpm\` ]; then\n rpm -qa | sort > /home/ubuntu/rpm-qa.txt\nfi\n\n# Services status\nsudo systemctl status --all > services.txt 2>/dev/null\n\n# NOTE(kchamart) The 'audit.log' can be useful in cases when QEMU\n# failed to start due to denials from SELinux — useful for CentOS\n# and Fedora machines. For Ubuntu (which runs AppArmor), DevStack\n# already captures the contents of /var/log/kern.log (via\n# \`journalctl -t kernel\` redirected into syslog.txt.gz), which\n# contains AppArmor-related messages.\nif [ -f /var/log/audit/audit.log ] ; then\n sudo cp /var/log/audit/audit.log /home/ubuntu/audit.log &&\n chmod +r /home/ubuntu/audit.log;\nfi\n\n# gzip and save any coredumps in /var/core\nif [ -d /var/core ]; then\n sudo gzip -r /var/core\n sudo cp -r /var/core /home/ubuntu/\nfi\n\nsudo ss -lntup | grep ':53' > /home/ubuntu/listen53.txt\n\n# NOTE(andreaf) Service logs are already in logs/ thanks for the\n# export-devstack-journal log. Apache logs are under apache/ thans to the\n# apache-logs-conf role.\ngrep -i deprecat /home/ubuntu/logs/*.txt /home/ubuntu/apache/*.log | \\\n sed -r 's/[0-9]{1,2}\\:[0-9]{1,2}\\:[0-9]{1,2}\\.[0-9]{1,3}/ /g' | \\\n sed -r 's/[0-9]{1,2}\\:[0-9]{1,2}\\:[0-9]{1,2}/ /g' | \\\n sed -r 's/[0-9]{1,4}-[0-9]{1,2}-[0-9]{1,4}/ /g' |\n sed -r 's/\\[.*\\]/ /g' | \\\n sed -r 's/\\s[0-9]+\\s/ /g' | \\\n awk '{if (\$0 in seen) {seen[\$0]++} else {out[++n]=\$0;seen[\$0]=1}} END { for (i=1; i<=n; i++) print seen[out[i]]\" :: \" out[i] }' > /home/ubuntu/deprecations.log\n" │ ├─20678 sudo systemctl status --all │ └─20679 systemctl status --all └─user@1000.service └─init.scope ├─5176 /usr/lib/systemd/systemd --user └─5177 "(sd-pam)" ● proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point Loaded: loaded (/usr/lib/systemd/system/proc-sys-fs-binfmt_misc.automount; static) Active: active (running) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● proc-sys-fs-binfmt_misc.mount Where: /proc/sys/fs/binfmt_misc Docs: https://docs.kernel.org/admin-guide/binfmt-misc.html https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems May 22 15:45:38 np0000001290 systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 1018 (systemd-binfmt) Notice: journal has been rotated since unit was started, output may be incomplete. ● dev-disk-by\x2ddiskseq-9.device - QEMU_HARDDISK Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda ● dev-disk-by\x2ddiskseq-9\x2dpart1.device - QEMU_HARDDISK cloudimg-rootfs Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda1.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda1 ● dev-disk-by\x2ddiskseq-9\x2dpart14.device - QEMU_HARDDISK 14 Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda14.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda14 ● dev-disk-by\x2ddiskseq-9\x2dpart15.device - QEMU_HARDDISK UEFI Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda15.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda15 ● dev-disk-by\x2ddiskseq-9\x2dpart16.device - QEMU_HARDDISK BOOT Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda16.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda16 ● dev-disk-by\x2did-scsi\x2d0QEMU_QEMU_HARDDISK_bbfb5b77\x2d3101\x2d4f18\x2da298\x2dba3857e210e0.device - QEMU_HARDDISK Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda ● dev-disk-by\x2did-scsi\x2d0QEMU_QEMU_HARDDISK_bbfb5b77\x2d3101\x2d4f18\x2da298\x2dba3857e210e0\x2dpart1.device - QEMU_HARDDISK cloudimg-rootfs Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda1.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda1 ● dev-disk-by\x2did-scsi\x2d0QEMU_QEMU_HARDDISK_bbfb5b77\x2d3101\x2d4f18\x2da298\x2dba3857e210e0\x2dpart14.device - QEMU_HARDDISK 14 Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda14.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda14 ● dev-disk-by\x2did-scsi\x2d0QEMU_QEMU_HARDDISK_bbfb5b77\x2d3101\x2d4f18\x2da298\x2dba3857e210e0\x2dpart15.device - QEMU_HARDDISK UEFI Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda15.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda15 ● dev-disk-by\x2did-scsi\x2d0QEMU_QEMU_HARDDISK_bbfb5b77\x2d3101\x2d4f18\x2da298\x2dba3857e210e0\x2dpart16.device - QEMU_HARDDISK BOOT Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda16.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda16 ● dev-disk-by\x2did-scsi\x2dSQEMU_QEMU_HARDDISK_bbfb5b77\x2d3101\x2d4f18\x2da298\x2dba3857e210e0.device - QEMU_HARDDISK Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda ● dev-disk-by\x2did-scsi\x2dSQEMU_QEMU_HARDDISK_bbfb5b77\x2d3101\x2d4f18\x2da298\x2dba3857e210e0\x2dpart1.device - QEMU_HARDDISK cloudimg-rootfs Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda1.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda1 ● dev-disk-by\x2did-scsi\x2dSQEMU_QEMU_HARDDISK_bbfb5b77\x2d3101\x2d4f18\x2da298\x2dba3857e210e0\x2dpart14.device - QEMU_HARDDISK 14 Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda14.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda14 ● dev-disk-by\x2did-scsi\x2dSQEMU_QEMU_HARDDISK_bbfb5b77\x2d3101\x2d4f18\x2da298\x2dba3857e210e0\x2dpart15.device - QEMU_HARDDISK UEFI Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda15.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda15 ● dev-disk-by\x2did-scsi\x2dSQEMU_QEMU_HARDDISK_bbfb5b77\x2d3101\x2d4f18\x2da298\x2dba3857e210e0\x2dpart16.device - QEMU_HARDDISK BOOT Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda16.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda16 ● dev-disk-by\x2dlabel-BOOT.device - QEMU_HARDDISK BOOT Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda16.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda16 May 22 15:45:38 np0000001290 systemd[1]: Found device dev-disk-by\x2dlabel-BOOT.device - QEMU_HARDDISK BOOT. ● dev-disk-by\x2dlabel-cloudimg\x2drootfs.device - QEMU_HARDDISK cloudimg-rootfs Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda1.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda1 ● dev-disk-by\x2dlabel-UEFI.device - QEMU_HARDDISK UEFI Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda15.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda15 May 22 15:45:38 np0000001290 systemd[1]: Found device dev-disk-by\x2dlabel-UEFI.device - QEMU_HARDDISK UEFI. ● dev-disk-by\x2dpartuuid-775e35ef\x2dc5e8\x2d42f0\x2da45c\x2d0ac96fbb60eb.device - QEMU_HARDDISK BOOT Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda16.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda16 ● dev-disk-by\x2dpartuuid-bc80cedc\x2dee0a\x2d454b\x2d96a5\x2d96563be416ef.device - QEMU_HARDDISK cloudimg-rootfs Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda1.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda1 ● dev-disk-by\x2dpartuuid-f33258b5\x2dbaae\x2d49d3\x2d88e1\x2d279aadc1f928.device - QEMU_HARDDISK 14 Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda14.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda14 ● dev-disk-by\x2dpartuuid-f772fa57\x2df630\x2d48aa\x2db7c5\x2dfaddedc383f3.device - QEMU_HARDDISK UEFI Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda15.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda15 ● dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dscsi\x2d0:0:0:0.device - QEMU_HARDDISK Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda ● dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dscsi\x2d0:0:0:0\x2dpart1.device - QEMU_HARDDISK cloudimg-rootfs Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda1.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda1 ● dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dscsi\x2d0:0:0:0\x2dpart14.device - QEMU_HARDDISK 14 Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda14.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda14 ● dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dscsi\x2d0:0:0:0\x2dpart15.device - QEMU_HARDDISK UEFI Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda15.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda15 ● dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dscsi\x2d0:0:0:0\x2dpart16.device - QEMU_HARDDISK BOOT Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda16.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda16 ● dev-disk-by\x2duuid-7dc15ce9\x2dd090\x2d44d7\x2dbb05\x2d2a36d545a8e3.device - QEMU_HARDDISK BOOT Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda16.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda16 ● dev-disk-by\x2duuid-8515de1c\x2dba7e\x2d467b\x2dadde\x2d6d9f8a8dbc1f.device - QEMU_HARDDISK cloudimg-rootfs Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda1.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda1 ● dev-disk-by\x2duuid-9FE0\x2dDE2B.device - QEMU_HARDDISK UEFI Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda15.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda15 ● dev-rfkill.device - /dev/rfkill Follows: unit currently follows state of sys-devices-virtual-misc-rfkill.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/virtual/misc/rfkill ● dev-sda.device - QEMU_HARDDISK Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda ● dev-sda1.device - QEMU_HARDDISK cloudimg-rootfs Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda1.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda1 Notice: journal has been rotated since unit was started, output may be incomplete. ● dev-sda14.device - QEMU_HARDDISK 14 Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda14.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda14 ● dev-sda15.device - QEMU_HARDDISK UEFI Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda15.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda15 ● dev-sda16.device - QEMU_HARDDISK BOOT Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda16.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda16 ● dev-ttyprintk.device - /dev/ttyprintk Follows: unit currently follows state of sys-devices-virtual-tty-ttyprintk.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/virtual/tty/ttyprintk ● dev-ttyS0.device - /dev/ttyS0 Follows: unit currently follows state of sys-devices-pnp0-00:00-00:00:0-00:00:0.0-tty-ttyS0.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pnp0/00:00/00:00:0/00:00:0.0/tty/ttyS0 May 22 15:45:38 np0000001290 systemd[1]: Found device dev-ttyS0.device - /dev/ttyS0. ● dev-ttyS1.device - /dev/ttyS1 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.1/tty/ttyS1 ● dev-ttyS10.device - /dev/ttyS10 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.10-tty-ttyS10.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.10/tty/ttyS10 ● dev-ttyS11.device - /dev/ttyS11 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.11-tty-ttyS11.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.11/tty/ttyS11 ● dev-ttyS12.device - /dev/ttyS12 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.12-tty-ttyS12.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.12/tty/ttyS12 ● dev-ttyS13.device - /dev/ttyS13 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.13-tty-ttyS13.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.13/tty/ttyS13 ● dev-ttyS14.device - /dev/ttyS14 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.14-tty-ttyS14.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.14/tty/ttyS14 ● dev-ttyS15.device - /dev/ttyS15 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.15-tty-ttyS15.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.15/tty/ttyS15 ● dev-ttyS16.device - /dev/ttyS16 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.16-tty-ttyS16.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.16/tty/ttyS16 ● dev-ttyS17.device - /dev/ttyS17 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.17-tty-ttyS17.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.17/tty/ttyS17 ● dev-ttyS18.device - /dev/ttyS18 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.18-tty-ttyS18.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.18/tty/ttyS18 ● dev-ttyS19.device - /dev/ttyS19 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.19-tty-ttyS19.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.19/tty/ttyS19 ● dev-ttyS2.device - /dev/ttyS2 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.2/tty/ttyS2 ● dev-ttyS20.device - /dev/ttyS20 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.20-tty-ttyS20.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.20/tty/ttyS20 ● dev-ttyS21.device - /dev/ttyS21 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.21-tty-ttyS21.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.21/tty/ttyS21 ● dev-ttyS22.device - /dev/ttyS22 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.22-tty-ttyS22.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.22/tty/ttyS22 ● dev-ttyS23.device - /dev/ttyS23 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.23-tty-ttyS23.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.23/tty/ttyS23 ● dev-ttyS24.device - /dev/ttyS24 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.24-tty-ttyS24.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.24/tty/ttyS24 ● dev-ttyS25.device - /dev/ttyS25 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.25-tty-ttyS25.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.25/tty/ttyS25 ● dev-ttyS26.device - /dev/ttyS26 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.26-tty-ttyS26.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.26/tty/ttyS26 ● dev-ttyS27.device - /dev/ttyS27 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.27-tty-ttyS27.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.27/tty/ttyS27 ● dev-ttyS28.device - /dev/ttyS28 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.28-tty-ttyS28.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.28/tty/ttyS28 ● dev-ttyS29.device - /dev/ttyS29 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.29-tty-ttyS29.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.29/tty/ttyS29 ● dev-ttyS3.device - /dev/ttyS3 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.3/tty/ttyS3 ● dev-ttyS30.device - /dev/ttyS30 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.30-tty-ttyS30.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.30/tty/ttyS30 ● dev-ttyS31.device - /dev/ttyS31 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.31-tty-ttyS31.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.31/tty/ttyS31 ● dev-ttyS4.device - /dev/ttyS4 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.4-tty-ttyS4.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.4/tty/ttyS4 ● dev-ttyS5.device - /dev/ttyS5 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.5-tty-ttyS5.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.5/tty/ttyS5 ● dev-ttyS6.device - /dev/ttyS6 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.6-tty-ttyS6.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.6/tty/ttyS6 ● dev-ttyS7.device - /dev/ttyS7 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.7-tty-ttyS7.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.7/tty/ttyS7 ● dev-ttyS8.device - /dev/ttyS8 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.8-tty-ttyS8.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.8/tty/ttyS8 ● dev-ttyS9.device - /dev/ttyS9 Follows: unit currently follows state of sys-devices-platform-serial8250-serial8250:0-serial8250:0.9-tty-ttyS9.device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.9/tty/ttyS9 ● sys-devices-pci0000:00-0000:00:02.1-0000:03:00.0-virtio1-net-enp3s0.device - Virtio 1.0 network device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.1/0000:03:00.0/virtio1/net/enp3s0 ● sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda1.device - QEMU_HARDDISK cloudimg-rootfs Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda1 ● sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda14.device - QEMU_HARDDISK 14 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda14 ● sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda15.device - QEMU_HARDDISK UEFI Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda15 ● sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda-sda16.device - QEMU_HARDDISK BOOT Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda/sda16 ● sys-devices-pci0000:00-0000:00:02.2-0000:04:00.0-virtio2-host0-target0:0:0-0:0:0:0-block-sda.device - QEMU_HARDDISK Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:0/block/sda ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.1/tty/ttyS1 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.1/tty/ttyS1 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.10-tty-ttyS10.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.10/tty/ttyS10 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.10/tty/ttyS10 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.11-tty-ttyS11.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.11/tty/ttyS11 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.11/tty/ttyS11 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.12-tty-ttyS12.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.12/tty/ttyS12 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.12/tty/ttyS12 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.13-tty-ttyS13.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.13/tty/ttyS13 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.13/tty/ttyS13 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.14-tty-ttyS14.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.14/tty/ttyS14 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.14/tty/ttyS14 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.15-tty-ttyS15.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.15/tty/ttyS15 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.15/tty/ttyS15 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.16-tty-ttyS16.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.16/tty/ttyS16 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.16/tty/ttyS16 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.17-tty-ttyS17.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.17/tty/ttyS17 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.17/tty/ttyS17 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.18-tty-ttyS18.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.18/tty/ttyS18 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.18/tty/ttyS18 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.19-tty-ttyS19.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.19/tty/ttyS19 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.19/tty/ttyS19 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.2/tty/ttyS2 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.2/tty/ttyS2 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.20-tty-ttyS20.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.20/tty/ttyS20 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.20/tty/ttyS20 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.21-tty-ttyS21.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.21/tty/ttyS21 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.21/tty/ttyS21 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.22-tty-ttyS22.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.22/tty/ttyS22 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.22/tty/ttyS22 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.23-tty-ttyS23.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.23/tty/ttyS23 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.23/tty/ttyS23 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.24-tty-ttyS24.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.24/tty/ttyS24 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.24/tty/ttyS24 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.25-tty-ttyS25.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.25/tty/ttyS25 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.25/tty/ttyS25 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.26-tty-ttyS26.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.26/tty/ttyS26 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.26/tty/ttyS26 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.27-tty-ttyS27.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.27/tty/ttyS27 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.27/tty/ttyS27 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.28-tty-ttyS28.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.28/tty/ttyS28 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.28/tty/ttyS28 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.29-tty-ttyS29.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.29/tty/ttyS29 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.29/tty/ttyS29 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.3/tty/ttyS3 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.3/tty/ttyS3 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.30-tty-ttyS30.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.30/tty/ttyS30 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.30/tty/ttyS30 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.31-tty-ttyS31.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.31/tty/ttyS31 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.31/tty/ttyS31 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.4-tty-ttyS4.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.4/tty/ttyS4 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.4/tty/ttyS4 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.5-tty-ttyS5.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.5/tty/ttyS5 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.5/tty/ttyS5 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.6-tty-ttyS6.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.6/tty/ttyS6 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.6/tty/ttyS6 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.7-tty-ttyS7.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.7/tty/ttyS7 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.7/tty/ttyS7 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.8-tty-ttyS8.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.8/tty/ttyS8 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.8/tty/ttyS8 ● sys-devices-platform-serial8250-serial8250:0-serial8250:0.9-tty-ttyS9.device - /sys/devices/platform/serial8250/serial8250:0/serial8250:0.9/tty/ttyS9 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/platform/serial8250/serial8250:0/serial8250:0.9/tty/ttyS9 ● sys-devices-pnp0-00:00-00:00:0-00:00:0.0-tty-ttyS0.device - /sys/devices/pnp0/00:00/00:00:0/00:00:0.0/tty/ttyS0 Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pnp0/00:00/00:00:0/00:00:0.0/tty/ttyS0 ● sys-devices-virtual-misc-rfkill.device - /sys/devices/virtual/misc/rfkill Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/virtual/misc/rfkill ● sys-devices-virtual-tty-ttyprintk.device - /sys/devices/virtual/tty/ttyprintk Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/virtual/tty/ttyprintk ● sys-module-configfs.device - /sys/module/configfs Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/module/configfs ● sys-module-fuse.device - /sys/module/fuse Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/module/fuse ● sys-subsystem-net-devices-enp3s0.device - Virtio 1.0 network device Loaded: loaded Active: active (plugged) since Fri 2026-05-22 15:45:38 UTC; 46min ago Device: /sys/devices/pci0000:00/0000:00:02.1/0000:03:00.0/virtio1/net/enp3s0 ● -.mount - Root Mount Loaded: loaded (/etc/fstab; generated) Active: active (mounted) since Fri 2026-05-22 15:45:37 UTC; 46min ago Where: / What: /dev/sda1 Docs: man:fstab(5) man:systemd-fstab-generator(8) Notice: journal has been rotated since unit was started, output may be incomplete. ● boot-efi.mount - /boot/efi Loaded: loaded (/etc/fstab; generated) Active: active (mounted) since Fri 2026-05-22 15:45:38 UTC; 46min ago Where: /boot/efi What: /dev/sda15 Docs: man:fstab(5) man:systemd-fstab-generator(8) Tasks: 0 (limit: 27561) Memory: 24.0K () CGroup: /system.slice/boot-efi.mount May 22 15:45:38 np0000001290 systemd[1]: Mounting boot-efi.mount - /boot/efi... May 22 15:45:38 np0000001290 systemd[1]: Mounted boot-efi.mount - /boot/efi. ● boot.mount - /boot Loaded: loaded (/etc/fstab; generated) Active: active (mounted) since Fri 2026-05-22 15:45:38 UTC; 46min ago Where: /boot What: /dev/sda16 Docs: man:fstab(5) man:systemd-fstab-generator(8) Tasks: 0 (limit: 27561) Memory: 160.0K () CGroup: /system.slice/boot.mount May 22 15:45:38 np0000001290 systemd[1]: Mounting boot.mount - /boot... May 22 15:45:38 np0000001290 systemd[1]: Mounted boot.mount - /boot. ● dev-hugepages.mount - Huge Pages File System Loaded: loaded (/proc/self/mountinfo; static) Active: active (mounted) since Fri 2026-05-22 15:45:38 UTC; 46min ago Where: /dev/hugepages What: hugetlbfs Docs: https://docs.kernel.org/admin-guide/mm/hugetlbpage.html https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Tasks: 0 (limit: 27561) Memory: 60.0K () CGroup: /dev-hugepages.mount Notice: journal has been rotated since unit was started, output may be incomplete. ● dev-mqueue.mount - POSIX Message Queue File System Loaded: loaded (/proc/self/mountinfo; static) Active: active (mounted) since Fri 2026-05-22 15:45:38 UTC; 46min ago Where: /dev/mqueue What: mqueue Docs: man:mq_overview(7) https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Tasks: 0 (limit: 27561) Memory: 4.0K () CGroup: /dev-mqueue.mount Notice: journal has been rotated since unit was started, output may be incomplete. ● proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System Loaded: loaded (/usr/lib/systemd/system/proc-sys-fs-binfmt_misc.mount; disabled; preset: disabled) Active: active (mounted) since Fri 2026-05-22 15:45:39 UTC; 46min ago TriggeredBy: ● proc-sys-fs-binfmt_misc.automount Where: /proc/sys/fs/binfmt_misc What: binfmt_misc Docs: https://docs.kernel.org/admin-guide/binfmt-misc.html https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Tasks: 0 (limit: 27561) Memory: 8.0K () CGroup: /proc-sys-fs-binfmt_misc.mount May 22 15:45:39 np0000001290 systemd[1]: Mounting proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System... May 22 15:45:39 np0000001290 systemd[1]: Mounted proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System. ● run-storpool-hugetlb.mount - /run/storpool/hugetlb Loaded: loaded (/proc/self/mountinfo) Active: active (mounted) since Fri 2026-05-22 15:47:02 UTC; 44min ago Where: /run/storpool/hugetlb What: hugetlb2m ● run-user-1000.mount - /run/user/1000 Loaded: loaded (/proc/self/mountinfo) Active: active (mounted) since Fri 2026-05-22 15:46:29 UTC; 45min ago Where: /run/user/1000 What: tmpfs ● sys-fs-fuse-connections.mount - FUSE Control File System Loaded: loaded (/proc/self/mountinfo; static) Active: active (mounted) since Fri 2026-05-22 15:45:38 UTC; 46min ago Where: /sys/fs/fuse/connections What: fusectl Docs: https://docs.kernel.org/filesystems/fuse.html https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Tasks: 0 (limit: 27561) Memory: 8.0K () CGroup: /sys-fs-fuse-connections.mount May 22 15:45:38 np0000001290 systemd[1]: Mounting sys-fs-fuse-connections.mount - FUSE Control File System... May 22 15:45:38 np0000001290 systemd[1]: Mounted sys-fs-fuse-connections.mount - FUSE Control File System. ● sys-kernel-config.mount - Kernel Configuration File System Loaded: loaded (/proc/self/mountinfo; static) Active: active (mounted) since Fri 2026-05-22 15:45:38 UTC; 46min ago Where: /sys/kernel/config What: configfs Docs: https://docs.kernel.org/filesystems/configfs.html https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Tasks: 0 (limit: 27561) Memory: 4.0K () CGroup: /sys-kernel-config.mount May 22 15:45:38 np0000001290 systemd[1]: Mounting sys-kernel-config.mount - Kernel Configuration File System... May 22 15:45:38 np0000001290 systemd[1]: Mounted sys-kernel-config.mount - Kernel Configuration File System. ● sys-kernel-debug.mount - Kernel Debug File System Loaded: loaded (/proc/self/mountinfo; static) Active: active (mounted) since Fri 2026-05-22 15:45:38 UTC; 46min ago Where: /sys/kernel/debug What: debugfs Docs: https://docs.kernel.org/filesystems/debugfs.html https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Tasks: 0 (limit: 27561) Memory: 4.0K () CGroup: /sys-kernel-debug.mount Notice: journal has been rotated since unit was started, output may be incomplete. ● sys-kernel-tracing.mount - Kernel Trace File System Loaded: loaded (/proc/self/mountinfo; static) Active: active (mounted) since Fri 2026-05-22 15:45:38 UTC; 46min ago Where: /sys/kernel/tracing What: tracefs Docs: https://docs.kernel.org/trace/ftrace.html https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Tasks: 0 (limit: 27561) Memory: 4.0K () CGroup: /sys-kernel-tracing.mount Notice: journal has been rotated since unit was started, output may be incomplete. ○ apport-autoreport.path - Process error reports when automatic reporting is enabled (file watch) Loaded: loaded (/usr/lib/systemd/system/apport-autoreport.path; enabled; preset: enabled) Active: inactive (dead) Triggers: ● apport-autoreport.service Condition: start condition unmet at Fri 2026-05-22 15:45:42 UTC; 46min ago May 22 15:45:42 np0000001290 systemd[1]: apport-autoreport.path - Process error reports when automatic reporting is enabled (file watch) was skipped because of an unmet condition check (ConditionPathExists=/var/lib/apport/autoreport). ● systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch Loaded: loaded (/usr/lib/systemd/system/systemd-ask-password-console.path; static) Active: active (waiting) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● systemd-ask-password-console.service Docs: man:systemd-ask-password-console.path(8) May 22 15:45:38 np0000001290 systemd[1]: Started systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch. ○ systemd-ask-password-plymouth.path - Forward Password Requests to Plymouth Directory Watch Loaded: loaded (/usr/lib/systemd/system/systemd-ask-password-plymouth.path; static) Active: inactive (dead) Triggers: ● systemd-ask-password-plymouth.service Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: http://www.freedesktop.org/wiki/Software/systemd/PasswordAgents May 22 15:45:38 np0000001290 systemd[1]: systemd-ask-password-plymouth.path - Forward Password Requests to Plymouth Directory Watch was skipped because of an unmet condition check (ConditionPathExists=/run/plymouth/pid). ● systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch Loaded: loaded (/usr/lib/systemd/system/systemd-ask-password-wall.path; static) Active: active (waiting) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● systemd-ask-password-wall.service Docs: man:systemd-ask-password-wall.path(8) Notice: journal has been rotated since unit was started, output may be incomplete. ○ tpm-udev.path - Handle dynamically added tpm devices Loaded: loaded (/usr/lib/systemd/system/tpm-udev.path; enabled; preset: enabled) Active: inactive (dead) Triggers: ● tpm-udev.service Condition: start condition unmet at Fri 2026-05-22 15:45:42 UTC; 46min ago May 22 15:45:42 np0000001290 systemd[1]: tpm-udev.path - Handle dynamically added tpm devices was skipped because of an unmet condition check (ConditionVirtualization=container). ● init.scope - System and Service Manager Loaded: loaded Transient: yes Active: active (running) since Fri 2026-05-22 15:45:37 UTC; 46min ago Docs: man:systemd(1) Tasks: 1 (limit: 27561) Memory: 8.6M () CGroup: /init.scope └─1 /sbin/init nofb May 22 16:31:46 np0000001290 systemd[1]: storpool_gui.service: Main process exited, code=exited, status=1/FAILURE May 22 16:31:46 np0000001290 systemd[1]: storpool_gui.service: Failed with result 'exit-code'. May 22 16:31:47 np0000001290 systemd[1]: storpool_gui.service: Scheduled restart job, restart counter is at 1747. May 22 16:31:47 np0000001290 systemd[1]: Started storpool_gui.service - storpool_gui. May 22 16:31:48 np0000001290 systemd[1]: storpool_gui.service: Main process exited, code=exited, status=1/FAILURE May 22 16:31:48 np0000001290 systemd[1]: storpool_gui.service: Failed with result 'exit-code'. May 22 16:31:49 np0000001290 systemd[1]: storpool_gui.service: Scheduled restart job, restart counter is at 1748. May 22 16:31:49 np0000001290 systemd[1]: Started storpool_gui.service - storpool_gui. May 22 16:31:49 np0000001290 systemd[1]: storpool_gui.service: Main process exited, code=exited, status=1/FAILURE May 22 16:31:49 np0000001290 systemd[1]: storpool_gui.service: Failed with result 'exit-code'. ● session-5.scope - Session 5 of User ubuntu Loaded: loaded (/run/systemd/transient/session-5.scope; transient) Transient: yes Active: active (abandoned) since Fri 2026-05-22 15:47:09 UTC; 44min ago Tasks: 3 Memory: 16.5M () CGroup: /user.slice/user-1000.slice/session-5.scope └─8569 /usr/bin/python3 May 22 15:47:12 np0000001290 sudo[8634]: pam_unix(sudo:session): session closed for user root May 22 15:47:13 np0000001290 sudo[8666]: ubuntu : PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/sh -c 'echo BECOME-SUCCESS-vbvtjvpdugdmujlrgyaahsnbyvbmmkem ; /usr/bin/python3' May 22 15:47:13 np0000001290 sudo[8666]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000) May 22 15:47:13 np0000001290 python3[8668]: ansible-ansible.legacy.command Invoked with argv=['storpool', 'placementGroup', 'virtual', 'addDisk', '111'] zuul_no_log=False zuul_log_id=in-loop-ignore zuul_output_max_bytes=1073741824 zuul_ansible_split_streams=False _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True _raw_params=None chdir=None executable=None creates=None removes=None stdin=None May 22 15:47:13 np0000001290 sudo[8666]: pam_unix(sudo:session): session closed for user root May 22 15:47:13 np0000001290 sudo[8679]: ubuntu : PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/sh -c 'echo BECOME-SUCCESS-etlcasntqpzwampmvpjemmjbpdpzzfeq ; /usr/bin/python3' May 22 15:47:13 np0000001290 sudo[8679]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000) May 22 15:47:14 np0000001290 python3[8681]: ansible-ansible.legacy.command Invoked with argv=['storpool', 'template', 'virtual', 'placeAll', 'virtual', 'replication', '1'] zuul_no_log=False zuul_log_id=in-loop-ignore zuul_output_max_bytes=1073741824 zuul_ansible_split_streams=False _uses_shell=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True _raw_params=None chdir=None executable=None creates=None removes=None stdin=None May 22 15:47:14 np0000001290 sudo[8679]: pam_unix(sudo:session): session closed for user root May 22 15:48:11 np0000001290 sshd[8483]: pam_unix(sshd:session): session closed for user ubuntu ● session-67.scope - Session 67 of User ubuntu Loaded: loaded (/run/systemd/transient/session-67.scope; transient) Transient: yes Active: active (running) since Fri 2026-05-22 16:31:02 UTC; 47s ago Tasks: 10 Memory: 27.3M () CGroup: /user.slice/user-1000.slice/session-67.scope ├─20085 "sshd: ubuntu [priv]" ├─20144 "sshd: ubuntu@notty" ├─20659 /bin/sh -c "sudo -H -S -n -u root /bin/sh -c 'echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3' && sleep 0" ├─20660 sudo -H -S -n -u root /bin/sh -c "echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3" ├─20661 /bin/sh -c "echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3" ├─20662 /usr/bin/python3 ├─20665 /bin/bash -c "sudo iptables-save > /home/ubuntu/iptables.txt\n\n# NOTE(sfernand): Run 'df' with a 60s timeout to prevent hangs from\n# stale NFS mounts.\ntimeout -s 9 60s df -h > /home/ubuntu/df.txt || true\n# If 'df' times out, the mount output helps debug which NFS share\n# is unresponsive.\nmount > /home/ubuntu/mount.txt\n\nfor py_ver in 2 3; do\n if [[ \`which python\${py_ver}\` ]]; then\n python\${py_ver} -m pip freeze > /home/ubuntu/pip\${py_ver}-freeze.txt\n fi\ndone\n\nif [ \`command -v dpkg\` ]; then\n dpkg -l> /home/ubuntu/dpkg-l.txt\nfi\nif [ \`command -v rpm\` ]; then\n rpm -qa | sort > /home/ubuntu/rpm-qa.txt\nfi\n\n# Services status\nsudo systemctl status --all > services.txt 2>/dev/null\n\n# NOTE(kchamart) The 'audit.log' can be useful in cases when QEMU\n# failed to start due to denials from SELinux — useful for CentOS\n# and Fedora machines. For Ubuntu (which runs AppArmor), DevStack\n# already captures the contents of /var/log/kern.log (via\n# \`journalctl -t kernel\` redirected into syslog.txt.gz), which\n# contains AppArmor-related messages.\nif [ -f /var/log/audit/audit.log ] ; then\n sudo cp /var/log/audit/audit.log /home/ubuntu/audit.log &&\n chmod +r /home/ubuntu/audit.log;\nfi\n\n# gzip and save any coredumps in /var/core\nif [ -d /var/core ]; then\n sudo gzip -r /var/core\n sudo cp -r /var/core /home/ubuntu/\nfi\n\nsudo ss -lntup | grep ':53' > /home/ubuntu/listen53.txt\n\n# NOTE(andreaf) Service logs are already in logs/ thanks for the\n# export-devstack-journal log. Apache logs are under apache/ thans to the\n# apache-logs-conf role.\ngrep -i deprecat /home/ubuntu/logs/*.txt /home/ubuntu/apache/*.log | \\\n sed -r 's/[0-9]{1,2}\\:[0-9]{1,2}\\:[0-9]{1,2}\\.[0-9]{1,3}/ /g' | \\\n sed -r 's/[0-9]{1,2}\\:[0-9]{1,2}\\:[0-9]{1,2}/ /g' | \\\n sed -r 's/[0-9]{1,4}-[0-9]{1,2}-[0-9]{1,4}/ /g' |\n sed -r 's/\\[.*\\]/ /g' | \\\n sed -r 's/\\s[0-9]+\\s/ /g' | \\\n awk '{if (\$0 in seen) {seen[\$0]++} else {out[++n]=\$0;seen[\$0]=1}} END { for (i=1; i<=n; i++) print seen[out[i]]\" :: \" out[i] }' > /home/ubuntu/deprecations.log\n" ├─20678 sudo systemctl status --all └─20679 systemctl status --all May 22 16:31:48 np0000001290 python3[20653]: ansible-stat Invoked with path=/etc/openstack follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 May 22 16:31:48 np0000001290 sudo[20651]: pam_unix(sudo:session): session closed for user root May 22 16:31:49 np0000001290 sudo[20660]: ubuntu : PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/sh -c 'echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3' May 22 16:31:49 np0000001290 sudo[20660]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000) May 22 16:31:49 np0000001290 python3[20662]: ansible-ansible.legacy.command Invoked with executable=/bin/bash _raw_params=sudo iptables-save > /home/ubuntu/iptables.txt # NOTE(sfernand): Run 'df' with a 60s timeout to prevent hangs from # stale NFS mounts. timeout -s 9 60s df -h > /home/ubuntu/df.txt || true # If 'df' times out, the mount output helps debug which NFS share # is unresponsive. mount > /home/ubuntu/mount.txt for py_ver in 2 3; do if [[ `which python${py_ver}` ]]; then python${py_ver} -m pip freeze > /home/ubuntu/pip${py_ver}-freeze.txt fi done if [ `command -v dpkg` ]; then dpkg -l> /home/ubuntu/dpkg-l.txt fi if [ `command -v rpm` ]; then rpm -qa | sort > /home/ubuntu/rpm-qa.txt fi # Services status sudo systemctl status --all > services.txt 2>/dev/null # NOTE(kchamart) The 'audit.log' can be useful in cases when QEMU # failed to start due to denials from SELinux — useful for CentOS # and Fedora machines. For Ubuntu (which runs AppArmor), DevStack # already captures the contents of /var/log/kern.log (via # `journalctl -t kernel` redirected into syslog.txt.gz), which # contains AppArmor-related messages. if [ -f /var/log/audit/audit.log ] ; then sudo cp /var/log/audit/audit.log /home/ubuntu/audit.log && chmod +r /home/ubuntu/audit.log; fi # gzip and save any coredumps in /var/core if [ -d /var/core ]; then sudo gzip -r /var/core sudo cp -r /var/core /home/ubuntu/ fi sudo ss -lntup | grep ':53' > /home/ubuntu/listen53.txt # NOTE(andreaf) Service logs are already in logs/ thanks for the # export-devstack-journal log. Apache logs are under apache/ thans to the # apache-logs-conf role. grep -i deprecat /home/ubuntu/logs/*.txt /home/ubuntu/apache/*.log | \ sed -r 's/[0-9]{1,2}\:[0-9]{1,2}\:[0-9]{1,2}\.[0-9]{1,3}/ /g' | \ sed -r 's/[0-9]{1,2}\:[0-9]{1,2}\:[0-9]{1,2}/ /g' | \ sed -r 's/[0-9]{1,4}-[0-9]{1,2}-[0-9]{1,4}/ /g' | sed -r 's/\[.*\]/ /g' | \ sed -r 's/\s[0-9]+\s/ /g' | \ awk '{if ($0 in seen) {seen[$0]++} else {out[++n]=$0;seen[$0]=1}} END { for (i=1; i<=n; i++) print seen[out[i]]" :: " out[i] }' > /home/ubuntu/deprecations.log _uses_shell=True zuul_no_log=False zuul_log_id=9ee7344d-e36b-6f85-ae59-000000000035-1-labspa1 zuul_output_max_bytes=1073741824 zuul_ansible_split_streams=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None creates=None removes=None stdin=None May 22 16:31:49 np0000001290 sudo[20667]: root : PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/sbin/iptables-save May 22 16:31:49 np0000001290 sudo[20667]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=0) May 22 16:31:49 np0000001290 sudo[20667]: pam_unix(sudo:session): session closed for user root May 22 16:31:49 np0000001290 sudo[20678]: root : PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/systemctl status --all May 22 16:31:49 np0000001290 sudo[20678]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=0) ● apparmor.service - Load AppArmor profiles Loaded: loaded (/usr/lib/systemd/system/apparmor.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:apparmor(7) https://gitlab.com/apparmor/apparmor/wikis/home/ Main PID: 1013 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting apparmor.service - Load AppArmor profiles... May 22 15:45:38 np0000001290 apparmor.systemd[1013]: Restarting AppArmor May 22 15:45:38 np0000001290 apparmor.systemd[1013]: /lib/apparmor/apparmor.systemd: 148: [: Illegal number: yes May 22 15:45:38 np0000001290 apparmor.systemd[1013]: Reloading AppArmor profiles May 22 15:45:38 np0000001290 systemd[1]: Finished apparmor.service - Load AppArmor profiles. ○ apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/usr/lib/systemd/system/apport-autoreport.service; static) Active: inactive (dead) TriggeredBy: ○ apport-autoreport.path ○ apport-autoreport.timer ● apport.service - automatic crash report generation Loaded: loaded (/usr/lib/systemd/system/apport.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:44 UTC; 46min ago Main PID: 4927 (code=exited, status=0/SUCCESS) May 22 15:45:44 np0000001290 systemd[1]: Starting apport.service - automatic crash report generation... May 22 15:45:44 np0000001290 systemd[1]: Finished apport.service - automatic crash report generation. ○ apt-daily.service - Daily apt download activities Loaded: loaded (/usr/lib/systemd/system/apt-daily.service; static) Active: inactive (dead) Docs: man:apt(8) ● blk-availability.service - Availability of block devices Loaded: loaded (/usr/lib/systemd/system/blk-availability.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:42 UTC; 46min ago May 22 15:45:42 np0000001290 systemd[1]: Finished blk-availability.service - Availability of block devices. ● cgconfig.service - Control Group configuration service Loaded: loaded (/usr/lib/systemd/system/cgconfig.service; enabled; preset: enabled) Drop-In: /usr/lib/systemd/system/cgconfig.service.d └─storpool.conf Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:cgconfigparser(8) Main PID: 498 (code=exited, status=0/SUCCESS) Notice: journal has been rotated since unit was started, output may be incomplete. ● chrony.service - chrony, an NTP client/server Loaded: loaded (/usr/lib/systemd/system/chrony.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:chronyd(8) man:chronyc(1) man:chrony.conf(5) Main PID: 4986 (chronyd) Tasks: 2 (limit: 27561) Memory: 4.5M () CGroup: /system.slice/chrony.service ├─4986 /usr/sbin/chronyd -F 1 └─4996 /usr/sbin/chronyd -F 1 May 22 15:45:44 np0000001290 systemd[1]: Started chrony.service - chrony, an NTP client/server. May 22 15:45:50 np0000001290 chronyd[4986]: Selected source 162.159.200.1 (2.ubuntu.pool.ntp.org) May 22 15:45:50 np0000001290 chronyd[4986]: System clock TAI offset set to 37 seconds May 22 15:46:56 np0000001290 chronyd[4986]: Selected source 193.238.174.38 (2.ubuntu.pool.ntp.org) May 22 15:46:57 np0000001290 chronyd[4986]: Received KoD RATE from 185.117.82.66 May 22 15:51:14 np0000001290 chronyd[4986]: Selected source 95.43.236.49 (0.ubuntu.pool.ntp.org) May 22 15:58:48 np0000001290 chronyd[4986]: Received KoD RATE from 185.117.82.66 May 22 16:04:11 np0000001290 chronyd[4986]: Received KoD RATE from 185.117.82.66 May 22 16:09:36 np0000001290 chronyd[4986]: Received KoD RATE from 185.117.82.66 May 22 16:25:44 np0000001290 chronyd[4986]: Received KoD RATE from 185.117.82.66 ● cloud-config.service - Cloud-init: Config Stage Loaded: loaded (/usr/lib/systemd/system/cloud-config.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:44 UTC; 46min ago Main PID: 4867 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 27561) Memory: 224.0K () CGroup: /system.slice/cloud-config.service May 22 15:45:43 np0000001290 systemd[1]: Starting cloud-config.service - Cloud-init: Config Stage... May 22 15:45:44 np0000001290 cloud-init[5095]: Cloud-init v. 25.2-0ubuntu1~24.04.1 running 'modules:config' at Fri, 22 May 2026 15:45:44 +0000. Up 8.90 seconds. May 22 15:45:44 np0000001290 systemd[1]: Finished cloud-config.service - Cloud-init: Config Stage. ● cloud-final.service - Cloud-init: Final Stage Loaded: loaded (/usr/lib/systemd/system/cloud-final.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:44 UTC; 46min ago Main PID: 5114 (code=exited, status=0/SUCCESS) Tasks: 0 Memory: 384.0K () CGroup: /system.slice/cloud-final.service May 22 15:45:44 np0000001290 systemd[1]: Starting cloud-final.service - Cloud-init: Final Stage... May 22 15:45:44 np0000001290 cloud-init[5121]: Cloud-init v. 25.2-0ubuntu1~24.04.1 running 'modules:final' at Fri, 22 May 2026 15:45:44 +0000. Up 9.37 seconds. May 22 15:45:44 np0000001290 cloud-init[5121]: Cloud-init v. 25.2-0ubuntu1~24.04.1 finished at Fri, 22 May 2026 15:45:44 +0000. Datasource DataSourceOpenStackLocal [net,ver=2]. Up 9.42 seconds May 22 15:45:44 np0000001290 systemd[1]: Finished cloud-final.service - Cloud-init: Final Stage. ○ cloud-init-hotplugd.service - Cloud-init: Hotplug Hook Loaded: loaded (/usr/lib/systemd/system/cloud-init-hotplugd.service; static) Active: inactive (dead) TriggeredBy: ● cloud-init-hotplugd.socket ● cloud-init-local.service - Cloud-init: Local Stage (pre-network) Loaded: loaded (/usr/lib/systemd/system/cloud-init-local.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:39 UTC; 46min ago Main PID: 1153 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 27561) Memory: 24.0M () CGroup: /system.slice/cloud-init-local.service May 22 15:45:38 np0000001290 systemd[1]: Starting cloud-init-local.service - Cloud-init: Local Stage (pre-network)... May 22 15:45:39 np0000001290 cloud-init[1171]: Cloud-init v. 25.2-0ubuntu1~24.04.1 running 'init-local' at Fri, 22 May 2026 15:45:39 +0000. Up 3.98 seconds. May 22 15:45:39 np0000001290 systemd[1]: Finished cloud-init-local.service - Cloud-init: Local Stage (pre-network). ● cloud-init.service - Cloud-init: Network Stage Loaded: loaded (/usr/lib/systemd/system/cloud-init.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:42 UTC; 46min ago Main PID: 3050 (code=exited, status=0/SUCCESS) May 22 15:45:41 np0000001290 cloud-init[3362]: ci-info: | 5 | local | :: | sp1 | U | May 22 15:45:41 np0000001290 cloud-init[3362]: ci-info: | 6 | local | :: | sp0 | U | May 22 15:45:41 np0000001290 cloud-init[3362]: ci-info: | 7 | local | :: | enp3s0 | U | May 22 15:45:41 np0000001290 cloud-init[3362]: ci-info: | 8 | local | :: | sp-api | U | May 22 15:45:41 np0000001290 cloud-init[3362]: ci-info: | 9 | multicast | :: | enp3s0 | U | May 22 15:45:41 np0000001290 cloud-init[3362]: ci-info: | 10 | multicast | :: | sp-api | U | May 22 15:45:41 np0000001290 cloud-init[3362]: ci-info: | 11 | multicast | :: | sp0 | U | May 22 15:45:41 np0000001290 cloud-init[3362]: ci-info: | 12 | multicast | :: | sp1 | U | May 22 15:45:41 np0000001290 cloud-init[3362]: ci-info: +-------+-------------+---------+-----------+-------+ May 22 15:45:42 np0000001290 systemd[1]: Finished cloud-init.service - Cloud-init: Network Stage. ● console-setup.service - Set console font and keymap Loaded: loaded (/usr/lib/systemd/system/console-setup.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Main PID: 1014 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting console-setup.service - Set console font and keymap... May 22 15:45:38 np0000001290 systemd[1]: Finished console-setup.service - Set console font and keymap. ● cron.service - Regular background program processing daemon Loaded: loaded (/usr/lib/systemd/system/cron.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:cron(8) Main PID: 4930 (cron) Tasks: 1 (limit: 27561) Memory: 9.0M () CGroup: /system.slice/cron.service └─4930 /usr/sbin/cron -f -P May 22 16:30:01 np0000001290 CRON[19406]: (root) CMD ([ -f /etc/storpool.conf ] && /usr/lib/storpool/storpool_periodic) May 22 16:30:01 np0000001290 CRON[19403]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0) May 22 16:30:01 np0000001290 CRON[19407]: (root) CMD ([ -f /etc/storpool.conf ] && /usr/lib/storpool/monitor) May 22 16:30:01 np0000001290 CRON[19400]: pam_unix(cron:session): session closed for user root May 22 16:30:01 np0000001290 CRON[19402]: pam_unix(cron:session): session closed for user root May 22 16:30:02 np0000001290 CRON[19401]: pam_unix(cron:session): session closed for user root May 22 16:30:42 np0000001290 CRON[19403]: pam_unix(cron:session): session closed for user root May 22 16:31:01 np0000001290 CRON[20070]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0) May 22 16:31:01 np0000001290 CRON[20071]: (root) CMD ([ -f /etc/storpool.conf ] && /usr/lib/storpool/monitor) May 22 16:31:43 np0000001290 CRON[20070]: pam_unix(cron:session): session closed for user root ● dbus.service - D-Bus System Message Bus Loaded: loaded (/usr/lib/systemd/system/dbus.service; static) Active: active (running) since Fri 2026-05-22 15:45:44 UTC; 46min ago TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) Main PID: 4868 (dbus-daemon) Tasks: 1 (limit: 27561) Memory: 1.9M () CGroup: /system.slice/dbus.service └─4868 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only May 22 15:45:43 np0000001290 systemd[1]: Starting dbus.service - D-Bus System Message Bus... May 22 15:45:44 np0000001290 dbus-daemon[4868]: [system] AppArmor D-Bus mediation is enabled May 22 15:45:44 np0000001290 systemd[1]: Started dbus.service - D-Bus System Message Bus. May 22 15:45:44 np0000001290 dbus-daemon[4868]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.2' (uid=0 pid=4892 comm="/usr/libexec/udisks2/udisksd" label="unconfined") May 22 15:45:44 np0000001290 dbus-daemon[4868]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' May 22 15:45:44 np0000001290 dbus-daemon[4868]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.14' (uid=0 pid=4886 comm="/usr/lib/snapd/snapd" label="unconfined") May 22 15:45:44 np0000001290 dbus-daemon[4868]: [system] Successfully activated service 'org.freedesktop.timedate1' May 22 16:11:36 np0000001290 dbus-daemon[4868]: [system] Activating via systemd: service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.269' (uid=990 pid=14855 comm="/usr/bin/fwupdmgr refresh" label="unconfined") May 22 16:11:36 np0000001290 dbus-daemon[4868]: [system] Successfully activated service 'org.freedesktop.fwupd' ○ dm-event.service - Device-mapper event daemon Loaded: loaded (/usr/lib/systemd/system/dm-event.service; static) Active: inactive (dead) TriggeredBy: ● dm-event.socket Docs: man:dmeventd(8) ○ dmesg.service - Save initial kernel messages after boot Loaded: loaded (/usr/lib/systemd/system/dmesg.service; enabled; preset: enabled) Active: inactive (dead) since Fri 2026-05-22 15:45:44 UTC; 46min ago Duration: 1.004s Main PID: 5143 (code=exited, status=0/SUCCESS) May 22 15:45:43 np0000001290 systemd[1]: Started dmesg.service - Save initial kernel messages after boot. May 22 15:45:44 np0000001290 systemd[1]: dmesg.service: Deactivated successfully. ○ dpkg-db-backup.service - Daily dpkg database backup service Loaded: loaded (/usr/lib/systemd/system/dpkg-db-backup.service; static) Active: inactive (dead) TriggeredBy: ● dpkg-db-backup.timer Docs: man:dpkg(1) ○ e2scrub_all.service - Online ext4 Metadata Check for All Filesystems Loaded: loaded (/usr/lib/systemd/system/e2scrub_all.service; static) Active: inactive (dead) TriggeredBy: ● e2scrub_all.timer Docs: man:e2scrub_all(8) ○ e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots Loaded: loaded (/usr/lib/systemd/system/e2scrub_reap.service; enabled; preset: enabled) Active: inactive (dead) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:e2scrub_all(8) Main PID: 4870 (code=exited, status=0/SUCCESS) May 22 15:45:43 np0000001290 systemd[1]: Starting e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots... May 22 15:45:44 np0000001290 systemd[1]: e2scrub_reap.service: Deactivated successfully. May 22 15:45:44 np0000001290 systemd[1]: Finished e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots. ○ emergency.service - Emergency Shell Loaded: loaded (/usr/lib/systemd/system/emergency.service; static) Active: inactive (dead) Docs: man:sulogin(8) ● finalrd.service - Create final runtime dir for shutdown pivot root Loaded: loaded (/usr/lib/systemd/system/finalrd.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:finalrd(1) Main PID: 1015 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting finalrd.service - Create final runtime dir for shutdown pivot root... May 22 15:45:38 np0000001290 systemd[1]: Finished finalrd.service - Create final runtime dir for shutdown pivot root. ○ fstrim.service - Discard unused blocks on filesystems from /etc/fstab Loaded: loaded (/usr/lib/systemd/system/fstrim.service; static) Active: inactive (dead) TriggeredBy: ● fstrim.timer Docs: man:fstrim(8) ○ fwupd-refresh.service - Refresh fwupd metadata and update motd Loaded: loaded (/usr/lib/systemd/system/fwupd-refresh.service; static) Active: inactive (dead) since Fri 2026-05-22 16:11:36 UTC; 20min ago TriggeredBy: ● fwupd-refresh.timer Docs: man:fwupdmgr(1) Process: 14855 ExecStart=/usr/bin/fwupdmgr refresh (code=exited, status=2) Main PID: 14855 (code=exited, status=2) May 22 16:11:36 np0000001290 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... May 22 16:11:36 np0000001290 systemd[1]: fwupd-refresh.service: Deactivated successfully. May 22 16:11:36 np0000001290 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. ○ getty-static.service - getty on tty2-tty6 if dbus and logind are not available Loaded: loaded (/usr/lib/systemd/system/getty-static.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:43 UTC; 46min ago May 22 15:45:43 np0000001290 systemd[1]: getty-static.service - getty on tty2-tty6 if dbus and logind are not available was skipped because of an unmet condition check (ConditionPathExists=!/usr/bin/dbus-daemon). ● getty@tty1.service - Getty on tty1 Loaded: loaded (/usr/lib/systemd/system/getty@.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:agetty(8) man:systemd-getty-generator(8) https://0pointer.de/blog/projects/serial-console.html Main PID: 5000 (agetty) Tasks: 1 (limit: 27561) Memory: 304.0K () CGroup: /system.slice/system-getty.slice/getty@tty1.service └─5000 /sbin/agetty -o "-p -- \\u" --noclear - linux May 22 15:45:44 np0000001290 systemd[1]: Started getty@tty1.service - Getty on tty1. ○ grub-common.service - Record successful boot for GRUB Loaded: loaded (/usr/lib/systemd/system/grub-common.service; enabled; preset: enabled) Active: inactive (dead) since Fri 2026-05-22 15:45:44 UTC; 46min ago Main PID: 4906 (code=exited, status=0/SUCCESS) May 22 15:45:43 np0000001290 systemd[1]: Starting grub-common.service - Record successful boot for GRUB... May 22 15:45:44 np0000001290 systemd[1]: grub-common.service: Deactivated successfully. May 22 15:45:44 np0000001290 systemd[1]: Finished grub-common.service - Record successful boot for GRUB. ○ grub-initrd-fallback.service - GRUB failed boot detection Loaded: loaded (/usr/lib/systemd/system/grub-initrd-fallback.service; enabled; preset: enabled) Active: inactive (dead) since Fri 2026-05-22 15:45:44 UTC; 46min ago Main PID: 4968 (code=exited, status=0/SUCCESS) May 22 15:45:44 np0000001290 systemd[1]: Starting grub-initrd-fallback.service - GRUB failed boot detection... May 22 15:45:44 np0000001290 systemd[1]: grub-initrd-fallback.service: Deactivated successfully. May 22 15:45:44 np0000001290 systemd[1]: Finished grub-initrd-fallback.service - GRUB failed boot detection. ● ifupdown-pre.service - Helper to synchronize boot up for ifupdown Loaded: loaded (/usr/lib/systemd/system/ifupdown-pre.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Main PID: 614 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting ifupdown-pre.service - Helper to synchronize boot up for ifupdown... May 22 15:45:38 np0000001290 systemd[1]: Finished ifupdown-pre.service - Helper to synchronize boot up for ifupdown. ○ initrd-cleanup.service - Cleaning Up and Shutting Down Daemons Loaded: loaded (/usr/lib/systemd/system/initrd-cleanup.service; static) Active: inactive (dead) ○ initrd-parse-etc.service - Mountpoints Configured in the Real Root Loaded: loaded (/usr/lib/systemd/system/initrd-parse-etc.service; static) Active: inactive (dead) ○ initrd-switch-root.service - Switch Root Loaded: loaded (/usr/lib/systemd/system/initrd-switch-root.service; static) Active: inactive (dead) ○ initrd-udevadm-cleanup-db.service - Cleanup udev Database Loaded: loaded (/usr/lib/systemd/system/initrd-udevadm-cleanup-db.service; static) Active: inactive (dead) ○ iscsid.service - iSCSI initiator daemon (iscsid) Loaded: loaded (/usr/lib/systemd/system/iscsid.service; disabled; preset: enabled) Active: inactive (dead) TriggeredBy: ● iscsid.socket Docs: man:iscsid(8) ● kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/usr/lib/systemd/system/kdump-tools.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:43 UTC; 46min ago Main PID: 1251 (code=exited, status=0/SUCCESS) May 22 15:45:39 np0000001290 systemd[1]: Starting kdump-tools.service - Kernel crash dump capture service... May 22 15:45:39 np0000001290 kdump-tools[1251]: Starting kdump-tools: May 22 15:45:39 np0000001290 kdump-tools[1257]: * Creating symlink /var/lib/kdump/vmlinuz May 22 15:45:39 np0000001290 kdump-tools[1275]: kdump-tools: Generating /var/lib/kdump/initrd.img-6.8.0-117-generic May 22 15:45:43 np0000001290 kdump-tools[1257]: * Creating symlink /var/lib/kdump/initrd.img May 22 15:45:43 np0000001290 kdump-tools[1257]: * loaded kdump kernel May 22 15:45:43 np0000001290 systemd[1]: Finished kdump-tools.service - Kernel crash dump capture service. ● keyboard-setup.service - Set the console keyboard layout Loaded: loaded (/usr/lib/systemd/system/keyboard-setup.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Main PID: 501 (code=exited, status=0/SUCCESS) Notice: journal has been rotated since unit was started, output may be incomplete. ● kmod-static-nodes.service - Create List of Static Device Nodes Loaded: loaded (/usr/lib/systemd/system/kmod-static-nodes.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Main PID: 502 (code=exited, status=0/SUCCESS) Notice: journal has been rotated since unit was started, output may be incomplete. ○ ldconfig.service - Rebuild Dynamic Linker Cache Loaded: loaded (/usr/lib/systemd/system/ldconfig.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:ldconfig(8) May 22 15:45:38 np0000001290 systemd[1]: ldconfig.service - Rebuild Dynamic Linker Cache was skipped because no trigger condition checks were met. ● lldpd.service - LLDP daemon Loaded: loaded (/usr/lib/systemd/system/lldpd.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:lldpd(8) Main PID: 4872 (lldpd) Tasks: 2 (limit: 27561) Memory: 5.8M () CGroup: /system.slice/lldpd.service ├─4872 "lldpd: monitor. " └─4891 "lldpd: connected to a9." May 22 15:45:44 np0000001290 lldpd[4891]: protocol CDPv1 disabled May 22 15:45:44 np0000001290 lldpd[4891]: protocol CDPv2 disabled May 22 15:45:44 np0000001290 lldpd[4891]: protocol SONMP disabled May 22 15:45:44 np0000001290 lldpd[4891]: protocol EDP disabled May 22 15:45:44 np0000001290 lldpd[4891]: protocol FDP disabled May 22 15:45:44 np0000001290 lldpd[4891]: libevent 2.1.12-stable initialized with epoll method May 22 15:45:44 np0000001290 systemd[1]: Started lldpd.service - LLDP daemon. May 22 15:45:44 np0000001290 lldpcli[4890]: lldpd should resume operations May 22 16:30:09 np0000001290 lldpd[4891]: removal request for address of 192.168.10.5%3, but no knowledge of it May 22 16:30:14 np0000001290 lldpd[4891]: unable to send packet on real device for sp1: No such device or address ○ logrotate.service - Rotate log files Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static) Active: inactive (dead) TriggeredBy: ● logrotate.timer Docs: man:logrotate(8) man:logrotate.conf(5) ○ lvm2-lvmpolld.service - LVM2 poll daemon Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmpolld.service; static) Active: inactive (dead) TriggeredBy: ● lvm2-lvmpolld.socket Docs: man:lvmpolld(8) ● lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling Loaded: loaded (/usr/lib/systemd/system/lvm2-monitor.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:dmeventd(8) man:lvcreate(8) man:lvchange(8) man:vgchange(8) Main PID: 503 (code=exited, status=0/SUCCESS) Notice: journal has been rotated since unit was started, output may be incomplete. ○ man-db.service - Daily man-db regeneration Loaded: loaded (/usr/lib/systemd/system/man-db.service; static) Active: inactive (dead) TriggeredBy: ● man-db.timer Docs: man:mandb(8) ● ModemManager.service - Modem Manager Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:44 UTC; 46min ago Main PID: 5010 (ModemManager) Tasks: 4 (limit: 27561) Memory: 8.0M () CGroup: /system.slice/ModemManager.service └─5010 /usr/sbin/ModemManager May 22 15:45:44 np0000001290 systemd[1]: Starting ModemManager.service - Modem Manager... May 22 15:45:44 np0000001290 ModemManager[5010]: ModemManager (version 1.23.4) starting in system bus... May 22 15:45:44 np0000001290 systemd[1]: Started ModemManager.service - Modem Manager. May 22 15:45:48 np0000001290 ModemManager[5010]: [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.1/0000:03:00.0': not supported by any plugin May 22 15:45:48 np0000001290 ModemManager[5010]: [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.5/0000:07:00.0': not supported by any plugin May 22 15:45:48 np0000001290 ModemManager[5010]: [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.6/0000:08:00.0': not supported by any plugin May 22 15:45:48 np0000001290 ModemManager[5010]: [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.7/0000:09:00.0': not supported by any plugin ○ modprobe@configfs.service - Load Kernel Module configfs Loaded: loaded (/usr/lib/systemd/system/modprobe@.service; static) Active: inactive (dead) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:modprobe(8) Main PID: 507 (code=exited, status=0/SUCCESS) Notice: journal has been rotated since unit was started, output may be incomplete. ○ modprobe@dm_mod.service - Load Kernel Module dm_mod Loaded: loaded (/usr/lib/systemd/system/modprobe@.service; static) Active: inactive (dead) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:modprobe(8) Main PID: 512 (code=exited, status=0/SUCCESS) Notice: journal has been rotated since unit was started, output may be incomplete. ○ modprobe@drm.service - Load Kernel Module drm Loaded: loaded (/usr/lib/systemd/system/modprobe@.service; static) Active: inactive (dead) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:modprobe(8) Main PID: 515 (code=exited, status=0/SUCCESS) Notice: journal has been rotated since unit was started, output may be incomplete. ○ modprobe@efi_pstore.service - Load Kernel Module efi_pstore Loaded: loaded (/usr/lib/systemd/system/modprobe@.service; static) Active: inactive (dead) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:modprobe(8) Main PID: 517 (code=exited, status=0/SUCCESS) ○ modprobe@fuse.service - Load Kernel Module fuse Loaded: loaded (/usr/lib/systemd/system/modprobe@.service; static) Active: inactive (dead) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:modprobe(8) Main PID: 519 (code=exited, status=0/SUCCESS) ○ modprobe@loop.service - Load Kernel Module loop Loaded: loaded (/usr/lib/systemd/system/modprobe@.service; static) Active: inactive (dead) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:modprobe(8) Main PID: 521 (code=exited, status=0/SUCCESS) ○ modprobe@nvme_fabrics.service - Load Kernel Module nvme_fabrics Loaded: loaded (/usr/lib/systemd/system/modprobe@.service; static) Active: inactive (dead) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:modprobe(8) Main PID: 526 (code=exited, status=0/SUCCESS) ○ motd-news.service - Message of the Day Loaded: loaded (/usr/lib/systemd/system/motd-news.service; static) Active: inactive (dead) TriggeredBy: ● motd-news.timer Docs: man:update-motd(8) ● multipathd.service - Device-Mapper Multipath Device Controller Loaded: loaded (/usr/lib/systemd/system/multipathd.service; disabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:46:55 UTC; 44min ago TriggeredBy: ○ multipathd.socket Main PID: 7266 (multipathd) Status: "up" Tasks: 7 Memory: 18.8M () CGroup: /system.slice/multipathd.service └─7266 /sbin/multipathd -d -s May 22 15:46:55 np0000001290 systemd[1]: Starting multipathd.service - Device-Mapper Multipath Device Controller... May 22 15:46:55 np0000001290 multipathd[7266]: multipathd v0.9.4: start up May 22 15:46:55 np0000001290 multipathd[7266]: reconfigure: setting up paths and maps May 22 15:46:55 np0000001290 systemd[1]: Started multipathd.service - Device-Mapper Multipath Device Controller. ○ netplan-ovs-cleanup.service - OpenVSwitch configuration for cleanup Loaded: loaded (/run/systemd/system/netplan-ovs-cleanup.service; enabled-runtime; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago ● networkd-dispatcher.service - Dispatcher daemon for systemd-networkd Loaded: loaded (/usr/lib/systemd/system/networkd-dispatcher.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:44 UTC; 46min ago Main PID: 4874 (networkd-dispat) Tasks: 1 (limit: 27561) Memory: 11.9M () CGroup: /system.slice/networkd-dispatcher.service └─4874 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers May 22 15:45:43 np0000001290 systemd[1]: Starting networkd-dispatcher.service - Dispatcher daemon for systemd-networkd... May 22 15:45:44 np0000001290 networkd-dispatcher[4874]: No valid path found for iwconfig May 22 15:45:44 np0000001290 networkd-dispatcher[4874]: No valid path found for iw May 22 15:45:44 np0000001290 systemd[1]: Started networkd-dispatcher.service - Dispatcher daemon for systemd-networkd. May 22 16:30:09 np0000001290 systemd[1]: networkd-dispatcher.service: Got notification message from PID 19571, but reception only permitted for main PID 4874 May 22 16:30:09 np0000001290 networkd-dispatcher[4874]: ERROR:Failed to get interface "sp-api" status: Command '['/usr/bin/networkctl', 'status', '--no-pager', '--no-legend', '--lines=0', '--', 'sp-api']' returned non-zero exit status 1. May 22 16:30:11 np0000001290 networkd-dispatcher[4874]: ERROR:Failed to get interface "sp0" status: Command '['/usr/bin/networkctl', 'status', '--no-pager', '--no-legend', '--lines=0', '--', 'sp0']' returned non-zero exit status 1. May 22 16:30:13 np0000001290 networkd-dispatcher[4874]: ERROR:Failed to get interface "sp1" status: Command '['/usr/bin/networkctl', 'status', '--no-pager', '--no-legend', '--lines=0', '--', 'sp1']' returned non-zero exit status 1. ● networking.service - Raise network interfaces Loaded: loaded (/usr/lib/systemd/system/networking.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:39 UTC; 46min ago Docs: man:interfaces(5) Main PID: 1239 (code=exited, status=0/SUCCESS) May 22 15:45:39 np0000001290 systemd[1]: Starting networking.service - Raise network interfaces... May 22 15:45:39 np0000001290 systemd[1]: Finished networking.service - Raise network interfaces. ○ nvmefc-boot-connections.service - Auto-connect to subsystems on FC-NVME devices found during boot Loaded: loaded (/usr/lib/systemd/system/nvmefc-boot-connections.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago May 22 15:45:38 np0000001290 systemd[1]: nvmefc-boot-connections.service - Auto-connect to subsystems on FC-NVME devices found during boot was skipped because of an unmet condition check (ConditionPathExists=/sys/class/fc/fc_udev_device/nvme_discovery). ○ nvmf-autoconnect.service - Connect NVMe-oF subsystems automatically during boot Loaded: loaded (/usr/lib/systemd/system/nvmf-autoconnect.service; enabled; preset: enabled) Active: inactive (dead) since Fri 2026-05-22 15:45:44 UTC; 46min ago Main PID: 4876 (code=exited, status=0/SUCCESS) May 22 15:45:43 np0000001290 systemd[1]: Starting nvmf-autoconnect.service - Connect NVMe-oF subsystems automatically during boot... May 22 15:45:44 np0000001290 systemd[1]: nvmf-autoconnect.service: Deactivated successfully. May 22 15:45:44 np0000001290 systemd[1]: Finished nvmf-autoconnect.service - Connect NVMe-oF subsystems automatically during boot. ○ open-iscsi.service - Login to default iSCSI targets Loaded: loaded (/usr/lib/systemd/system/open-iscsi.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:42 UTC; 46min ago Docs: man:iscsiadm(8) man:iscsid(8) May 22 15:45:42 np0000001290 systemd[1]: open-iscsi.service - Login to default iSCSI targets was skipped because no trigger condition checks were met. ○ open-vm-tools.service - Service for virtual machines hosted on VMware Loaded: loaded (/usr/lib/systemd/system/open-vm-tools.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: http://open-vm-tools.sourceforge.net/about.php May 22 15:45:38 np0000001290 systemd[1]: open-vm-tools.service - Service for virtual machines hosted on VMware was skipped because of an unmet condition check (ConditionVirtualization=vmware). ● plymouth-quit-wait.service - Hold until boot process finishes up Loaded: loaded (/usr/lib/systemd/system/plymouth-quit-wait.service; static) Active: active (exited) since Fri 2026-05-22 15:45:44 UTC; 46min ago Main PID: 4959 (code=exited, status=0/SUCCESS) May 22 15:45:44 np0000001290 systemd[1]: Starting plymouth-quit-wait.service - Hold until boot process finishes up... May 22 15:45:44 np0000001290 systemd[1]: Finished plymouth-quit-wait.service - Hold until boot process finishes up. ● plymouth-quit.service - Terminate Plymouth Boot Screen Loaded: loaded (/usr/lib/systemd/system/plymouth-quit.service; static) Active: active (exited) since Fri 2026-05-22 15:45:44 UTC; 46min ago Main PID: 4962 (code=exited, status=1/FAILURE) May 22 15:45:44 np0000001290 systemd[1]: Starting plymouth-quit.service - Terminate Plymouth Boot Screen... May 22 15:45:44 np0000001290 systemd[1]: Finished plymouth-quit.service - Terminate Plymouth Boot Screen. ● plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data Loaded: loaded (/usr/lib/systemd/system/plymouth-read-write.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Main PID: 1016 (code=exited, status=1/FAILURE) May 22 15:45:38 np0000001290 systemd[1]: Starting plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data... May 22 15:45:38 np0000001290 systemd[1]: Finished plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data. ○ plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago May 22 15:45:38 np0000001290 systemd[1]: plymouth-start.service - Show Plymouth Boot Screen was skipped because of an unmet condition check (ConditionKernelCommandLine=splash). ○ plymouth-switch-root.service - Plymouth switch root service Loaded: loaded (/usr/lib/systemd/system/plymouth-switch-root.service; static) Active: inactive (dead) ● polkit.service - Authorization Manager Loaded: loaded (/usr/lib/systemd/system/polkit.service; static) Active: active (running) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:polkit(8) Main PID: 4877 (polkitd) Tasks: 4 (limit: 27561) Memory: 1.9M () CGroup: /system.slice/polkit.service └─4877 /usr/lib/polkit-1/polkitd --no-debug May 22 15:45:44 np0000001290 systemd[1]: Starting polkit.service - Authorization Manager... May 22 15:45:44 np0000001290 polkitd[4877]: Started polkitd version 124 May 22 15:45:44 np0000001290 polkitd[4877]: Loading rules from directory /etc/polkit-1/rules.d May 22 15:45:44 np0000001290 polkitd[4877]: Loading rules from directory /usr/share/polkit-1/rules.d May 22 15:45:44 np0000001290 polkitd[4877]: Finished loading, compiling and executing 6 rules May 22 15:45:44 np0000001290 polkitd[4877]: Acquired the name org.freedesktop.PolicyKit1 on the system bus May 22 15:45:44 np0000001290 systemd[1]: Started polkit.service - Authorization Manager. ○ pollinate.service - Pollinate to seed the pseudo random number generator Loaded: loaded (/usr/lib/systemd/system/pollinate.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: https://launchpad.net/pollinate May 22 15:45:44 np0000001290 systemd[1]: pollinate.service - Pollinate to seed the pseudo random number generator was skipped because of an unmet condition check (ConditionPathExists=!/var/cache/pollinate/seeded). × rc-local.service - /etc/rc.local Compatibility Loaded: loaded (/usr/lib/systemd/system/rc-local.service; enabled-runtime; preset: enabled) Drop-In: /usr/lib/systemd/system/rc-local.service.d └─debian.conf Active: failed (Result: exit-code) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:systemd-rc-local-generator(8) May 22 15:45:44 np0000001290 rc.local[4893]: Error setting new values. Common errors: May 22 15:45:44 np0000001290 rc.local[4893]: - Do you have proper administration rights? (super-user?) May 22 15:45:44 np0000001290 rc.local[4893]: - Is the governor you requested available and modprobed? May 22 15:45:44 np0000001290 rc.local[4893]: - Trying to set an invalid policy? May 22 15:45:44 np0000001290 rc.local[4893]: - Trying to set a specific frequency, but userspace governor is not available, May 22 15:45:44 np0000001290 rc.local[4893]: for example because of hardware which cannot be set to a specific frequency May 22 15:45:44 np0000001290 rc.local[4893]: or because the userspace governor isn't loaded? May 22 15:45:44 np0000001290 systemd[1]: rc-local.service: Control process exited, code=exited, status=237/KEYRING May 22 15:45:44 np0000001290 systemd[1]: rc-local.service: Failed with result 'exit-code'. May 22 15:45:44 np0000001290 systemd[1]: Failed to start rc-local.service - /etc/rc.local Compatibility. ○ rescue.service - Rescue Shell Loaded: loaded (/usr/lib/systemd/system/rescue.service; static) Active: inactive (dead) Docs: man:sulogin(8) ● rsyslog.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:44 UTC; 46min ago TriggeredBy: ● syslog.socket Docs: man:rsyslogd(8) man:rsyslog.conf(5) https://www.rsyslog.com/doc/ Main PID: 4966 (rsyslogd) Tasks: 4 (limit: 27561) Memory: 12.0M () CGroup: /system.slice/rsyslog.service └─4966 /usr/sbin/rsyslogd -n -iNONE May 22 16:31:34 np0000001290 rsyslogd[4966]: action 'action-9-builtin:omfile' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2312.0 try https://www.rsyslog.com/e/2007 ] May 22 16:31:34 np0000001290 rsyslogd[4966]: action 'action-9-builtin:omfile' resumed (module 'builtin:omfile') [v8.2312.0 try https://www.rsyslog.com/e/2359 ] May 22 16:31:34 np0000001290 rsyslogd[4966]: action 'action-9-builtin:omfile' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2312.0 try https://www.rsyslog.com/e/2007 ] May 22 16:31:34 np0000001290 rsyslogd[4966]: action 'action-9-builtin:omfile' resumed (module 'builtin:omfile') [v8.2312.0 try https://www.rsyslog.com/e/2359 ] May 22 16:31:34 np0000001290 rsyslogd[4966]: action 'action-9-builtin:omfile' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2312.0 try https://www.rsyslog.com/e/2007 ] May 22 16:31:34 np0000001290 rsyslogd[4966]: action 'action-9-builtin:omfile' resumed (module 'builtin:omfile') [v8.2312.0 try https://www.rsyslog.com/e/2359 ] May 22 16:31:34 np0000001290 rsyslogd[4966]: action 'action-9-builtin:omfile' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2312.0 try https://www.rsyslog.com/e/2007 ] May 22 16:31:34 np0000001290 rsyslogd[4966]: action 'action-9-builtin:omfile' resumed (module 'builtin:omfile') [v8.2312.0 try https://www.rsyslog.com/e/2359 ] May 22 16:31:34 np0000001290 rsyslogd[4966]: action 'action-9-builtin:omfile' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2312.0 try https://www.rsyslog.com/e/2007 ] May 22 16:31:34 np0000001290 rsyslogd[4966]: action 'action-9-builtin:omfile' suspended (module 'builtin:omfile'), next retry is Fri May 22 16:32:04 2026, retry nbr 0. There should be messages before this one giving the reason for suspension. [v8.2312.0 try https://www.rsyslog.com/e/2007 ] ○ secureboot-db.service - Secure Boot updates for DB and DBX Loaded: loaded (/usr/lib/systemd/system/secureboot-db.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:44 UTC; 46min ago May 22 15:45:44 np0000001290 systemd[1]: secureboot-db.service - Secure Boot updates for DB and DBX was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/db-d719b2cb-3d3a-4596-a3bc-dad00e67656f). ● serial-getty@ttyS0.service - Serial Getty on ttyS0 Loaded: loaded (/usr/lib/systemd/system/serial-getty@.service; enabled-runtime; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:agetty(8) man:systemd-getty-generator(8) https://0pointer.de/blog/projects/serial-console.html Main PID: 4972 (agetty) Tasks: 1 (limit: 27561) Memory: 220.0K () CGroup: /system.slice/system-serial\x2dgetty.slice/serial-getty@ttyS0.service └─4972 /sbin/agetty -o "-p -- \\u" --keep-baud 115200,57600,38400,9600 - vt220 May 22 15:45:44 np0000001290 systemd[1]: Started serial-getty@ttyS0.service - Serial Getty on ttyS0. ● setvtrgb.service - Set console scheme Loaded: loaded (/usr/lib/systemd/system/setvtrgb.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:44 UTC; 46min ago Main PID: 4973 (code=exited, status=0/SUCCESS) May 22 15:45:44 np0000001290 systemd[1]: Starting setvtrgb.service - Set console scheme... May 22 15:45:44 np0000001290 systemd[1]: Finished setvtrgb.service - Set console scheme. ○ smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon Loaded: loaded (/usr/lib/systemd/system/smartmontools.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:smartd(8) man:smartd.conf(5) May 22 15:45:44 np0000001290 systemd[1]: smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon was skipped because of an unmet condition check (ConditionVirtualization=no). ● snapd.apparmor.service - Load AppArmor profiles managed internally by snapd Loaded: loaded (/usr/lib/systemd/system/snapd.apparmor.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:39 UTC; 46min ago Main PID: 1152 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting snapd.apparmor.service - Load AppArmor profiles managed internally by snapd... May 22 15:45:39 np0000001290 snapd-apparmor[1152]: main.go:143: No profiles to load May 22 15:45:39 np0000001290 systemd[1]: Finished snapd.apparmor.service - Load AppArmor profiles managed internally by snapd. ○ snapd.autoimport.service - Auto import assertions from block devices Loaded: loaded (/usr/lib/systemd/system/snapd.autoimport.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:44 UTC; 46min ago May 22 15:45:44 np0000001290 systemd[1]: snapd.autoimport.service - Auto import assertions from block devices was skipped because no trigger condition checks were met. ○ snapd.core-fixup.service - Automatically repair incorrect owner/permissions on core devices Loaded: loaded (/usr/lib/systemd/system/snapd.core-fixup.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:snap(1) May 22 15:45:44 np0000001290 systemd[1]: snapd.core-fixup.service - Automatically repair incorrect owner/permissions on core devices was skipped because no trigger condition checks were met. ○ snapd.failure.service - Failure handling of the snapd snap Loaded: loaded (/usr/lib/systemd/system/snapd.failure.service; static) Active: inactive (dead) ○ snapd.recovery-chooser-trigger.service - Wait for the Ubuntu Core chooser trigger Loaded: loaded (/usr/lib/systemd/system/snapd.recovery-chooser-trigger.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:44 UTC; 46min ago May 22 15:45:44 np0000001290 systemd[1]: snapd.recovery-chooser-trigger.service - Wait for the Ubuntu Core chooser trigger was skipped because of an unmet condition check (ConditionKernelCommandLine=snapd_recovery_mode). ● snapd.seeded.service - Wait until snapd is fully seeded Loaded: loaded (/usr/lib/systemd/system/snapd.seeded.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:44 UTC; 46min ago Main PID: 4882 (code=exited, status=0/SUCCESS) May 22 15:45:44 np0000001290 systemd[1]: Starting snapd.seeded.service - Wait until snapd is fully seeded... May 22 15:45:44 np0000001290 systemd[1]: Finished snapd.seeded.service - Wait until snapd is fully seeded. ○ snapd.service - Snap Daemon Loaded: loaded (/usr/lib/systemd/system/snapd.service; enabled; preset: enabled) Active: inactive (dead) since Fri 2026-05-22 15:45:52 UTC; 45min ago Duration: 8.006s TriggeredBy: ● snapd.socket Main PID: 4886 (code=exited, status=42) May 22 15:45:44 np0000001290 snapd[4886]: daemon.go:276: started snapd/2.73+ubuntu24.04 (series 16; classic) ubuntu/24.04 (amd64) linux/6.8.0-117-generic. May 22 15:45:44 np0000001290 snapd[4886]: daemon.go:370: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap) May 22 15:45:44 np0000001290 snapd[4886]: backends.go:70: AppArmor status: apparmor is enabled and all features are available May 22 15:45:44 np0000001290 snapd[4886]: backend.go:145: reloading profiles for snap-confine May 22 15:45:44 np0000001290 systemd[1]: Started snapd.service - Snap Daemon. May 22 15:45:49 np0000001290 snapd[4886]: daemon.go:556: gracefully waiting for running hooks May 22 15:45:49 np0000001290 snapd[4886]: daemon.go:558: done waiting for running hooks May 22 15:45:52 np0000001290 snapd[4886]: overlord.go:538: Released state lock file May 22 15:45:52 np0000001290 snapd[4886]: daemon stop requested to wait for socket activation May 22 15:45:52 np0000001290 systemd[1]: snapd.service: Deactivated successfully. ○ snapd.snap-repair.service - Automatically fetch and run repair assertions Loaded: loaded (/usr/lib/systemd/system/snapd.snap-repair.service; static) Active: inactive (dead) TriggeredBy: ○ snapd.snap-repair.timer Docs: man:snap(1) ○ snapd.system-shutdown.service - Ubuntu core (all-snaps) system shutdown helper setup service Loaded: loaded (/usr/lib/systemd/system/snapd.system-shutdown.service; enabled; preset: enabled) Active: inactive (dead) ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/usr/lib/systemd/system/ssh.service; disabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:46:28 UTC; 45min ago TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Main PID: 5168 (sshd) Tasks: 1 (limit: 27561) Memory: 4.3M () CGroup: /system.slice/ssh.service └─5168 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups" May 22 15:46:28 np0000001290 systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... May 22 15:46:28 np0000001290 sshd[5168]: Server listening on 0.0.0.0 port 22. May 22 15:46:28 np0000001290 sshd[5168]: Server listening on :: port 22. May 22 15:46:28 np0000001290 systemd[1]: Started ssh.service - OpenBSD Secure Shell server. May 22 15:46:29 np0000001290 sshd[5170]: Accepted publickey for ubuntu from 10.4.3.140 port 40616 ssh2: ED25519 SHA256:ZuVSgb3Wi8Kk0PUCLMFIh/91KQtAC+CdVUdaFz7DwiM May 22 15:46:29 np0000001290 sshd[5170]: pam_unix(sshd:session): session opened for user ubuntu(uid=1000) by ubuntu(uid=0) May 22 15:47:09 np0000001290 sshd[8483]: Accepted publickey for ubuntu from 172.17.24.95 port 44744 ssh2: RSA SHA256:XOedE2JuM9pXYa2B9jc7ipUso9pd17+Q+79EoI4pyfA May 22 15:47:09 np0000001290 sshd[8483]: pam_unix(sshd:session): session opened for user ubuntu(uid=1000) by ubuntu(uid=0) May 22 16:31:02 np0000001290 sshd[20085]: Accepted publickey for ubuntu from 172.17.24.95 port 40952 ssh2: RSA SHA256:XOedE2JuM9pXYa2B9jc7ipUso9pd17+Q+79EoI4pyfA May 22 16:31:02 np0000001290 sshd[20085]: pam_unix(sshd:session): session opened for user ubuntu(uid=1000) by ubuntu(uid=0) × storpool_abrtsync.service - storpool_abrtsync Loaded: loaded (/usr/lib/systemd/system/storpool_abrtsync.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Fri 2026-05-22 15:47:09 UTC; 44min ago Duration: 3.169s Process: 7991 ExecStart=/usr/sbin/storpool_abrtsync (code=exited, status=1/FAILURE) Process: 8499 ExecStopPost=/bin/rm -f /run/storpool_abrtsync.pid (code=exited, status=0/SUCCESS) Main PID: 7991 (code=exited, status=1/FAILURE) May 22 15:47:09 np0000001290 /usr/sbin/storpool_abrtsync.bin[8479]: /usr/lib/storpool/storpool_kdump exit status 0 May 22 15:47:09 np0000001290 storpool_abrtsync-loader[7991]: Child 8479: SP_RAUTH_TOKEN does not seem to be configured, please check... May 22 15:47:09 np0000001290 storpool_abrtsync-loader[7991]: Warning: SIGCHLD handler "DEFAULT" not defined. May 22 15:47:09 np0000001290 storpool_abrtsync[7991]: SIGCHLD handler "DEFAULT" not defined. May 22 15:47:09 np0000001290 storpool_abrtsync-loader[7991]: childPid:8479 finished with sret:256 May 22 15:47:09 np0000001290 storpool_abrtsync-loader[7991]: lost storpool_abrtsync.bin (pid:8479) exited with 1 May 22 15:47:09 np0000001290 storpool_abrtsync-loader[7991]: 3 crashes in 1800sec May 22 15:47:09 np0000001290 storpool_abrtsync-loader[7991]: Loader finished with Exit(1) May 22 15:47:09 np0000001290 systemd[1]: storpool_abrtsync.service: Main process exited, code=exited, status=1/FAILURE May 22 15:47:09 np0000001290 systemd[1]: storpool_abrtsync.service: Failed with result 'exit-code'. ● storpool_beacon.service - StorPool beacon service Loaded: loaded (/usr/lib/systemd/system/storpool_beacon.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:47:06 UTC; 44min ago Main PID: 7970 (storpool_beacon) Tasks: 3 (limit: 27561) CGroup: /storpool.slice/storpool-common.slice/storpool_beacon.service ├─ 7970 /usr/bin/perl /usr/sbin/storpool_beacon -- └─19896 /usr/sbin/storpool_beacon.bin -l -p /run/storpool_beacon.bin.pid "" -n 1 -t 60 -a b2p2.b -e 2 -W 6 May 22 16:31:40 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:41 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:42 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:43 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:44 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:45 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:46 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:47 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:48 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:49 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. ● storpool_block.service - StorPool block device client service Loaded: loaded (/usr/lib/systemd/system/storpool_block.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:47:06 UTC; 44min ago Main PID: 7971 (storpool_block) Tasks: 3 (limit: 27561) CGroup: /storpool.slice/storpool-common.slice/storpool_block.service ├─ 7971 /usr/bin/perl /usr/sbin/storpool_block -- └─19881 /usr/sbin/storpool_block.bin -l -p /run/storpool_block.bin.pid -b 0 -i 1 -a b2p2.b -N -W 6 May 22 16:30:17 np0000001290 storpool_block-loader[7971]: found /usr/sbin/storpool_block.bin May 22 16:30:17 np0000001290 storpool_block-loader[7971]: Runtime configuration: __ [run] __ kernelname = 6.8.0-117-generic __ libc_name = musl __ libc_ver = 1.2.1.4 __ May 22 16:30:17 np0000001290 storpool_block-loader[7971]: Starting 'storpool_block.bin' May 22 16:30:17 np0000001290 storpool_block-loader[7971]: created /var/spool/storpool/storpool_block.19881 May 22 16:30:17 np0000001290 storpool_block-loader[7971]: created /var/spool/storpool/storpool_block.19881/storpool.conf.d May 22 16:30:17 np0000001290 storpool_block-loader[19881]: exec: cgexec -g cpuset:storpool.slice/block -g memory:storpool.slice/common /usr/sbin/storpool_block.bin -l -p /run/storpool_block.bin.pid -b 0 -i 1 -a b2p2.b -N -W 6 May 22 16:30:17 np0000001290 storpool_block-loader[7971]: started childPid:19881 May 22 16:30:17 np0000001290 storpool_block[19881]: [info] Obtained time information from storpool_rdma: tscPerUsec 2395 May 22 16:30:17 np0000001290 storpool_block-loader[19882]: setAffinityProcCGroup cpus_rdma cgroups:-g cpuset:storpool.slice/rdma -g memory:storpool.slice/common pid:700 May 22 16:30:17 np0000001290 storpool_block[19881]: [info] Error: can't connect to beacon @ /var/run/storpool//beacon.sock. Will retry after 1 second. ● storpool_cgmove.service - Clean root cgroup from user processes Loaded: loaded (/usr/lib/systemd/system/storpool_cgmove.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:47:06 UTC; 44min ago Process: 7986 ExecStart=/usr/lib/storpool/storpool_cgmove (code=exited, status=0/SUCCESS) Main PID: 7986 (code=exited, status=0/SUCCESS) May 22 15:47:06 np0000001290 storpool_cgmove[7986]: executing: cgclassify -g cpuset:/system.slice 7986 May 22 15:47:06 np0000001290 storpool_cgmove[7986]: executing: cgclassify -g cpuset:/system.slice 7991 May 22 15:47:06 np0000001290 storpool_cgmove[7986]: executing: cgclassify -g cpuset:/system.slice 7992 May 22 15:47:06 np0000001290 storpool_cgmove[7986]: executing: cgclassify -g cpuset:/system.slice 7993 May 22 15:47:06 np0000001290 storpool_cgmove[7986]: executing: cgclassify -g cpuset:/system.slice 7994 May 22 15:47:06 np0000001290 storpool_cgmove[7986]: executing: cgclassify -g cpuset:/system.slice 8026 May 22 15:47:06 np0000001290 storpool_cgmove[8235]: Error changing group of pid 8026: No such process May 22 15:47:06 np0000001290 storpool_cgmove[7986]: executing: cgclassify -g cpuset:/system.slice 8027 May 22 15:47:06 np0000001290 storpool_cgmove[8236]: Error changing group of pid 8027: No such process May 22 15:47:06 np0000001290 systemd[1]: Finished storpool_cgmove.service - Clean root cgroup from user processes. ● storpool_controller.service - StorPool controller service Loaded: loaded (/usr/lib/systemd/system/storpool_controller.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:47:06 UTC; 44min ago Main PID: 7972 (storpool_contro) Tasks: 2 (limit: 27561) CGroup: /system.slice/storpool_controller.service ├─7972 /usr/bin/perl /usr/sbin/storpool_controller └─8089 /usr/sbin/storpool_controller.bin -l -p /run/storpool_controller.bin.pid -i 1 -A 192.168.10.5 -W 6 May 22 15:47:06 np0000001290 storpool_controller-loader[8089]: exec: cgexec -g cpuset:system.slice -g memory:system.slice /usr/sbin/storpool_controller.bin -l -p /run/storpool_controller.bin.pid -i 1 -A 192.168.10.5 -W 6 May 22 15:47:06 np0000001290 storpool_controller-loader[7972]: started childPid:8089 May 22 15:47:06 np0000001290 storpool_controller-loader[8090]: setAffinityProcCGroup cpus_rdma cgroups:-g cpuset:storpool.slice/rdma -g memory:storpool.slice/common pid:700 May 22 15:47:06 np0000001290 storpool_controller[8089]: [debug] Calibrating clock ... May 22 15:47:06 np0000001290 storpool_controller[8089]: [debug] TSC rate: 2395 MHz May 22 15:47:06 np0000001290 storpool_controller[8089]: [debug] random seed: 3454030393 May 22 15:47:06 np0000001290 storpool_controller[8089]: [info] Attempting connection to mgmt May 22 15:47:06 np0000001290 storpool_controller[8089]: [err] Could not send identification to mgmt, aborting connection May 22 15:47:07 np0000001290 storpool_controller[8089]: [info] Attempting connection to mgmt May 22 15:47:07 np0000001290 storpool_controller[8089]: [info] Connected to management ● storpool_dre.service - StorPool Disaster Recovery Engine Loaded: loaded (/usr/lib/systemd/system/storpool_dre.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 16:30:14 UTC; 1min 36s ago Main PID: 19827 (storpool_dre) Tasks: 1 (limit: 27561) Memory: 23.4M () CGroup: /system.slice/storpool_dre.service └─19827 /opt/storpool/python3/bin/python3 /usr/lib/storpool/storpool_dre May 22 16:30:14 np0000001290 systemd[1]: storpool_dre.service: Scheduled restart job, restart counter is at 4. May 22 16:30:14 np0000001290 systemd[1]: Started storpool_dre.service - StorPool Disaster Recovery Engine. May 22 16:30:29 np0000001290 storpool_dre[19827]: 2026-05-22 16:30:29 DEBUG storpool_dre[19827]: [OPS]: cannot list services: timed out ● storpool_gui.service - storpool_gui Loaded: loaded (/usr/lib/systemd/system/storpool_gui.service; enabled; preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2026-05-22 16:31:49 UTC; 739ms ago Process: 20656 ExecStart=/usr/lib/storpool/storpool_gui --staticdir /usr/lib/storpool/gui/root/dist --rootdir /usr/lib/storpool/gui/root (code=exited, status=1/FAILURE) Main PID: 20656 (code=exited, status=1/FAILURE) ● storpool_hugepages.service - StorPool hugepages reservation Loaded: loaded (/usr/lib/systemd/system/storpool_hugepages.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:47:05 UTC; 44min ago Process: 7922 ExecStart=/usr/sbin/storpool_hugepages -R (code=exited, status=0/SUCCESS) Main PID: 7922 (code=exited, status=0/SUCCESS) May 22 15:47:04 np0000001290 systemd[1]: Starting storpool_hugepages.service - StorPool hugepages reservation... May 22 15:47:05 np0000001290 /usr/sbin/storpool_hugepages[7922]: already have 292 (including 1(nvme phys) + 0(nvme disks)) hugepages on numa 0 (currently 292) May 22 15:47:05 np0000001290 systemd[1]: Finished storpool_hugepages.service - StorPool hugepages reservation. ● storpool_kdump.service - Gather diagnostic information after a kernel crash Loaded: loaded (/usr/lib/systemd/system/storpool_kdump.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:47:06 UTC; 44min ago Process: 7973 ExecStart=/usr/lib/storpool/storpool_kdump (code=exited, status=0/SUCCESS) Main PID: 7973 (code=exited, status=0/SUCCESS) May 22 15:47:06 np0000001290 systemd[1]: Starting storpool_kdump.service - Gather diagnostic information after a kernel crash... May 22 15:47:06 np0000001290 systemd[1]: Finished storpool_kdump.service - Gather diagnostic information after a kernel crash. × storpool_logd.service - The StorPool Logd Service Loaded: loaded (/usr/lib/systemd/system/storpool_logd.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Fri 2026-05-22 15:47:22 UTC; 44min ago Duration: 2.451s Process: 8787 ExecStart=/usr/sbin/storpool_logd (code=exited, status=1/FAILURE) Process: 8788 ExecStartPost=/bin/sh -c DIR=/sys/fs/cgroup/memory/system.slice/storpool_logd.service ; echo 100M | tee $DIR/memory.limit_in_bytes $DIR/memory.memsw.limit_in_bytes 1>/dev/null || exit 0 (code=exited, status=0/SUCCESS) Main PID: 8787 (code=exited, status=1/FAILURE) May 22 15:47:22 np0000001290 systemd[1]: storpool_logd.service: Scheduled restart job, restart counter is at 3. May 22 15:47:22 np0000001290 systemd[1]: storpool_logd.service: Start request repeated too quickly. May 22 15:47:22 np0000001290 systemd[1]: storpool_logd.service: Failed with result 'exit-code'. May 22 15:47:22 np0000001290 systemd[1]: Failed to start storpool_logd.service - The StorPool Logd Service. × storpool_mgmt.service - StorPool management service Loaded: loaded (/usr/lib/systemd/system/storpool_mgmt.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Fri 2026-05-22 16:30:13 UTC; 1min 36s ago Duration: 43min 7.235s Process: 7974 ExecStart=/usr/sbin/storpool_mgmt (code=exited, status=1/FAILURE) Process: 19815 ExecStopPost=/bin/rm -f /run/storpool_mgmt.pid (code=exited, status=0/SUCCESS) Main PID: 7974 (code=exited, status=1/FAILURE) May 22 16:30:13 np0000001290 storpool_mgmt-loader[7974]: Child 19785: Cannot find device "sp-api" May 22 16:30:13 np0000001290 storpool_mgmt[19785]: [err] Error: bind() fd:31 port:81 (Address not available) May 22 16:30:13 np0000001290 storpool_mgmt-loader[7974]: Child 19785: bind: No such file or directory May 22 16:30:13 np0000001290 storpool_mgmt[19800]: Cannot find device "sp-api" May 22 16:30:13 np0000001290 storpool_mgmt-loader[7974]: childPid:19785 finished with sret:512 May 22 16:30:13 np0000001290 storpool_mgmt-loader[7974]: lost storpool_mgmt.bin (pid:19785) exited with 2 May 22 16:30:13 np0000001290 storpool_mgmt-loader[7974]: 3 crashes in 1800sec May 22 16:30:13 np0000001290 storpool_mgmt-loader[7974]: Loader finished with Exit(1) May 22 16:30:13 np0000001290 systemd[1]: storpool_mgmt.service: Main process exited, code=exited, status=1/FAILURE May 22 16:30:13 np0000001290 systemd[1]: storpool_mgmt.service: Failed with result 'exit-code'. ● storpool_nvmed.service - StorPool nvmed service Loaded: loaded (/usr/lib/systemd/system/storpool_nvmed.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:47:05 UTC; 44min ago Main PID: 7926 (storpool_nvmed) Tasks: 2 (limit: 27561) CGroup: /storpool.slice/storpool-common.slice/storpool_nvmed.service ├─7926 /usr/bin/perl /usr/sbin/storpool_nvmed └─7948 /usr/sbin/storpool_nvmed.bin -l -p /run/storpool_nvmed.bin.pid -W 6 May 22 15:47:05 np0000001290 storpool_nvmed-loader[7926]: Runtime configuration: __ [run] __ kernelname = 6.8.0-117-generic __ libc_name = musl __ libc_ver = 1.2.1.4 __ May 22 15:47:05 np0000001290 storpool_nvmed-loader[7926]: Starting 'storpool_nvmed.bin' May 22 15:47:05 np0000001290 storpool_nvmed-loader[7926]: created /var/spool/storpool/storpool_nvmed.7948 May 22 15:47:05 np0000001290 storpool_nvmed-loader[7926]: created /var/spool/storpool/storpool_nvmed.7948/storpool.conf.d May 22 15:47:05 np0000001290 storpool_nvmed-loader[7948]: exec: cgexec -g cpuset:storpool.slice/beacon -g memory:storpool.slice/common /usr/sbin/storpool_nvmed.bin -l -p /run/storpool_nvmed.bin.pid -W 6 May 22 15:47:05 np0000001290 storpool_nvmed-loader[7926]: started childPid:7948 May 22 15:47:05 np0000001290 storpool_nvmed[7948]: [debug] Calibrating clock ... May 22 15:47:05 np0000001290 storpool_nvmed-loader[7949]: setAffinityProcCGroup cpus_rdma cgroups:-g cpuset:storpool.slice/rdma -g memory:storpool.slice/common pid:700 May 22 15:47:05 np0000001290 storpool_nvmed[7948]: [debug] TSC rate: 2395 MHz May 22 15:47:05 np0000001290 storpool_nvmed[7948]: [debug] random seed: 445069393 ● storpool_qos.service - Automatically update StorPool volumes QoS settings Loaded: loaded (/usr/lib/systemd/system/storpool_qos.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:47:06 UTC; 44min ago Main PID: 7992 (storpool_qos) Tasks: 1 (limit: 27561) Memory: 15.2M () CGroup: /system.slice/storpool_qos.service └─7992 /opt/storpool/python3/bin/python3 /usr/lib/storpool/storpool_qos daemon May 22 15:47:06 np0000001290 systemd[1]: Started storpool_qos.service - Automatically update StorPool volumes QoS settings. May 22 15:47:13 np0000001290 storpool_qos[7992]: The active API is now on our SP_OURID(1) ● storpool_server.service - StorPool server service Loaded: loaded (/usr/lib/systemd/system/storpool_server.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:47:06 UTC; 44min ago Main PID: 7993 (storpool_server) Tasks: 3 (limit: 27561) CGroup: /storpool.slice/storpool-common.slice/storpool_server.service ├─ 7993 /usr/bin/perl /usr/sbin/storpool_server -- └─19873 /usr/sbin/storpool_server.bin -l -p /run/storpool_server.bin.pid -b 0 -C 512 -N -i 1 -a b2p2.b -W 6 May 22 16:30:17 np0000001290 storpool_server-loader[19878]: setAffinityProcCGroup cpus_rdma cgroups:-g cpuset:storpool.slice/rdma -g memory:storpool.slice/common pid:700 May 22 16:30:17 np0000001290 storpool_server[19873]: [info] Obtained time information from storpool_rdma: tscPerUsec 2395 May 22 16:30:17 np0000001290 storpool_server[19873]: [notice] running as server 1 May 22 16:30:17 np0000001290 storpool_server-loader[7993]: Child 19873: Can't decode PCI from virtio2!(../../devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:1/block/sdb) at /usr/lib/storpool/storcli-helper.pl line 129. May 22 16:30:17 np0000001290 storpool_server-loader[7993]: Child 19873: Program '/usr/lib/storpool/storcli-helper.pl' (pid 19923) exited with non-zero status 255 May 22 16:30:17 np0000001290 storpool_server-loader[7993]: Child 19873: Can't decode PCI from virtio2!(../../devices/pci0000:00/0000:00:02.2/0000:04:00.0/virtio2/host0/target0:0:0/0:0:0:1/block/sdb) at /usr/lib/storpool/storcli-helper.pl line 129. May 22 16:30:17 np0000001290 storpool_server-loader[7993]: Child 19873: Program '/usr/lib/storpool/storcli-helper.pl' (pid 19927) exited with non-zero status 255 May 22 16:30:18 np0000001290 storpool_server-loader[7993]: Child 19873: Could not parse the hpssacli output: Could not run obtain the list of controllers: [Errno 2] No such file or directory: 'ssacli' May 22 16:30:18 np0000001290 storpool_server[19873]: [debug] task[0x1250b28] done /dev/sdb1: 111: QEMU_HARDDISK/ff1e347f-de2f-4737-ab60-052974138f0b May 22 16:30:18 np0000001290 storpool_server[19873]: [info] /dev/sdb1: adding as data disk 111 ○ storpool_server_1.service - StorPool server service Loaded: loaded (/usr/lib/systemd/system/storpool_server_1.service; disabled; preset: enabled) Active: inactive (dead) ○ storpool_server_2.service - StorPool server service Loaded: loaded (/usr/lib/systemd/system/storpool_server_2.service; disabled; preset: enabled) Active: inactive (dead) ○ storpool_server_3.service - StorPool server service Loaded: loaded (/usr/lib/systemd/system/storpool_server_3.service; disabled; preset: enabled) Active: inactive (dead) × storpool_stat.service - storpool_stat Loaded: loaded (/usr/lib/systemd/system/storpool_stat.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Fri 2026-05-22 15:47:09 UTC; 44min ago Duration: 3.664s Process: 7994 ExecStart=/usr/sbin/storpool_stat (code=exited, status=1/FAILURE) Process: 8580 ExecStopPost=/bin/rm -f /run/storpool_stat.pid (code=exited, status=0/SUCCESS) Main PID: 7994 (code=exited, status=1/FAILURE) May 22 15:47:09 np0000001290 storpool_stat-loader[8560]: exec: cgexec -g cpuset:system.slice -g memory:system.slice /usr/sbin/storpool_stat.bin -l -p /run/storpool_stat.bin.pid -W 6 May 22 15:47:09 np0000001290 storpool_stat-loader[7994]: started childPid:8560 May 22 15:47:09 np0000001290 storpool_stat-loader[8562]: setAffinityProcCGroup cpus_rdma cgroups:-g cpuset:storpool.slice/rdma -g memory:storpool.slice/common pid:700 May 22 15:47:09 np0000001290 /usr/sbin/storpool_stat.bin[8560]: File "/usr/sbin/storpool_stat.bin", line 33, in sys.exit(load_entry_point('splib', 'console_scripts', 'storpool_stat.bin')()) File "/opt/storpool/python3/lib/python3.8/site-packages/sp/tools/stat.py", line 1347, in main logger.exception("".join(traceback.format_stack())) Traceback (most recent call last): File "/opt/storpool/python3/lib/python3.8/site-packages/sp/tools/stat.py", line 1344, in main _main() File "/opt/storpool/python3/lib/python3.8/site-packages/sp/tools/stat.py", line 1281, in _main prepare_conf(cmd_args) File "/opt/storpool/python3/lib/python3.8/site-packages/sp/tools/stat.py", line 1168, in prepare_conf conf.rauth = cfg["SP_RAUTH_TOKEN"] File "/opt/storpool/python3/lib/python3.8/site-packages/storpool/spconfig.py", line 171, in __getitem__ return self._dict[key] KeyError: 'SP_RAUTH_TOKEN' May 22 15:47:09 np0000001290 storpool_stat-loader[7994]: childPid:8560 finished with sret:0 May 22 15:47:09 np0000001290 storpool_stat-loader[7994]: lost storpool_stat.bin (pid:8560) exited with 0 May 22 15:47:09 np0000001290 storpool_stat-loader[7994]: 3 crashes in 1800sec May 22 15:47:09 np0000001290 storpool_stat-loader[7994]: Loader finished with Exit(1) May 22 15:47:09 np0000001290 systemd[1]: storpool_stat.service: Main process exited, code=exited, status=1/FAILURE May 22 15:47:09 np0000001290 systemd[1]: storpool_stat.service: Failed with result 'exit-code'. ● storpool_volumecare.service - StorPool Volumecare Loaded: loaded (/usr/lib/systemd/system/storpool_volumecare.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 16:31:35 UTC; 14s ago Main PID: 20317 (storpool_volume) Tasks: 1 (limit: 27561) Memory: 15.7M () CGroup: /system.slice/storpool_volumecare.service └─20317 /opt/storpool/python3/bin/python3 /usr/lib/storpool/storpool_volumecare.py May 22 16:31:35 np0000001290 systemd[1]: storpool_volumecare.service: Scheduled restart job, restart counter is at 9. May 22 16:31:35 np0000001290 systemd[1]: Started storpool_volumecare.service - StorPool Volumecare. ○ sysstat-collect.service - system activity accounting tool Loaded: loaded (/usr/lib/systemd/system/sysstat-collect.service; static) Active: inactive (dead) since Fri 2026-05-22 16:30:00 UTC; 1min 49s ago TriggeredBy: ● sysstat-collect.timer Docs: man:sa1(8) Process: 19392 ExecStart=/usr/lib/sysstat/sa1 1 1 (code=exited, status=0/SUCCESS) Main PID: 19392 (code=exited, status=0/SUCCESS) May 22 16:30:00 np0000001290 systemd[1]: Starting sysstat-collect.service - system activity accounting tool... May 22 16:30:00 np0000001290 systemd[1]: sysstat-collect.service: Deactivated successfully. May 22 16:30:00 np0000001290 systemd[1]: Finished sysstat-collect.service - system activity accounting tool. ○ sysstat-summary.service - Generate a daily summary of process accounting Loaded: loaded (/usr/lib/systemd/system/sysstat-summary.service; static) Active: inactive (dead) TriggeredBy: ● sysstat-summary.timer Docs: man:sa2(8) ● sysstat.service - Resets System Activity Logs Loaded: loaded (/usr/lib/systemd/system/sysstat.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:sa1(8) man:sadc(8) man:sar(1) Main PID: 4888 (code=exited, status=0/SUCCESS) May 22 15:45:44 np0000001290 systemd[1]: Starting sysstat.service - Resets System Activity Logs... May 22 15:45:44 np0000001290 systemd[1]: Finished sysstat.service - Resets System Activity Logs. ○ systemd-ask-password-console.service - Dispatch Password Requests to Console Loaded: loaded (/usr/lib/systemd/system/systemd-ask-password-console.service; static) Active: inactive (dead) TriggeredBy: ● systemd-ask-password-console.path Docs: man:systemd-ask-password-console.service(8) ○ systemd-ask-password-plymouth.service - Forward Password Requests to Plymouth Loaded: loaded (/usr/lib/systemd/system/systemd-ask-password-plymouth.service; static) Active: inactive (dead) TriggeredBy: ○ systemd-ask-password-plymouth.path Docs: http://www.freedesktop.org/wiki/Software/systemd/PasswordAgents ○ systemd-ask-password-wall.service - Forward Password Requests to Wall Loaded: loaded (/usr/lib/systemd/system/systemd-ask-password-wall.service; static) Active: inactive (dead) TriggeredBy: ● systemd-ask-password-wall.path Docs: man:systemd-ask-password-wall.service(8) ○ systemd-battery-check.service - Check battery level during early boot Loaded: loaded (/usr/lib/systemd/system/systemd-battery-check.service; static) Active: inactive (dead) Docs: man:systemd-battery-check.service(8) ● systemd-binfmt.service - Set Up Additional Binary Formats Loaded: loaded (/usr/lib/systemd/system/systemd-binfmt.service; static) Active: active (exited) since Fri 2026-05-22 15:45:39 UTC; 46min ago Docs: man:systemd-binfmt.service(8) man:binfmt.d(5) https://docs.kernel.org/admin-guide/binfmt-misc.html https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Main PID: 1018 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting systemd-binfmt.service - Set Up Additional Binary Formats... May 22 15:45:39 np0000001290 systemd[1]: Finished systemd-binfmt.service - Set Up Additional Binary Formats. ○ systemd-bsod.service - Displays emergency message in full screen. Loaded: loaded (/usr/lib/systemd/system/systemd-bsod.service; static) Active: inactive (dead) Docs: man:systemd-bsod.service(8) ○ systemd-firstboot.service - First Boot Wizard Loaded: loaded (/usr/lib/systemd/system/systemd-firstboot.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-firstboot(1) May 22 15:45:38 np0000001290 systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes). ○ systemd-fsck-root.service - File System Check on Root Device Loaded: loaded (/usr/lib/systemd/system/systemd-fsck-root.service; enabled-runtime; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-fsck-root.service(8) ● systemd-fsck@dev-disk-by\x2dlabel-BOOT.service - File System Check on /dev/disk/by-label/BOOT Loaded: loaded (/usr/lib/systemd/system/systemd-fsck@.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-fsck@.service(8) Main PID: 893 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting systemd-fsck@dev-disk-by\x2dlabel-BOOT.service - File System Check on /dev/disk/by-label/BOOT... May 22 15:45:38 np0000001290 systemd-fsck[979]: BOOT: clean, 604/58496 files, 42348/233728 blocks May 22 15:45:38 np0000001290 systemd[1]: Finished systemd-fsck@dev-disk-by\x2dlabel-BOOT.service - File System Check on /dev/disk/by-label/BOOT. ● systemd-fsck@dev-disk-by\x2dlabel-UEFI.service - File System Check on /dev/disk/by-label/UEFI Loaded: loaded (/usr/lib/systemd/system/systemd-fsck@.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-fsck@.service(8) Main PID: 943 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting systemd-fsck@dev-disk-by\x2dlabel-UEFI.service - File System Check on /dev/disk/by-label/UEFI... May 22 15:45:38 np0000001290 systemd-fsck[993]: fsck.fat 4.2 (2021-01-31) May 22 15:45:38 np0000001290 systemd-fsck[993]: /dev/sda15: 12 files, 12499/213663 clusters May 22 15:45:38 np0000001290 systemd[1]: Finished systemd-fsck@dev-disk-by\x2dlabel-UEFI.service - File System Check on /dev/disk/by-label/UEFI. ○ systemd-fsckd.service - File System Check Daemon to report status Loaded: loaded (/usr/lib/systemd/system/systemd-fsckd.service; static) Active: inactive (dead) since Fri 2026-05-22 15:46:08 UTC; 45min ago Duration: 30.063s TriggeredBy: ● systemd-fsckd.socket Docs: man:systemd-fsckd.service(8) Main PID: 952 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Started systemd-fsckd.service - File System Check Daemon to report status. May 22 15:46:08 np0000001290 systemd[1]: systemd-fsckd.service: Deactivated successfully. ○ systemd-hibernate-resume.service - Resume from hibernation Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate-resume.service; static) Active: inactive (dead) Docs: man:systemd-hibernate-resume.service(8) ○ systemd-hibernate.service - System Hibernate Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; static) Active: inactive (dead) Docs: man:systemd-hibernate.service(8) ○ systemd-hwdb-update.service - Rebuild Hardware Database Loaded: loaded (/usr/lib/systemd/system/systemd-hwdb-update.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:hwdb(7) man:systemd-hwdb(8) May 22 15:45:38 np0000001290 systemd[1]: systemd-hwdb-update.service - Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc). ○ systemd-hybrid-sleep.service - System Hybrid Suspend+Hibernate Loaded: loaded (/usr/lib/systemd/system/systemd-hybrid-sleep.service; static) Active: inactive (dead) Docs: man:systemd-hybrid-sleep.service(8) ○ systemd-initctl.service - initctl Compatibility Daemon Loaded: loaded (/usr/lib/systemd/system/systemd-initctl.service; static) Active: inactive (dead) TriggeredBy: ● systemd-initctl.socket Docs: man:systemd-initctl.service(8) ○ systemd-journal-catalog-update.service - Rebuild Journal Catalog Loaded: loaded (/usr/lib/systemd/system/systemd-journal-catalog-update.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-journald.service(8) man:journald.conf(5) May 22 15:45:38 np0000001290 systemd[1]: systemd-journal-catalog-update.service - Rebuild Journal Catalog was skipped because of an unmet condition check (ConditionNeedsUpdate=/var). ● systemd-journal-flush.service - Flush Journal to Persistent Storage Loaded: loaded (/usr/lib/systemd/system/systemd-journal-flush.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Main PID: 569 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Persistent Storage... May 22 15:45:38 np0000001290 systemd[1]: Finished systemd-journal-flush.service - Flush Journal to Persistent Storage. ● systemd-journald.service - Journal Service Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static) Drop-In: /usr/lib/systemd/system/systemd-journald.service.d └─nice.conf Active: active (running) since Fri 2026-05-22 15:45:38 UTC; 46min ago TriggeredBy: ● systemd-journald-dev-log.socket ● systemd-journald.socket ○ systemd-journald-audit.socket Docs: man:systemd-journald.service(8) man:journald.conf(5) Main PID: 497 (systemd-journal) Status: "Processing requests..." Tasks: 1 (limit: 27561) FD Store: 22 (limit: 4224) Memory: 33.9M () CGroup: /system.slice/systemd-journald.service └─497 /usr/lib/systemd/systemd-journald May 22 15:45:38 np0000001290 systemd-journald[497]: Collecting audit messages is disabled. May 22 15:45:38 np0000001290 systemd-journald[497]: Journal started May 22 15:45:38 np0000001290 systemd-journald[497]: Runtime Journal (/run/log/journal/3a7da1302af14cfbb9b1f2a2906f9d66) is 8.0M, max 64.0M, 56.0M free. May 22 15:45:38 np0000001290 systemd-journald[497]: Time spent on flushing to /var/log/journal/3a7da1302af14cfbb9b1f2a2906f9d66 is 38.707ms for 1003 entries. May 22 15:45:38 np0000001290 systemd-journald[497]: System Journal (/var/log/journal/3a7da1302af14cfbb9b1f2a2906f9d66) is 31.0M, max 4.0G, 3.9G free. May 22 15:45:38 np0000001290 systemd-journald[497]: Received client request to flush runtime journal. May 22 15:45:38 np0000001290 systemd-journald[497]: /var/log/journal/3a7da1302af14cfbb9b1f2a2906f9d66/system.journal: Journal file uses a different sequence number ID, rotating. May 22 15:45:38 np0000001290 systemd-journald[497]: Rotating system journal. May 22 15:46:29 np0000001290 systemd-journald[497]: /var/log/journal/3a7da1302af14cfbb9b1f2a2906f9d66/user-1000.journal: Journal file uses a different sequence number ID, rotating. Notice: journal has been rotated since unit was started, output may be incomplete. ● systemd-logind.service - User Login Management Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static) Drop-In: /usr/lib/systemd/system/systemd-logind.service.d └─dbus.conf Active: active (running) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:sd-login(3) man:systemd-logind.service(8) man:logind.conf(5) man:org.freedesktop.login1(5) Main PID: 4889 (systemd-logind) Status: "Processing requests..." Tasks: 1 (limit: 27561) FD Store: 0 (limit: 512) Memory: 1.7M () CGroup: /system.slice/systemd-logind.service └─4889 /usr/lib/systemd/systemd-logind May 22 15:45:44 np0000001290 systemd-logind[4889]: Watching system buttons on /dev/input/event0 (Power Button) May 22 15:45:44 np0000001290 systemd-logind[4889]: Watching system buttons on /dev/input/event1 (AT Translated Set 2 keyboard) May 22 15:45:44 np0000001290 systemd-logind[4889]: New seat seat0. May 22 15:45:44 np0000001290 systemd[1]: Started systemd-logind.service - User Login Management. May 22 15:46:29 np0000001290 systemd-logind[4889]: New session 2 of user ubuntu. May 22 15:47:09 np0000001290 systemd-logind[4889]: New session 5 of user ubuntu. May 22 15:48:06 np0000001290 systemd-logind[4889]: Session 2 logged out. Waiting for processes to exit. May 22 15:48:06 np0000001290 systemd-logind[4889]: Removed session 2. May 22 15:48:11 np0000001290 systemd-logind[4889]: Session 5 logged out. Waiting for processes to exit. May 22 16:31:02 np0000001290 systemd-logind[4889]: New session 67 of user ubuntu. ○ systemd-machine-id-commit.service - Commit a transient machine-id on disk Loaded: loaded (/usr/lib/systemd/system/systemd-machine-id-commit.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-machine-id-commit.service(8) May 22 15:45:38 np0000001290 systemd[1]: systemd-machine-id-commit.service - Commit a transient machine-id on disk was skipped because of an unmet condition check (ConditionPathIsMountPoint=/etc/machine-id). ● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Main PID: 529 (code=exited, status=0/SUCCESS) ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/usr/lib/systemd/system/systemd-networkd-wait-online.service; enabled; preset: enabled) Drop-In: /run/systemd/system/systemd-networkd-wait-online.service.d └─10-netplan.conf Active: active (exited) since Fri 2026-05-22 15:45:41 UTC; 46min ago Docs: man:systemd-networkd-wait-online.service(8) Main PID: 3020 (code=exited, status=0/SUCCESS) May 22 15:45:39 np0000001290 systemd[1]: Starting systemd-networkd-wait-online.service - Wait for Network to be Configured... May 22 15:45:41 np0000001290 systemd[1]: Finished systemd-networkd-wait-online.service - Wait for Network to be Configured. ● systemd-networkd.service - Network Configuration Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:39 UTC; 46min ago TriggeredBy: ● systemd-networkd.socket Docs: man:systemd-networkd.service(8) man:org.freedesktop.network1(5) Main PID: 1179 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 27561) FD Store: 0 (limit: 512) Memory: 3.2M () CGroup: /system.slice/systemd-networkd.service └─1179 /usr/lib/systemd/systemd-networkd May 22 15:45:41 np0000001290 systemd-networkd[1179]: sp-api: Gained IPv6LL May 22 16:30:09 np0000001290 systemd-networkd[1179]: sp-api: Link DOWN May 22 16:30:09 np0000001290 systemd-networkd[1179]: sp-api: Lost carrier May 22 16:30:09 np0000001290 systemd-networkd[1179]: sp-api: DHCPv6 lease lost May 22 16:30:11 np0000001290 systemd-networkd[1179]: sp0: Link DOWN May 22 16:30:11 np0000001290 systemd-networkd[1179]: sp0: Lost carrier May 22 16:30:11 np0000001290 systemd-networkd[1179]: sp0: DHCPv6 lease lost May 22 16:30:13 np0000001290 systemd-networkd[1179]: sp1: Link DOWN May 22 16:30:13 np0000001290 systemd-networkd[1179]: sp1: Lost carrier May 22 16:30:13 np0000001290 systemd-networkd[1179]: sp1: DHCPv6 lease lost ○ systemd-pcrmachine.service - TPM2 PCR Machine ID Measurement Loaded: loaded (/usr/lib/systemd/system/systemd-pcrmachine.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-pcrmachine.service(8) ○ systemd-pcrphase-initrd.service - TPM2 PCR Barrier (initrd) Loaded: loaded (/usr/lib/systemd/system/systemd-pcrphase-initrd.service; static) Active: inactive (dead) Docs: man:systemd-pcrphase-initrd.service(8) ○ systemd-pcrphase-sysinit.service - TPM2 PCR Barrier (Initialization) Loaded: loaded (/usr/lib/systemd/system/systemd-pcrphase-sysinit.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:42 UTC; 46min ago Docs: man:systemd-pcrphase-sysinit.service(8) May 22 15:45:42 np0000001290 systemd[1]: systemd-pcrphase-sysinit.service - TPM2 PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionSecurity=measured-uki). ○ systemd-pcrphase.service - TPM2 PCR Barrier (User) Loaded: loaded (/usr/lib/systemd/system/systemd-pcrphase.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:systemd-pcrphase.service(8) May 22 15:45:44 np0000001290 systemd[1]: systemd-pcrphase.service - TPM2 PCR Barrier (User) was skipped because of an unmet condition check (ConditionSecurity=measured-uki). ○ systemd-pstore.service - Platform Persistent Storage Archival Loaded: loaded (/usr/lib/systemd/system/systemd-pstore.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-pstore(8) May 22 15:45:38 np0000001290 systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). ○ systemd-quotacheck.service - File System Quota Check Loaded: loaded (/usr/lib/systemd/system/systemd-quotacheck.service; static) Active: inactive (dead) Docs: man:systemd-quotacheck.service(8) ● systemd-random-seed.service - Load/Save OS Random Seed Loaded: loaded (/usr/lib/systemd/system/systemd-random-seed.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-random-seed.service(8) man:random(4) Main PID: 570 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting systemd-random-seed.service - Load/Save OS Random Seed... May 22 15:45:38 np0000001290 systemd[1]: Finished systemd-random-seed.service - Load/Save OS Random Seed. ● systemd-remount-fs.service - Remount Root and Kernel File Systems Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; enabled-runtime; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-remount-fs.service(8) https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Main PID: 530 (code=exited, status=0/SUCCESS) ○ systemd-repart.service - Repartition Root Disk Loaded: loaded (/usr/lib/systemd/system/systemd-repart.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-repart.service(8) May 22 15:45:38 np0000001290 systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met. ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:39 UTC; 46min ago Docs: man:systemd-resolved.service(8) man:org.freedesktop.resolve1(5) https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Main PID: 1138 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 27561) Memory: 4.8M () CGroup: /system.slice/systemd-resolved.service └─1138 /usr/lib/systemd/systemd-resolved May 22 15:45:39 np0000001290 systemd-resolved[1138]: Positive Trust Anchors: May 22 15:45:39 np0000001290 systemd-resolved[1138]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d May 22 15:45:39 np0000001290 systemd-resolved[1138]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 170.0.0.192.in-addr.arpa 171.0.0.192.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa ipv4only.arpa corp home internal intranet lan local private test May 22 15:45:39 np0000001290 systemd-resolved[1138]: Using system hostname 'np0000001290'. May 22 15:45:39 np0000001290 systemd[1]: Started systemd-resolved.service - Network Name Resolution. May 22 15:45:39 np0000001290 systemd-resolved[1138]: Under memory pressure, flushing caches. May 22 15:45:39 np0000001290 systemd-resolved[1138]: Flushed all caches. May 22 15:45:44 np0000001290 systemd-resolved[1138]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 10.2.1.254. May 22 15:46:31 np0000001290 systemd-resolved[1138]: Under memory pressure, flushing caches. May 22 15:46:31 np0000001290 systemd-resolved[1138]: Flushed all caches. ○ systemd-rfkill.service - Load/Save RF Kill Switch Status Loaded: loaded (/usr/lib/systemd/system/systemd-rfkill.service; static) Active: inactive (dead) TriggeredBy: ● systemd-rfkill.socket Docs: man:systemd-rfkill.service(8) ○ systemd-soft-reboot.service - Reboot System Userspace Loaded: loaded (/usr/lib/systemd/system/systemd-soft-reboot.service; static) Active: inactive (dead) Docs: man:systemd-soft-reboot.service(8) ○ systemd-suspend-then-hibernate.service - System Suspend then Hibernate Loaded: loaded (/usr/lib/systemd/system/systemd-suspend-then-hibernate.service; static) Active: inactive (dead) Docs: man:systemd-suspend-then-hibernate.service(8) ○ systemd-suspend.service - System Suspend Loaded: loaded (/usr/lib/systemd/system/systemd-suspend.service; static) Active: inactive (dead) Docs: man:systemd-suspend.service(8) ● systemd-sysctl.service - Apply Kernel Variables Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-sysctl.service(8) man:sysctl.d(5) Main PID: 572 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables... May 22 15:45:38 np0000001290 systemd[1]: Finished systemd-sysctl.service - Apply Kernel Variables. ○ systemd-sysext.service - Merge System Extension Images into /usr/ and /opt/ Loaded: loaded (/usr/lib/systemd/system/systemd-sysext.service; disabled; preset: enabled) Active: inactive (dead) Docs: man:systemd-sysext.service(8) ○ systemd-sysusers.service - Create System Users Loaded: loaded (/usr/lib/systemd/system/systemd-sysusers.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:sysusers.d(5) man:systemd-sysusers.service(8) May 22 15:45:38 np0000001290 systemd[1]: systemd-sysusers.service - Create System Users was skipped because no trigger condition checks were met. ○ systemd-tmpfiles-clean.service - Cleanup of Temporary Directories Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-clean.service; static) Active: inactive (dead) since Fri 2026-05-22 16:00:35 UTC; 31min ago TriggeredBy: ● systemd-tmpfiles-clean.timer Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 12256 ExecStart=systemd-tmpfiles --clean (code=exited, status=0/SUCCESS) Main PID: 12256 (code=exited, status=0/SUCCESS) May 22 16:00:35 np0000001290 systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... May 22 16:00:35 np0000001290 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. May 22 16:00:35 np0000001290 systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. ● systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup-dev-early.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Main PID: 573 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully... May 22 15:45:38 np0000001290 systemd[1]: Finished systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully. ● systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup-dev.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Main PID: 585 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev... May 22 15:45:38 np0000001290 systemd[1]: Finished systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev. ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Main PID: 1021 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting systemd-tmpfiles-setup.service - Create Volatile Files and Directories... May 22 15:45:38 np0000001290 systemd[1]: Finished systemd-tmpfiles-setup.service - Create Volatile Files and Directories. ○ systemd-tpm2-setup-early.service - TPM2 SRK Setup (Early) Loaded: loaded (/usr/lib/systemd/system/systemd-tpm2-setup-early.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-tpm2-setup.service(8) ○ systemd-tpm2-setup.service - TPM2 SRK Setup Loaded: loaded (/usr/lib/systemd/system/systemd-tpm2-setup.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-tpm2-setup.service(8) May 22 15:45:38 np0000001290 systemd[1]: systemd-tpm2-setup.service - TPM2 SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki). ○ systemd-udev-settle.service - Wait for udev To Complete Device Initialization Loaded: loaded (/usr/lib/systemd/system/systemd-udev-settle.service; static) Active: inactive (dead) Docs: man:systemd-udev-settle.service(8) ● systemd-udev-trigger.service - Coldplug All udev Devices Loaded: loaded (/usr/lib/systemd/system/systemd-udev-trigger.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:udev(7) man:systemd-udevd.service(8) Main PID: 531 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Finished systemd-udev-trigger.service - Coldplug All udev Devices. ● systemd-udevd.service - Rule-based Manager for Device Events and Files Loaded: loaded (/usr/lib/systemd/system/systemd-udevd.service; static) Drop-In: /usr/lib/systemd/system/systemd-udevd.service.d └─syscall-architecture.conf Active: active (running) since Fri 2026-05-22 15:45:38 UTC; 46min ago TriggeredBy: ● systemd-udevd-control.socket ● systemd-udevd-kernel.socket Docs: man:systemd-udevd.service(8) man:udev(7) Main PID: 590 (systemd-udevd) Status: "Processing with 40 children at max" Tasks: 1 Memory: 21.3M () CGroup: /system.slice/systemd-udevd.service └─udev └─590 /usr/lib/systemd/systemd-udevd May 22 15:45:38 np0000001290 (udev-worker)[598]: enp9s0: Could not set WakeOnLan to off, ignoring: Operation not supported May 22 15:45:38 np0000001290 (udev-worker)[598]: enp9s0: Could not set Alias=, MACAddress=/MACAddressPolicy=, TransmitQueues=, ReceiveQueues=, TransmitQueueLength=, MTUBytes=, GenericSegmentOffloadMaxBytes= or GenericSegmentOffloadMaxSegments=, ignoring: Invalid argument May 22 15:45:38 np0000001290 (udev-worker)[605]: enp7s0: Could not set WakeOnLan to off, ignoring: Operation not supported May 22 15:45:38 np0000001290 (udev-worker)[605]: enp7s0: Could not set Alias=, MACAddress=/MACAddressPolicy=, TransmitQueues=, ReceiveQueues=, TransmitQueueLength=, MTUBytes=, GenericSegmentOffloadMaxBytes= or GenericSegmentOffloadMaxSegments=, ignoring: Invalid argument May 22 15:45:38 np0000001290 (udev-worker)[598]: sp1: Could not set WakeOnLan to off, ignoring: Operation not supported May 22 15:45:38 np0000001290 (udev-worker)[598]: sp1: Could not set Alias=, MACAddress=/MACAddressPolicy=, TransmitQueues=, ReceiveQueues=, TransmitQueueLength=, MTUBytes=, GenericSegmentOffloadMaxBytes= or GenericSegmentOffloadMaxSegments=, ignoring: Invalid argument May 22 15:45:38 np0000001290 (udev-worker)[613]: sp0: Could not set WakeOnLan to off, ignoring: Operation not supported May 22 15:45:38 np0000001290 (udev-worker)[613]: sp0: Could not set Alias=, MACAddress=/MACAddressPolicy=, TransmitQueues=, ReceiveQueues=, TransmitQueueLength=, MTUBytes=, GenericSegmentOffloadMaxBytes= or GenericSegmentOffloadMaxSegments=, ignoring: Invalid argument May 22 15:45:38 np0000001290 (udev-worker)[652]: sp-api: Could not set WakeOnLan to off, ignoring: Operation not supported May 22 15:45:38 np0000001290 (udev-worker)[652]: sp-api: Could not set Alias=, MACAddress=/MACAddressPolicy=, TransmitQueues=, ReceiveQueues=, TransmitQueueLength=, MTUBytes=, GenericSegmentOffloadMaxBytes= or GenericSegmentOffloadMaxSegments=, ignoring: Invalid argument ○ systemd-update-done.service - Update is Completed Loaded: loaded (/usr/lib/systemd/system/systemd-update-done.service; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-update-done.service(8) May 22 15:45:38 np0000001290 systemd[1]: systemd-update-done.service - Update is Completed was skipped because no trigger condition checks were met. ○ systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP Loaded: loaded (/usr/lib/systemd/system/systemd-update-utmp-runlevel.service; static) Active: inactive (dead) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:systemd-update-utmp-runlevel.service(8) man:utmp(5) Main PID: 5115 (code=exited, status=0/SUCCESS) May 22 15:45:44 np0000001290 systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP... May 22 15:45:44 np0000001290 systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully. May 22 15:45:44 np0000001290 systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP. ● systemd-update-utmp.service - Record System Boot/Shutdown in UTMP Loaded: loaded (/usr/lib/systemd/system/systemd-update-utmp.service; static) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-update-utmp.service(8) man:utmp(5) Main PID: 1146 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP... May 22 15:45:38 np0000001290 systemd[1]: Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP. ● systemd-user-sessions.service - Permit User Sessions Loaded: loaded (/usr/lib/systemd/system/systemd-user-sessions.service; static) Active: active (exited) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:systemd-user-sessions.service(8) Main PID: 4931 (code=exited, status=0/SUCCESS) May 22 15:45:44 np0000001290 systemd[1]: Starting systemd-user-sessions.service - Permit User Sessions... May 22 15:45:44 np0000001290 systemd[1]: Finished systemd-user-sessions.service - Permit User Sessions. ○ tpm-udev.service - Handle dynamically added tpm devices Loaded: loaded (/usr/lib/systemd/system/tpm-udev.service; static) Active: inactive (dead) TriggeredBy: ○ tpm-udev.path ○ ua-reboot-cmds.service - Ubuntu Pro reboot cmds Loaded: loaded (/usr/lib/systemd/system/ua-reboot-cmds.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:44 UTC; 46min ago May 22 15:45:44 np0000001290 systemd[1]: ua-reboot-cmds.service - Ubuntu Pro reboot cmds was skipped because of an unmet condition check (ConditionPathExists=/var/lib/ubuntu-advantage/private/machine-token.json). ○ ua-timer.service - Ubuntu Pro Timer for running repeated jobs Loaded: loaded (/usr/lib/systemd/system/ua-timer.service; static) Active: inactive (dead) TriggeredBy: ○ ua-timer.timer ○ ubuntu-advantage.service - Ubuntu Pro Background Auto Attach Loaded: loaded (/usr/lib/systemd/system/ubuntu-advantage.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:ubuntu-advantage https://ubuntu.com/advantage May 22 15:45:44 np0000001290 systemd[1]: ubuntu-advantage.service - Ubuntu Pro Background Auto Attach was skipped because no trigger condition checks were met. ● udisks2.service - Disk Manager Loaded: loaded (/usr/lib/systemd/system/udisks2.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:udisks(8) Main PID: 4892 (udisksd) Tasks: 6 (limit: 27561) Memory: 7.5M () CGroup: /system.slice/udisks2.service └─4892 /usr/libexec/udisks2/udisksd May 22 15:45:44 np0000001290 systemd[1]: Starting udisks2.service - Disk Manager... May 22 15:45:44 np0000001290 udisksd[4892]: udisks daemon version 2.10.1 starting May 22 15:45:44 np0000001290 udisksd[4892]: Acquired the name org.freedesktop.UDisks2 on the system message bus May 22 15:45:44 np0000001290 systemd[1]: Started udisks2.service - Disk Manager. ● ufw.service - Uncomplicated firewall Loaded: loaded (/usr/lib/systemd/system/ufw.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:ufw(8) Main PID: 1024 (code=exited, status=0/SUCCESS) May 22 15:45:38 np0000001290 systemd[1]: Starting ufw.service - Uncomplicated firewall... May 22 15:45:38 np0000001290 systemd[1]: Finished ufw.service - Uncomplicated firewall. × unbound-resolvconf.service - Unbound asyncronous resolvconf update helper Loaded: loaded (/usr/lib/systemd/system/unbound-resolvconf.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Fri 2026-05-22 15:45:44 UTC; 46min ago Duration: 24ms Main PID: 5015 (code=exited, status=1/FAILURE) May 22 15:45:44 np0000001290 systemd[1]: Started unbound-resolvconf.service - Unbound asyncronous resolvconf update helper. May 22 15:45:44 np0000001290 resolvconf[5031]: Dropped protocol specifier '.unbound' from 'lo.unbound'. Using 'lo' (ifindex=1). May 22 15:45:44 np0000001290 resolvconf[5031]: Failed to set DNS configuration: Link lo is loopback device. May 22 15:45:44 np0000001290 systemd[1]: unbound-resolvconf.service: Main process exited, code=exited, status=1/FAILURE May 22 15:45:44 np0000001290 systemd[1]: unbound-resolvconf.service: Failed with result 'exit-code'. ● unbound.service - Unbound DNS server Loaded: loaded (/usr/lib/systemd/system/unbound.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:unbound(8) Main PID: 4951 (unbound) Tasks: 1 (limit: 27561) Memory: 14.4M () CGroup: /system.slice/unbound.service └─4951 /usr/sbin/unbound -d -p May 22 15:45:44 np0000001290 systemd[1]: Starting unbound.service - Unbound DNS server... May 22 15:45:44 np0000001290 (unbound)[4951]: unbound.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_OPTS May 22 15:45:44 np0000001290 unbound[4951]: [4951:0] notice: init module 0: subnetcache May 22 15:45:44 np0000001290 unbound[4951]: [4951:0] notice: init module 1: validator May 22 15:45:44 np0000001290 unbound[4951]: [4951:0] notice: init module 2: iterator May 22 15:45:44 np0000001290 unbound[4951]: [4951:0] info: start of service (unbound 1.19.2). May 22 15:45:44 np0000001290 systemd[1]: Started unbound.service - Unbound DNS server. ○ update-notifier-download.service - Download data for packages that failed at package install time Loaded: loaded (/usr/lib/systemd/system/update-notifier-download.service; static) Active: inactive (dead) since Fri 2026-05-22 15:50:38 UTC; 41min ago TriggeredBy: ● update-notifier-download.timer Process: 9678 ExecStart=/usr/lib/update-notifier/package-data-downloader (code=exited, status=0/SUCCESS) Main PID: 9678 (code=exited, status=0/SUCCESS) May 22 15:50:38 np0000001290 systemd[1]: Starting update-notifier-download.service - Download data for packages that failed at package install time... May 22 15:50:38 np0000001290 systemd[1]: update-notifier-download.service: Deactivated successfully. May 22 15:50:38 np0000001290 systemd[1]: Finished update-notifier-download.service - Download data for packages that failed at package install time. ○ update-notifier-motd.service - Check to see whether there is a new version of Ubuntu available Loaded: loaded (/usr/lib/systemd/system/update-notifier-motd.service; static) Active: inactive (dead) TriggeredBy: ● update-notifier-motd.timer ● user-runtime-dir@1000.service - User Runtime Directory /run/user/1000 Loaded: loaded (/usr/lib/systemd/system/user-runtime-dir@.service; static) Active: active (exited) since Fri 2026-05-22 15:46:29 UTC; 45min ago Docs: man:user@.service(5) Main PID: 5172 (code=exited, status=0/SUCCESS) May 22 15:46:29 np0000001290 systemd[1]: Starting user-runtime-dir@1000.service - User Runtime Directory /run/user/1000... May 22 15:46:29 np0000001290 systemd[1]: Finished user-runtime-dir@1000.service - User Runtime Directory /run/user/1000. ● user@1000.service - User Manager for UID 1000 Loaded: loaded (/usr/lib/systemd/system/user@.service; static) Drop-In: /usr/lib/systemd/system/user@.service.d └─10-login-barrier.conf, timeout.conf Active: active (running) since Fri 2026-05-22 15:46:29 UTC; 45min ago Docs: man:user@.service(5) Main PID: 5176 (systemd) Status: "Ready." Tasks: 2 Memory: 3.1M () CGroup: /user.slice/user-1000.slice/user@1000.service └─init.scope ├─5176 /usr/lib/systemd/systemd --user └─5177 "(sd-pam)" May 22 15:46:29 np0000001290 systemd[5176]: Listening on pk-debconf-helper.socket - debconf communication socket. May 22 15:46:29 np0000001290 systemd[5176]: Listening on snapd.session-agent.socket - REST API socket for snapd user session agent. May 22 15:46:29 np0000001290 systemd[5176]: Listening on dbus.socket - D-Bus User Message Bus Socket. May 22 15:46:29 np0000001290 systemd[5176]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation). May 22 15:46:29 np0000001290 systemd[5176]: Reached target sockets.target - Sockets. May 22 15:46:29 np0000001290 systemd[5176]: Reached target basic.target - Basic System. May 22 15:46:29 np0000001290 systemd[5176]: Reached target default.target - Main User Target. May 22 15:46:29 np0000001290 systemd[5176]: Startup finished in 152ms. May 22 15:46:29 np0000001290 systemd[1]: Started user@1000.service - User Manager for UID 1000. May 22 15:51:30 np0000001290 systemd[5176]: launchpadlib-cache-clean.service - Clean up old files in the Launchpadlib cache was skipped because of an unmet condition check (ConditionPathExists=/home/ubuntu/.launchpadlib/api.launchpad.net/cache). ○ uuidd.service - Daemon for generating UUIDs Loaded: loaded (/usr/lib/systemd/system/uuidd.service; indirect; preset: enabled) Active: inactive (dead) TriggeredBy: ● uuidd.socket Docs: man:uuidd(8) ○ vgauth.service - Authentication service for virtual machines hosted on VMware Loaded: loaded (/usr/lib/systemd/system/vgauth.service; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: http://github.com/vmware/open-vm-tools May 22 15:45:38 np0000001290 systemd[1]: vgauth.service - Authentication service for virtual machines hosted on VMware was skipped because of an unmet condition check (ConditionVirtualization=vmware). ● -.slice - Root Slice Loaded: loaded Active: active since Fri 2026-05-22 15:45:37 UTC; 46min ago Docs: man:systemd.special(7) Tasks: 316 Memory: 2.6G () CPU: 15min 29.870s CGroup: / ├─init.scope │ └─1 /sbin/init nofb ├─storpool.slice │ └─storpool-common.slice │ ├─storpool_beacon.service │ │ ├─ 7970 /usr/bin/perl /usr/sbin/storpool_beacon -- │ │ └─19896 /usr/sbin/storpool_beacon.bin -l -p /run/storpool_beacon.bin.pid "" -n 1 -t 60 -a b2p2.b -e 2 -W 6 │ ├─storpool_block.service │ │ ├─ 7971 /usr/bin/perl /usr/sbin/storpool_block -- │ │ └─19881 /usr/sbin/storpool_block.bin -l -p /run/storpool_block.bin.pid -b 0 -i 1 -a b2p2.b -N -W 6 │ ├─storpool_nvmed.service │ │ ├─7926 /usr/bin/perl /usr/sbin/storpool_nvmed │ │ └─7948 /usr/sbin/storpool_nvmed.bin -l -p /run/storpool_nvmed.bin.pid -W 6 │ └─storpool_server.service │ ├─ 7993 /usr/bin/perl /usr/sbin/storpool_server -- │ └─19873 /usr/sbin/storpool_server.bin -l -p /run/storpool_server.bin.pid -b 0 -C 512 -N -i 1 -a b2p2.b -W 6 ├─system.slice │ ├─ModemManager.service │ │ └─5010 /usr/sbin/ModemManager │ ├─chrony.service │ │ ├─4986 /usr/sbin/chronyd -F 1 │ │ └─4996 /usr/sbin/chronyd -F 1 │ ├─cron.service │ │ └─4930 /usr/sbin/cron -f -P │ ├─dbus.service │ │ └─4868 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only │ ├─lldpd.service │ │ ├─4872 "lldpd: monitor. " │ │ └─4891 "lldpd: connected to a9." │ ├─multipathd.service │ │ └─7266 /sbin/multipathd -d -s │ ├─networkd-dispatcher.service │ │ └─4874 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers │ ├─polkit.service │ │ └─4877 /usr/lib/polkit-1/polkitd --no-debug │ ├─rsyslog.service │ │ └─4966 /usr/sbin/rsyslogd -n -iNONE │ ├─ssh.service │ │ └─5168 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups" │ ├─storpool_controller.service │ │ ├─7972 /usr/bin/perl /usr/sbin/storpool_controller │ │ └─8089 /usr/sbin/storpool_controller.bin -l -p /run/storpool_controller.bin.pid -i 1 -A 192.168.10.5 -W 6 │ ├─storpool_dre.service │ │ └─19827 /opt/storpool/python3/bin/python3 /usr/lib/storpool/storpool_dre │ ├─storpool_gui.service │ │ └─20680 /opt/storpool/python3/bin/python3 /usr/lib/storpool/storpool_gui --staticdir /usr/lib/storpool/gui/root/dist --rootdir /usr/lib/storpool/gui/root │ ├─storpool_qos.service │ │ └─7992 /opt/storpool/python3/bin/python3 /usr/lib/storpool/storpool_qos daemon │ ├─storpool_volumecare.service │ │ └─20317 /opt/storpool/python3/bin/python3 /usr/lib/storpool/storpool_volumecare.py │ ├─system-getty.slice │ │ └─getty@tty1.service │ │ └─5000 /sbin/agetty -o "-p -- \\u" --noclear - linux │ ├─system-serial\x2dgetty.slice │ │ └─serial-getty@ttyS0.service │ │ └─4972 /sbin/agetty -o "-p -- \\u" --keep-baud 115200,57600,38400,9600 - vt220 │ ├─systemd-journald.service │ │ └─497 /usr/lib/systemd/systemd-journald │ ├─systemd-logind.service │ │ └─4889 /usr/lib/systemd/systemd-logind │ ├─systemd-networkd.service │ │ └─1179 /usr/lib/systemd/systemd-networkd │ ├─systemd-resolved.service │ │ └─1138 /usr/lib/systemd/systemd-resolved │ ├─systemd-udevd.service │ │ └─udev │ │ └─590 /usr/lib/systemd/systemd-udevd │ ├─udisks2.service │ │ └─4892 /usr/libexec/udisks2/udisksd │ └─unbound.service │ └─4951 /usr/sbin/unbound -d -p └─user.slice └─user-1000.slice ├─session-5.scope │ └─8569 /usr/bin/python3 ├─session-67.scope │ ├─20085 "sshd: ubuntu [priv]" │ ├─20144 "sshd: ubuntu@notty" │ ├─20659 /bin/sh -c "sudo -H -S -n -u root /bin/sh -c 'echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3' && sleep 0" │ ├─20660 sudo -H -S -n -u root /bin/sh -c "echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3" │ ├─20661 /bin/sh -c "echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3" │ ├─20662 /usr/bin/python3 │ ├─20665 /bin/bash -c "sudo iptables-save > /home/ubuntu/iptables.txt\n\n# NOTE(sfernand): Run 'df' with a 60s timeout to prevent hangs from\n# stale NFS mounts.\ntimeout -s 9 60s df -h > /home/ubuntu/df.txt || true\n# If 'df' times out, the mount output helps debug which NFS share\n# is unresponsive.\nmount > /home/ubuntu/mount.txt\n\nfor py_ver in 2 3; do\n if [[ \`which python\${py_ver}\` ]]; then\n python\${py_ver} -m pip freeze > /home/ubuntu/pip\${py_ver}-freeze.txt\n fi\ndone\n\nif [ \`command -v dpkg\` ]; then\n dpkg -l> /home/ubuntu/dpkg-l.txt\nfi\nif [ \`command -v rpm\` ]; then\n rpm -qa | sort > /home/ubuntu/rpm-qa.txt\nfi\n\n# Services status\nsudo systemctl status --all > services.txt 2>/dev/null\n\n# NOTE(kchamart) The 'audit.log' can be useful in cases when QEMU\n# failed to start due to denials from SELinux — useful for CentOS\n# and Fedora machines. For Ubuntu (which runs AppArmor), DevStack\n# already captures the contents of /var/log/kern.log (via\n# \`journalctl -t kernel\` redirected into syslog.txt.gz), which\n# contains AppArmor-related messages.\nif [ -f /var/log/audit/audit.log ] ; then\n sudo cp /var/log/audit/audit.log /home/ubuntu/audit.log &&\n chmod +r /home/ubuntu/audit.log;\nfi\n\n# gzip and save any coredumps in /var/core\nif [ -d /var/core ]; then\n sudo gzip -r /var/core\n sudo cp -r /var/core /home/ubuntu/\nfi\n\nsudo ss -lntup | grep ':53' > /home/ubuntu/listen53.txt\n\n# NOTE(andreaf) Service logs are already in logs/ thanks for the\n# export-devstack-journal log. Apache logs are under apache/ thans to the\n# apache-logs-conf role.\ngrep -i deprecat /home/ubuntu/logs/*.txt /home/ubuntu/apache/*.log | \\\n sed -r 's/[0-9]{1,2}\\:[0-9]{1,2}\\:[0-9]{1,2}\\.[0-9]{1,3}/ /g' | \\\n sed -r 's/[0-9]{1,2}\\:[0-9]{1,2}\\:[0-9]{1,2}/ /g' | \\\n sed -r 's/[0-9]{1,4}-[0-9]{1,2}-[0-9]{1,4}/ /g' |\n sed -r 's/\\[.*\\]/ /g' | \\\n sed -r 's/\\s[0-9]+\\s/ /g' | \\\n awk '{if (\$0 in seen) {seen[\$0]++} else {out[++n]=\$0;seen[\$0]=1}} END { for (i=1; i<=n; i++) print seen[out[i]]\" :: \" out[i] }' > /home/ubuntu/deprecations.log\n" │ ├─20678 sudo systemctl status --all │ └─20679 systemctl status --all └─user@1000.service └─init.scope ├─5176 /usr/lib/systemd/systemd --user └─5177 "(sd-pam)" May 22 16:31:47 np0000001290 systemd[1]: storpool_gui.service: Scheduled restart job, restart counter is at 1747. May 22 16:31:47 np0000001290 systemd[1]: Started storpool_gui.service - storpool_gui. May 22 16:31:48 np0000001290 systemd[1]: storpool_gui.service: Main process exited, code=exited, status=1/FAILURE May 22 16:31:48 np0000001290 systemd[1]: storpool_gui.service: Failed with result 'exit-code'. May 22 16:31:49 np0000001290 systemd[1]: storpool_gui.service: Scheduled restart job, restart counter is at 1748. May 22 16:31:49 np0000001290 systemd[1]: Started storpool_gui.service - storpool_gui. May 22 16:31:49 np0000001290 systemd[1]: storpool_gui.service: Main process exited, code=exited, status=1/FAILURE May 22 16:31:49 np0000001290 systemd[1]: storpool_gui.service: Failed with result 'exit-code'. May 22 16:31:50 np0000001290 systemd[1]: storpool_gui.service: Scheduled restart job, restart counter is at 1749. May 22 16:31:50 np0000001290 systemd[1]: Started storpool_gui.service - storpool_gui. ● storpool-alloc.slice - Slice /storpool/alloc Loaded: loaded Active: active since Fri 2026-05-22 15:47:06 UTC; 44min ago Tasks: 0 Memory: 4.0K () CGroup: /storpool.slice/storpool-alloc.slice May 22 16:30:13 np0000001290 storpool_mgmt[19785]: [info] got service up for 1.server.0 (1), 1779464830586050 May 22 16:30:13 np0000001290 storpool_mgmt[19785]: [info] got service up for 2.client (32770), 1779464830583404 May 22 16:30:13 np0000001290 storpool_mgmt[19785]: [info] got service up for 1.mgmt (61441), 1779467413313211 May 22 16:30:13 np0000001290 storpool_mgmt-loader[7974]: Child 19785: Cannot find device "sp-api" May 22 16:30:13 np0000001290 storpool_mgmt[19785]: [err] Error: bind() fd:31 port:81 (Address not available) May 22 16:30:13 np0000001290 storpool_mgmt-loader[7974]: Child 19785: bind: No such file or directory May 22 16:30:13 np0000001290 storpool_mgmt-loader[7974]: childPid:19785 finished with sret:512 May 22 16:30:13 np0000001290 storpool_mgmt-loader[7974]: lost storpool_mgmt.bin (pid:19785) exited with 2 May 22 16:30:13 np0000001290 storpool_mgmt-loader[7974]: 3 crashes in 1800sec May 22 16:30:13 np0000001290 storpool_mgmt-loader[7974]: Loader finished with Exit(1) ● storpool-common.slice - Slice /storpool/common Loaded: loaded Active: active since Fri 2026-05-22 15:47:04 UTC; 44min ago Tasks: 11 Memory: 620.0K () CGroup: /storpool.slice/storpool-common.slice ├─storpool_beacon.service │ ├─ 7970 /usr/bin/perl /usr/sbin/storpool_beacon -- │ └─19896 /usr/sbin/storpool_beacon.bin -l -p /run/storpool_beacon.bin.pid "" -n 1 -t 60 -a b2p2.b -e 2 -W 6 ├─storpool_block.service │ ├─ 7971 /usr/bin/perl /usr/sbin/storpool_block -- │ └─19881 /usr/sbin/storpool_block.bin -l -p /run/storpool_block.bin.pid -b 0 -i 1 -a b2p2.b -N -W 6 ├─storpool_nvmed.service │ ├─7926 /usr/bin/perl /usr/sbin/storpool_nvmed │ └─7948 /usr/sbin/storpool_nvmed.bin -l -p /run/storpool_nvmed.bin.pid -W 6 └─storpool_server.service ├─ 7993 /usr/bin/perl /usr/sbin/storpool_server -- └─19873 /usr/sbin/storpool_server.bin -l -p /run/storpool_server.bin.pid -b 0 -C 512 -N -i 1 -a b2p2.b -W 6 May 22 16:31:40 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:41 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:42 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:43 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:44 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:45 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:46 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:47 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:48 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. May 22 16:31:49 np0000001290 storpool_beacon[19896]: [warning] all interfaces down. Please check your network configuration. ● storpool.slice - Slice /storpool Loaded: loaded Drop-In: /usr/lib/systemd/system/storpool.slice.d └─90-MemoryLimit.conf Active: active since Fri 2026-05-22 15:47:04 UTC; 44min ago Tasks: 11 Memory: 1.4G () CGroup: /storpool.slice └─storpool-common.slice ├─storpool_beacon.service │ ├─ 7970 /usr/bin/perl /usr/sbin/storpool_beacon -- │ └─19896 /usr/sbin/storpool_beacon.bin -l -p /run/storpool_beacon.bin.pid "" -n 1 -t 60 -a b2p2.b -e 2 -W 6 ├─storpool_block.service │ ├─ 7971 /usr/bin/perl /usr/sbin/storpool_block -- │ └─19881 /usr/sbin/storpool_block.bin -l -p /run/storpool_block.bin.pid -b 0 -i 1 -a b2p2.b -N -W 6 ├─storpool_nvmed.service │ ├─7926 /usr/bin/perl /usr/sbin/storpool_nvmed │ └─7948 /usr/sbin/storpool_nvmed.bin -l -p /run/storpool_nvmed.bin.pid -W 6 └─storpool_server.service ├─ 7993 /usr/bin/perl /usr/sbin/storpool_server -- └─19873 /usr/sbin/storpool_server.bin -l -p /run/storpool_server.bin.pid -b 0 -C 512 -N -i 1 -a b2p2.b -W 6 May 22 15:47:04 np0000001290 systemd[1]: storpool.slice: Failed to set 'memory.limit_in_bytes' attribute on '/storpool.slice' to '-1': Invalid argument May 22 15:47:04 np0000001290 systemd[1]: Created slice storpool.slice - Slice /storpool. ● system-getty.slice - Slice /system/getty Loaded: loaded Active: active since Fri 2026-05-22 15:45:44 UTC; 46min ago Tasks: 1 Memory: 332.0K () CGroup: /system.slice/system-getty.slice └─getty@tty1.service └─5000 /sbin/agetty -o "-p -- \\u" --noclear - linux May 22 15:45:44 np0000001290 systemd[1]: Created slice system-getty.slice - Slice /system/getty. ● system-modprobe.slice - Slice /system/modprobe Loaded: loaded Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Tasks: 0 Memory: 216.0K () CGroup: /system.slice/system-modprobe.slice Notice: journal has been rotated since unit was started, output may be incomplete. ● system-serial\x2dgetty.slice - Slice /system/serial-getty Loaded: loaded Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Tasks: 1 Memory: 248.0K () CGroup: /system.slice/system-serial\x2dgetty.slice └─serial-getty@ttyS0.service └─4972 /sbin/agetty -o "-p -- \\u" --keep-baud 115200,57600,38400,9600 - vt220 Notice: journal has been rotated since unit was started, output may be incomplete. ● system-systemd\x2dfsck.slice - Slice /system/systemd-fsck Loaded: loaded Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Tasks: 0 Memory: 1.0M () CGroup: /system.slice/system-systemd\x2dfsck.slice May 22 15:45:38 np0000001290 systemd-fsck[979]: BOOT: clean, 604/58496 files, 42348/233728 blocks Notice: journal has been rotated since unit was started, output may be incomplete. ● system.slice - System Slice Loaded: loaded Drop-In: /usr/lib/systemd/system/system.slice.d └─90-MemoryLimit.conf Active: active since Fri 2026-05-22 15:45:37 UTC; 46min ago Docs: man:systemd.special(7) Tasks: 47 Memory: 468.2M () CGroup: /system.slice ├─ModemManager.service │ └─5010 /usr/sbin/ModemManager ├─chrony.service │ ├─4986 /usr/sbin/chronyd -F 1 │ └─4996 /usr/sbin/chronyd -F 1 ├─cron.service │ └─4930 /usr/sbin/cron -f -P ├─dbus.service │ └─4868 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only ├─lldpd.service │ ├─4872 "lldpd: monitor. " │ └─4891 "lldpd: connected to a9." ├─multipathd.service │ └─7266 /sbin/multipathd -d -s ├─networkd-dispatcher.service │ └─4874 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers ├─polkit.service │ └─4877 /usr/lib/polkit-1/polkitd --no-debug ├─rsyslog.service │ └─4966 /usr/sbin/rsyslogd -n -iNONE ├─ssh.service │ └─5168 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups" ├─storpool_controller.service │ ├─7972 /usr/bin/perl /usr/sbin/storpool_controller │ └─8089 /usr/sbin/storpool_controller.bin -l -p /run/storpool_controller.bin.pid -i 1 -A 192.168.10.5 -W 6 ├─storpool_dre.service │ └─19827 /opt/storpool/python3/bin/python3 /usr/lib/storpool/storpool_dre ├─storpool_gui.service │ └─20680 /opt/storpool/python3/bin/python3 /usr/lib/storpool/storpool_gui --staticdir /usr/lib/storpool/gui/root/dist --rootdir /usr/lib/storpool/gui/root ├─storpool_qos.service │ └─7992 /opt/storpool/python3/bin/python3 /usr/lib/storpool/storpool_qos daemon ├─storpool_volumecare.service │ └─20317 "[storpool_volume]" ├─system-getty.slice │ └─getty@tty1.service │ └─5000 /sbin/agetty -o "-p -- \\u" --noclear - linux ├─system-serial\x2dgetty.slice │ └─serial-getty@ttyS0.service │ └─4972 /sbin/agetty -o "-p -- \\u" --keep-baud 115200,57600,38400,9600 - vt220 ├─systemd-journald.service │ └─497 /usr/lib/systemd/systemd-journald ├─systemd-logind.service │ └─4889 /usr/lib/systemd/systemd-logind ├─systemd-networkd.service │ └─1179 /usr/lib/systemd/systemd-networkd ├─systemd-resolved.service │ └─1138 /usr/lib/systemd/systemd-resolved ├─systemd-udevd.service │ └─udev │ └─590 /usr/lib/systemd/systemd-udevd ├─udisks2.service │ └─4892 /usr/libexec/udisks2/udisksd └─unbound.service └─4951 /usr/sbin/unbound -d -p May 22 16:31:49 np0000001290 storpool_gui[20656]: result = self._get_param(None, "SP_RAUTH_TOKEN", "") May 22 16:31:49 np0000001290 storpool_gui[20656]: File "/opt/storpool/python3/lib/python3.8/site-packages/sp/tools/gui/src/config/config_parser.py", line 30, in _get_param May 22 16:31:49 np0000001290 storpool_gui[20656]: raise ValueError(f"For {arg} - Missing key in sp_cfg: {config_key}") May 22 16:31:49 np0000001290 storpool_gui[20656]: ValueError: For None - Missing key in sp_cfg: SP_RAUTH_TOKEN May 22 16:31:50 np0000001290 storpool_volumecare.py[20317]: Traceback (most recent call last): May 22 16:31:50 np0000001290 storpool_volumecare.py[20317]: File "/usr/lib/storpool/storpool_volumecare.py", line 33, in May 22 16:31:50 np0000001290 storpool_volumecare.py[20317]: sys.exit(load_entry_point('splib', 'console_scripts', 'storpool_volumecare.py')()) May 22 16:31:50 np0000001290 storpool_volumecare.py[20317]: File "/opt/storpool/python3/lib/python3.8/site-packages/sp/tools/volumecare/sp_vc.py", line 141, in main May 22 16:31:50 np0000001290 storpool_volumecare.py[20317]: raise TimeoutError("socket.timeout in wait_check_run") from None May 22 16:31:50 np0000001290 storpool_volumecare.py[20317]: TimeoutError: socket.timeout in wait_check_run ● user-1000.slice - User Slice of UID 1000 Loaded: loaded Drop-In: /usr/lib/systemd/system/user-.slice.d └─10-defaults.conf Active: active since Fri 2026-05-22 15:46:29 UTC; 45min ago Docs: man:user@.service(5) Tasks: 15 (limit: 60635) Memory: 91.4M () CGroup: /user.slice/user-1000.slice ├─session-5.scope │ └─8569 /usr/bin/python3 ├─session-67.scope │ ├─20085 "sshd: ubuntu [priv]" │ ├─20144 "sshd: ubuntu@notty" │ ├─20659 /bin/sh -c "sudo -H -S -n -u root /bin/sh -c 'echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3' && sleep 0" │ ├─20660 sudo -H -S -n -u root /bin/sh -c "echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3" │ ├─20661 /bin/sh -c "echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3" │ ├─20662 /usr/bin/python3 │ ├─20665 /bin/bash -c "sudo iptables-save > /home/ubuntu/iptables.txt\n\n# NOTE(sfernand): Run 'df' with a 60s timeout to prevent hangs from\n# stale NFS mounts.\ntimeout -s 9 60s df -h > /home/ubuntu/df.txt || true\n# If 'df' times out, the mount output helps debug which NFS share\n# is unresponsive.\nmount > /home/ubuntu/mount.txt\n\nfor py_ver in 2 3; do\n if [[ \`which python\${py_ver}\` ]]; then\n python\${py_ver} -m pip freeze > /home/ubuntu/pip\${py_ver}-freeze.txt\n fi\ndone\n\nif [ \`command -v dpkg\` ]; then\n dpkg -l> /home/ubuntu/dpkg-l.txt\nfi\nif [ \`command -v rpm\` ]; then\n rpm -qa | sort > /home/ubuntu/rpm-qa.txt\nfi\n\n# Services status\nsudo systemctl status --all > services.txt 2>/dev/null\n\n# NOTE(kchamart) The 'audit.log' can be useful in cases when QEMU\n# failed to start due to denials from SELinux — useful for CentOS\n# and Fedora machines. For Ubuntu (which runs AppArmor), DevStack\n# already captures the contents of /var/log/kern.log (via\n# \`journalctl -t kernel\` redirected into syslog.txt.gz), which\n# contains AppArmor-related messages.\nif [ -f /var/log/audit/audit.log ] ; then\n sudo cp /var/log/audit/audit.log /home/ubuntu/audit.log &&\n chmod +r /home/ubuntu/audit.log;\nfi\n\n# gzip and save any coredumps in /var/core\nif [ -d /var/core ]; then\n sudo gzip -r /var/core\n sudo cp -r /var/core /home/ubuntu/\nfi\n\nsudo ss -lntup | grep ':53' > /home/ubuntu/listen53.txt\n\n# NOTE(andreaf) Service logs are already in logs/ thanks for the\n# export-devstack-journal log. Apache logs are under apache/ thans to the\n# apache-logs-conf role.\ngrep -i deprecat /home/ubuntu/logs/*.txt /home/ubuntu/apache/*.log | \\\n sed -r 's/[0-9]{1,2}\\:[0-9]{1,2}\\:[0-9]{1,2}\\.[0-9]{1,3}/ /g' | \\\n sed -r 's/[0-9]{1,2}\\:[0-9]{1,2}\\:[0-9]{1,2}/ /g' | \\\n sed -r 's/[0-9]{1,4}-[0-9]{1,2}-[0-9]{1,4}/ /g' |\n sed -r 's/\\[.*\\]/ /g' | \\\n sed -r 's/\\s[0-9]+\\s/ /g' | \\\n awk '{if (\$0 in seen) {seen[\$0]++} else {out[++n]=\$0;seen[\$0]=1}} END { for (i=1; i<=n; i++) print seen[out[i]]\" :: \" out[i] }' > /home/ubuntu/deprecations.log\n" │ ├─20678 sudo systemctl status --all │ └─20679 systemctl status --all └─user@1000.service └─init.scope ├─5176 /usr/lib/systemd/systemd --user └─5177 "(sd-pam)" May 22 16:31:48 np0000001290 python3[20653]: ansible-stat Invoked with path=/etc/openstack follow=False get_checksum=True get_mime=True get_attributes=True checksum_algorithm=sha1 May 22 16:31:48 np0000001290 sudo[20651]: pam_unix(sudo:session): session closed for user root May 22 16:31:49 np0000001290 sudo[20660]: ubuntu : PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/sh -c 'echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3' May 22 16:31:49 np0000001290 sudo[20660]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1000) May 22 16:31:49 np0000001290 python3[20662]: ansible-ansible.legacy.command Invoked with executable=/bin/bash _raw_params=sudo iptables-save > /home/ubuntu/iptables.txt # NOTE(sfernand): Run 'df' with a 60s timeout to prevent hangs from # stale NFS mounts. timeout -s 9 60s df -h > /home/ubuntu/df.txt || true # If 'df' times out, the mount output helps debug which NFS share # is unresponsive. mount > /home/ubuntu/mount.txt for py_ver in 2 3; do if [[ `which python${py_ver}` ]]; then python${py_ver} -m pip freeze > /home/ubuntu/pip${py_ver}-freeze.txt fi done if [ `command -v dpkg` ]; then dpkg -l> /home/ubuntu/dpkg-l.txt fi if [ `command -v rpm` ]; then rpm -qa | sort > /home/ubuntu/rpm-qa.txt fi # Services status sudo systemctl status --all > services.txt 2>/dev/null # NOTE(kchamart) The 'audit.log' can be useful in cases when QEMU # failed to start due to denials from SELinux — useful for CentOS # and Fedora machines. For Ubuntu (which runs AppArmor), DevStack # already captures the contents of /var/log/kern.log (via # `journalctl -t kernel` redirected into syslog.txt.gz), which # contains AppArmor-related messages. if [ -f /var/log/audit/audit.log ] ; then sudo cp /var/log/audit/audit.log /home/ubuntu/audit.log && chmod +r /home/ubuntu/audit.log; fi # gzip and save any coredumps in /var/core if [ -d /var/core ]; then sudo gzip -r /var/core sudo cp -r /var/core /home/ubuntu/ fi sudo ss -lntup | grep ':53' > /home/ubuntu/listen53.txt # NOTE(andreaf) Service logs are already in logs/ thanks for the # export-devstack-journal log. Apache logs are under apache/ thans to the # apache-logs-conf role. grep -i deprecat /home/ubuntu/logs/*.txt /home/ubuntu/apache/*.log | \ sed -r 's/[0-9]{1,2}\:[0-9]{1,2}\:[0-9]{1,2}\.[0-9]{1,3}/ /g' | \ sed -r 's/[0-9]{1,2}\:[0-9]{1,2}\:[0-9]{1,2}/ /g' | \ sed -r 's/[0-9]{1,4}-[0-9]{1,2}-[0-9]{1,4}/ /g' | sed -r 's/\[.*\]/ /g' | \ sed -r 's/\s[0-9]+\s/ /g' | \ awk '{if ($0 in seen) {seen[$0]++} else {out[++n]=$0;seen[$0]=1}} END { for (i=1; i<=n; i++) print seen[out[i]]" :: " out[i] }' > /home/ubuntu/deprecations.log _uses_shell=True zuul_no_log=False zuul_log_id=9ee7344d-e36b-6f85-ae59-000000000035-1-labspa1 zuul_output_max_bytes=1073741824 zuul_ansible_split_streams=False expand_argument_vars=True stdin_add_newline=True strip_empty_ends=True argv=None chdir=None creates=None removes=None stdin=None May 22 16:31:49 np0000001290 sudo[20667]: root : PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/sbin/iptables-save May 22 16:31:49 np0000001290 sudo[20667]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=0) May 22 16:31:49 np0000001290 sudo[20667]: pam_unix(sudo:session): session closed for user root May 22 16:31:49 np0000001290 sudo[20678]: root : PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/systemctl status --all May 22 16:31:49 np0000001290 sudo[20678]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=0) ● user.slice - User and Session Slice Loaded: loaded (/usr/lib/systemd/system/user.slice; static) Drop-In: /usr/lib/systemd/system/user.slice.d └─90-MemoryLimit.conf Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd.special(7) Tasks: 15 Memory: 91.6M () CGroup: /user.slice └─user-1000.slice ├─session-5.scope │ └─8569 /usr/bin/python3 ├─session-67.scope │ ├─20085 "sshd: ubuntu [priv]" │ ├─20144 "sshd: ubuntu@notty" │ ├─20659 /bin/sh -c "sudo -H -S -n -u root /bin/sh -c 'echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3' && sleep 0" │ ├─20660 sudo -H -S -n -u root /bin/sh -c "echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3" │ ├─20661 /bin/sh -c "echo BECOME-SUCCESS-zcqeojlqkjkrsrzmxqaaagtuyzvbouxl ; /usr/bin/python3" │ ├─20662 /usr/bin/python3 │ ├─20665 /bin/bash -c "sudo iptables-save > /home/ubuntu/iptables.txt\n\n# NOTE(sfernand): Run 'df' with a 60s timeout to prevent hangs from\n# stale NFS mounts.\ntimeout -s 9 60s df -h > /home/ubuntu/df.txt || true\n# If 'df' times out, the mount output helps debug which NFS share\n# is unresponsive.\nmount > /home/ubuntu/mount.txt\n\nfor py_ver in 2 3; do\n if [[ \`which python\${py_ver}\` ]]; then\n python\${py_ver} -m pip freeze > /home/ubuntu/pip\${py_ver}-freeze.txt\n fi\ndone\n\nif [ \`command -v dpkg\` ]; then\n dpkg -l> /home/ubuntu/dpkg-l.txt\nfi\nif [ \`command -v rpm\` ]; then\n rpm -qa | sort > /home/ubuntu/rpm-qa.txt\nfi\n\n# Services status\nsudo systemctl status --all > services.txt 2>/dev/null\n\n# NOTE(kchamart) The 'audit.log' can be useful in cases when QEMU\n# failed to start due to denials from SELinux — useful for CentOS\n# and Fedora machines. For Ubuntu (which runs AppArmor), DevStack\n# already captures the contents of /var/log/kern.log (via\n# \`journalctl -t kernel\` redirected into syslog.txt.gz), which\n# contains AppArmor-related messages.\nif [ -f /var/log/audit/audit.log ] ; then\n sudo cp /var/log/audit/audit.log /home/ubuntu/audit.log &&\n chmod +r /home/ubuntu/audit.log;\nfi\n\n# gzip and save any coredumps in /var/core\nif [ -d /var/core ]; then\n sudo gzip -r /var/core\n sudo cp -r /var/core /home/ubuntu/\nfi\n\nsudo ss -lntup | grep ':53' > /home/ubuntu/listen53.txt\n\n# NOTE(andreaf) Service logs are already in logs/ thanks for the\n# export-devstack-journal log. Apache logs are under apache/ thans to the\n# apache-logs-conf role.\ngrep -i deprecat /home/ubuntu/logs/*.txt /home/ubuntu/apache/*.log | \\\n sed -r 's/[0-9]{1,2}\\:[0-9]{1,2}\\:[0-9]{1,2}\\.[0-9]{1,3}/ /g' | \\\n sed -r 's/[0-9]{1,2}\\:[0-9]{1,2}\\:[0-9]{1,2}/ /g' | \\\n sed -r 's/[0-9]{1,4}-[0-9]{1,2}-[0-9]{1,4}/ /g' |\n sed -r 's/\\[.*\\]/ /g' | \\\n sed -r 's/\\s[0-9]+\\s/ /g' | \\\n awk '{if (\$0 in seen) {seen[\$0]++} else {out[++n]=\$0;seen[\$0]=1}} END { for (i=1; i<=n; i++) print seen[out[i]]\" :: \" out[i] }' > /home/ubuntu/deprecations.log\n" │ ├─20678 sudo systemctl status --all │ └─20679 systemctl status --all └─user@1000.service └─init.scope ├─5176 /usr/lib/systemd/systemd --user └─5177 "(sd-pam)" May 22 15:47:03 np0000001290 systemd[1]: user.slice: Failed to set 'memory.limit_in_bytes' attribute on '/user.slice' to '-1': Invalid argument Notice: journal has been rotated since unit was started, output may be incomplete. ○ apport-forward.socket - Unix socket for apport crash forwarding Loaded: loaded (/usr/lib/systemd/system/apport-forward.socket; enabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:42 UTC; 46min ago Listen: /run/apport.socket (Stream) Accepted: 0; Connected: 0; May 22 15:45:42 np0000001290 systemd[1]: apport-forward.socket - Unix socket for apport crash forwarding was skipped because of an unmet condition check (ConditionVirtualization=container). ● cloud-init-hotplugd.socket - cloud-init hotplug hook socket Loaded: loaded (/usr/lib/systemd/system/cloud-init-hotplugd.socket; enabled; preset: enabled) Active: active (listening) since Fri 2026-05-22 15:45:42 UTC; 46min ago Triggers: ● cloud-init-hotplugd.service Listen: /run/cloud-init/share/hook-hotplug-cmd (FIFO) CGroup: /system.slice/cloud-init-hotplugd.socket May 22 15:45:42 np0000001290 systemd[1]: Listening on cloud-init-hotplugd.socket - cloud-init hotplug hook socket. ● dbus.socket - D-Bus System Message Bus Socket Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static) Active: active (running) since Fri 2026-05-22 15:45:42 UTC; 46min ago Triggers: ● dbus.service Listen: /run/dbus/system_bus_socket (Stream) CGroup: /system.slice/dbus.socket May 22 15:45:42 np0000001290 systemd[1]: Listening on dbus.socket - D-Bus System Message Bus Socket. ● dm-event.socket - Device-mapper event daemon FIFOs Loaded: loaded (/usr/lib/systemd/system/dm-event.socket; enabled; preset: enabled) Active: active (listening) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● dm-event.service Docs: man:dmeventd(8) Listen: /run/dmeventd-server (FIFO) /run/dmeventd-client (FIFO) CGroup: /system.slice/dm-event.socket Notice: journal has been rotated since unit was started, output may be incomplete. ● iscsid.socket - Open-iSCSI iscsid Socket Loaded: loaded (/usr/lib/systemd/system/iscsid.socket; enabled; preset: enabled) Active: active (listening) since Fri 2026-05-22 15:45:42 UTC; 46min ago Triggers: ● iscsid.service Docs: man:iscsid(8) man:iscsiadm(8) Listen: @ISCSIADM_ABSTRACT_NAMESPACE (Stream) CGroup: /system.slice/iscsid.socket May 22 15:45:42 np0000001290 systemd[1]: Listening on iscsid.socket - Open-iSCSI iscsid Socket. ● lvm2-lvmpolld.socket - LVM2 poll daemon socket Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmpolld.socket; enabled; preset: enabled) Active: active (listening) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● lvm2-lvmpolld.service Docs: man:lvmpolld(8) Listen: /run/lvm/lvmpolld.socket (Stream) CGroup: /system.slice/lvm2-lvmpolld.socket Notice: journal has been rotated since unit was started, output may be incomplete. ● lxd-installer.socket - Helper to install lxd snap on demand Loaded: loaded (/usr/lib/systemd/system/lxd-installer.socket; enabled; preset: enabled) Active: active (listening) since Fri 2026-05-22 15:45:42 UTC; 46min ago Listen: /run/lxd-installer.socket (Stream) Accepted: 0; Connected: 0; Tasks: 0 (limit: 27561) Memory: 4.0K () CGroup: /system.slice/lxd-installer.socket May 22 15:45:42 np0000001290 systemd[1]: Starting lxd-installer.socket - Helper to install lxd snap on demand... May 22 15:45:42 np0000001290 systemd[1]: Listening on lxd-installer.socket - Helper to install lxd snap on demand. ○ multipathd.socket - multipathd control socket Loaded: loaded (/usr/lib/systemd/system/multipathd.socket; disabled; preset: enabled) Active: inactive (dead) Triggers: ● multipathd.service Listen: @/org/kernel/linux/storage/multipathd (Stream) ● snapd.socket - Socket activation for snappy daemon Loaded: loaded (/usr/lib/systemd/system/snapd.socket; enabled; preset: enabled) Active: active (listening) since Fri 2026-05-22 15:45:42 UTC; 46min ago Triggers: ● snapd.service Listen: /run/snapd.socket (Stream) /run/snapd-snap.socket (Stream) Tasks: 0 (limit: 27561) Memory: 4.0K () CGroup: /system.slice/snapd.socket May 22 15:45:42 np0000001290 systemd[1]: Starting snapd.socket - Socket activation for snappy daemon... May 22 15:45:42 np0000001290 systemd[1]: Listening on snapd.socket - Socket activation for snappy daemon. ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/usr/lib/systemd/system/ssh.socket; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:42 UTC; 46min ago Triggers: ● ssh.service Listen: 0.0.0.0:22 (Stream) [::]:22 (Stream) CGroup: /system.slice/ssh.socket May 22 15:45:42 np0000001290 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell server socket. ● syslog.socket - Syslog Socket Loaded: loaded (/usr/lib/systemd/system/syslog.socket; static) Active: active (running) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● rsyslog.service Docs: man:systemd.special(7) https://www.freedesktop.org/wiki/Software/systemd/syslog Listen: /run/systemd/journal/syslog (Datagram) CGroup: /system.slice/syslog.socket Notice: journal has been rotated since unit was started, output may be incomplete. ● systemd-fsckd.socket - fsck to fsckd communication Socket Loaded: loaded (/usr/lib/systemd/system/systemd-fsckd.socket; static) Active: active (listening) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● systemd-fsckd.service Docs: man:systemd-fsckd.service(8) man:systemd-fsck@.service(8) man:systemd-fsck-root.service(8) Listen: /run/systemd/fsck.progress (Stream) CGroup: /system.slice/systemd-fsckd.socket Notice: journal has been rotated since unit was started, output may be incomplete. ● systemd-initctl.socket - initctl Compatibility Named Pipe Loaded: loaded (/usr/lib/systemd/system/systemd-initctl.socket; static) Active: active (listening) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● systemd-initctl.service Docs: man:systemd-initctl.socket(8) Listen: /run/initctl (FIFO) CGroup: /system.slice/systemd-initctl.socket Notice: journal has been rotated since unit was started, output may be incomplete. ○ systemd-journald-audit.socket - Journal Audit Socket Loaded: loaded (/usr/lib/systemd/system/systemd-journald-audit.socket; disabled; preset: enabled) Active: inactive (dead) Triggers: ● systemd-journald.service Docs: man:systemd-journald.service(8) man:journald.conf(5) Listen: audit 1 (Netlink) ● systemd-journald-dev-log.socket - Journal Socket (/dev/log) Loaded: loaded (/usr/lib/systemd/system/systemd-journald-dev-log.socket; static) Active: active (running) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● systemd-journald.service Docs: man:systemd-journald.service(8) man:journald.conf(5) Listen: /run/systemd/journal/dev-log (Datagram) CGroup: /system.slice/systemd-journald-dev-log.socket Notice: journal has been rotated since unit was started, output may be incomplete. ● systemd-journald.socket - Journal Socket Loaded: loaded (/usr/lib/systemd/system/systemd-journald.socket; static) Active: active (running) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● systemd-journald.service Docs: man:systemd-journald.service(8) man:journald.conf(5) Listen: /run/systemd/journal/socket (Datagram) /run/systemd/journal/stdout (Stream) CGroup: /system.slice/systemd-journald.socket Notice: journal has been rotated since unit was started, output may be incomplete. ● systemd-networkd.socket - Network Service Netlink Socket Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.socket; enabled; preset: enabled) Active: active (running) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● systemd-networkd.service Docs: man:systemd-networkd.service(8) man:rtnetlink(7) Listen: route 1361 (Netlink) CGroup: /system.slice/systemd-networkd.socket Notice: journal has been rotated since unit was started, output may be incomplete. ○ systemd-pcrextend.socket - TPM2 PCR Extension (Varlink) Loaded: loaded (/usr/lib/systemd/system/systemd-pcrextend.socket; disabled; preset: enabled) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-pcrextend(8) Listen: /run/systemd/io.systemd.PCRExtend (Stream) Accepted: 0; Connected: 0; ● systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch Loaded: loaded (/usr/lib/systemd/system/systemd-rfkill.socket; static) Active: active (listening) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● systemd-rfkill.service Docs: man:systemd-rfkill.socket(8) Listen: /dev/rfkill (Special) CGroup: /system.slice/systemd-rfkill.socket May 22 15:45:38 np0000001290 systemd[1]: Listening on systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch. ● systemd-sysext.socket - System Extension Image Management (Varlink) Loaded: loaded (/usr/lib/systemd/system/systemd-sysext.socket; disabled; preset: enabled) Active: active (listening) since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd-sysext(8) Listen: /run/systemd/io.systemd.sysext (Stream) Accepted: 0; Connected: 0; CGroup: /system.slice/systemd-sysext.socket May 22 15:45:38 np0000001290 systemd[1]: Listening on systemd-sysext.socket - System Extension Image Management (Varlink). ● systemd-udevd-control.socket - udev Control Socket Loaded: loaded (/usr/lib/systemd/system/systemd-udevd-control.socket; static) Active: active (running) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● systemd-udevd.service Docs: man:systemd-udevd-control.socket(8) man:udev(7) Listen: /run/udev/control (SequentialPacket) CGroup: /system.slice/systemd-udevd-control.socket Notice: journal has been rotated since unit was started, output may be incomplete. ● systemd-udevd-kernel.socket - udev Kernel Socket Loaded: loaded (/usr/lib/systemd/system/systemd-udevd-kernel.socket; static) Active: active (running) since Fri 2026-05-22 15:45:38 UTC; 46min ago Triggers: ● systemd-udevd.service Docs: man:systemd-udevd-kernel.socket(8) man:udev(7) Listen: kobject-uevent 1 (Netlink) CGroup: /system.slice/systemd-udevd-kernel.socket Notice: journal has been rotated since unit was started, output may be incomplete. ● uuidd.socket - UUID daemon activation socket Loaded: loaded (/usr/lib/systemd/system/uuidd.socket; enabled; preset: enabled) Active: active (listening) since Fri 2026-05-22 15:45:42 UTC; 46min ago Triggers: ● uuidd.service Listen: /run/uuidd/request (Stream) CGroup: /system.slice/uuidd.socket May 22 15:45:42 np0000001290 systemd[1]: Listening on uuidd.socket - UUID daemon activation socket. ● basic.target - Basic System Loaded: loaded (/usr/lib/systemd/system/basic.target; static) Active: active since Fri 2026-05-22 15:45:43 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:43 np0000001290 systemd[1]: Reached target basic.target - Basic System. ○ blockdev@dev-disk-by\x2dlabel-BOOT.target - Block Device Preparation for /dev/disk/by-label/BOOT Loaded: loaded (/usr/lib/systemd/system/blockdev@.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ blockdev@dev-disk-by\x2dlabel-cloudimg\x2drootfs.target - Block Device Preparation for /dev/disk/by-label/cloudimg-rootfs Loaded: loaded (/usr/lib/systemd/system/blockdev@.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ blockdev@dev-disk-by\x2dlabel-UEFI.target - Block Device Preparation for /dev/disk/by-label/UEFI Loaded: loaded (/usr/lib/systemd/system/blockdev@.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ blockdev@dev-sda15.target - Block Device Preparation for /dev/sda15 Loaded: loaded (/usr/lib/systemd/system/blockdev@.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ blockdev@dev-sda16.target - Block Device Preparation for /dev/sda16 Loaded: loaded (/usr/lib/systemd/system/blockdev@.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ● cloud-config.target - Cloud-config availability Loaded: loaded (/usr/lib/systemd/system/cloud-config.target; static) Active: active since Fri 2026-05-22 15:45:42 UTC; 46min ago May 22 15:45:42 np0000001290 systemd[1]: Reached target cloud-config.target - Cloud-config availability. ● cloud-init.target - Cloud-init target Loaded: loaded (/usr/lib/systemd/system/cloud-init.target; enabled-runtime; preset: enabled) Active: active since Fri 2026-05-22 15:45:44 UTC; 46min ago May 22 15:45:44 np0000001290 systemd[1]: Reached target cloud-init.target - Cloud-init target. ○ cryptsetup-pre.target - Local Encrypted Volumes (Pre) Loaded: loaded (/usr/lib/systemd/system/cryptsetup-pre.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ● cryptsetup.target - Local Encrypted Volumes Loaded: loaded (/usr/lib/systemd/system/cryptsetup.target; static) Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:38 np0000001290 systemd[1]: Reached target cryptsetup.target - Local Encrypted Volumes. ○ emergency.target - Emergency Mode Loaded: loaded (/usr/lib/systemd/system/emergency.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ final.target - Late Shutdown Services Loaded: loaded (/usr/lib/systemd/system/final.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ first-boot-complete.target - First Boot Complete Loaded: loaded (/usr/lib/systemd/system/first-boot-complete.target; static) Active: inactive (dead) Condition: start condition unmet at Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:38 np0000001290 systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes). ● getty-pre.target - Preparation for Logins Loaded: loaded (/usr/lib/systemd/system/getty-pre.target; static) Active: active since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:systemd.special(7) man:systemd-getty-generator(8) https://0pointer.de/blog/projects/serial-console.html May 22 15:45:44 np0000001290 systemd[1]: Reached target getty-pre.target - Preparation for Logins. ● getty.target - Login Prompts Loaded: loaded (/usr/lib/systemd/system/getty.target; static) Active: active since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:systemd.special(7) man:systemd-getty-generator(8) https://0pointer.de/blog/projects/serial-console.html May 22 15:45:44 np0000001290 systemd[1]: Reached target getty.target - Login Prompts. ● graphical.target - Graphical Interface Loaded: loaded (/usr/lib/systemd/system/graphical.target; static) Active: active since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:44 np0000001290 systemd[1]: Reached target graphical.target - Graphical Interface. ○ hibernate.target - System Hibernation Loaded: loaded (/usr/lib/systemd/system/hibernate.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ hybrid-sleep.target - Hybrid Suspend+Hibernate Loaded: loaded (/usr/lib/systemd/system/hybrid-sleep.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ initrd-fs.target - Initrd File Systems Loaded: loaded (/usr/lib/systemd/system/initrd-fs.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ initrd-root-device.target - Initrd Root Device Loaded: loaded (/usr/lib/systemd/system/initrd-root-device.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ initrd-root-fs.target - Initrd Root File System Loaded: loaded (/usr/lib/systemd/system/initrd-root-fs.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ initrd-switch-root.target - Switch Root Loaded: loaded (/usr/lib/systemd/system/initrd-switch-root.target; static) Active: inactive (dead) ○ initrd-usr-fs.target - Initrd /usr File System Loaded: loaded (/usr/lib/systemd/system/initrd-usr-fs.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ initrd.target - Initrd Default Target Loaded: loaded (/usr/lib/systemd/system/initrd.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ● integritysetup.target - Local Integrity Protected Volumes Loaded: loaded (/usr/lib/systemd/system/integritysetup.target; static) Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd.special(7) Notice: journal has been rotated since unit was started, output may be incomplete. ● local-fs-pre.target - Preparation for Local File Systems Loaded: loaded (/usr/lib/systemd/system/local-fs-pre.target; static) Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:38 np0000001290 systemd[1]: Reached target local-fs-pre.target - Preparation for Local File Systems. ● local-fs.target - Local File Systems Loaded: loaded (/usr/lib/systemd/system/local-fs.target; static) Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:38 np0000001290 systemd[1]: Reached target local-fs.target - Local File Systems. ● multi-user.target - Multi-User System Loaded: loaded (/usr/lib/systemd/system/multi-user.target; static) Active: active since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:44 np0000001290 systemd[1]: Reached target multi-user.target - Multi-User System. ● network-online.target - Network is Online Loaded: loaded (/usr/lib/systemd/system/network-online.target; static) Active: active since Fri 2026-05-22 15:45:42 UTC; 46min ago Docs: man:systemd.special(7) https://systemd.io/NETWORK_ONLINE May 22 15:45:42 np0000001290 systemd[1]: Reached target network-online.target - Network is Online. ● network-pre.target - Preparation for Network Loaded: loaded (/usr/lib/systemd/system/network-pre.target; static) Active: active since Fri 2026-05-22 15:45:39 UTC; 46min ago Docs: man:systemd.special(7) https://systemd.io/NETWORK_ONLINE May 22 15:45:39 np0000001290 systemd[1]: Reached target network-pre.target - Preparation for Network. ● network.target - Network Loaded: loaded (/usr/lib/systemd/system/network.target; static) Active: active since Fri 2026-05-22 15:45:39 UTC; 46min ago Docs: man:systemd.special(7) https://systemd.io/NETWORK_ONLINE May 22 15:45:39 np0000001290 systemd[1]: Reached target network.target - Network. ● nss-lookup.target - Host and Network Name Lookups Loaded: loaded (/usr/lib/systemd/system/nss-lookup.target; static) Active: active since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:44 np0000001290 systemd[1]: Reached target nss-lookup.target - Host and Network Name Lookups. ○ nss-user-lookup.target - User and Group Name Lookups Loaded: loaded (/usr/lib/systemd/system/nss-user-lookup.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ● paths.target - Path Units Loaded: loaded (/usr/lib/systemd/system/paths.target; static) Active: active since Fri 2026-05-22 15:45:42 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:42 np0000001290 systemd[1]: Reached target paths.target - Path Units. ○ remote-cryptsetup.target - Remote Encrypted Volumes Loaded: loaded (/usr/lib/systemd/system/remote-cryptsetup.target; disabled; preset: enabled) Active: inactive (dead) Docs: man:systemd.special(7) ● remote-fs-pre.target - Preparation for Remote File Systems Loaded: loaded (/usr/lib/systemd/system/remote-fs-pre.target; static) Active: active since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:44 np0000001290 systemd[1]: Reached target remote-fs-pre.target - Preparation for Remote File Systems. ● remote-fs.target - Remote File Systems Loaded: loaded (/usr/lib/systemd/system/remote-fs.target; enabled; preset: enabled) Active: active since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:44 np0000001290 systemd[1]: Reached target remote-fs.target - Remote File Systems. ○ remote-veritysetup.target - Remote Verity Protected Volumes Loaded: loaded (/usr/lib/systemd/system/remote-veritysetup.target; disabled; preset: enabled) Active: inactive (dead) Docs: man:systemd.special(7) ○ rescue.target - Rescue Mode Loaded: loaded (/usr/lib/systemd/system/rescue.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ shutdown.target - System Shutdown Loaded: loaded (/usr/lib/systemd/system/shutdown.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ sleep.target - Sleep Loaded: loaded (/usr/lib/systemd/system/sleep.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ● slices.target - Slice Units Loaded: loaded (/usr/lib/systemd/system/slices.target; static) Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd.special(7) Notice: journal has been rotated since unit was started, output may be incomplete. ● snapd.mounts-pre.target - Mounting snaps Loaded: loaded (/usr/lib/systemd/system/snapd.mounts-pre.target; static) Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Notice: journal has been rotated since unit was started, output may be incomplete. ● snapd.mounts.target - Mounted snaps Loaded: loaded (/usr/lib/systemd/system/snapd.mounts.target; static) Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Notice: journal has been rotated since unit was started, output may be incomplete. ● sockets.target - Socket Units Loaded: loaded (/usr/lib/systemd/system/sockets.target; static) Active: active since Fri 2026-05-22 15:45:42 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:42 np0000001290 systemd[1]: Reached target sockets.target - Socket Units. ○ soft-reboot.target - Reboot System Userspace Loaded: loaded (/usr/lib/systemd/system/soft-reboot.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ suspend-then-hibernate.target - Suspend; Hibernate if not used for a period of time Loaded: loaded (/usr/lib/systemd/system/suspend-then-hibernate.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ suspend.target - Suspend Loaded: loaded (/usr/lib/systemd/system/suspend.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ● swap.target - Swaps Loaded: loaded (/usr/lib/systemd/system/swap.target; static) Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd.special(7) Notice: journal has been rotated since unit was started, output may be incomplete. ● sysinit.target - System Initialization Loaded: loaded (/usr/lib/systemd/system/sysinit.target; static) Active: active since Fri 2026-05-22 15:45:42 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:42 np0000001290 systemd[1]: Reached target sysinit.target - System Initialization. ● time-set.target - System Time Set Loaded: loaded (/usr/lib/systemd/system/time-set.target; static) Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd.special(7) Notice: journal has been rotated since unit was started, output may be incomplete. ● time-sync.target - System Time Synchronized Loaded: loaded (/usr/lib/systemd/system/time-sync.target; static) Active: active since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:44 np0000001290 systemd[1]: Reached target time-sync.target - System Time Synchronized. ● timers.target - Timer Units Loaded: loaded (/usr/lib/systemd/system/timers.target; static) Active: active since Fri 2026-05-22 15:45:44 UTC; 46min ago Docs: man:systemd.special(7) May 22 15:45:44 np0000001290 systemd[1]: Reached target timers.target - Timer Units. ○ umount.target - Unmount All Filesystems Loaded: loaded (/usr/lib/systemd/system/umount.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ○ veritysetup-pre.target - Local Verity Protected Volumes (Pre) Loaded: loaded (/usr/lib/systemd/system/veritysetup-pre.target; static) Active: inactive (dead) Docs: man:systemd.special(7) ● veritysetup.target - Local Verity Protected Volumes Loaded: loaded (/usr/lib/systemd/system/veritysetup.target; static) Active: active since Fri 2026-05-22 15:45:38 UTC; 46min ago Docs: man:systemd.special(7) Notice: journal has been rotated since unit was started, output may be incomplete. ○ apport-autoreport.timer - Process error reports when automatic reporting is enabled (timer based) Loaded: loaded (/usr/lib/systemd/system/apport-autoreport.timer; enabled; preset: enabled) Active: inactive (dead) Trigger: n/a Triggers: ● apport-autoreport.service Condition: start condition unmet at Fri 2026-05-22 15:45:42 UTC; 46min ago May 22 15:45:42 np0000001290 systemd[1]: apport-autoreport.timer - Process error reports when automatic reporting is enabled (timer based) was skipped because of an unmet condition check (ConditionPathExists=/var/lib/apport/autoreport). ● dpkg-db-backup.timer - Daily dpkg database backup timer Loaded: loaded (/usr/lib/systemd/system/dpkg-db-backup.timer; enabled; preset: enabled) Active: active (waiting) since Fri 2026-05-22 15:45:44 UTC; 46min ago Trigger: Sat 2026-05-23 00:00:00 UTC; 7h left Triggers: ● dpkg-db-backup.service Docs: man:dpkg(1) May 22 15:45:44 np0000001290 systemd[1]: Started dpkg-db-backup.timer - Daily dpkg database backup timer. ● e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems Loaded: loaded (/usr/lib/systemd/system/e2scrub_all.timer; enabled; preset: enabled) Active: active (waiting) since Fri 2026-05-22 15:45:44 UTC; 46min ago Trigger: Sun 2026-05-24 03:10:01 UTC; 1 day 10h left Triggers: ● e2scrub_all.service May 22 15:45:44 np0000001290 systemd[1]: Started e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems. ● fstrim.timer - Discard unused filesystem blocks once a week Loaded: loaded (/usr/lib/systemd/system/fstrim.timer; enabled; preset: enabled) Active: active (waiting) since Fri 2026-05-22 15:45:44 UTC; 46min ago Trigger: Mon 2026-05-25 00:39:42 UTC; 2 days left Triggers: ● fstrim.service Docs: man:fstrim May 22 15:45:44 np0000001290 systemd[1]: Started fstrim.timer - Discard unused filesystem blocks once a week. ● fwupd-refresh.timer - Refresh fwupd metadata regularly Loaded: loaded (/usr/lib/systemd/system/fwupd-refresh.timer; enabled; preset: enabled) Active: active (waiting) since Fri 2026-05-22 15:45:44 UTC; 46min ago Trigger: Fri 2026-05-22 17:45:56 UTC; 1h 14min left Triggers: ● fwupd-refresh.service May 22 15:45:44 np0000001290 systemd[1]: Started fwupd-refresh.timer - Refresh fwupd metadata regularly. ● logrotate.timer - Daily rotation of log files Loaded: loaded (/usr/lib/systemd/system/logrotate.timer; enabled; preset: enabled) Active: active (waiting) since Fri 2026-05-22 15:45:44 UTC; 46min ago Trigger: Sat 2026-05-23 00:00:00 UTC; 7h left Triggers: ● logrotate.service Docs: man:logrotate(8) man:logrotate.conf(5) May 22 15:45:44 np0000001290 systemd[1]: Started logrotate.timer - Daily rotation of log files. ● man-db.timer - Daily man-db regeneration Loaded: loaded (/usr/lib/systemd/system/man-db.timer; enabled; preset: enabled) Active: active (waiting) since Fri 2026-05-22 15:45:44 UTC; 46min ago Trigger: Fri 2026-05-22 17:06:08 UTC; 34min left Triggers: ● man-db.service Docs: man:mandb(8) May 22 15:45:44 np0000001290 systemd[1]: Started man-db.timer - Daily man-db regeneration. ● motd-news.timer - Message of the Day Loaded: loaded (/usr/lib/systemd/system/motd-news.timer; enabled; preset: enabled) Active: active (waiting) since Fri 2026-05-22 15:45:44 UTC; 46min ago Trigger: Sat 2026-05-23 02:07:31 UTC; 9h left Triggers: ● motd-news.service May 22 15:45:44 np0000001290 systemd[1]: Started motd-news.timer - Message of the Day. ○ snapd.snap-repair.timer - Timer to automatically fetch and run repair assertions Loaded: loaded (/usr/lib/systemd/system/snapd.snap-repair.timer; enabled; preset: enabled) Active: inactive (dead) Trigger: n/a Triggers: ● snapd.snap-repair.service Condition: start condition unmet at Fri 2026-05-22 15:45:44 UTC; 46min ago May 22 15:45:44 np0000001290 systemd[1]: snapd.snap-repair.timer - Timer to automatically fetch and run repair assertions was skipped because no trigger condition checks were met. ● sysstat-collect.timer - Run system activity accounting tool every 10 minutes Loaded: loaded (/usr/lib/systemd/system/sysstat-collect.timer; enabled; preset: enabled) Active: active (waiting) since Fri 2026-05-22 15:45:44 UTC; 46min ago Trigger: Fri 2026-05-22 16:40:00 UTC; 8min left Triggers: ● sysstat-collect.service May 22 15:45:44 np0000001290 systemd[1]: Started sysstat-collect.timer - Run system activity accounting tool every 10 minutes. ● sysstat-summary.timer - Generate summary of yesterday's process accounting Loaded: loaded (/usr/lib/systemd/system/sysstat-summary.timer; enabled; preset: enabled) Active: active (waiting) since Fri 2026-05-22 15:45:44 UTC; 46min ago Trigger: Sat 2026-05-23 00:07:00 UTC; 7h left Triggers: ● sysstat-summary.service May 22 15:45:44 np0000001290 systemd[1]: Started sysstat-summary.timer - Generate summary of yesterday's process accounting. ● systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-clean.timer; static) Active: active (waiting) since Fri 2026-05-22 15:45:42 UTC; 46min ago Trigger: Sat 2026-05-23 16:00:35 UTC; 23h left Triggers: ● systemd-tmpfiles-clean.service Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) May 22 15:45:42 np0000001290 systemd[1]: Started systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories. ○ ua-timer.timer - Ubuntu Pro Timer for running repeated jobs Loaded: loaded (/usr/lib/systemd/system/ua-timer.timer; enabled; preset: enabled) Active: inactive (dead) Trigger: n/a Triggers: ● ua-timer.service Condition: start condition unmet at Fri 2026-05-22 15:45:42 UTC; 46min ago May 22 15:45:42 np0000001290 systemd[1]: ua-timer.timer - Ubuntu Pro Timer for running repeated jobs was skipped because of an unmet condition check (ConditionPathExists=/var/lib/ubuntu-advantage/private/machine-token.json). ● update-notifier-download.timer - Download data for packages that failed at package install time Loaded: loaded (/usr/lib/systemd/system/update-notifier-download.timer; enabled; preset: enabled) Active: active (waiting) since Fri 2026-05-22 15:45:42 UTC; 46min ago Trigger: Sat 2026-05-23 15:50:38 UTC; 23h left Triggers: ● update-notifier-download.service May 22 15:45:42 np0000001290 systemd[1]: Started update-notifier-download.timer - Download data for packages that failed at package install time. ● update-notifier-motd.timer - Check to see whether there is a new version of Ubuntu available Loaded: loaded (/usr/lib/systemd/system/update-notifier-motd.timer; enabled; preset: enabled) Active: active (waiting) since Fri 2026-05-22 15:45:44 UTC; 46min ago Trigger: Thu 2026-05-28 03:27:06 UTC; 5 days left Triggers: ● update-notifier-motd.service May 22 15:45:44 np0000001290 systemd[1]: Started update-notifier-motd.timer - Check to see whether there is a new version of Ubuntu available.