[Kolab-devel] OpenLDAP problem

[Buchan Milne]

Martin Konold wrote:
> Hi,
> 
> I have seen now multiple times an OpenLDAP server hanging and using 100% cpu.
> 
> This is the trace
> 
> stat64("/kolab/var/openldap/openldap-data/__db.003", {st_mode=S_IFREG|0600, 
> st_size=98304, ...}) = 0
> open("/kolab/var/openldap/openldap-data/__db.003", O_RDWR|O_CREAT|O_LARGEFILE, 
> 0600) = 4
> fcntl64(4, F_SETFD, FD_CLOEXEC)         = 0
> mmap2(NULL, 98304, PROT_READ|PROT_WRITE, MAP_SHARED, 4, 0) = 0x401fb000
> close(4)                                = 0
> stat64("/kolab/var/openldap/openldap-data/__db.004", {st_mode=S_IFREG|0600, 
> st_size=368640, ...}) = 0
> open("/kolab/var/openldap/openldap-data/__db.004", O_RDWR|O_CREAT|O_LARGEFILE, 
> 0600) = 4
> fcntl64(4, F_SETFD, FD_CLOEXEC)         = 0
> mmap2(NULL, 368640, PROT_READ|PROT_WRITE, MAP_SHARED, 4, 0) = 0x40213000
> close(4)                                = 0
> stat64("/kolab/var/openldap/openldap-data/__db.005", {st_mode=S_IFREG|0600, 
> st_size=16384, ...}) = 0
> open("/kolab/var/openldap/openldap-data/__db.005", O_RDWR|O_CREAT|O_LARGEFILE, 
> 0600) = 4
> fcntl64(4, F_SETFD, FD_CLOEXEC)         = 0
> mmap2(NULL, 16384, PROT_READ|PROT_WRITE, MAP_SHARED, 4, 0) = 0x4026d000
> close(4)                                = 0
> stat64("/kolab/var/openldap/openldap-data/id2entry.bdb", {st_mode=S_IFREG|
> 0600, st_size=32768, ...}) = 0
> stat64("/kolab/var/openldap/openldap-data/id2entry.bdb", {st_mode=S_IFREG|
> 0600, st_size=32768, ...}) = 0
> open("/kolab/var/openldap/openldap-data/id2entry.bdb", O_RDONLY|O_LARGEFILE) = 
> 4
> fcntl64(4, F_SETFD, FD_CLOEXEC)         = 0
> read(4, "\0\0\0\0\1\0\0\0\0\0\0\0b1\5\0\t\0\0\0\0@\0\0\0\t\0\0\0"..., 512) = 
> 512
> close(4)                                = 0
> stat64("/kolab/var/openldap/openldap-data/id2entry.bdb", {st_mode=S_IFREG|
> 0600, st_size=32768, ...}) = 0
> open("/kolab/var/openldap/openldap-data/id2entry.bdb", O_RDONLY|O_LARGEFILE) = 
> 4
> fcntl64(4, F_SETFD, FD_CLOEXEC)         = 0
> fstat64(4, {st_mode=S_IFREG|0600, st_size=32768, ...}) = 0
> sched_yield()                           = 0
> sched_yield()                           = 0
> sched_yield()                           = 0
> sched_yield()                           = 0
> sched_yield()                           = 0
> 
> Does this look familiar to anyone?

You would need to give some information on the size of the database, 
whether you have done tuning, whether you have had openldap shut down 
badly, whether you have run database recovery etc or not.

If you have a large database (or a very busy one), ensure you have a 
checkpoint setting in your database definition. If this is not the case, 
  stop slapd, run database recovery (ie 'db_recover -h <path to ldap 
database>') and start openldap again. Then try and find out why your 
database needed recovery ...

(Note, I don't currently run Kolab, since I have many other applications 
which use LDAP, which are more important, none of which overwrite my 
LDAP configuration :-(), so I am not sure exactly how (ie DB_CONFIG 
files) how Kolab configures OpenLDAP.

Regards,
Buchan

-- 
Buchan Milne                      Senior Support Technician
Obsidian Systems                  http://www.obsidian.co.za
B.Eng                                RHCE (803004789010797)