SLF4J log error in stdout console ROR 6.1-1.17.5

With ROR 6.1-1.17.5 , i got a SLF4J log error in stdout console for each elasticsearch restart (ES 6.1.1 and RHEL 6.7).

SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See SLF4J Error Codes for further details.

on /usr/share/elasticsearch/plugins/readonlyrest directory we have total 81 jar files.
ls -ltr /usr/share/elasticsearch/plugins/readonlyrest/slf command retrun slf4j-api-1.7.25.jar

we got the errors in multiple nodes but the elasticsearch started OK.
what are the implications of this error?

Hi Simone , can you please update ?
we don’t see any impact , everything looks ok , just want to know if we need to have this missing jar file or if there’s a patch coming soon which is going to solve it .


Hi @alonzo. You’re right. The log has no impact on ROR’s work or ROR’s logs (we’re using log4j, like Elasticsearch does). At the moment I don’t know why slf4j is not able to load proper implementation (there is one in classpath). But you don’t have to be worry about it.

1 Like

great , good to know that. thank you .