On Tue, 2020-05-19 at 19:02 +0100, Richard W.M. Jones wrote: > I was trying to chase down why modules.dep is no longer built in > Rawhide (which affects supermin and therefore libguestfs), but it > looks like there's a much more serious problem: > > https://kojipkgs.fedoraproject.org//work/tasks/8242/44698242/root.log > (from https://koji.fedoraproject.org/koji/taskinfo?taskID=44698142) > > DEBUG util.py:602: Running transaction > DEBUG util.py:602: /usr/bin/systemctl: error while loading shared > libraries: libibverbs.so.1: cannot open shared object file: No such > file or directory > DEBUG util.py:602: /sbin/udevadm: error while loading shared > libraries: libibverbs.so.1: cannot open shared object file: No such > file or directory > DEBUG util.py:602: /sbin/udevadm: error while loading shared > libraries: libibverbs.so.1: cannot open shared object file: No such > file or directory > DEBUG util.py:602: /sbin/udevadm: error while loading shared > libraries: libibverbs.so.1: cannot open shared object file: No such > file or directory Just to double check, I installed a rawhide installation and then ran ldd on both systemctl and udevadm. Neither of these are linked to libibverbs as far as I can tell. If they use libibverbs, they do it via dlopen, not static linking. So that being the case, these errors make no sense. > DEBUG util.py:602: /var/tmp/rpm-tmp.pYK3f6: line 6: 2005996 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset dbus.socket Starting here, the error changes to a core dump instead of a library not found, so maybe this is after the libibverbs package is finally installed and libibverbs.so.1 is now found? > DEBUG util.py:602: /var/tmp/rpm-tmp.pYK3f6: line 13: 2005999 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset \--global dbus.socket > DEBUG util.py:602: /var/tmp/rpm-tmp.heiSf7: line 6: 2006029 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset dbus-broker.service > DEBUG util.py:602: /var/tmp/rpm-tmp.heiSf7: line 13: 2006032 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset \--global dbus-broker.service > DEBUG util.py:602: /var/tmp/rpm-tmp.NScHA9: line 9: 2006061 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset polkit.service > DEBUG util.py:602: /var/tmp/rpm-tmp.05AcI8: line 6: 2006069 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset dm-event.socket > DEBUG util.py:602: /var/tmp/rpm-tmp.05AcI8: line 11: 2006072 > Segmentation fault (core dumped) systemctl enable dm-event.socket > DEBUG util.py:602: /var/tmp/rpm-tmp.05AcI8: line 12: 2006080 > Segmentation fault (core dumped) systemctl start dm-event.socket > > /dev/null 2>&1 > DEBUG util.py:602: /var/tmp/rpm-tmp.4iXDa7: line 6: 2006113 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset saslauthd.service > DEBUG util.py:602: /var/tmp/rpm-tmp.8CYlZ7: line 6: 2006121 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset rdisc.service > DEBUG util.py:602: /var/tmp/rpm-tmp.mIKYA7: line 6: 2006130 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset mdmonitor.service raid-check.{service,timer} > DEBUG util.py:602: /var/tmp/rpm-tmp.mIKYA7: line 8: 2006133 > Segmentation fault (core dumped) /usr/bin/systemctl disable > mdmonitor-takeover.service > /dev/null 2>&1 > DEBUG util.py:602: /var/tmp/rpm-tmp.pk6AR5: line 6: 2006141 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset numad.service > DEBUG util.py:602: /var/tmp/rpm-tmp.eLxfL5: line 7: 2006179 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset virtlockd.socket virtlockd-admin.socket > DEBUG util.py:602: /var/tmp/rpm-tmp.eLxfL5: line 14: 2006182 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset virtlogd.socket virtlogd-admin.socket > DEBUG util.py:602: /var/tmp/rpm-tmp.eLxfL5: line 21: 2006189 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset libvirtd.socket libvirtd-ro.socket libvirtd-admin.socket > DEBUG util.py:602: /var/tmp/rpm-tmp.eLxfL5: line 28: 2006196 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset libvirtd-tcp.socket libvirtd-tls.socket > DEBUG util.py:602: /var/tmp/rpm-tmp.eLxfL5: line 35: 2006203 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset libvirtd.service > DEBUG util.py:602: /var/tmp/rpm-tmp.bk1ZR5: line 6: 2006222 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset blk-availability.service lvm2-monitor.service > DEBUG util.py:602: /var/tmp/rpm-tmp.bk1ZR5: line 13: 2006225 > Segmentation fault (core dumped) systemctl enable lvm2- > monitor.service > DEBUG util.py:602: /var/tmp/rpm-tmp.bk1ZR5: line 13: 2006232 > Segmentation fault (core dumped) systemctl start lvm2- > monitor.service > /dev/null 2>&1 > DEBUG util.py:602: /var/tmp/rpm-tmp.bk1ZR5: line 20: 2006239 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset lvm2-lvmpolld.socket > DEBUG util.py:602: /var/tmp/rpm-tmp.bk1ZR5: line 25: 2006246 > Segmentation fault (core dumped) systemctl enable lvm2- > lvmpolld.socket > DEBUG util.py:602: /var/tmp/rpm-tmp.bk1ZR5: line 26: 2006254 > Segmentation fault (core dumped) systemctl start lvm2- > lvmpolld.socket > /dev/null 2>&1 > DEBUG util.py:602: /var/tmp/rpm-tmp.M5VjN9: line 6: 2006725 > Segmentation fault (core dumped) /usr/bin/systemctl --no-reload > preset brltty.service Up until here, these have all been the same. Failed %pre or %post scriptlets because of systemctl failures. > DEBUG util.py:602: /bin/kernel-install: line 137: > /etc/kernel/install.d/: Is a directory > DEBUG util.py:600: Error in POSTTRANS scriptlet in rpm package > kernel-core But this is different, and it's the cause of your problem (well, it's the immediate cause anyway). The kernel-install script is failing because it's passing /etc/kernel/install.d/ to something that wants something other than a directory. That could be because a failed scriptlet elsewhere has resulted in that directory being empty, so some glob is returning the directory instead of the files in the directory, so it could still be the systemctl issue, but it would be worth looking into install-kernel to see. OK, so install-kernel is part of systemd (I'm seeing a pattern here). It generates an array of plugins that should be called for the new kernel. It does all plugins in .install, /etc/kernel/install.d/, and /usr/lib/kernel/install.d. My guess here is that the %POSTTRANS of the kernel-core package is calling install-kernel, which is failing with the above error, causing the kernel-core %POSTTRANS to error out prematurely, resulting in the missing modules.dep file that is breaking your build. At this point, I can't see what the problem can be other than either a bad build of systemd, or if the recent upgrade to rdma- core-29, with the new libibverbs-29 package, has caused a failure in systemd because it needs relinked or something. But that can only be the case if it's some sort of weak dependency based on dlopen as both the rpm tools and ldd are not picking up the libibverbs dependency. If that's the case, the systemd and/or udev rpm packages should have an explicit requires on libibverbs I think. Anyway, at this point, I don't know if the rdma-core-owner people can help. I think this is first in the hands of the systemd folks. > DEBUG util.py:602: /var/tmp/rpm-tmp.6RiAo6: line 34: 2006782 > Segmentation fault (core dumped) /bin/systemctl is-active > libvirtd.service > /dev/null 2>&1 > DEBUG util.py:602: /var/tmp/rpm-tmp.LMHzS9: line 4: 2006829 > Segmentation fault (core dumped) /usr/bin/systemd-run > /usr/bin/systemctl start man-db-cache-update > /dev/null 2>&1 > > Rich. > > -- Doug Ledford <dledford@xxxxxxxxxx> GPG KeyID: B826A3330E572FDD Fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx
