#Logs from OpenDJ-in-opendj-init-0 2019-04-09 13:34:56,620 [INFO] [wait-for-it] - Hi world, waiting for config backend to be ready before running /opt/scripts/entrypoint.sh 2019-04-09 13:34:58,052 [INFO] [wait-for-it] - Config backend is ready. 2019-04-09 13:34:58,052 [INFO] [wait-for-it] - Now executing the arguments passed to /opt/scripts/wait-for-it: /opt/scripts/entrypoint.sh INFO - 2019-04-09 13:34:58,972 - Syncing OpenDJ certs. INFO - 2019-04-09 13:35:01,680 - Checking certificate's Subject Alt Name (SAN) INFO - 2019-04-09 13:35:01,971 - Re-generating OpenDJ certs with SAN support. INFO - 2019-04-09 13:35:05,570 - Installing OpenDJ. INFO - 2019-04-09 13:35:59,937 - Configuring OpenDJ. INFO - 2019-04-09 13:36:32,808 - Creating indexes for userRoot backend. INFO - 2019-04-09 13:37:48,469 - Creating indexes for site backend. INFO - 2019-04-09 13:38:19,070 - Adding data into LDAP. [09/Apr/2019:13:38:57 +0000] category=CORE severity=NOTICE msgID=org.opends.messages.core.134 msg=Gluu-OpenDJ 3.0.1-gluu (build 20180801142102, revision number c5ad2e4846d8aeb501ffdfe5ae2dfd35136dfa68) starting up [09/Apr/2019:13:39:00 +0000] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.21 msg=Installation Directory: /opt/opendj [09/Apr/2019:13:39:00 +0000] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.23 msg=Instance Directory: /opt/opendj [09/Apr/2019:13:39:00 +0000] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.17 msg=JVM Information: 1.8.0_171-b11 by Oracle Corporation, 64-bit architecture, 464519168 bytes heap size [09/Apr/2019:13:39:00 +0000] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.18 msg=JVM Host: opendj-init-0.opendj.default.svc.cluster.local, running Linux 4.15.0 amd64, 2087550976 bytes physical memory size, number of processors available 2 [09/Apr/2019:13:39:00 +0000] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.19 msg=JVM Arguments: "-Dorg.opends.server.scriptName=start-ds" [09/Apr/2019:13:39:01 +0000] category=PLUGGABLE severity=NOTICE msgID=org.opends.messages.backend.513 msg=The database backend site containing 2 entries has started [09/Apr/2019:13:39:01 +0000] category=PLUGGABLE severity=NOTICE msgID=org.opends.messages.backend.513 msg=The database backend userRoot containing 166 entries has started [09/Apr/2019:13:39:02 +0000] category=EXTENSIONS severity=NOTICE msgID=org.opends.messages.extension.221 msg=DIGEST-MD5 SASL mechanism using a server fully qualified domain name of: opendj-init-0.opendj.default.svc.cluster.local [09/Apr/2019:13:39:03 +0000] category=PROTOCOL severity=NOTICE msgID=org.opends.messages.protocol.276 msg=Started listening for new connections on Administration Connector 0.0.0.0 port 4444 [09/Apr/2019:13:39:03 +0000] category=PROTOCOL severity=NOTICE msgID=org.opends.messages.protocol.276 msg=Started listening for new connections on LDAPS Connection Handler 0.0.0.0 port 1636 [09/Apr/2019:13:39:03 +0000] category=CORE severity=NOTICE msgID=org.opends.messages.core.135 msg=The Directory Server has started successfully [09/Apr/2019:13:39:03 +0000] category=CORE severity=NOTICE msgID=org.opends.messages.core.139 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID org.opends.messages.core-135): The Directory Server has started successfully