Critical When not using --strict, if ChronicleLogTailer fails to start, the rest of the runtime does not start, resulting in an only partially usable instance.
Component Loading Status displays on the console, but does not appear in the server log. INFO [main] [org.nuxeo.runtime.osgi.OSGiRuntimeService] Nuxeo Platform Started does not appear in the server log.
To reproduce, get a new Nuxeo and start it. Stop it and remove the day's cq4 file from data/stream/audit/audit/P-00. Start Nuxeo, and an exception like the following should be generated on startup:
2019-09-11T14:25:24,403 ERROR [main] [org.nuxeo.osgi.OSGiAdapter] Error during Framework Listener execution : class org.nuxeo.runtime.osgi.OSGiRuntimeService java.lang.IllegalStateException: Unable to move to the last committed offset, ChronicleLogTailer{basePath='/home/harlan/nuxeo-server-10.10-tomcat/nxserver/data/stream/audit/audit', id=AuditLogWriter:audit-00, closed=false, codec=org.nuxeo.lib.stream.codec.NoCodec@7cdab66c} offset: 77953656422420 at org.nuxeo.lib.stream.log.chronicle.ChronicleLogTailer.toLastCommitted(ChronicleLogTailer.java:175) ~[nuxeo-stream-10.10-HF10.jar:?] at org.nuxeo.lib.stream.log.chronicle.ChronicleLogTailer.<init>(ChronicleLogTailer.java:82) ~[nuxeo-stream-10.10-HF10.jar:?] at org.nuxeo.lib.stream.log.chronicle.ChronicleLogAppender.createTailer(ChronicleLogAppender.java:315) ~[nuxeo-stream-10.10-HF10.jar:?] at org.nuxeo.lib.stream.log.chronicle.ChronicleLogManager.lambda$doCreateTailer$3(ChronicleLogManager.java:215) ~[nuxeo-stream-10.10-HF10.jar:?]
The Exception should not prevent the rest of the runtime from starting
or
the unavailability of the audit log component should be displayed in the Component Loading Status
or
the server should not start when the exception occurs/audit log component is unavailable.
