Creating accounts problem

[quanah]

Then you will continue to run into this problem. Xen has a serious bug in it that does not allow it to work with various software.

Please read:
Virtualization Zimbra

--Quanah

[Rich Graves]

You're going to need to move at least the Zimbra LDAP server off of Xen. Search forums for "virtualisation xen".

Raw hardware, OpenVZ, and VMWare will work. KVT and Xen 3.1 (as in FC8) need to be tested.

[quanah]

Anything using sleepycat would need to be removed from the Xen VM. LDAP is one of those things, but not the only one of those things. SA uses sleepycat, for example. So does Amavis.

--Quanah

[d64]

Originally Posted by Rich Graves

You're going to need to move at least the Zimbra LDAP server off of Xen. Search forums for "virtualisation xen".

Raw hardware, OpenVZ, and VMWare will work. KVT and Xen 3.1 (as in FC8) need to be tested.

Can Zimbra use ANY OpenLDAP server, or am I required to use the Zimbra LDAP?

[quanah]

You need to use the Zimbra shipped OpenLDAP.

[d64]

Originally Posted by quanah

You need to use the Zimbra shipped OpenLDAP.

I tried to look around, but didn't find a thread/doc on how to separate the LDAP to another system in an existing installation. Are there any docs for that?

The BDB issue is strange, though. Seems people are running systems much busier than mine under Xen without such problems.

[quanah]

Originally Posted by d64

The BDB issue is strange, though. Seems people are running systems much busier than mine under Xen without such problems.

Without issue is questionable. The locking subsystem simple doesn't work with Xen. When/how they hit issues is somewhat like Russian roulette.

--Quanah

[d64]

Originally Posted by quanah

Without issue is questionable. The locking subsystem simple doesn't work with Xen. When/how they hit issues is somewhat like Russian roulette.

--Quanah

FWIW, after I updated the (distribution provided) kernel on the virtual machine Zimbra is running on to the latest provided version, I have not had any further LDAP problems. It has only been a little more than a week, but before the update I had to run the db recovery command every couple of days. It'll be interesting to see if the problem went away.

My talks with people knowing more of Xen than I were not conclusive but their opinion was that there's no known reason for this error to still be happening today.

EDIT: About three weeks now (with slowly increasing number of users too) and the problem has not come up again. If this keeps up for some time more I'll be ready to believe that the issue has been fixed on my setup..