On Tue, Aug 07, 2018 at 09:36:25AM -0300, Andreas Hasenack wrote:
On Tue, Aug 7, 2018 at 8:04 AM Sumit Bose sbose@redhat.com wrote:
On Mon, Jul 23, 2018 at 10:01:26AM +0200, Jakub Hrozek wrote:
Unfortunately these tests don’t have an option to raise the debug level so stepping throught them with gdb is the only option I’m afraid..
I think I didn't properly mock sss_nss_make_request_timeout() here. Instead of the provided call which just mock the results the original one is used which tries to talk to SSSD which either does not run or does not know about the test user, hence the return code 0x02 (ENOENT).
If you run the test with strace you should see that the test program tries to connect to /var/lib/sss/pipes/nss which is not expected. I'll try to fix this.
Indeed it does try that connect a few times:
11933 connect(3, {sa_family=AF_UNIX, sun_path="/var/lib/sss/pipes/nss"}, 110) = -1 ENOENT (No such file or directory)
Thanks for the confirmation.
But something is still unexplained: the same test works just fine in debian, and doesn't try to connect to that socket.
This is just linker magic. Due to my fault sss_nss_make_request_timeout() is defined twice and which symbol is picked might depend on specific linker options used.
bye, Sumit
I might try updating nss. I have 3.36, and debian has 3.38.
Thanks! _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/sssd-users@lists.fedorahosted....