http://bugzilla.opensuse.org/show_bug.cgi?id=1094762 Bug ID: 1094762 Summary: Systemd timeouts while zypper dup upgrade from 42.3 - starts when old systemd package gets erased and replaced Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening@forge.provo.novell.com Reporter: abittner@opensuse.org QA Contact: jsrain@suse.com Found By: --- Blocker: --- I am apparently having major trouble while upgrading a normal 42.3 system via zypper dup to 15.0 I have even found some other people talking about this behavior in a very recent thread on opensuse ml: <https://lists.opensuse.org/opensuse/2018-05/msg00801.html> I am having the very same troubles as the thread starter. All following upgrades of packages that are systemd or services related seem to fail to talk to the crashed or non responsive systemd main components. journalctl still works and I have traced it to some following loglines: ..... May 26 22:49:40 dpg-ppb-smu-tux01 [RPM][14252]: erase libldap-2_4-2-2.4.44-18.1.x86_64: success May 26 22:49:40 dpg-ppb-smu-tux01 [RPM][14252]: install libldap-2_4-2-2.4.46-lp150.7.1.x86_64: success May 26 22:49:40 dpg-ppb-smu-tux01 [RPM][14252]: Transaction ID 5b09c864 finished: 0 May 26 22:49:40 dpg-ppb-smu-tux01 [RPM][14255]: Transaction ID 5b09c864 started May 26 22:49:40 dpg-ppb-smu-tux01 [RPM][14255]: erase libcurl4-7.37.0-36.1.x86_64: success May 26 22:49:41 dpg-ppb-smu-tux01 [RPM][14255]: install libcurl4-7.59.0-lp150.1.1.x86_64: success May 26 22:49:41 dpg-ppb-smu-tux01 [RPM][14255]: erase libcurl4-7.37.0-36.1.x86_64: success May 26 22:49:41 dpg-ppb-smu-tux01 [RPM][14255]: install libcurl4-7.59.0-lp150.1.1.x86_64: success May 26 22:49:41 dpg-ppb-smu-tux01 [RPM][14255]: Transaction ID 5b09c864 finished: 0 May 26 22:49:41 dpg-ppb-smu-tux01 [RPM][14258]: Transaction ID 5b09c865 started May 26 22:49:41 dpg-ppb-smu-tux01 [RPM][14258]: erase systemd-228-50.1.x86_64: success May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses..... ..... when the zypper dup erases the systemd-228-50.1.x86_64 package from 42.3 it then installs the new systemd package from leap 15.0 I suppose and the trouble begins there. .... May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus[1011]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 dbus-daemon[1011]: Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses May 26 22:49:41 dpg-ppb-smu-tux01 polkitd[1099]: Reloading rules May 26 22:49:42 dpg-ppb-smu-tux01 systemd-sysusers[14264]: Creating group systemd-coredump with gid 480. May 26 22:49:42 dpg-ppb-smu-tux01 systemd-sysusers[14264]: Creating user systemd-coredump (systemd Core Dumper) with uid 480 and gid 480. May 26 22:49:42 dpg-ppb-smu-tux01 nscd[1035]: 1035 monitored file `/etc/group` was moved into place, adding watch May 26 22:49:42 dpg-ppb-smu-tux01 nscd[1035]: 1035 monitored file `/etc/passwd` was moved into place, adding watch May 26 22:49:42 dpg-ppb-smu-tux01 nscd[1035]: 1035 monitored file `/etc/group` was written to May 26 22:49:42 dpg-ppb-smu-tux01 nscd[1035]: 1035 monitored file `/etc/passwd` was written to May 26 22:49:42 dpg-ppb-smu-tux01 polkitd[1099]: Collecting garbage unconditionally... May 26 22:49:42 dpg-ppb-smu-tux01 systemd[1]: Reexecuting. ..... Can I be of any help on how to track down the root cause of this bug? I am worried that my production system is now in some limbo state whenever this whole zypper dup eventually might finish. The thread speaks about successfull reboots after a very long zypper dup upgrade process though, but I am having important data on this machine and I am unsure if the dup process really goes through properly with all packages even when systemd is nonresponsive. Any emergency hints? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.