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
Segfault during replication startup on Arm device #2805
Comments
Comment from biosehnsucht at 2018-06-01 23:23:44 While diagnosing this issue on freeipa-users mailing list, Mark Reynolds supplied a proposed patch which appears to solve the problem (worked both on 1.3.7 and 1.3.8):
I'm not sure if this requires further work before being applied widely as this might be Arm specific. Mark asked me to open this issue and also supply him with the build output with and without the above patch, which I am doing (once the build completes). |
Comment from mreynolds (@mreynolds389) at 2018-06-02 15:08:21 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2018-06-02 15:08:49 The ARM issues were fixed in 1.4.0 via #2677 This ticket is for backing porting those changes... |
Comment from mreynolds (@mreynolds389) at 2018-06-02 15:08:50 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2018-06-04 03:19:36 Turns out this does not cleanly back port to 1.3.8. Best to just check the current compiler warnings and do a fresh patch for 1.3.8. |
Comment from mreynolds (@mreynolds389) at 2018-06-08 21:15:07 |
Comment from mreynolds (@mreynolds389) at 2018-06-08 21:15:13 Metadata Update from @mreynolds389:
|
Comment from biosehnsucht at 2018-06-11 22:56:55 It looks like you backported the fixes, then updated to 1.4.0.10 - should we expect an updated 1.3.8.x package to make it's way to Fedora 27 eventually, or a 1.4.x package, or ... ? |
Comment from biosehnsucht at 2018-06-11 23:03:22 Sorry, I just saw it in updates-testing. I didn't think to check there at first. Looking forward to it clearing testing so we can move forward with putting Pis into production, but I am going to go ahead and actually try that package (in place of my compiled version) on our testing Pi ASAP :) |
Comment from mreynolds (@mreynolds389) at 2018-06-11 23:04:50
👍 |
Comment from biosehnsucht at 2018-06-12 01:06:38 Well, it died further than the non-testing version, but unlike my compiled version did die during replica setup ... Not sure if the problem is in 389-ds-base or elsewhere (since I uninstalled all the IPA packages and reinstalled them with testing repo enabled, so some things are testing and others aren't). slapd doesn't crash, it's just an error loading an LDIF now?
The log file:
Perhaps the problem is the master wasn't fully removed before hand... though I did |
Comment from mreynolds (@mreynolds389) at 2018-06-12 01:17:45 Error 68 means you tried adding an entry that already existed in your database. Its certainly not a bug. I don't see how that could be related to anything in 389-ds-base unless the entry actually does NOT exist. You could verify by looking in the DS access log (/var/log/dirsrv/slapd-YOUR_INSTANCE/access) and find the dn of the entry that triggered the "err=68". Then do a search on the database for that entry. If its not there then we have a serious bug. If it is there, then it looks like its an issue on the IPA install (really in this case an error 68 can probably be ignored). |
Comment from biosehnsucht at 2018-06-12 02:27:47 I tried uninstalling and reinstalling all the IPA related packages (with also running Tomorrow I'm going to just reinstall Fedora on the Pi again to start from a clean slate. That worked before ... |
Comment from mreynolds (@mreynolds389) at 2018-06-12 04:14:41 If it is crashing, can you get a core file/stack trace of the crash? Thanks! |
Comment from biosehnsucht at 2018-06-13 23:27:40 I installed a fresh copy of Fedora 27, installed regular (not testing) FreeIPA packages, then installed just the 389-ds-core update-testing package. I was able to setup the replica without any issues. The other ARM issue I'm aware of, https://pagure.io/freeipa/issue/7337 , still applies, the workaround (from that issue) of |
Comment from biosehnsucht at 2018-07-13 20:06:25 An FYI update. Previously I was testing F27 armhfp. I've just tested in F28 aarch64 and neither this issue nor the other ARM issue (which previously we had to work around with the changes to |
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49746
Issue Description
On Arm platform (specifically Pi 3 running fc27.armv7hl) during
ipa-replica-install
, 389-ds crashes when trying to start up the replication to the master with a segfault.Package Version and Platform
Steps to reproduce
ipa-replica-install
[33/41]: enabling S4U2Proxy delegation
, 389-ds crashes (or has crashed before?)Actual results
Expected results
ipa-replica-install
completes successfully.The text was updated successfully, but these errors were encountered: