[opensuse] zypper dup - systemd related endless timeouts for even more endless number of packages
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. ( 568/2995) Installing: logrotate-3.13.0-lp150.2.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 try-restart logrotate.service: Connection timed out See system logs and 'systemctl status logrotate.service' for details. Failed to try-restart logrotate.timer: Connection timed out See system logs and 'systemctl status logrotate.timer' for details. (many more.....) (I am zypper dup-ing from via a screen terminal, exchanges zypper repos (oss, update-oss, non-oss, update-non-oss) via yast from 42.3 as url address to 15.0 obviously before), and issued a zypper dup --download-in-advance, not updates zypper itself or anything else) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-25 14:10, cagsm wrote:
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 :(
It is certainly tested, but you hit something that did not happen on the tests. I think that your network failed :-? No, something else. org.freedesktop.systemd1? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On Fri, May 25, 2018 at 2:18 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
It is certainly tested, but you hit something that did not happen on the tests. I think that your network failed :-? No, something else. org.freedesktop.systemd1?
as wrote, I have waited to at least test a second completely different system. All coming from 42.3, via zypper dup, in screen, via remote ssh into the system. All network interfaces are dhcp-v4 or fixed ipv4 ethernet, wired. nothing special. something is being replaced and restarted and then not available any more to subsequent next calles and queries to it, systemd related or its components and connected stuff. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, May 25, 2018 at 2:10 PM, cagsm <cumandgets0mem00f@gmail.com> wrote:
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.
( 568/2995) Installing: logrotate-3.13.0-lp150.2.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 try-restart logrotate.service: Connection timed out See system logs and 'systemctl status logrotate.service' for details. Failed to try-restart logrotate.timer: Connection timed out See system logs and 'systemctl status logrotate.timer' for details.
(1457/2995) Installing: cups-2.2.7-lp150.1.1.x86_64 .....................................................................................................................[done] Additional rpm output: SysV service cups-lpd@ does not exist, skipping SysV service cups-lpd does not exist, skipping Failed to reload daemon: Activation of org.freedesktop.systemd1 timed out Failed to preset unit: Connection timed out Failed to preset unit: Activation of org.freedesktop.systemd1 timed out Failed to preset unit: Activation of org.freedesktop.systemd1 timed out systemd service cups-lpd.service does not exist. Failed to reload daemon: Activation of org.freedesktop.systemd1 timed out Failed to try-restart cups.service: Connection timed out See system logs and 'systemctl status cups.service' for details. .... (1461/2995) Installing: cups-filters-1.20.3-lp150.1.1.x86_64 ............................................................................................................[done] Additional rpm output: Failed to reload daemon: Activation of org.freedesktop.systemd1 timed out Failed to disable unit: Activation of org.freedesktop.systemd1 timed out Failed to stop cups-browsed.service: Connection timed out See system logs and 'systemctl status cups-browsed.service' for details. Failed to get load state of cups-browsed.service: Activation of org.freedesktop.systemd1 timed out Failed to reload daemon: Activation of org.freedesktop.systemd1 timed out .... (1490/2995) Installing: samba-4.7.6+git.54.6e3276c9872-lp150.2.20.x86_64 ................................................................................................[done] Additional rpm output: SysV service samba-ad-dc does not exist, skipping Failed to reload daemon: Activation of org.freedesktop.systemd1 timed out Failed to preset unit: Activation of org.freedesktop.systemd1 timed out Updating /etc/sysconfig/samba ... Failed to reload daemon: Activation of org.freedesktop.systemd1 timed out Failed to try-restart nmb.service: Connection timed out See system logs and 'systemctl status nmb.service' for details. Failed to try-restart smb.service: Connection timed out See system logs and 'systemctl status smb.service' for details. .... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-25 14:29, cagsm wrote:
On Fri, May 25, 2018 at 2:10 PM, cagsm <> wrote:
I get plenty of this kind of messages:
...
(1457/2995) Installing: cups-2.2.7-lp150.1.1.x86_64 .....................................................................................................................[done] Additional rpm output: SysV service cups-lpd@ does not exist, skipping SysV service cups-lpd does not exist, skipping Failed to reload daemon: Activation of org.freedesktop.systemd1 timed out Failed to preset unit: Connection timed out Failed to preset unit: Activation of org.freedesktop.systemd1 timed out Failed to preset unit: Activation of org.freedesktop.systemd1 timed out systemd service cups-lpd.service does not exist. Failed to reload daemon: Activation of org.freedesktop.systemd1 timed out Failed to try-restart cups.service: Connection timed out See system logs and 'systemctl status cups.service' for details. ....
It must be this one: Telcontar:~ # locate org.freedesktop.systemd1.ser /usr/share/dbus-1/services/org.freedesktop.systemd1.service /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service Telcontar:~ # Try to restart it manually, see what it says. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On Fri, May 25, 2018 at 3:35 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
It must be this one: Telcontar:~ # locate org.freedesktop.systemd1.ser /usr/share/dbus-1/services/org.freedesktop.systemd1.service /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service Try to restart it manually, see what it says.
well i am still inside the still-upgrading system, i will just wait for the end of these delays.. its got still plenty of packages left to go ..... (2325/2995) Installing: ModemManager-1.6.12-lp150.1.4.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 try-restart ModemManager.service: Activation of org.freedesktop.systemd1 timed out See system logs and 'systemctl status ModemManager.service' for details. ..... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-25 16:01, cagsm wrote:
On Fri, May 25, 2018 at 3:35 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
It must be this one: Telcontar:~ # locate org.freedesktop.systemd1.ser /usr/share/dbus-1/services/org.freedesktop.systemd1.service /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service Try to restart it manually, see what it says.
well i am still inside the still-upgrading system, i will just wait for the end of these delays.. its got still plenty of packages left to go
Well, the idea is to start it now and see if it clears the delays. And also find out why it happened. So at least find the status: Telcontar:~ # systemctl status org.freedesktop.systemd1 ● org.freedesktop.systemd1.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) Telcontar:~ # -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
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
On Fri, May 25, 2018 at 8:04 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
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.
I have a third machine which didnt show any of this kind of trouble at all, also from 42.3 to 15.0 same upgrade via zypper dup. Now I wonder how can I check in what logs or what is the name of the main systemd process or component to check after? What logs do I check how? I have all rebooted the affected machines after the zypper dup eventually went through even if it took hours, and they all came up fine. The problematic machines were having for example reboot problems toward the end complaining about not finding certain files after issuing the reboot command, so I even needed a reboot -f to make it work. But they seem to have come back up normal into the 15.0 How can I find out what happend via the logs and how to avoid other machines waiting for the upgrade? TIA. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-25 20:04, Andrei Borzenkov wrote:
25.05.2018 15:10, cagsm пишет:
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.
I see them today. I'm updating a virtual machine via "zypper dup" from beta something to final, and I'm seeing them. It is going very slow. I can not copy paste from virtual box, it simply gets nothing in the clipboard despite being enabled. ssh to guest fails, ssh to host works, so I can extract some data that way. See attached. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 2018-05-27 12:06, Carlos E. R. wrote:
On 2018-05-25 20:04, Andrei Borzenkov wrote:
25.05.2018 15:10, cagsm пишет:
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.
I see them today.
I'm updating a virtual machine via "zypper dup" from beta something to final, and I'm seeing them. It is going very slow.
I can not copy paste from virtual box, it simply gets nothing in the clipboard despite being enabled. ssh to guest fails, ssh to host works, so I can extract some data that way. See attached.
I have paused the virtual machine so that I can run tests on the machine that people suggest here. Also took a snapshot of this instant. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
27.05.2018 13:18, Carlos E. R. пишет:
On 2018-05-27 12:06, Carlos E. R. wrote:
On 2018-05-25 20:04, Andrei Borzenkov wrote:
25.05.2018 15:10, cagsm пишет:
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.
I see them today.
I'm updating a virtual machine via "zypper dup" from beta something to final, and I'm seeing them. It is going very slow.
I can not copy paste from virtual box, it simply gets nothing in the clipboard despite being enabled. ssh to guest fails, ssh to host works, so I can extract some data that way. See attached.
I have paused the virtual machine so that I can run tests on the machine that people suggest here. Also took a snapshot of this instant.
I would suggest open bug report, assign to systemd. This will draw attention of exactly the right people.
On Sun, May 27, 2018 at 12:27 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
I would suggest open bug report, assign to systemd. This will draw attention of exactly the right people.
Bugs mailing list shows a bug already discussing this thread and issues with systemd: <https://lists.opensuse.org/opensuse-bugs/2018-05/msg03710.html> <http://bugzilla.opensuse.org/show_bug.cgi?id=1094762> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-27 12:27, Andrei Borzenkov wrote:
27.05.2018 13:18, Carlos E. R. пишет:
On 2018-05-27 12:06, Carlos E. R. wrote:
On 2018-05-25 20:04, Andrei Borzenkov wrote:
25.05.2018 15:10, cagsm пишет:
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.
I see them today.
I'm updating a virtual machine via "zypper dup" from beta something to final, and I'm seeing them. It is going very slow.
I can not copy paste from virtual box, it simply gets nothing in the clipboard despite being enabled. ssh to guest fails, ssh to host works, so I can extract some data that way. See attached.
I have paused the virtual machine so that I can run tests on the machine that people suggest here. Also took a snapshot of this instant.
I would suggest open bug report, assign to systemd. This will draw attention of exactly the right people.
Ok, doing so now. <https://bugzilla.opensuse.org/show_bug.cgi?id=1094771> -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On Sun, May 27, 2018 at 12:53 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
Ok, doing so now. <https://bugzilla.opensuse.org/show_bug.cgi?id=1094771>
dupe of: <http://bugzilla.opensuse.org/show_bug.cgi?id=1094762> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-27 12:55, cagsm wrote:
On Sun, May 27, 2018 at 12:53 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
Ok, doing so now. <https://bugzilla.opensuse.org/show_bug.cgi?id=1094771>
dupe of: <http://bugzilla.opensuse.org/show_bug.cgi?id=1094762>
Well, two reports, lets see if there is some response now. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (3)
-
Andrei Borzenkov -
cagsm -
Carlos E. R.