Ticket #3257 (closed defect: worksforme)
Couldn't bind to LDAP server, result code: 49
| Reported by: | ajbotani@… | Owned by: | cperez@… |
|---|---|---|---|
| Milestone: | 2.0.X | Component: | users |
| Severity: | normal | Keywords: | |
| Cc: |
Description (last modified by jacalvo@…) (diff)
Error
Couldn't bind to LDAP server, result code: 49
Trace
Couldn't bind to LDAP server, result code: 49 at /usr/share/perl5/EBox/Ldap.pm line 1124
EBox::Ldap::safeBind('Net::LDAP=HASH(0x7f521353cc68)', 'cn=ebox,dc=servidor2,dc=pqrmnt8,dc=lan', '.a5-v3oMTibnHq2Q') called at /usr/share/perl5/EBox/Ldap.pm line 137
EBox::Ldap::ldapCon('EBox::Ldap=HASH(0x7f52134bc3a8)') called at /usr/share/perl5/EBox/Ldap.pm line 330
EBox::Ldap::search('EBox::Ldap=HASH(0x7f52134bc3a8)', 'HASH(0x7f52126d0400)') called at /usr/share/perl5/EBox/UsersAndGroups.pm line 1989
EBox::UsersAndGroups::groups('EBox::UsersAndGroups=HASH(0x7f5212761ca8)') called at /usr/share/perl5/EBox/CGI/UsersAndGroups/Users.pm line 47
EBox::CGI::UsersAndGroups::Users::_process('EBox::CGI::UsersAndGroups::Users=HASH(0x7f52122d6c40)') called at /usr/share/perl5/EBox/CGI/Base.pm line 275
EBox::CGI::Base::run('EBox::CGI::UsersAndGroups::Users=HASH(0x7f52122d6c40)') called at /usr/share/perl5/EBox/CGI/Run.pm line 129
EBox::CGI::Run::run('EBox::CGI::Run', 'UsersAndGroups/Users', 'EBox') called at /usr/share/zentyal/cgi/ebox.cgi line 34
ModPerl::ROOT::ModPerl::Registry::usr_share_zentyal_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0x7f52112d7b88)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0x7f52134b4110)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x7f52134b4110)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x7f52112d7b88)') called at -e line 0
eval {...} called at -e line 0
Attachments
Change History
Changed 20 months ago by anonymous
-
attachment
zentyal.log
added
comment:1 Changed 20 months ago by jacalvo@…
- Owner changed from jacalvo@… to cperez@…
- Description modified (diff)
- Milestone changed from 2.2 to 2.2.X
comment:2 Changed 20 months ago by cperez@…
That error means that the pasword for LDAP admin user is incorrect. Have you done something special like reinstalling or manual change?
comment:3 Changed 20 months ago by jacalvo@…
- Status changed from new to closed
- Resolution set to worksforme
Please reopen if you can provide detailed information about the steps you followed to get this error. Otherwise we can't reproduce it.
comment:4 Changed 18 months ago by jan.tatarik@…
- Status changed from closed to reopened
- Resolution worksforme deleted
Encountered the same error with Users and Groups 2.2.4.
I got an idea what might be going on when I noticed my LDAP password contained a slash character (XqKJCqV/EyA0Xfgh). I replaced the slash with '1' on both master and slave (XqKJCqV1EyA0Xfgh) and sure enough - now it works.
I suspect the admin password, as entered in the HTML form on the slave machine, is getting modified the form handler - perhaps special characters get encoded? Didn't really try to debug it.
comment:5 Changed 18 months ago by jacalvo@…
- Summary changed from Bug report from Zentyal Server to Couldn't bind to LDAP server, result code: 49
comment:7 Changed 18 months ago by cperez@…
Hi,
Can you explain how you changed the password in master and slave machines?
Thank you
comment:8 Changed 18 months ago by jan.tatarik@…
On the master I simply edited /var/lib/zentyal/conf/ebox-ldap.passwd and restarted.
As to the client - ran /usr/share/zentyal-users/reinstall and then typed in the modified master password in the Zentyal GUI when setting up ldap slave.
I also ran the slave reinstall few times before modifying the master password, double checking I'm using the same password on both sides. Didn't help. Then modified the password, replaced '/' with '-' and that didn't work either. My bet is alphanumeric characters are fine, but I didn't try anything else after I got it working with '1'.
comment:9 Changed 18 months ago by cperez@…
I don't understand how could this happend, / is a valid char in password. What happends if you change that '1' with a '2' for example?
Thank you for your help
comment:10 Changed 18 months ago by cperez@…
- Status changed from reopened to closed
- Resolution set to worksforme
Sorry, I couldn't reproduce this, '/' in the password works for me, probably you had some other problem during setup
Reopen if you can provide more information,
Best regards
zentyal.log