Having an issue upgrading 42 to 43 beta via DNF. Upgrade goes smoothly to about 380 files and then quits with the error: systemd.hostnamed.service failed.
Thoughts?
No idea why it fails but I see AVC denies in the upgrade log.
I saw this at the end of the upgrade process, but after a closer look it started quite early during the upgrade, but continued.
first occurence:
Sep 23 12:18:58 phantom systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
Sep 23 12:18:58 phantom audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=polkit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Sep 23 12:18:58 phantom audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=bolt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? te
rminal=? res=success'
Sep 23 12:18:58 phantom audit[855]: AVC avc: denied { create } for pid=855 comm="systemd-hostnam" name="io.systemd.Hostname" scontext=system_u:system_r:systemd_hostnamed_t:s0 tcontext=system_u:object_r:
init_var_run_t:s0 tclass=sock_file permissive=0
Sep 23 12:18:58 phantom audit[855]: SYSCALL arch=c000003e syscall=49 success=no exit=-13 a0=9 a1=7ffd160ba470 a2=23 a3=637365442e656d61 items=0 ppid=1 pid=855 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsui
d=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-hostnam" exe="/usr/lib/systemd/systemd-hostnamed" subj=system_u:system_r:systemd_hostnamed_t:s0 key=(null)
Sep 23 12:18:58 phantom audit: PROCTITLE proctitle="/usr/lib/systemd/systemd-hostnamed"
Sep 23 12:18:58 phantom systemd-hostnamed[855]: Failed to bind to Varlink socket: Permission denied
Sep 23 12:18:58 phantom systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=1/FAILURE
Sep 23 12:18:58 phantom systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'.
Sep 23 12:18:58 phantom systemd[1]: Failed to start systemd-hostnamed.service - Hostname Service.
Sep 23 12:18:58 phantom audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 23 12:18:58 phantom systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
all res=failed occurences:
Sep 23 12:18:58 phantom audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 23 12:18:58 phantom audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 23 12:24:36 phantom audit[28468]: ADD_USER pid=28468 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:useradd_t:s0 msg='op=add-user acct="gnome-initial-setup" exe="/usr/bin/useradd" hostname=? addr=? terminal=? res=failed'
Sep 23 12:40:53 phantom audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 23 12:40:53 phantom kernel: audit: type=1131 audit(1758624053.923:232): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 23 12:43:50 phantom audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 23 12:43:50 phantom audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 23 12:44:05 phantom audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf5-offline-transaction comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 23 12:44:05 phantom audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf5-offline-transaction-cleanup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 23 12:45:48 phantom audit[28664]: AUDIT1101 pid=28664 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:local_login_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=? acct="mark" exe="/usr/bin/login" hostname=phantom addr=? terminal=/dev/tty2 res=failed'
Sep 23 12:45:48 phantom kernel: audit: type=1101 audit(1758624348.145:3816): pid=28664 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:local_login_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=? acct="mark" exe="/usr/bin/login" hostname=phantom addr=? terminal=/dev/tty2 res=failed'
Sep 23 12:47:25 phantom audit[56847]: AUDIT1100 pid=56847 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:local_login_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=? acct="root" exe="/usr/bin/login" hostname=phantom addr=? terminal=/dev/tty2 res=failed'
Sep 23 12:47:25 phantom kernel: audit: type=1100 audit(1758624445.520:3819): pid=56847 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:local_login_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=? acct="root" exe="/usr/bin/login" hostname=phantom addr=? terminal=/dev/tty2 res=failed'
Sep 23 12:47:27 phantom audit[56847]: AUDIT1112 pid=56847 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:local_login_t:s0-s0:c0.c1023 msg='op=login id=0 exe="/usr/bin/login" hostname=phantom addr=? terminal=tty2 res=failed'
Sep 23 12:47:27 phantom kernel: audit: type=1112 audit(1758624447.438:3820): pid=56847 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:local_login_t:s0-s0:c0.c1023 msg='op=login id=0 exe="/usr/bin/login" hostname=phantom addr=? terminal=tty2 res=failed'
the lines at the end were my login attempts because the automatic reboot have failed
Sep 23 12:44:02 phantom audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=run-p55670-i55671 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 23 12:44:04 phantom dnf5[843]: [6495/6495] Removing libgcc-0:15.2.1-1. 100% | 0.0 B/s | 10.0 B | 01m22s
Sep 23 12:44:04 phantom dnf5[843]: Warning: skipped OpenPGP checks for 3282 packages from repositories: copr:copr.fedorainfracloud.org:anotheruser:test, fedora, fedora-cisco-openh264, rpmfusion-free, rpmfusion-free-tainted, rpmfusion-free-updates-testing, rpmfusion-nonfree, rpmfusion-nonfree-nvidia-driver
Sep 23 12:44:04 phantom dnf5[843]: Transaction complete! Cleaning up and rebooting...
Sep 23 12:44:05 phantom dnf5[843]: [org.freedesktop.DBus.Error.AccessDenied] Access denied due to active block inhibitor
Sep 23 12:44:05 phantom audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf5-offline-transaction comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 23 12:44:05 phantom systemd[1]: dnf5-offline-transaction.service: Main process exited, code=exited, status=1/FAILURE
Sep 23 12:44:05 phantom systemd[1]: dnf5-offline-transaction.service: Failed with result 'exit-code'.
Sep 23 12:44:05 phantom systemd[1]: Failed to start dnf5-offline-transaction.service - Offline upgrades/transactions using DNF 5.
Sep 23 12:44:05 phantom systemd[1]: dnf5-offline-transaction.service: Consumed 7min 54.610s CPU time, 21.9G memory peak.
Sep 23 12:44:05 phantom systemd[1]: dnf5-offline-transaction.service: Triggering OnFailure= dependencies.
Sep 23 12:44:05 phantom systemd[1]: Reached target system-update.target - Offline System Update.
Sep 23 12:44:05 phantom systemd[1]: Starting dnf5-offline-transaction-cleanup.service - Offline upgrade/transaction using DNF 5 failed...
Sep 23 12:44:05 phantom systemd[1]: system-update-cleanup.service - Remove the Offline System Updates Symlink was skipped because no trigger condition checks were met.
Sep 23 12:44:05 phantom systemctl[55854]: Call to Reboot failed: Access denied
Sep 23 12:44:05 phantom systemd[1]: dnf5-offline-transaction-cleanup.service: Main process exited, code=exited, status=1/FAILURE
Sep 23 12:44:05 phantom systemd[1]: dnf5-offline-transaction-cleanup.service: Failed with result 'exit-code'.
Sep 23 12:44:05 phantom systemd[1]: Failed to start dnf5-offline-transaction-cleanup.service - Offline upgrade/transaction using DNF 5 failed.
Sep 23 12:44:05 phantom audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf5-offline-transaction-cleanup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 23 12:44:31 phantom runuser[46838]: pam_unix(runuser:session): session closed for user akmods
Sep 23 12:44:31 phantom audit[46838]: AUDIT1106 pid=46838 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_unix acct="akmods" exe="/usr/bin/runuser" hostname=? addr=? terminal=? res=success'
it even finished building the nvidia kernel modules with akmods.
after a while I rebooted via CTRL+ALT+DEL
Then you have to set SELinux to “permissive” in /etc/selinux/config and reboot. You can set it back to “enforcing” once all the SELinux issues are fixed.
This log is from an dnf5 offline-update reboot session! How am I supposed to do this?
But it may be a good hint for others who want to upgrade to set SELinux to permissive first.
It looks like it went though the whole update process and then just the final reboot command was blocked “due to active block inhibitor”. It might mean that there was still a Akmod build running in the background and inhibiting the reboot? I don’t know, but my guess for a workaround would be to do an online CLI update (ideally from the non-graphical “multi-user” mode).
Edit: It does look like something is wrong with the SELinux perms though, so maybe setting SELinux to permissive mode temporarily would work around the problem. There are two errors and I’m unclear which is the source of the problem. Running the update from the CLI might also work around SELinux permissions.
Do you have the rpmfusion nvidia drivers?
I recall a comment recently that akmods builds can break offline updates.
Anyone else know more about this?
It went through. Yeah, you’re right, the kernel modules were built after that, but it already started
Sep 23 12:43:34 phantom dracut[32971]: ========================================================================
Sep 23 12:43:34 phantom dracut[32971]: dracut cmdline:
Sep 23 12:43:34 phantom dracut[32971]: rd.driver.pre=btrfs
Sep 23 12:43:35 phantom dracut[32971]: *** Creating initramfs image file '/boot/initramfs-6.17.0-0.rc6.49.fc43.x86_64.img' done ***
Sep 23 12:43:38 phantom systemd[1]: Created slice system-akmods\x2dkeygen.slice - Slice /system/akmods-keygen.
Sep 23 12:43:38 phantom systemd[1]: akmods-keygen@akmods-keygen.service - Akmods Secure boot MOK Key Generation was skipped because no trigger condition checks were met.
Sep 23 12:43:38 phantom systemd[1]: Created slice system-akmods.slice - Slice /system/akmods.
Sep 23 12:43:38 phantom systemd[1]: Reached target akmods-keygen.target.
I always upgrade via dnf system-upgrade download --releasever=xx
It was the first time that I used dnf5 offline reboot instead of dnf system-upgrade reboot, but I guess the outcome would be the same 
So your upgrade ultimately succeeded, but you are seeing sporadic SELinux errors (notably for systemd-hostnamed)? To fix the SELinux permissions, I think running sudo fixfiles -F onboot and then rebooting your system ought to work.
everything is good! There were no SELinux errors after reboot. Everything looks ok and system is stable, even suspend with s2idle + Nvidia seem to work.
So I am quite puzzled why @bdconnolly 's attempt to upgrade to f43 failed after only 380 files.
1 Like
SELinux solution not working either. I’m puzzled, too.
I guess this was directed at me. Yes, rpmfusion drivers. No idea if akmods break offline updates. Do regular updates online, but release upgrades are offline.
According to dnf history, I also upgraded from f41 to f42 with nvidia drivers installed, but it looks like akmods was not run during upgrade process, but rather during the first first boot of f42.
ID Command line Date and time Action(s) Altered
449 dnf -y install --nogpgcheck --disablerepo=* /tmp/akmods.RZF8HM3T/results/kmod-nvidia-6.14.1-300.fc42.x86_64-570.133.07-1. 2025-04-12 08:20:35 1
448 dnf system-upgrade download --releasever=42 2025-04-12 08:05:36 5467
is there any log you could share?
dnf system-upgrade log
If you use BTRFS, then try a btrfs scrub first.
sudo btrfs scrub start -Brd / should come back with no errors. And run a journalctrl -f session in another terminal. It will report names (or inodes? ) of damaged files.
Nope. When it fails, I can only revert to a backup image.
This is 42 to 43.
What does systemctl status systemd-hostnamed.service show? Do you have the service masked?
brian@51mR2:~$ systemctl status systemd-hostnamed.service
â—‹ systemd-hostnamed.service - Hostname Service
Loaded: loaded (/usr/lib/systemd/system/systemd-hostnamed.service; static)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: inactive (dead) since Wed 2025-09-24 17:51:13 EDT; 26min ago
Duration: 30.323s
Invocation: d203012793d44ae4a90d231ce3949f9b
TriggeredBy: â—Ź systemd-hostnamed.socket
Docs: man:systemd-hostnamed.service(8)
man:hostname(5)
man:machine-info(5)
man:org.freedesktop.hostname1(5)
Process: 6886 ExecStart=/usr/lib/systemd/systemd-hostnamed (code=exited, status=0/SUCCESS)
Main PID: 6886 (code=exited, status=0/SUCCESS)
Status: “Shutting down…”
Mem peak: 3.4M
CPU: 45ms
Sep 24 17:50:43 51mR2 systemd[1]: Starting systemd-hostnamed.service - Hostname Service…
Sep 24 17:50:43 51mR2 systemd[1]: Started systemd-hostnamed.service - Hostname Service.
Sep 24 17:51:13 51mR2 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
It looks like it is working. It seems like an odd thing to block an upgrade. It isn’t normally that important of a service. I’d be tempted to set it so that it will never report failure (even if it failed) and see if that is enough to get the upgrade to finish.
Is plymouth enabled? Press ESC once during upgrade or remove rhgb from kernel cmdline and you will see the packages upgraded last.
tried… failed.
How? I’m game.