Describe the bug
OpenDJ containers after version 4.3.1 refuses to start.
To Reproduce
Steps to reproduce the behavior:
docker run -h ldap-01.domain.com -p 1389:1389 -p 1636:1636 -p 4444:4444 --name ldap-01 openidentityplatform/opendj:4.4.1 as described here
Expected behavior
Container would start.
Screenshots
[root@salt srv]# docker run --rm -h ldap-01.domain.com -p 1389:1389 -p 1636:1636 -p 4444:4444 --name ldap-01 openidentityplatform/opendj:4.4.1
Instance data Directory is empty. Creating new DJ instance
BASE DN is dc=example,dc=com
Password set to password
Running /opt/opendj/bootstrap/setup.sh
Setting up default OpenDJ instance
Configuring Directory Server .....
Error Configuring Directory Server.
See /tmp/opendj-setup-2815916878706871712.log for a detailed log of the failed
operation.
Please report this error and provide the log file mentioned above.
To see basic server configuration status and configuration, you can launch
/opt/opendj/bin/status
Try to upgrade OpenDJ
* OpenDJ has already been upgraded to version
4.4.1.a215512b69fe3609239b13872d4edfd463f13734
Starting OpenDJ
[16/Mar/2019:15:53:39 +0000] category=com.forgerock.opendj.ldap.config.config severity=NOTICE msgID=571 msg=Loaded extension from file '/opt/opendj/lib/extensions/snmp-mib2605.jar' (build 4.4.1, revision a215512b69fe3609239b13872d4edfd463f13734)
An error occurred while attempting to bootstrap the Directory Server: Unable to load the configuration-enabled schema: FileNotFoundException: 02-config.ldif (No such file or directory) (FileInputStream.java:-2 FileInputStream.java:195 FileInputStream.java:138 FileReader.java:72 ConfigurationHandler.java:1222 ConfigurationHandler.java:217 ConfigurationHandler.java:199 DirectoryServer.java:1288 DirectoryServer.java:5015)
[16/Mar/2019:15:53:39 +0000] category=CORE severity=NOTICE msgID=139 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerShutdown, alert ID org.opends.messages.core-141): The Directory Server has started the shutdown process. The shutdown was initiated by an instance of class org.opends.server.core.DirectoryServerShutdownHook and the reason provided for the shutdown was The Directory Server shutdown hook detected that the JVM is shutting down. This generally indicates that JVM received an external request to stop (e.g., through a kill signal)
[16/Mar/2019:15:53:39 +0000] category=CORE severity=ERROR msgID=140 msg=An uncaught exception during processing for thread Directory Server Shutdown Hook has caused it to terminate abnormally. The stack trace for that exception is: NullPointerException (DirectoryServer.java:4252 DirectoryServerShutdownHook.java:64)
[16/Mar/2019:15:53:39 +0000] category=CORE severity=NOTICE msgID=139 msg=The Directory Server has sent an alert notification generated by class org.opends.server.api.DirectoryThread (alert type org.opends.server.UncaughtException, alert ID org.opends.messages.core-140): An uncaught exception during processing for thread Directory Server Shutdown Hook has caused it to terminate abnormally. The stack trace for that exception is: NullPointerException (DirectoryServer.java:4252 DirectoryServerShutdownHook.java:64)
Desktop (please complete the following information):
Describe the bug
OpenDJ containers after version 4.3.1 refuses to start.
To Reproduce
Steps to reproduce the behavior:
docker run -h ldap-01.domain.com -p 1389:1389 -p 1636:1636 -p 4444:4444 --name ldap-01 openidentityplatform/opendj:4.4.1as described hereExpected behavior
Container would start.
Screenshots
Desktop (please complete the following information):