Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla: Bug 1639354
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
struct nss_ctx contains 70319310 bytes in 2485433 blocks (ref 0) 0x7f02fc89f3c0 struct cache_req_result * contains 6899 bytes in 222 blocks (ref 0) 0x7f0315381180 struct cache_req_result contains 6883 bytes in 221 blocks (ref 0) 0x7f0315382890 [sanitized] contains 25 bytes in 1 blocks (ref 0) 0x7f0315387020 struct ldb_result contains 6802 bytes in 219 blocks (ref 0) 0x7f03153756a0 struct ldb_message * contains 6762 bytes in 218 blocks (ref 0) 0x7f0315383640 struct ldb_message contains 6746 bytes in 217 blocks (ref 0) 0x7f031537a280 struct ldb_message_element contains 6590 bytes in 214 blocks (ref 0) 0x7f0315393680 struct ldb_val contains 27 bytes in 2 blocks (ref 0) 0x7f0315393580 ../common/ldb_pack.c:425 contains 11 bytes in 1 blocks (ref 0) 0x7f0315393600 ../common/ldb_pack.c:376 contains 20 bytes in 1 blocks (ref 0) 0x7f0315393500 struct ldb_val contains 27 bytes in 2 blocks (ref 0) 0x7f0315393400 ../common/ldb_pack.c:425 contains 11 bytes in 1 blocks (ref 0) 0x7f0315393480 ../common/ldb_pack.c:376 contains 11 bytes in 1 blocks (ref 0) 0x7f0315393380 struct ldb_val contains 6247 bytes in 200 blocks (ref 0) 0x7f031538c0d0 ../common/ldb_pack.c:425 contains 17 bytes in 1 blocks (ref 0) 0x7f0315393300
Metadata Update from @pbrezina: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1639354
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.16.4
Metadata Update from @jhrozek: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4860
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.