This message is printed:
[[sssd[krb5_child[806]]]] [unpack_buffer] (0x0100): cmd [241] uid [750760304990436485] gid [546972675207544] validate [none] offline [@�] UPN [__libc_pthread_init]
Actual uid is: 174800005 = 0x0xA6B3C85 Printed uid is: 750760304990436485 = 0xA6B3C850A6B3C85
This is not going to be addressed by SSSD. The bug is in the filesystem (JFFS2), which is incompatible with 32-bit UID and GID values. This is not a supported filesystem for the deployment of SSSD and never will be.
keywords: krb5_child uid gid unpack_buffer print => resolution: => invalid status: new => closed
Metadata Update from @georgem: - Issue set to the milestone: NEEDS_TRIAGE
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/2431
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.