It looks like this is related to https://issues.apache.org/jira/browse/SOLR-17063
I'm investigating, but it looks like it would be appropriate to open a Jira issue for this. Thanks for reporting! Michael On Wed, Feb 21, 2024 at 4:52 PM Thomas Corthals <tho...@klascement.net> wrote: > > Hi > > I've been using api/node/logging/messages since 9.3 and api/node/logging > with older versions to get logs and with Solr 9.5.0 this no longer outputs > the history and causes an ERROR instead. I can get the logs with the v1 API > at solr/admin/info/logging so they are stored correctly. > > On a freshly started Docker container with the official Solr image: > > $ curl -s http://localhost:8983/api/node/logging/messages?since=0 > > {"info":{"levels":["ALL","TRACE","DEBUG","INFO","WARN","ERROR","FATAL","OFF"],"buffer":50,"last":1708551723017},"responseHeader":{"status":0,"QTime":54},"watcher":"Log4j2","history":[{}]} > > $ curl -s http://localhost:8983/solr/admin/info/logging?since=0 > > { > "responseHeader":{ > "status":0, > "QTime":1 > }, > "info":{ > "levels":["ALL","TRACE","DEBUG","INFO","WARN","ERROR","FATAL","OFF"], > "last":1708551745996, > "buffer":50 > }, > "history":{ > "numFound":4, > "start":0, > "numFoundExact":true, > "docs":[{ > "time":"2024-02-21T21:42:02.510Z", > "level":"WARN", > "logger":"org.apache.solr.util.StartupLoggingUtils", > "message":"Jetty request logging enabled. Will retain logs for last 3 > days. See chapter \"Configuring Logging\" in reference guide for how to > configure.", > "core":"" > },{ > "time":"2024-02-21T21:42:02.514Z", > "level":"WARN", > "logger":"org.apache.solr.core.CoreContainer", > "message":"Not all security plugins configured! > authentication=disabled authorization=disabled. Solr is only as secure as > you make it. Consider configuring authentication/authorization before > exposing Solr to users internal or external. See > https://s.apache.org/solrsecurity for more info", > "core":"" > },{ > "time":"2024-02-21T21:42:03.017Z", > "level":"WARN", > "logger":"org.glassfish.jersey.message.internal.MessagingBinders", > "message":"A class jakarta.activation.DataSource for a default > provider MessageBodyWriter<jakarta.activation.DataSource> was not found. > The provider is not available.", > "core":"" > },{ > "time":"2024-02-21T21:42:25.996Z", > "level":"ERROR", > "logger":"org.glassfish.jersey.server.ServerRuntime$Responder", > "message":"An I/O error has occurred while writing a response message > entity to the container output stream.", > "trace_id":"null-4", > "core":"" > }] > }, > "watcher":"Log4j2" > } > > Is this something I'm missing on my side or something that's missing in the > official Docker container or Solr itself? > > Thomas
