Good morning, (f39 workstation last patched Thursday, August 22)
My boot logs (from journalctl -b > log20240826.txt) contain the warning below. Note that for context, I'm including the last 5 lines before the warning and the first 5 lines after the warning. I also added line numbers. - - - - - - 1021 Aug 26 08:01:58 coyote systemd[1]: RTC configured in localtime, applying delta of -360 minutes to system time. 1022 Aug 26 08:01:58 coyote systemd[1]: Relabeled /dev, /dev/shm, /run, /sys/fs/cgroup in 78.112ms. 1023 Aug 26 08:01:58 coyote systemd[1]: systemd 254.16-1.fc39 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) 1024 Aug 26 08:01:58 coyote systemd[1]: Detected architecture x86-64. 1025 Aug 26 08:01:58 coyote systemd[1]: bpf-lsm: LSM BPF program attached /1026 Aug 26 08:01:58 coyote systemd-sysv-generator[595]: SysV service '/etc/rc.d/init.d/network' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it safe, robust and future-proof. ! This compatibility logic is deprecated, expect removal soon. !/ 1027 Aug 26 08:01:58 coyote systemd[1]: initrd-switch-root.service: Deactivated successfully. 1028 Aug 26 08:01:58 coyote systemd[1]: Stopped initrd-switch-root.service - Switch Root. 1029 Aug 26 08:01:58 coyote systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1. 1030 Aug 26 08:01:58 coyote systemd[1]: Created slice system-akmods\x2dkeygen.slice - Slice /system/akmods-keygen. 1031 Aug 26 08:01:58 coyote systemd[1]: Created slice system-getty.slice - Slice /system/getty. - - - - - - Line 1026 is the line of concern. Is this a false alarm that I can ignore, or a ticking time bomb (a warning that needs attention soon), a problem for which I've been lucky to not yet see symptoms (other than the log entry), or a major immediate problem? The warning suggests updating some package. I do a "dnf upgrade" weekly. Why did the update not already automatically happen? -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
