Are these dnf errors a problem?

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

   Running scriptlet: systemd-resolved-253.12-1.fc38.x86_64                          
150/150
   Running scriptlet: kernel-modules-core-6.5.8-200.fc38.x86_64                      
150/150
   Running scriptlet: kernel-core-6.5.8-200.fc38.x86_64                              
150/150
   Running scriptlet: selinux-policy-targeted-38.30-1.fc38.noarch                    
150/150
   Running scriptlet: nss-3.94.0-2.fc38.x86_64                                       
150/150
   Running scriptlet: kernel-modules-6.5.8-200.fc38.x86_64                           
150/150
   Running scriptlet: libqalculate-4.8.0-1.fc38.x86_64                               
150/150
Failed to reload daemon: Connection timed out

Failed to list units: Connection timed out

Failed to start jobs: Connection timed out

Failed to list units: Connection timed out

Failed to reload daemon: Connection timed out

-- 
Eyal at Home (fedora(a)eyal.emu.id.au)

[Samuel Sieb]

On 10/29/23 17:25, fedora(a)eyal.emu.id.au 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.

On 30/10/2023 12.03, Samuel Sieb wrote:
>  On 10/29/23 17:25, fedora(a)eyal.emu.id.au 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. 
Thanks Samuel,

It looks OK, but just in case, will reinstalling the mentioned packages help? hurt?
risky?
	systemd-udev
	systemd
or is there a way to request re-running just the scriptlets?

-- 
Eyal at Home (fedora(a)eyal.emu.id.au)

[Samuel Sieb]

On 10/29/23 20:06, fedora(a)eyal.emu.id.au wrote:
>  On 30/10/2023 12.03, Samuel Sieb wrote:
> > On 10/29/23 17:25, fedora(a)eyal.emu.id.au 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.
>  
>  Thanks Samuel,
>  
>  It looks OK, but just in case, will reinstalling the mentioned packages 
>  help? hurt? risky?
>       systemd-udev
>       systemd 
It won't hurt anything.

>  or is there a way to request re-running just the scriptlets? 
There isn't.