Ldap.pm:1124 EBox::Ldap::safeBind - Couldn't bind to LDAP server, result code: 49

[expertgeeks@…]

I have set up 2 installations from Zentyal 2.2 CD, created a master LDAP server & slave machine, changed the local LDAP rule to enabled in the Firewall, but when the module is enabled on the slave machine I get;

OK 
The server encountered an internal error or misconfiguration and was unable to complete your request. 
Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log. 

Zentyal log on the Slave Machine;

2012/02/16 14:05:57 INFO> GlobalImpl.pm:653 EBox::GlobalImpl::saveAllModules - Changes saved successfully
2012/02/16 14:07:16 ERROR> Ldap.pm:1124 EBox::Ldap::safeBind - Couldn't bind to LDAP server, result code: 49
2012/02/16 14:07:16 ERROR> ConfigureModuleController.pm:74 EBox::CGI::ServiceModule::ConfigureModuleController::__ANON__ - Failed to enable: Couldn't bind to LDAP server, result code: 49
2012/02/16 14:09:13 INFO> GlobalImpl.pm:539 EBox::GlobalImpl::saveAllModules - Saving config and restarting services: firewall users
2012/02/16 14:09:13 INFO> Base.pm:228 EBox::Module::Base::save - Restarting service for module: firewall
2012/02/16 14:09:14 INFO> GlobalImpl.pm:653 EBox::GlobalImpl::saveAllModules - Changes saved successfully
2012/02/16 14:09:37 INFO> GlobalImpl.pm:539 EBox::GlobalImpl::saveAllModules - Saving config and restarting services: firewall users
2012/02/16 14:09:37 INFO> Base.pm:228 EBox::Module::Base::save - Restarting service for module: firewall
2012/02/16 14:09:38 INFO> Base.pm:228 EBox::Module::Base::save - Restarting service for module: users
2012/02/16 14:09:39 ERROR> Ldap.pm:1124 EBox::Ldap::safeBind - Couldn't bind to LDAP server, result code: 49
2012/02/16 14:09:39 ERROR> GlobalImpl.pm:612 EBox::GlobalImpl::__ANON__ - Failed to save changes in module users: Couldn't bind to LDAP server, result code: 49
2012/02/16 14:09:39 ERROR> GlobalImpl.pm:664 EBox::GlobalImpl::saveAllModules - The following modules failed while saving their changes, their state is unknown: users
2012/02/16 14:10:04 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/02/16 14:10:05 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/02/16 14:10:07 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/02/16 14:10:08 ERROR> Ldap.pm:1103 EBox::Ldap::safeConnect - Couldn't connect to LDAP server ldapi://%2fvar%2frun%2fslapd%2fldapi, retrying
2012/02/16 14:10:09 ERROR> Ldap.pm:1107 EBox::Ldap::safeConnect - FATAL: Couldn't connect to LDAP server: ldapi://%2fvar%2frun%2fslapd%2fldapi
2012/02/16 14:17:04 INFO> Service.pm:716 EBox::Module::Service::restartService - Restarting service for module: events
2012/02/16 14:17:07 INFO> EventDaemon.pm:307 EBox::EventDaemon::_loadModules - EBox::Event::Dispatcher::Log loaded from registeredDispatchers

[jamor@…]

Hello Expertgeeks,

result code 49 means 'invalid credentials' so the password or another information about your masters is incorrect.

Run '/usr/share/zentyla-users/reinstall' in the slave and setup again. Also make sure than your master can resolve your slave name.

Regards,

Javier

[smupinya@…]

I have downloaded the Zentyal-2.2 software and have setup both a master running in a vm and a slave on bare metal. Have performed all the updates, followed the instructions and referenced the trac log system numerous times in regards to issues with ldap. I can put users into master and they will sync on slave without 2 much problem, but the captive portal module (installed on slave as it is the gateway) will not validate against the master with this in the /var/log/zentyal-captiveportal/error.log "Ldap.pm:1124 EBox::Ldap::safeBind - Couldn't bind to LDAP server, result code: 49". Going through the trac log system I have seen numerous requests from users in regards to LDAP issues and it seems the overwhelming majority of which get pushed off on the "reinstall" solution because the password is incorrect in the configuration.

When looking at /var/log/zentyal/error.log it is astonishing at how many entries that are about uninitialized values being utilized in a whole slew of perl modules. This sounds like poor programming and perhaps this actually plays a huge role in why you have so many help tickets listed.

[jamor@…]

Hello,

it seems the relevant error is "Ldap.pm:1124 EBox::Ldap::safeBind - Couldn't bind to LDAP server, result code: 49"

result code 49 means 'invalid credentials', so srely the problem is that you are configuring your slave with a incorrect password.

Regards,

Javier