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
Crash while triming the retro changelog #1537
Comments
Comment from tbordaz (@tbordaz) at 2015-06-25 19:49:19 The crash occurs:
The problem could be trigger by small cn=changelog entry cache
The bug could be at https://git.fedorahosted.org/cgit/389/ds.git/tree/ldap/servers/slapd/back-ldbm/ldbm_delete.c#n1264. If '!create_tombstone_entry' (that is the case for cn=changelog), 'e' was updated and so could be NULL. |
Comment from tbordaz (@tbordaz) at 2015-06-26 14:39:42 attachment |
Comment from tbordaz (@tbordaz) at 2015-06-26 14:40:12 attachment |
Comment from tbordaz (@tbordaz) at 2015-06-26 14:40:37 attachment |
Comment from mreynolds (@mreynolds389) at 2015-07-21 00:26:19 attachment |
Comment from nhosoi (@nhosoi) at 2015-07-21 00:45:01 Looks good. Does your fix need to be backported to the older version, too? |
Comment from nhosoi (@nhosoi) at 2015-07-21 00:58:16 Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1244926 |
Comment from mreynolds (@mreynolds389) at 2015-07-21 02:39:45 29043c5..2a8a8c8 master -> master 0e31d81..6d43988 389-ds-base-1.3.4 -> 389-ds-base-1.3.4 c81f40a..1cde230 389-ds-base-1.3.3 -> 389-ds-base-1.3.3 64b54d4..21a1196 389-ds-base-1.3.2 -> 389-ds-base-1.3.2 35f75ce..95a7fbd 389-ds-base-1.3.1 -> 389-ds-base-1.3.1 8173360..f5552bf 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 |
Comment from nhosoi (@nhosoi) at 2015-07-21 04:27:21 Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1244970 |
Comment from tbordaz (@tbordaz) at 2017-02-11 22:59:46 Metadata Update from @tbordaz:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48206
Community use on Centos is running 389-ds-base-1.3.3.1-16.el7_1.x86_64
When trimming the retroCL, it deletes an entry. Then retrieve the entry from the cache (no creation of tombstone) to remove it from the cache.
Apparently if the entry cachen is small, it can fail to retrieve it and not testing this special condition
The text was updated successfully, but these errors were encountered: