-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building/installing RPMs fail in Oracle Linux 8.3 #12071
Comments
Tried to reproduce using the 8.3 VM image here, built fine without errors. You might want to examine your coredumps, and possibly also your hardware. |
Did you update kernel and other packages? I tried to build in VM (ESXi 6.5)
with all packages updated
…On Tue, May 18, 2021, 15:57 Rich Ercolani ***@***.***> wrote:
Tried to reproduce using the 8.3 VM image here
<https://yum.oracle.com/oracle-linux-templates.html>, built fine without
errors.
You might want to examine your coredumps, and possibly also your hardware.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#12071 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHX2DHIOR2YCJOJ7VWCLSTLTOIMW5ANCNFSM45B3HBNA>
.
|
Yes, "dnf upgrade" reports no updates available, I was booted into the latest kernel. I was using kvm, though, not VMware. (5.2 from buster-backports, in case it somehow becomes relevant later.) |
Don't understand. Reinstalled VM. OL8.3 Minimal install, added 2GB more memory (total is 4GB). Only other software installed is nano, wget, tmux and mc Downloaded latest zfs - rc5 - same errors |
More generally, while I'm happy to try and offer insight, if rpmbuild is segfaulting, and it's not because it's running on a ZFS filesystem, that's probably an issue to take up with the distro providers or rpmbuild upstream (though I would not be surprised if RH's response was "cannot reproduce, go complain to Oracle"). Have you tried building any other RPMs in this VM? |
No, but I definitely will try to |
Same:
VMWare Workstation 16, Ryzen 3700X. |
Tried to build scst RPMs on the same system (ESXi). Works fine
|
Nice. Maybe find and try another DKMS package? edit: Sorry, I didn't read your log output carefully enough. That is fascinating. Not sure what to suggest trying next, other than "a more complicated DKMS module", but you really should go complain to Oracle about the VM not working right (though they might tell you to run it on KVM, if you're using the same VM source as me...) |
Tried on real host - DL360 Gen8 with 2*2660V2
|
Okay, so it's not specific to VMware, that's one thing ticked off. Have you tried building it on Centos 8, VM or real hardware? Because as I mentioned above, I tried on an updated OEL8 VM in KVM, and a CentOS 8 VM in VirtualBox and KVM, and none of them crashed and burned. So my bets are, in order of likelihood, problem with OEL, (muuuuch less likely, unless your home machine secretly had identical chips) hardware problem. |
Please look at my previous message. It was real hardware - HPE Proliant DL360 Gen8, 128GB RAM, Dual Xeon E5-2660V2, Oracle Linux 8.3, slightly different kernel version |
Also this machine has working installation of zfs-2.0.1 dkms, but it was built a few months before |
Yes, I saw what you said, that's why I mentioned real hardware - the question was "have you tried Centos 8, (on VM or real hardware)?" |
Also, after this error rpm-db gets corrupted
|
Ew, I believe that means it trashed your rpmdb while dying. :C |
|
It seems like they can reproduce it every time now, though, which seems like the point at which you should report it to the distro providing the rpmbuild. |
Thank you for you advice. Could please provide more information how to do it? I'm not familiar with containers |
https://bugzilla.redhat.com/show_bug.cgi?id=1705320 Fixed by installing ncompress
Now it builds without errors |
Sounds like the lesson is "stop using rpmbuild as root". Also, I still say you should point out this problem exists in EL8 to your distro provider and try to get them to pull in the fix linked. |
Having an old enough version of "file" and no "uncompress" program installed can cause rpmbuild as root to crash and mangle rpmdb. So let's check for uncompress and the version of file, and if the latter is too old and the former is absent, refuse to build rpm targets. Closes: openzfs#12071 Closes: openzfs#12168 Signed-off-by: Rich Ercolani <rincebrain@gmail.com>
Having an old enough version of "file" and no "uncompress" program installed can cause rpmbuild as root to crash and mangle rpmdb. So let's add a build dependency for RPM-based systems. Closes: openzfs#12071 Closes: openzfs#12168 Signed-off-by: Rich Ercolani <rincebrain@gmail.com>
Having an old enough version of "file" and no "uncompress" program installed can cause rpmbuild as root to crash and mangle rpmdb. So let's add a build dependency for RPM-based systems. Closes: openzfs#12071 Closes: openzfs#12168 Signed-off-by: Rich Ercolani <rincebrain@gmail.com>
Having an old enough version of "file" and no "uncompress" program installed can cause rpmbuild as root to crash and mangle rpmdb. So let's add a build dependency for RPM-based systems. Closes: openzfs#12071 Closes: openzfs#12168 Signed-off-by: Rich Ercolani <rincebrain@gmail.com>
Having an old enough version of "file" and no "uncompress" program installed can cause rpmbuild as root to crash and mangle rpmdb. So let's add a build dependency for RPM-based systems. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Tony Hutter <hutter2@llnl.gov> Signed-off-by: Rich Ercolani <rincebrain@gmail.com> Closes: #12071 Closes: #12168
System information
Describe the problem you're observing
Cannot build zfs from tarball
Describe how to reproduce the problem
Include any warning/errors/backtraces from the system logs
Building process stucks at
journalctl -f show coredumps
The text was updated successfully, but these errors were encountered: