Topic: LDAP Address Book in Horde showing 'Blank name' entries

[jacktripper1000]

Hello,

I just installed SME Server 7.4 and found that the horde address book is weirdly showing 5 entries, all with name 'Blank name'. When I click any one of these, they are all empty.

I have about 9 users so its not even correct in number of entries. I have no idea where to look.

The only thing I could find is

message log shows this:

Code: [Select]

Feb 21 16:50:28 sme slapd[6355]: conn=7 op=13 SRCH base="ou=Users,dc=server,dc=com" scope=1 deref=0 filter="(&(objectClass=posixAccount)(uid=test))"
Feb 21 16:50:28 sme slapd[6355]: conn=7 op=13 SRCH attr=uid userPassword uidNumber gidNumber cn homeDirectory loginShell gecos description objectClass
Feb 21 16:50:28 sme slapd[6355]: conn=7 op=13 SEARCH RESULT tag=101 err=0 nentries=1 text=
Feb 21 16:50:28 sme slapd[6355]: conn=7 op=14 SRCH base="dc=server,dc=com" scope=2 deref=0 filter="(&(objectClass=shadowAccount)(uid=test))"
Feb 21 16:50:28 sme slapd[6355]: conn=7 op=14 SRCH attr=uid userPassword shadowLastChange shadowMax shadowMin shadowWarning shadowInactive shadowExpire shadowFlag
Feb 21 16:50:28 sme slapd[6355]: conn=7 op=14 SEARCH RESULT tag=101 err=0 nentries=1 text=
Feb 21 16:50:28 sme slapd[6355]: conn=7 op=15 SRCH base="ou=Groups,dc=server,dc=com" scope=1 deref=0 filter="(&(objectClass=posixGroup))"
Feb 21 16:50:28 sme slapd[6355]: conn=7 op=15 SRCH attr=cn userPassword memberUid uniqueMember gidNumber
Feb 21 16:50:28 sme slapd[6355]: conn=7 op=15 SEARCH RESULT tag=101 err=0 nentries=16 text=
Feb 21 16:50:28 sme slapd[6355]: conn=24 fd=23 ACCEPT from IP=127.0.0.1:33112 (IP=127.0.0.1:389)
Feb 21 16:50:28 sme slapd[6355]: conn=24 op=0 BIND dn="" method=128
Feb 21 16:50:28 sme slapd[6355]: conn=24 op=0 RESULT tag=97 err=0 text=
Feb 21 16:50:28 sme slapd[6355]: conn=24 op=1 UNBIND
Feb 21 16:50:28 sme slapd[6355]: conn=24 fd=23 closed

Is there something I need to setup?

I have the following contribs installed:

Code: [Select]

LDAP
Crontab Manager
Email Whitelist Blacklist
Service Control
PHPLDapAdmin
PHP Sysinfo
BackupPC
PHPMyAdmin
OCS Inventory Tools
VMWare
Redmine
Subversion
Mail Queue Manager

I tried installing another machine with no contribs. It seems to show the addresses correctly.

Where do I start?
Please help!

- Jack

[David Harper]

Please file a bug in bugzilla so this issue can be investigated. If you could also post the bug number in the thread for future reference, that would be great.

[CharlieBrady]

Please file a bug in bugzilla so this issue can be investigated.

With all those contribs installed, including one which allows arbitrary changes to be made to LDAP content, then I don't know who you'll find who wants to investigate this. Core SME server developers won't. OP is responsible for breaking LDAP, not a bug in SME server software.

[jacktripper1000]

You are correct. I don't think it is a bug in SME server. Hence I didn't file one.
However I am asking if someone has seen something like this or any clue where to look.
I don't want to repeat this mistake.

>>> OP is responsible for breaking LDAP
BTW, What's OP?

[CharlieBrady]

You are correct. I don't think it is a bug in SME server. Hence I didn't file one.
However I am asking if someone has seen something like this or any clue where to look.
I don't want to repeat this mistake.

Don't install so many contribs - preferably don't install any, and don't install any you are not sure you need. If you want to install a contrib, test it first on another system.

>>> OP is responsible for breaking LDAP
BTW, What's OP?

Original poster. You!

[jacktripper1000]

I guess I got overly ambition.
Currently we have these systems:

1. Openfiler for NAS
2. Scalix on a CentOS 5 server
3. Redmine and VMWare virtual server
4. Ebox Platform for user authentication

I was trying to integrate all the functionality together. Guess that is not a good idea.

We do need LDAP support though so I will integrate that along with original install and keep all the rest separate.

Cheers.

[jacktripper1000]

FWIW, I have reproduced the problem.
Here are the steps:

1. Install SME server 7.4 clean install.
2. Enable SSH (this should not matter, but anyhow).
3. Create a user called test.
4. Enable Workgroup mode, PDC, Roaming profiles Off.
5. Update server to latest version.
6. Issue signal-event post-upgrade; signal-event reboot
7. Install LDAP: yum install e-smith-base+ldap e-smith-samba+ldap --enablerepo=smetest --enablerepo=smeupdates-testing
8. Issue signal-event post-upgrade; signal-event reboot
9. Enable webmail. And check.

And then it happens.

Has anyone got LDAP package working?

Let me know if I should file a bug for this.

[cactus]

FWIW, I have reproduced the problem.
Here are the steps:

1. Install SME server 7.4 clean install.
2. Enable SSH (this should not matter, but anyhow).
3. Create a user called test.
4. Enable Workgroup mode, PDC, Roaming profiles Off.
5. Update server to latest version.
6. Issue signal-event post-upgrade; signal-event reboot
7. Install LDAP: yum install e-smith-base+ldap e-smith-samba+ldap --enablerepo=smetest --enablerepo=smeupdates-testing
8. Issue signal-event post-upgrade; signal-event reboot
9. Enable webmail. And check.

And then it happens.

Has anyone got LDAP package working?

Let me know if I should file a bug for this.

Perhaps, it seems at least you have found a method to reproduce (although it is a awfully long and complex one, you might want to reduce this), but you fail to give all details, what are the settings for the test user for instance. Did you observer any errors/warnings during upgrade?

[Stefano]

As the contribs you install are in smetest repository, I think:
- you should know that they are in  beta status
- you should raise a bug

Thank you

Ciao
Stefano

[jacktripper1000]

It looks like a horde bug (or maybe LDAP package). Seems like the full LDAP features are not understood by horde.

[jacktripper1000]

Perhaps, it seems at least you have found a method to reproduce (although it is a awfully long and complex one, you might want to reduce this), but you fail to give all details, what are the settings for the test user for instance. Did you observer any errors/warnings during upgrade?

I don't think it is too long. I just wanted to be detailed.
The actual steps I think are have atleast one user, enable PDC, update and install LDAP.
I think it is something to do with update and LDAP or maybe just LDAP messing horde.

- Jack

[jacktripper1000]

Tested again on a clean machine.
Simply installing LDAP package breaks Horde address book.

- Jack

[Stefano]

Tested again on a clean machine.
Simply installing LDAP package breaks Horde address book.

- Jack

well.. I don't see any bug reference in your post..

ciao
Stefano

[Craig Cabrey]

Tested again on a clean machine.
Simply installing LDAP package breaks Horde address book.

- Jack

Shouldn't this be considered a bug if LDAP is to be the base for future SME releases?

In the meantime, I would suggest trying GroupOffice; It is much better than Horde and should work.

Craig

[CharlieBrady]

Tested again on a clean machine.
Simply installing LDAP package breaks Horde address book.

OK, so don't install "LDAP package".

What "LDAP package", BTW?