MIC nic user login issue

[parag_k_]

I've configured NIS in my cluster setup. and user root of the host and head node can loging into MIC without password. But when a user is trying to login from the host to mic it asks password. after giving password it goes through. Home directory is mounted properly. nad user can loging from head node to Host node without password.

[JJK]

how did you set up NIS support on the Xeon Phi's ? is pam auth support using NIS available? Is the user's home directory available on the Phi (autofs?)

[parag_k_]

I"ve configured NIS as mentioned in the MPSS_user_guide-3.6 in the section “6.1.3 Enabling NIS Service”. User’s home directory in permanently mounted on Phi without autofs.

How to setup pam auth support ? please suggest.

[parag_k_]

Hi, can anyone help me on this ?

[JJK]

what happens if you set the LogLevel to DEBUG in the /etc/ssh/sshd_config file on the Xeon Phi:

1. change the loglevel in /etc/ssh/sshd_config
2. run '/etc/init.d/sshd restart'
3. monitor /var/log/messages
4. have a regular user connect

the file /var/log/messages should now fill up with debug statements - it will also list whether ssh attempts to read the user's authorized_keys file.

A second thing to test is:

1. have the user connect (by typing in his or her password)
2. keep the user session open
3. let the user connect a second time - is the password still needed? if not then it's an automount issue. If it is needed , then it's a ssh config/permissions issue.

[parag_k_]

Hi JJk,

Thanks for your reply.....below are the logs....it looks it is not automount issue...

================================

Nov 17 14:10:27 miccn-04-mic0 authpriv.err sshd[5177]: PAM unable to dlopen(/lib64/security/pam_ldap.so): /lib64/security/pam_ldap.so: cannot open shared object file: No such file or directory
Nov 17 14:10:27 miccn-04-mic0 authpriv.err sshd[5177]: PAM adding faulty module: /lib64/security/pam_ldap.so
Nov 17 14:10:55 miccn-04-mic0 authpriv.notice sshd[5179]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=host  user=anurag
Nov 17 14:10:57 miccn-04-mic0 auth.err sshd[5177]: error: PAM: Authentication failure for anurag from host
Nov 17 14:10:58 miccn-04-mic0 authpriv.notice sshd[5183]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=host  user=anurag
Nov 17 14:10:59 miccn-04-mic0 auth.err sshd[5177]: error: PAM: Authentication failure for anurag from host
Nov 17 14:10:59 miccn-04-mic0 auth.info sshd[5177]: Connection closed by 10.1.1.40 [preauth]
Nov 17 14:11:31 miccn-04-mic0 authpriv.err sshd[5184]: PAM unable to dlopen(/lib64/security/pam_ldap.so): /lib64/security/pam_ldap.so: cannot open shared object file: No such file or directory
Nov 17 14:11:31 miccn-04-mic0 authpriv.err sshd[5184]: PAM adding faulty module: /lib64/security/pam_ldap.so

=================================================================================

Nov 17 14:34:25 miccn-04-mic0 authpriv.err sshd[5325]: PAM unable to dlopen(/lib64/security/pam_ldap.so): /lib64/security/pam_ldap.so: cannot open shared object file: No such file or directory
Nov 17 14:34:25 miccn-04-mic0 authpriv.err sshd[5325]: PAM adding faulty module: /lib64/security/pam_ldap.so
Nov 17 14:34:25 miccn-04-mic0 authpriv.err sshd[5325]: PAM unable to dlopen(/lib64/security/pam_inix.so): /lib64/security/pam_inix.so: cannot open shared object file: No such file or directory
Nov 17 14:34:25 miccn-04-mic0 authpriv.err sshd[5325]: PAM adding faulty module: /lib64/security/pam_inix.so

this is the logs from /var/log/messages

[JJK]

the pam_ldap warning can be fixed by installing the k1om RPM pam-ldap.

Do this first, then have the user reconnect : there should be different warnings/errors for a faulty ssh key.

[parag_k_]

Many Thanks JJK,

I got a clue out of your suggestion to resolved the issue. now it is all okey.

Can you please help in setting up MIC environment on Head Node, as there is no mic card install on it.

[JJK]

Just install the Intel MPSS stack on the head node, with the exception of the kernel module - that way all files are present.

You might want to disable the autostart of the mpss module to avoid boot up delays.