Ticket #3279 (closed defect: fixed)
EBox::SambaLdapUser::sharingName Referral received
| Reported by: | 3@… | Owned by: | cperez@… |
|---|---|---|---|
| Milestone: | 2.2.X | Component: | base |
| Severity: | normal | Keywords: | |
| Cc: | saf@… |
Description (last modified by jacalvo@…) (diff)
Unknown error at EBox::SambaLdapUser::sharingName Referral received
Error
Unknown error at EBox::SambaLdapUser::sharingName Referral received
Trace
Unknown error at EBox::SambaLdapUser::sharingName Referral received at /usr/share/perl5/EBox/Ldap.pm line 701
EBox::Ldap::_errorOnLdap('Net::LDAP::Search=HASH(0x277f1f38)', 'HASH(0x276fd078)') called at /usr/share/perl5/EBox/Ldap.pm line 341
EBox::Ldap::search('EBox::Ldap=HASH(0x2573f430)', 'HASH(0x276fd078)') called at /usr/share/perl5/EBox/SambaLdapUser.pm line 738
EBox::SambaLdapUser::sharingName('EBox::SambaLdapUser=HASH(0x27685320)', 'sekretari') called at /usr/share/perl5/EBox/SambaLdapUser.pm line 633
EBox::SambaLdapUser::_groupSharing('EBox::SambaLdapUser=HASH(0x27685320)', 'sekretari') called at /usr/share/perl5/EBox/SambaLdapUser.pm line 455
EBox::SambaLdapUser::_groupAddOns('EBox::SambaLdapUser=HASH(0x27685320)', 'sekretari') called at /usr/share/perl5/EBox/UsersAndGroups.pm line 2490
EBox::UsersAndGroups::allGroupAddOns('EBox::UsersAndGroups=HASH(0x25797c30)', 'sekretari') called at /usr/share/perl5/EBox/CGI/UsersAndGroups/Group.pm line 52
EBox::CGI::UsersAndGroups::Group::_process('EBox::CGI::UsersAndGroups::Group=HASH(0x27704488)') called at /usr/share/perl5/EBox/CGI/Base.pm line 275
EBox::CGI::Base::run('EBox::CGI::UsersAndGroups::Group=HASH(0x27704488)') called at /usr/share/perl5/EBox/CGI/Run.pm line 129
EBox::CGI::Run::run('EBox::CGI::Run', 'UsersAndGroups/Group', '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(0x2763a268)') 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(0x275f5450)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x275f5450)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x2763a268)') 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:2 Changed 20 months ago by jacalvo@…
- Owner changed from jacalvo@… to cperez@…
- Description modified (diff)
- Summary changed from Bug report from Zentyal Server to EBox::SambaLdapUser::sharingName Referral received
comment:3 Changed 20 months ago by cperez@…
- Status changed from new to closed
- Resolution set to worksforme
Probably this is caused by a misconfiguration, master shouldn't have modules depending on LDAP installed, so if you did that you will need to reinstall users modules on master:
/usr/share/zentyal-users/reinstall
comment:4 Changed 20 months ago by saf@…
- Cc saf@… added
- Status changed from closed to reopened
- Resolution worksforme deleted
We haven't install any module depending on LDAP on master. Master is Zental 2.0.4, and slave is 2.2.1. If we use 2.0.4 as slave, we have no error.
comment:5 Changed 20 months ago by cperez@…
Hi again,
Please, can you post the result of the following command on the master?
sudo slapcat -b cn=config | grep schema
comment:6 Changed 20 months ago by saf@…
result:
dn: cn=schema,cn=config cn: schema dn: cn={0}core,cn=schema,cn=config dn: cn={1}cosine,cn=schema,cn=config dn: cn={2}nis,cn=schema,cn=config dn: cn={3}inetorgperson,cn=schema,cn=config dn: cn={4}passwords,cn=schema,cn=config dn: cn={5}master,cn=schema,cn=config dn: cn={6}slaves,cn=schema,cn=config olcAccess: {2}to dn.base="cn=subschema" by * read
comment:7 Changed 20 months ago by saf@…
sorry, formatting... result:
dn: cn=schema,cn=config
cn: schema
dn: cn={0}core,cn=schema,cn=config
dn: cn={1}cosine,cn=schema,cn=config
dn: cn={2}nis,cn=schema,cn=config
dn: cn={3}inetorgperson,cn=schema,cn=config
dn: cn={4}passwords,cn=schema,cn=config
dn: cn={5}master,cn=schema,cn=config
dn: cn={6}slaves,cn=schema,cn=config
olcAccess: {2}to dn.base="cn=subschema" by * read
comment:8 Changed 20 months ago by cperez@…
weird,
Your schemas seem ok, so something different is happening. I wanna check attributes for the user you are trying to access/modify. Please, do this search for me and post here the results (don't forget to empty sensitive fields, like passwords or names):
# DN=dc=zentyal,dc=com (fill this with your DN) # ldapsearch -x -w $(cat /etc/ldap.secret) -D cn=ebox,$DN -b $DN uid=cperez
I've been chasing this bug for a long time, let's see if today is my day :P
comment:10 Changed 20 months ago by saf@…
Such commands executed on master or slave return the same result, which I understand as empty:
# extended LDIF # # LDAPv3 # base <dc=jnt,dc=office,dc=local> with scope subtree # filter: uid=Reklama # requesting: ALL # # search result search: 2 result: 0 Success # numResponses: 1
Note: on Master we created new user group named "Reklama", add to this group 1 user. Then we want to see users of this group on Slave interface. Slave 2.0.4 shows user without errors, and slave 2.2 returns error.
Maybe I may execute another commands to give you more information?
Sorry for my English.
zentyal.log