LDAP solutions with Open Grid Scheduler

• qrsh failed: No such file or directory If your qrsh session is not working properly and gives this error:

  qrsh -verbose -l hostname=koala hostname Your job 6617000 ("hostname") has been submitted waiting for interactive job to be scheduled ... Your interactive job 6617000 has been successfully scheduled. Establishing /usr/bin/ssh session to host koala.cluster.loc ... qrsh_starter: executing child process (null) failed: No such file or directory /usr/bin/ssh exited with exit code 0 reading exit code from shepherd ... 1

When we add the optoin -noshell the qrsh command will run:

qrsh -noshell -verbose -l hostname=koala hostname
Your job 6617014 ("hostname") has been submitted
waiting for interactive job to be scheduled ...
Your interactive job 6617014 has been successfully scheduled.
Establishing /usr/bin/ssh session to host koala.cluster.loc ...
koala
/usr/bin/ssh exited with exit code 0
reading exit code from shepherd ... 0

The failed: No such file or directory, is caused by the LDAP not having a default shell set. The LDAP server is in our case a Windows ADS 2008 server and there is no attribute default shell. The solution is simple set in the nslcd.conf file the attribute loginshell:

filter passwd (&(objectClass=user)(!(objectClass=computer))(uidNumber=*)(unixHomeDirectory=*))
map passwd uid sAMAccountName
map passwd uidnumber uidNumber
map passwd homedirectory unixHomeDirectory
map passwd loginshell "/bin/bash"
map passwd gecos displayName
filter shadow (&(objectClass=user)(!(objectClass=computer))(uidNumber=*)(unixHomeDirectory=*))
map shadow uid sAMAccountName
filter group (&(objectClass=group)(gidNumber=*))