[SSSD] SSSD Configuration issue

Nitesh Mehare nitesh26 at gmail.com
Tue Nov 15 11:54:08 UTC 2011


is that the output which is expected in the trace.
Something missing in the trace which suggest any config problem???


On Tue, Nov 15, 2011 at 5:22 PM, Nitesh Mehare <nitesh26 at gmail.com> wrote:

> This is the output of strace for the user which is in ldap server.
>
> bash-3.2# strace -e open su - nitback1
> open("/etc/ld.so.cache", O_RDONLY)      = 3
> open("/lib64/libpam.so.0", O_RDONLY)    = 3
> open("/lib64/libpam_misc.so.0", O_RDONLY) = 3
> open("/lib64/libcrypt.so.1", O_RDONLY)  = 3
> open("/lib64/libdl.so.2", O_RDONLY)     = 3
> open("/lib64/libc.so.6", O_RDONLY)      = 3
> open("/lib64/libaudit.so.0", O_RDONLY)  = 3
> open("/usr/lib/locale/locale-archive", O_RDONLY) = 3
> open("/etc/nsswitch.conf", O_RDONLY)    = 3
> open("/etc/ld.so.cache", O_RDONLY)      = 3
> open("/lib64/libnss_files.so.2", O_RDONLY) = 3
> open("/etc/passwd", O_RDONLY)           = 3
> open("/etc/ld.so.cache", O_RDONLY)      = 3
> open("/lib64/libnss_sss.so.2", O_RDONLY) = 3
> open("/etc/pam.d/su-l", O_RDONLY)       = 4
> open("/etc/pam.d/su", O_RDONLY)         = 5
> open("/lib64/security/pam_rootok.so", O_RDONLY) = 6
> open("/etc/ld.so.cache", O_RDONLY)      = 6
> open("/lib64/libselinux.so.1", O_RDONLY) = 6
> open("/lib64/libsepol.so.1", O_RDONLY)  = 6
> open("/etc/selinux/config", O_RDONLY)   = 6
> open("/proc/mounts", O_RDONLY)          = 6
> open("/etc/pam.d/system-auth", O_RDONLY) = 6
> open("/lib64/security/pam_env.so", O_RDONLY) = 7
> open("/lib64/security/pam_unix.so", O_RDONLY) = 7
> open("/etc/ld.so.cache", O_RDONLY)      = 7
> open("/usr/lib64/libcrack.so.2", O_RDONLY) = 7
> open("/lib64/libnsl.so.1", O_RDONLY)    = 7
> open("/lib64/security/pam_succeed_if.so", O_RDONLY) = 7
> open("/lib64/security/pam_sss.so", O_RDONLY) = 7
> open("/lib64/security/pam_deny.so", O_RDONLY) = 7
> open("/etc/pam.d/su", O_RDONLY)         = 5
> open("/etc/pam.d/system-auth", O_RDONLY) = 6
> open("/lib64/security/pam_localuser.so", O_RDONLY) = 7
> open("/lib64/security/pam_permit.so", O_RDONLY) = 7
> open("/etc/pam.d/su", O_RDONLY)         = 5
> open("/etc/pam.d/system-auth", O_RDONLY) = 6
> open("/lib64/security/pam_cracklib.so", O_RDONLY) = 7
> open("/lib64/security/pam_keyinit.so", O_RDONLY) = 5
> open("/etc/pam.d/su", O_RDONLY)         = 5
> open("/etc/pam.d/system-auth", O_RDONLY) = 6
> open("/lib64/security/pam_mkhomedir.so", O_RDONLY) = 7
> open("/lib64/security/pam_limits.so", O_RDONLY) = 7
> open("/lib64/security/pam_xauth.so", O_RDONLY) = 6
> open("/etc/pam.d/other", O_RDONLY)      = 4
> open("/etc/passwd", O_RDONLY)           = 4
> open("/proc/filesystems", O_RDONLY)     = 4
> open("/usr/lib64/gconv/gconv-modules.cache", O_RDONLY) = 5
> open("/etc/passwd", O_RDONLY)           = 4
> open("/etc/passwd", O_RDONLY)           = 4
> open("/etc/passwd", O_RDONLY)           = 4
> Creating directory '/home/nitback1'.
> open("/etc/skel/", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 4
> open("/etc/skel//.bash_logout", O_RDONLY) = 5
> open("/home/nitback1/.bash_logout", O_WRONLY|O_CREAT|O_TRUNC, 0600) = 6
> open("/etc/skel//.bash_profile", O_RDONLY) = 5
> open("/home/nitback1/.bash_profile", O_WRONLY|O_CREAT|O_TRUNC, 0600) = 6
> open("/etc/skel//.emacs", O_RDONLY)     = 5
> open("/home/nitback1/.emacs", O_WRONLY|O_CREAT|O_TRUNC, 0600) = 6
> open("/etc/skel//.bashrc", O_RDONLY)    = 5
> open("/home/nitback1/.bashrc", O_WRONLY|O_CREAT|O_TRUNC, 0600) = 6
> Creating directory '/home/nitback1/.mozilla'.
> open("/etc/skel//.mozilla", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 5
> Creating directory '/home/nitback1/.mozilla/extensions'.
> open("/etc/skel//.mozilla/extensions", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 6
> Creating directory '/home/nitback1/.mozilla/plugins'.
> open("/etc/skel//.mozilla/plugins", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 6
> open("/etc/passwd", O_RDONLY)           = 4
> open("/etc/security/limits.conf", O_RDONLY) = 4
> open("/etc/security/limits.d", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 4
> open("/etc/passwd", O_RDONLY)           = 4
> open("/var/run/utmp", O_RDONLY)         = 4
>
>
>
>
> On Tue, Nov 15, 2011 at 5:16 PM, Jakub Hrozek <jhrozek at redhat.com> wrote:
>
>> On Tue, Nov 15, 2011 at 09:24:57AM +0530, Nitesh Mehare wrote:
>> >    Here is the snapshot of the file
>> >
>> >    -bash-3.2# cat /etc/pam.d/sshd
>> >    #%PAM-1.0
>> >    authA A A A A A  includeA A A A A  system-auth
>> >    accountA A A  requiredA A A A  pam_nologin.so
>> >    accountA A A  includeA A A A A  system-auth
>> >    passwordA A  includeA A A A A  system-auth
>> >    sessionA A A  optionalA A A A  pam_keyinit.so force revoke
>> >    sessionA A A  includeA A A A A  system-auth
>> >    sessionA A A  requiredA A A A  pam_loginuid.so
>> >    -bash-3.2#
>>
>> Provided that you still use the same system-auth file as you provided in
>> one of the first comments, everything looks fine.
>>
>> Can you run:
>> strace -e open su - $username
>>
>> That should tell us whether the pam stack is actually opening the module
>> or not.
>> _______________________________________________
>> sssd-devel mailing list
>> sssd-devel at lists.fedorahosted.org
>> https://fedorahosted.org/mailman/listinfo/sssd-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/sssd-devel/attachments/20111115/b0421071/attachment.html>


More information about the sssd-devel mailing list