25.05.2018 15:10, cagsm пишет:
There seems to be a moment while zypper dup (coming from 42.3) when apparently the system process or daemon seems to be getting replaced or something happens, that follwing package updates/upgrades try to trigger a restart or reload of systemd or its parts and always fail into a timeout for a very long time over and over again, thus delaying the whole zypper dup process to a multi-hour (last system I tried) endeavour.
I was waiting to post this message to the list, to make sure a second system were behaving the same (annoying to my likings) way, and yes it does. I will probably wait and sit this out again, and this will take many hours here....
Is this the proper way? Is this happening for everybody? Is this the desired experience for us end-users? Is there no better way of handling this?
I cant remember of these tens? hundreds? of packages all trying to communicate to or with systemd components, and failing timeouting in previous opensuse releases/upgrades.
Has this never been tested? Dont seems right to me. Maybe I am too enthusiastic about all of this :(
I get plenty of this kind of messages:
( 564/2995) Installing: wicked-service-0.6.47-lp150.1.1.x86_64 ..........................................................................................................[done] Additional rpm output: Failed to reload daemon: Activation of org.freedesktop.systemd1 timed out Failed to reload daemon: Activation of org.freedesktop.systemd1 timed out Failed to enable unit: Connection timed out Failed to reload daemon: Activation of org.freedesktop.systemd1 timed out Failed to try-restart wickedd.service: Activation of org.freedesktop.systemd1 timed out See system logs and 'systemctl status wickedd.service' for details.
I tried update and I did not see them. It sounds like dbus daemon was restarted or crashed. You may try to check logs whether it was the case. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org