Second PAB created for user
Sun Java(tm) System Messaging Server 6.2-7.05 (built Sep 5 2006)
libimta.so 6.2-7.05 (built 12:18:44, Sep 5 2006)
We have two frontend MEM's to one backend store (all using the above versions). We're still using Mess Express (not UWC). We had a customer report that his address book had disappeared. Upon searching the LDAP logs in o=PAB we found that indeed a new address book was created, however his older one still existed:
Entry of the additional PAB:
dn: un=AddressBookcf9c80a,ou=UID, ou=people, dc=yyy,dc=xx,o=pab
changetype: add
un: AddressBookcf9c80a
objectClass: top
objectClass: pab
cn: Address Book
However the true (original) address book is:
dn: un=AddressBook41f0c69,ou=UID, ou=people, dc=yyy, dc=xx,o=pab
un: AddressBook41f0c69
objectClass: top
objectClass: pab
cn: Address Book
When he logged into ME, he could only see the newer one (the first one in the above) even tho the original one with many entries in it was still in LDAP. The newer one was created by the messaging user that is configured, but why? Has anyone else seen this? We deleted the newer one (had only two addressbook entries) and then they were able to see the original again once they logged in.
[1288 byte] By [
JHU_JESa] at [2007-11-26 15:58:45]
# 1
Hi,
> When he logged into ME, he could only see the newer
> one (the first one in the above) even tho the
> original one with many entries in it was still in
> LDAP. The newer one was created by the messaging
> user that is configured, but why?
If I had to guess, I would say that for some reason the PAB was not accessible (when the LDAP search was performed there were no results) so ME created a fresh addressbook.
Do you have a replicated master/slave ldap environment? Have you had any directory issues recently, modified ACI's etc?
> Has anyone else
> seen this?
I haven't heard of a case like this.
The most common issue with PAB's in ME is that the dn: of a user is changed, so the paburi which uses the dn: as a key into the o=pab tree doesn't correspond so you get an error when accessing the PAB.
Regards,
Shane.
# 3
Hi,
> Thanks the response. We have had some issues with
> the DS being slow in responding which is leading us
> to bringing in another server to help off load
> searches. We are in a master/slave environment.
> Hopefully this is the only such case.
Just are reminder that Messaging server MUST point to the master directory server for PAB access (local.service.pab.ldaphost).
> I'm aware of the uid changes because unfortunately
> that happens here way too often and we have to change
> all kinds of attributes. This is not the case here.
Fortunately there was a re-think by the engineers for the address-book used by UWC. It key's off the users uid and not their dn so dn changes for a user don't affect the address book access.
Regards,
Shane.
