Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1275433
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
Description of problem: - We are seeing the following being logged in /var/log/messages: - sssd[nss]: Stored copy of corrupted mmap cache in file '/var/lib/sss/mc/passwd_corrupted#012' Version-Release number of selected component (if applicable): - sssd-1.12.4-47.el6 How reproducible: - Very unlikely Steps to Reproduce: 1. Need more info 2. 3. Actual results: - sssd[nss]: Stored copy of corrupted mmap cache in file '/var/lib/sss/mc/passwd_corrupted#012' Expected results: - mmap does not become corrupted Additional info:
Fields changed
blockedby: => blocking: => changelog: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => mark: no => 0 milestone: NEEDS_TRIAGE => SSSD Patches welcome patch: => 0 review: True => 0 selected: => testsupdated: => 0
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Patches welcome
Seeing similar:
Aug 29 13:37:17 barry sssd[nss]: Stored copy of corrupted mmap cache in file '/var/lib/sss/mc/group_corrupted#012' Aug 4 14:12:38 europa sssd[nss]: Stored copy of corrupted mmap cache in file '/var/lib/sss/mc/group_corrupted#012'
This is with sssd-1.15.2-50.el7.x86_64
@orion, may I ask you for a cache dump and full logs when hitting this situation?
By the (private) comments in the Red Hat bugzilla may be the case you're hitting a known group rename issue on SSSD (which I may have a PR opened with a fix).
Metadata Update from @fidencio: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None
Seeing similar: Aug 29 13:37:17 barry sssd[nss]: Stored copy of corrupted mmap cache in file '/var/lib/sss/group_corrupted#012' Aug 4 14:12:38 europa sssd[nss]: Stored copy of corrupted mmap cache in file '/var/lib/sss/group_corrupted#012' This is with sssd-1.15.2-50.el7.x86_64
Seeing similar: Aug 29 13:37:17 barry sssd[nss]: Stored copy of corrupted mmap cache in file '/var/lib/sss/group_corrupted#012' Aug 4 14:12:38 europa sssd[nss]: Stored copy of corrupted mmap cache in file '/var/lib/sss/group_corrupted#012'
I have a suspicion that it happens when there are two groups/users with the same ID in sssd caches. One of reasons might be renaming group/user.It would be good if you could share more context from sssd_nss log files and not just two lines,
Metadata Update from @lslebodn: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false)
I"ve sent more info directly to Fabiano.
And I forwarded them to the core developers (lslebodn included, of course).
Metadata Update from @fidencio: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false)
Metadata Update from @sbose: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue close_status updated to: duplicate
Duplicate of https://pagure.io/SSSD/sssd/issue/3571
Metadata Update from @sbose: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue status updated to: Open (was: Closed)
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/4262
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.