Modify

Ticket #3797 (closed defect: worksforme)

Opened 16 months ago

Last modified 7 months ago

Couldn't bind to LDAP server, result code: 1

Reported by: p.ricardok@… Owned by: jamor@…
Milestone: 3.0.X Component: users
Severity: minor Keywords:
Cc:

Description (last modified by jamor@…) (diff)

Erro ao abrir o modulo usuários e grupos

Error

Couldn't bind to LDAP server, result code: 1

Trace

Couldn't bind to LDAP server, result code: 1 at /usr/share/perl5/EBox/Ldap.pm line 1124
	EBox::Ldap::safeBind('Net::LDAP=HASH(0xba142d90)', 'cn=ebox,dc=SRV-FW-03', 'T-LKE9.MhwE-Z7hU') called at /usr/share/perl5/EBox/Ldap.pm line 137
	EBox::Ldap::ldapCon('EBox::Ldap=HASH(0xb8bcc790)') called at /usr/share/perl5/EBox/Ldap.pm line 330
	EBox::Ldap::search('EBox::Ldap=HASH(0xb8bcc790)', 'HASH(0xba348940)') called at /usr/share/perl5/EBox/UsersAndGroups.pm line 2005
	EBox::UsersAndGroups::groups('EBox::UsersAndGroups=HASH(0xb9b94160)') called at /usr/share/perl5/EBox/CGI/UsersAndGroups/Users.pm line 47
	EBox::CGI::UsersAndGroups::Users::_process('EBox::CGI::UsersAndGroups::Users=HASH(0xba345470)') called at /usr/share/perl5/EBox/CGI/Base.pm line 275
	EBox::CGI::Base::run('EBox::CGI::UsersAndGroups::Users=HASH(0xba345470)') 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(0xba345cb0)') 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(0xba142700)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
	ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xba142700)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
	ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xba345cb0)') called at -e line 0
	eval {...} called at -e line 0

Attachments

zentyal.log Download (182.5 KB) - added by anonymous 16 months ago.
zentyal.log
software.log Download (26.3 KB) - added by anonymous 16 months ago.
software.log

Change History

Changed 16 months ago by anonymous

zentyal.log

Changed 16 months ago by anonymous

software.log

comment:1 Changed 16 months ago by jamor@…

  • Summary changed from Bug report from Zentyal Server to Couldn't bind to LDAP server, result code: 1
  • Component changed from base to users
  • Description modified (diff)
  • Severity changed from normal to minor

Hello P.Rikardo,

result code 1 means 'operations error'. It is the first time i see it in Zentyal but since it could be caused by bad synchronism between LDAp server and their clients a restart could help:

sudo /etc/init.d/zentyal users restart

Your server is a standalone or is an slave?. It was the first time you accessed to users? have you do any LDAP operation before?.

Regards, Javier

comment:2 Changed 16 months ago by p.ricardok@…

yes it is a server standalone, had already moved to ldap before installing the module's zentyal

comment:3 Changed 16 months ago by jamor@…

So you have already modified the LDAP server before installing Zentyal?. In this case better is to do a reinstall and setup it again.

For this:

sudo /usr/share/zentyal-users/reinstall

And then enter in the web interface and enable users again.

comment:4 Changed 16 months ago by jamor@…

  • Status changed from new to accepted

comment:5 Changed 16 months ago by jamor@…

  • Status changed from accepted to closed
  • Resolution set to worksforme

Hello P Ricardok,

I think the cause was to have a already modified LDAP which have entries incompatibles with Zentyal and likely the reinstall command should fix that.

If I am wrong, please reopen the ticket and give us more feedback.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.