Ldap - Can't 'log in' but can ldapsearch - (Log) transport endpoint not connected
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have this problem:
I'm on centos 7 I tryed to set ldap remote credentials access by this:
[192.168.9.105 #] authconfig --enableldap --enableldapauth
--ldapserver=ldap://192.168.9.104 --ldapbasedn="dc=myco,dc=local"
--enablemkhomedir --update
launching this query (on the same host I run authconfig on) i get:
[192.168.9.105 #] ldapsearch -x uid=ldaprptest -b dc=myco,dc=local -h 192.168.9.104
I got the result:
# extended LDIF
#
# LDAPv3
# base <dc=myco,dc=local> wlocalh scope subtree
# filter: uid=ldaprptest
# requesting: ALL
#
# ldaprptest, People, myco.local
dn: uid=ldaprptest,ou=People,dc=myco,dc=local
objectClass: top
objectClass: account
objectClass: posixAccount
objectClass: shadowAccount
cn: ldaprptest
uid: ldaprptest
uidNumber: 9988
gidNumber: 100
homeDirectory: /home/ldaprptest
loginShell: /bin/bash
gecos: LDAP Replication Test User
userPassword:: e2NyeXB0fXg=
shadowLastChange: 17058
shadowMin: 0
shadowMax: 99999
shadowWarning: 7
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
so I'm sure it can connect
after trying
su ldaprptest
I [192.168.9.105 #] cat /var/log/messages and I get:
Mar 11 20:02:57 Centos-client-test-slave nslcd[3313]:
[d062c2] <passwd="ldaprptest"> failed to bind to LDAP server ldap://192.168.9.103:
Can't contact LDAP server: Transport endpoint is not connected
Mar 11 20:02:57 Centos-client-test-slave nslcd[3313]:
[d062c2] <passwd="ldaprptest"> no available LDAP server found:
Can't contact LDAP server: Transport endpoint is not connected
Mar 11 20:02:57 Centos-client-test-slave rsyslogd:
imjournal: rename() failed for new path: '/var/lib/rsyslog/imjournal.state':
Permission denied [v8.24.0-34.el7 try http://www.rsyslog.com/e/0 ]
EDIT:
look at logs: it seemps it try to connect to 192.168.9.103 even though I set it up to go 192.168.9.104
also:
What does it mean transport endpoint is not connected?
EDIT2
my /etc/nslcd.conf is this:
uid nslcd
gid ldap
uri ldap://192.168.9.104
base "dc=myco,dc=local"
ssl no
tls_cacertdir /etc/openldap/cacerts
centos authentication ldap
add a comment |
I have this problem:
I'm on centos 7 I tryed to set ldap remote credentials access by this:
[192.168.9.105 #] authconfig --enableldap --enableldapauth
--ldapserver=ldap://192.168.9.104 --ldapbasedn="dc=myco,dc=local"
--enablemkhomedir --update
launching this query (on the same host I run authconfig on) i get:
[192.168.9.105 #] ldapsearch -x uid=ldaprptest -b dc=myco,dc=local -h 192.168.9.104
I got the result:
# extended LDIF
#
# LDAPv3
# base <dc=myco,dc=local> wlocalh scope subtree
# filter: uid=ldaprptest
# requesting: ALL
#
# ldaprptest, People, myco.local
dn: uid=ldaprptest,ou=People,dc=myco,dc=local
objectClass: top
objectClass: account
objectClass: posixAccount
objectClass: shadowAccount
cn: ldaprptest
uid: ldaprptest
uidNumber: 9988
gidNumber: 100
homeDirectory: /home/ldaprptest
loginShell: /bin/bash
gecos: LDAP Replication Test User
userPassword:: e2NyeXB0fXg=
shadowLastChange: 17058
shadowMin: 0
shadowMax: 99999
shadowWarning: 7
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
so I'm sure it can connect
after trying
su ldaprptest
I [192.168.9.105 #] cat /var/log/messages and I get:
Mar 11 20:02:57 Centos-client-test-slave nslcd[3313]:
[d062c2] <passwd="ldaprptest"> failed to bind to LDAP server ldap://192.168.9.103:
Can't contact LDAP server: Transport endpoint is not connected
Mar 11 20:02:57 Centos-client-test-slave nslcd[3313]:
[d062c2] <passwd="ldaprptest"> no available LDAP server found:
Can't contact LDAP server: Transport endpoint is not connected
Mar 11 20:02:57 Centos-client-test-slave rsyslogd:
imjournal: rename() failed for new path: '/var/lib/rsyslog/imjournal.state':
Permission denied [v8.24.0-34.el7 try http://www.rsyslog.com/e/0 ]
EDIT:
look at logs: it seemps it try to connect to 192.168.9.103 even though I set it up to go 192.168.9.104
also:
What does it mean transport endpoint is not connected?
EDIT2
my /etc/nslcd.conf is this:
uid nslcd
gid ldap
uri ldap://192.168.9.104
base "dc=myco,dc=local"
ssl no
tls_cacertdir /etc/openldap/cacerts
centos authentication ldap
Have you tried restarting the nslcd service?
– grawity
Mar 12 at 12:49
I rebooted the whole machine, is it the same?
– DDS
Mar 12 at 13:11
In the sense that nslcd will have also been restarted along with everything else, it is, yes.
– Gabe
Mar 12 at 15:05
add a comment |
I have this problem:
I'm on centos 7 I tryed to set ldap remote credentials access by this:
[192.168.9.105 #] authconfig --enableldap --enableldapauth
--ldapserver=ldap://192.168.9.104 --ldapbasedn="dc=myco,dc=local"
--enablemkhomedir --update
launching this query (on the same host I run authconfig on) i get:
[192.168.9.105 #] ldapsearch -x uid=ldaprptest -b dc=myco,dc=local -h 192.168.9.104
I got the result:
# extended LDIF
#
# LDAPv3
# base <dc=myco,dc=local> wlocalh scope subtree
# filter: uid=ldaprptest
# requesting: ALL
#
# ldaprptest, People, myco.local
dn: uid=ldaprptest,ou=People,dc=myco,dc=local
objectClass: top
objectClass: account
objectClass: posixAccount
objectClass: shadowAccount
cn: ldaprptest
uid: ldaprptest
uidNumber: 9988
gidNumber: 100
homeDirectory: /home/ldaprptest
loginShell: /bin/bash
gecos: LDAP Replication Test User
userPassword:: e2NyeXB0fXg=
shadowLastChange: 17058
shadowMin: 0
shadowMax: 99999
shadowWarning: 7
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
so I'm sure it can connect
after trying
su ldaprptest
I [192.168.9.105 #] cat /var/log/messages and I get:
Mar 11 20:02:57 Centos-client-test-slave nslcd[3313]:
[d062c2] <passwd="ldaprptest"> failed to bind to LDAP server ldap://192.168.9.103:
Can't contact LDAP server: Transport endpoint is not connected
Mar 11 20:02:57 Centos-client-test-slave nslcd[3313]:
[d062c2] <passwd="ldaprptest"> no available LDAP server found:
Can't contact LDAP server: Transport endpoint is not connected
Mar 11 20:02:57 Centos-client-test-slave rsyslogd:
imjournal: rename() failed for new path: '/var/lib/rsyslog/imjournal.state':
Permission denied [v8.24.0-34.el7 try http://www.rsyslog.com/e/0 ]
EDIT:
look at logs: it seemps it try to connect to 192.168.9.103 even though I set it up to go 192.168.9.104
also:
What does it mean transport endpoint is not connected?
EDIT2
my /etc/nslcd.conf is this:
uid nslcd
gid ldap
uri ldap://192.168.9.104
base "dc=myco,dc=local"
ssl no
tls_cacertdir /etc/openldap/cacerts
centos authentication ldap
I have this problem:
I'm on centos 7 I tryed to set ldap remote credentials access by this:
[192.168.9.105 #] authconfig --enableldap --enableldapauth
--ldapserver=ldap://192.168.9.104 --ldapbasedn="dc=myco,dc=local"
--enablemkhomedir --update
launching this query (on the same host I run authconfig on) i get:
[192.168.9.105 #] ldapsearch -x uid=ldaprptest -b dc=myco,dc=local -h 192.168.9.104
I got the result:
# extended LDIF
#
# LDAPv3
# base <dc=myco,dc=local> wlocalh scope subtree
# filter: uid=ldaprptest
# requesting: ALL
#
# ldaprptest, People, myco.local
dn: uid=ldaprptest,ou=People,dc=myco,dc=local
objectClass: top
objectClass: account
objectClass: posixAccount
objectClass: shadowAccount
cn: ldaprptest
uid: ldaprptest
uidNumber: 9988
gidNumber: 100
homeDirectory: /home/ldaprptest
loginShell: /bin/bash
gecos: LDAP Replication Test User
userPassword:: e2NyeXB0fXg=
shadowLastChange: 17058
shadowMin: 0
shadowMax: 99999
shadowWarning: 7
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
so I'm sure it can connect
after trying
su ldaprptest
I [192.168.9.105 #] cat /var/log/messages and I get:
Mar 11 20:02:57 Centos-client-test-slave nslcd[3313]:
[d062c2] <passwd="ldaprptest"> failed to bind to LDAP server ldap://192.168.9.103:
Can't contact LDAP server: Transport endpoint is not connected
Mar 11 20:02:57 Centos-client-test-slave nslcd[3313]:
[d062c2] <passwd="ldaprptest"> no available LDAP server found:
Can't contact LDAP server: Transport endpoint is not connected
Mar 11 20:02:57 Centos-client-test-slave rsyslogd:
imjournal: rename() failed for new path: '/var/lib/rsyslog/imjournal.state':
Permission denied [v8.24.0-34.el7 try http://www.rsyslog.com/e/0 ]
EDIT:
look at logs: it seemps it try to connect to 192.168.9.103 even though I set it up to go 192.168.9.104
also:
What does it mean transport endpoint is not connected?
EDIT2
my /etc/nslcd.conf is this:
uid nslcd
gid ldap
uri ldap://192.168.9.104
base "dc=myco,dc=local"
ssl no
tls_cacertdir /etc/openldap/cacerts
centos authentication ldap
centos authentication ldap
edited Mar 12 at 16:59
DDS
asked Mar 12 at 11:23
DDSDDS
487311
487311
Have you tried restarting the nslcd service?
– grawity
Mar 12 at 12:49
I rebooted the whole machine, is it the same?
– DDS
Mar 12 at 13:11
In the sense that nslcd will have also been restarted along with everything else, it is, yes.
– Gabe
Mar 12 at 15:05
add a comment |
Have you tried restarting the nslcd service?
– grawity
Mar 12 at 12:49
I rebooted the whole machine, is it the same?
– DDS
Mar 12 at 13:11
In the sense that nslcd will have also been restarted along with everything else, it is, yes.
– Gabe
Mar 12 at 15:05
Have you tried restarting the nslcd service?
– grawity
Mar 12 at 12:49
Have you tried restarting the nslcd service?
– grawity
Mar 12 at 12:49
I rebooted the whole machine, is it the same?
– DDS
Mar 12 at 13:11
I rebooted the whole machine, is it the same?
– DDS
Mar 12 at 13:11
In the sense that nslcd will have also been restarted along with everything else, it is, yes.
– Gabe
Mar 12 at 15:05
In the sense that nslcd will have also been restarted along with everything else, it is, yes.
– Gabe
Mar 12 at 15:05
add a comment |
1 Answer
1
active
oldest
votes
Check the configuration written by authconfig; since the log messages are about nslcd, try cat /etc/nslcd.conf to make sure it has the correct contents.
To make sure that the correct configuration is picked up, run nslcd in debug mode. You'll have to stop both the nslcd and nscd services – I think centos uses systemd, so systemctl stop nslcd and systemctl stop nscd – and run nslcd -d.
Transport endpoint not connected just means that no network connection was established. In this case, the reason appears to be the misconfiguration.
question edited: required file added
– DDS
Mar 12 at 16:59
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1413359%2fldap-cant-log-in-but-can-ldapsearch-log-transport-endpoint-not-connecte%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Check the configuration written by authconfig; since the log messages are about nslcd, try cat /etc/nslcd.conf to make sure it has the correct contents.
To make sure that the correct configuration is picked up, run nslcd in debug mode. You'll have to stop both the nslcd and nscd services – I think centos uses systemd, so systemctl stop nslcd and systemctl stop nscd – and run nslcd -d.
Transport endpoint not connected just means that no network connection was established. In this case, the reason appears to be the misconfiguration.
question edited: required file added
– DDS
Mar 12 at 16:59
add a comment |
Check the configuration written by authconfig; since the log messages are about nslcd, try cat /etc/nslcd.conf to make sure it has the correct contents.
To make sure that the correct configuration is picked up, run nslcd in debug mode. You'll have to stop both the nslcd and nscd services – I think centos uses systemd, so systemctl stop nslcd and systemctl stop nscd – and run nslcd -d.
Transport endpoint not connected just means that no network connection was established. In this case, the reason appears to be the misconfiguration.
question edited: required file added
– DDS
Mar 12 at 16:59
add a comment |
Check the configuration written by authconfig; since the log messages are about nslcd, try cat /etc/nslcd.conf to make sure it has the correct contents.
To make sure that the correct configuration is picked up, run nslcd in debug mode. You'll have to stop both the nslcd and nscd services – I think centos uses systemd, so systemctl stop nslcd and systemctl stop nscd – and run nslcd -d.
Transport endpoint not connected just means that no network connection was established. In this case, the reason appears to be the misconfiguration.
Check the configuration written by authconfig; since the log messages are about nslcd, try cat /etc/nslcd.conf to make sure it has the correct contents.
To make sure that the correct configuration is picked up, run nslcd in debug mode. You'll have to stop both the nslcd and nscd services – I think centos uses systemd, so systemctl stop nslcd and systemctl stop nscd – and run nslcd -d.
Transport endpoint not connected just means that no network connection was established. In this case, the reason appears to be the misconfiguration.
edited Mar 13 at 9:06
answered Mar 12 at 15:06
GabeGabe
1,817715
1,817715
question edited: required file added
– DDS
Mar 12 at 16:59
add a comment |
question edited: required file added
– DDS
Mar 12 at 16:59
question edited: required file added
– DDS
Mar 12 at 16:59
question edited: required file added
– DDS
Mar 12 at 16:59
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1413359%2fldap-cant-log-in-but-can-ldapsearch-log-transport-endpoint-not-connecte%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you tried restarting the nslcd service?
– grawity
Mar 12 at 12:49
I rebooted the whole machine, is it the same?
– DDS
Mar 12 at 13:11
In the sense that nslcd will have also been restarted along with everything else, it is, yes.
– Gabe
Mar 12 at 15:05