Stephane, I can't reproduce the hang on my test machine with gdb. (Despite your investigation seems right for me). CPU usage stay low, as usual on this machine (same slapd config than the production servers, but only 1 CPU is available).
To prove I made the right steps :-) : $ gdb --args ldapsearch ldaps://front -x [...] (gdb) break write Function "write" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (write) pending. (gdb) run Starting program: /usr/bin/ldapsearch ldaps://front -x conti [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Breakpoint 1, __GI___libc_write (fd=3, buf=0x55555578b2f0, nbytes=14) at ../sysdeps/unix/sysv/linux/write.c:27 27 ../sysdeps/unix/sysv/linux/write.c: No such file or directory. (gdb) continue Continuing. Breakpoint 1, __GI___libc_write (fd=1, buf=0x55555578b2f0, nbytes=16) at ../sysdeps/unix/sysv/linux/write.c:27 27 in ../sysdeps/unix/sysv/linux/write.c Another information (maybe not important, or not related to this case): since monday, I started to migrate LDAP DB backend from BDB to LMDB. So I must wait next slapd hang to be sure DB change have no impact on this issue. (in the past there were sometimes 2 or 3 weeks elapsed between two slap hang). note: I reverted DB backend on my test machine but without reproducing the issue too -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
