On (04/10/17 12:46), Galen Johnson wrote:
It's possible as we've had that happen in the past (and
complained loudly to the team that keeps doing it). Is there any way to read those files
to see which users/groups are contained in them so we can verify? ldbsearch doesn't
seem to read them or I'm giving it the wrong args. If this is already in the
troubleshooting/debug docs, I've missed it.
Memory cache is in binary format.
If you renamed group the it is a known bug
If it is a colliding UID/GID then preffered way is to fix it on server side.