[22/Jul/2016:11:35:20 +0200] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381717 msg=Installation Directory:  /opt/opendj-2.6.2
[22/Jul/2016:11:35:20 +0200] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381719 msg=Instance Directory:      /opt/opendj-2.6.2
[22/Jul/2016:11:35:20 +0200] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381713 msg=JVM Information: 1.8.0_91-8u91-b14-0ubuntu4~16.04.1-b14 by Oracle Corporation, 64-bit architecture, 3711959040 bytes heap size
[22/Jul/2016:11:35:20 +0200] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381714 msg=JVM Host: triglav.nlight.eu, running Linux 4.4.0-24-generic amd64, 16696905728 bytes physical memory size, number of processors available 8
[22/Jul/2016:11:35:20 +0200] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381715 msg=JVM Arguments: "-Dorg.opends.server.scriptName=start-ds"
[22/Jul/2016:11:35:20 +0200] category=JEB severity=NOTICE msgID=8847402 msg=The database backend userRoot containing 4005 entries has started
[22/Jul/2016:11:35:20 +0200] category=EXTENSIONS severity=NOTICE msgID=1507549 msg=DIGEST-MD5 SASL mechanism using a server fully qualified domain name of: localhost
[22/Jul/2016:11:35:20 +0200] category=SYNC severity=NOTICE msgID=15139020 msg=Replication server RS(9664) started listening for new connections on address 0.0.0.0 port 10989
[22/Jul/2016:11:35:21 +0200] category=SYNC severity=NOTICE msgID=15138878 msg=Directory server DS(23955) has connected to replication server RS(9664) for domain "cn=admin data" at localhost/127.0.0.1:10989 with generation ID 113844
[22/Jul/2016:11:35:21 +0200] category=SYNC severity=NOTICE msgID=15138878 msg=Directory server DS(161) has connected to replication server RS(9664) for domain "dc=example,dc=com" at localhost/127.0.0.1:10989 with generation ID 19681402
[22/Jul/2016:11:35:21 +0200] category=SYNC severity=NOTICE msgID=15138878 msg=Directory server DS(17438) has connected to replication server RS(9664) for domain "cn=schema" at localhost/127.0.0.1:10989 with generation ID 8408
[22/Jul/2016:11:35:21 +0200] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on Administration Connector 0.0.0.0 port 10444
[22/Jul/2016:11:35:21 +0200] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on LDAP Connection Handler 0.0.0.0 port 10389
[22/Jul/2016:11:35:21 +0200] category=CORE severity=NOTICE msgID=458887 msg=The Directory Server has started successfully
[22/Jul/2016:11:35:21 +0200] category=CORE severity=NOTICE msgID=458891 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 458887):  The Directory Server has started successfully
[22/Jul/2016:11:36:24 +0200] category=CORE severity=NOTICE msgID=458891 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 458893):  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)
[22/Jul/2016:11:36:29 +0200] category=BACKEND severity=NOTICE msgID=9896306 msg=The backend userRoot is now taken offline
[22/Jul/2016:11:36:29 +0200] category=CORE severity=NOTICE msgID=458955 msg=The Directory Server is now stopped
