ltsp-cluster

Login with ldap impossible

Asked by Eric Trezel

First, my setup :

One root-server with ltsp-control-center and load balancer
One appserver

I already have ltsp running with ldap auth in one free-access room, and it works fine.
I'd like to create three more free-access rooms, and I decided to try ltsp-cluster (over 50 machines, it seems better).

My server works, until I configure it for ldap auth (same config as ldap-auth config in ltsp server that already runs):

I configured app. server for ldap only

LDAP auth is working (ldap users don't get any message for login error, but session's start stays over and over on a black screen with "turning cursor".

More : I can't stay logged on the server, even with ssh connexion on the app server !

COnnexion is shutted down after a few seconds... just enough to tail syslog and notice these lines :
ltsp-clsuter-accountmanager : killing user "eric"
It's the same thing when trying to log with ldap user and local user.

If someone could help me, it would be great

Thanks

E. Trezel

Question information

Language:
English Edit question
Status:
Answered
For:
ltsp-cluster Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Marc Gariépy (mgariepy) said : 		#1

Hi,

Can you verify that the following services are running on the applications server:
* bus-daemon --system
* ltsp-cluster-lbagent
* ltsp-cluster-accountmanager
* inetd

plus can you verify that you have '''libpam-ck-connector''' installed and configured in your pam configuration

Revision history for this message
Eric Trezel (eric-trezel) said : 		#2

Hi,

> Marc Gariépy requested for more information:
> Hi,
>
> Can you verify that the following services are running on the applications server:
> * bus-daemon --system
> * ltsp-cluster-lbagent
> * ltsp-cluster-accountmanager
> * inetd
>
> plus can you verify that you have '''libpam-ck-connector''' installed
> and configured in your pam configuration

It was in /etc/pam.d/common-session (original file), but not in mine.
I add these two lines to my /etc/pam.d/common-session file :
session optional pam_ecryptfs.so unwrap
session optional pam_ck_connector.so nox11

and now it works fine

Thanks a lot for your efficient help

--
Eric Trezel
-------------------------------
Technicien informatique
Fac. des Sciences et Techniques de Limoges
05.55.45.72.57

Revision history for this message
Marc Gariépy (mgariepy) said : 		#3

you are welcome.

Revision history for this message
Karoly CZOVEK (karoly-czovek) said : 		#4

Same issue like this, but works fine on faster thinclients,
I mean intel atom based 1.6GHz ones ...

With older clients, running on VIA C3/800MHz
with 256MB ram the same issue presents.

I configured the PAM like eric, let me see what happens...

Revision history for this message
Shrenik (shrenik-bhura) said : 		#5

Coincidentally, I have the exactly same assortment of TCs as Karoly and have tested the same. They work absolutely fine with the above fix. Thanks Marc .

It would be great to know the other pam module settings that are ideal for an ltsp-cluster setup. Have raised a separate query for the same.

Thanks once again.

Can you help with this problem?

Provide an answer of your own, or ask Eric Trezel for more information if necessary.

To post a message you must log in.