On 10/29/23 17:25, fedora@xxxxxxxxxxxxxx wrote:
F38
Yesterday I did a 'dnf update' when the machine had issues (I know, a
bad idea).
During the update I noticed these failures (see below). Each time there
was some wait before proceeding.
I think that systemd was the cause as other cron jobs encountered this
error:
Failed to retrieve unit state: Connection timed out
Do I need to do something now? After a reboot things look fine.
TIA
Running scriptlet:
systemd-udev-253.10-1.fc38.x86_64 105/150
Failed to set unit properties on systemd-timesyncd.service: Connection
timed out
Failed to set unit properties on systemd-udevd.service: Connection timed
out
Running scriptlet:
systemd-253.10-1.fc38.x86_64 123/150
Failed to set unit properties on systemd-hostnamed.service: Connection
timed out
Failed to set unit properties on systemd-timedated.service: Connection
timed out
Failed to set unit properties on systemd-journald.service: Connection
timed out
Failed to set unit properties on systemd-localed.service: Connection
timed out
Failed to set unit properties on systemd-userdbd.service: Connection
timed out
Failed to set unit properties on systemd-oomd.service: Connection timed out
It looks like dbus wasn't working or something like that. These errors
might be a problem, depending on what properties it was trying to set.
But if everything's working, then it's probably ok.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
