Instance 389-ds destroyed herself

Hello everyone,
Sorry for my english.

I’m having an issue with a 389-ds instance. Following an indexing issue, a command to destroy the instance was apparently executed.

Has this happened to anyone else?

Some additional details that I hope will help.

When creating the instance, I chose the DBD format and not the DBM format.

I run the indexing via a scheduled task.

Here is the command:
/usr/sbin/dsconf “$INSTANCE_NAME” backend index reindex “$BACKEND_NAME” --attr “$INDEX”

Here is an extract of the logs.

[05/May/2025:09:29:58.535599639 +0200] - INFO - main - 389-Directory/2.4.5 B2024.198.0000 starting up
[05/May/2025:09:29:58.537862743 +0200] - INFO - main - Setting the maximum file descriptor limit to: 524288
[05/May/2025:09:29:58.632774044 +0200] - INFO - PBKDF2_SHA256 - Based on CPU performance, chose 4000 rounds
[05/May/2025:09:29:58.637385791 +0200] - INFO - ldbm_instance_config_cachememsize_set - force a minimal value 512000
[05/May/2025:09:29:58.639580535 +0200] - INFO - ldbm_instance_config_set - instance: lpfuserroot attr nsslapd-cachesize
[05/May/2025:09:29:58.641015514 +0200] - INFO - ldbm_instance_config_set - instance: lpfuserroot attr nsslapd-cachememsize
[05/May/2025:09:29:58.642986770 +0200] - INFO - ldbm_instance_config_set - instance: lpfuserroot attr nsslapd-readonly
[05/May/2025:09:29:58.644630648 +0200] - INFO - ldbm_instance_config_set - instance: lpfuserroot attr nsslapd-require-index
[05/May/2025:09:29:58.646203986 +0200] - INFO - ldbm_instance_config_set - instance: lpfuserroot attr nsslapd-require-internalop-index
[05/May/2025:09:29:58.647807645 +0200] - INFO - ldbm_instance_config_set - instance: lpfuserroot attr nsslapd-dncachememsize
[05/May/2025:09:29:58.651055971 +0200] - INFO - ldbm_instance_config_cachememsize_set - force a minimal value 512000
[05/May/2025:09:29:58.652844388 +0200] - INFO - ldbm_instance_config_set - instance: lpfroot attr nsslapd-cachesize
[05/May/2025:09:29:58.654425457 +0200] - INFO - ldbm_instance_config_set - instance: lpfroot attr nsslapd-cachememsize
[05/May/2025:09:29:58.655813107 +0200] - INFO - ldbm_instance_config_set - instance: lpfroot attr nsslapd-readonly
[05/May/2025:09:29:58.657644703 +0200] - INFO - ldbm_instance_config_set - instance: lpfroot attr nsslapd-require-index
[05/May/2025:09:29:58.659171552 +0200] - INFO - ldbm_instance_config_set - instance: lpfroot attr nsslapd-require-internalop-index
[05/May/2025:09:29:58.660667102 +0200] - INFO - ldbm_instance_config_set - instance: lpfroot attr nsslapd-dncachememsize
[05/May/2025:09:29:58.664041907 +0200] - INFO - dbmdb_make_env - MBD environment created with maxsize=2147483648.
[05/May/2025:09:29:58.666387470 +0200] - INFO - dbmdb_make_env - MBD environment created with max readers=126.
[05/May/2025:09:29:58.667882779 +0200] - INFO - dbmdb_make_env - MBD environment created with max database instances=512.
[05/May/2025:09:29:58.718332473 +0200] - INFO - validate_num_config_reservedescriptors - reserve descriptors changed from 64 to 114
[05/May/2025:09:29:58.720398418 +0200] - INFO - connection_table_new - Number of connection sub-tables 1, each containing 63886 slots.
[05/May/2025:09:29:58.741984231 +0200] - INFO - slapd_daemon - slapd started. Listening on All Interfaces port 389 for LDAP requests
[05/May/2025:09:29:58.743858657 +0200] - INFO - slapd_daemon - Listening on /run/slapd-wamdirectory01.socket for LDAPI requests
[05/May/2025:09:30:01.742225991 +0200] - INFO - vattr_check_thread - No role/cos definition in o=lpfuserroot
[05/May/2025:09:30:01.744320725 +0200] - INFO - vattr_check_thread - No role/cos definition in o=lpfroot
[05/May/2025:09:30:44.975412438 +0200] - INFO - ct_thread_cleanup - slapd shutting down - signaling connection table threads
[05/May/2025:09:30:44.977880860 +0200] - INFO - op_thread_cleanup - slapd shutting down - signaling operation threads - op stack size 2 max work q size 1 max work q stack size 1
[05/May/2025:09:30:44.981125616 +0200] - INFO - slapd_daemon - slapd shutting down - waiting for 1 thread to terminate
[05/May/2025:09:30:45.197472066 +0200] - INFO - slapd_daemon - slapd shutting down - closing down internal subsystems and plugins
[05/May/2025:09:30:45.226472606 +0200] - INFO - ldbm_back_instance_set_destructor - Set of instances destroyed
[05/May/2025:09:30:45.228450012 +0200] - INFO - connection_post_shutdown_cleanup - slapd shutting down - freed 1 work q stack objects - freed 2 op stack objects

Thanks in advance for any help.

Hello and welcome to the openSUSE forums.

You have tagged this as “other” for the openSUSE version you use. Please then explain which one it is.

Hello,
I don’t use openSUSE but Oracle LINUX.
I throw a bottle into the sea for my bug. I had read an article 389 on your forum so I tried my luck. Maybe a member had already had the problem and knew why.
You can delete my request if is not appropriate

In any case, thank you for taking the time to read this.

Well, you are welcome of course, but it would have been more effective if you had told us from the very beginning.

3 Likes