Good Friday everyone, I am trying out the new version of both gms and frontend v0.9.3. During the deployment of the gms I got the following messages:

2022-12-02 12:25:59.457:INFO:oejshC.ROOT:main: 1 Spring WebApplicationInitializers detected on classpath
 SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
 SLF4J: Defaulting to no-operation (NOP) logger implementation
 SLF4J: See <http://www.slf4j.org/codes.html#StaticLoggerBinder> for further details.
 2022-12-02 12:25:59.531:INFO:oejs.session:main: DefaultSessionIdManager workerName=node0
 2022-12-02 12:25:59.531:INFO:oejs.session:main: No SessionScavenger set, using defaults
 2022-12-02 12:25:59.533:INFO:oejs.session:main: node0 Scavenging every 600000ms
 2022-12-02 12:25:59.597:INFO:oejshC.ROOT:main: Initializing Spring root WebApplicationContext
 SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder".
 SLF4J: Defaulting to no-operation MDCAdapter implementation.
 SLF4J: See <http://www.slf4j.org/codes.html#no_static_mdc_binder> for further details.
 ANTLR Tool version 4.5 used for code generation does not match the current runtime version 4.7.2ANTLR Runtime version 4.5 used for parser compilation does not match the current runtime version 4.7.2ANTLR Tool version 4.5 used for code generation does not match the current runtime version 4.7.2ANTLR Runtime version 4.5 used for parser compilation does not match the current runtime version 4.7.2ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
 ANTLR Tool version 4.5 used for code generation does not match the current runtime version 4.7.2ANTLR Runtime version 4.5 used for parser compilation does not match the current runtime version 4.7.2ANTLR Tool version 4.5 used for code generation does not match the current runtime version 4.7.2ANTLR Runtime version 4.5 used for parser compilation does not match the current runtime version 4.7.22022-12-02 12:26:53.116:INFO:oejshC.ROOT:main: Initializing Spring DispatcherServlet 'apiServlet'
 2022-12-02 12:26:53.639:INFO:oejshC.ROOT:main: Initializing Spring DispatcherServlet 'authServlet'
 2022-12-02 12:26:53.711:INFO:oejshC.ROOT:main: Initializing Spring DispatcherServlet 'openapiServlet'
 2022-12-02 12:26:56.239:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@6eda5c9{Open source GMS,/,[file:///tmp/jetty-0_0_0_0-8080-war_war-_-any-11220994130116230824/webapp/, jar:file:///tmp/jetty-0_0_0_0-8080-war_war-_-any-11220994130116230824/webapp/WEB-INF/lib/swagger-ui-4.10.3.jar!/META-INF/resources],AVAILABLE}{file:///datahub/datahub-gms/bin/war.war}
 2022-12-02 12:26:56.261:INFO:oejs.AbstractConnector:main: Started ServerConnector@4387b79e{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}
 2022-12-02 12:26:56.263:INFO:oejs.Server:main: Started @71782ms

I know those errors don't usually mean that there has been an error during the deployment, and Datahub's performance isn't affected at all, but as I didn't obtain the message

INFO  c.d.m.ingestion.IngestionScheduler:251 - Successfully 		fetched 4 ingestion sources.

I thought that maybe something was wrong (which at first it doesn't feel like it) But anyways I just wanted to let you know those two things as in previous versions didn't happen 🙂

Looks like some of the security fixes are causing some conflicting versions and its missing the expected logger. This is a very good catch! I’ll look into getting this resolved. Thanks!

@brainy-tent-14503 Hello, when can we expect these changes to be released? I see the current version is v0.9.3 which doesn't include your merged modifications. My frontend and gms pods aren't logging, how can I get these changes into my deployment?

Next release is targeting mid-next week. That said there are builds from that merge here GMS

<http://docker.io/linkedin/datahub-gms:2de9d3d|docker.io/linkedin/datahub-gms:2de9d3d>

and frontend

<http://docker.io/linkedin/datahub-frontend-react:2de9d3d|docker.io/linkedin/datahub-frontend-react:2de9d3d>

which I pull from the build logs when it was merged. Those images include the logging fix with some but as few as possible changes from v0.9.3

@brainy-tent-14503 I'm seeing the same error for 0.9.3's standalone mae/mce consumer

Picked up JAVA_TOOL_OPTIONS:
ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
 :: Spring Boot ::               (v2.5.12)
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See <http://www.slf4j.org/codes.html#StaticLoggerBinder> for further details.

The same tag above works for all consumers and their images. The fix was hopefully comprehensive for all modules like the frontend, gms, mae, mce, etc

Got it, thanks!

Having the same issue as above using 0.2.118 / 0.91, please confirm once new fixed version is released, thank you 😁

@brainy-tent-14503 I appreciate the prompt update with the linked docker images. Im in k8s using these charts: https://github.com/acryldata/datahub-helm. Am I correct in assuming that your fix will be released here:https://github.com/datahub-project/datahub/releases and then picked up by the next acryldata release that follows? Thank you for your work and time on this issue.

The next OSS release is being cut today, a helm chart update will follow shortly.