Hello, you write below, that stain/* shouldn't be used as it is not part of Apache Jena project and that there's 5.1.0 in dockerhub. Yes, there are several 5.* images in dockerhub, but I don't know which ones of them are part of Apache Jena project. Can you help ?
Jaana > 17.10.2024 14.38 EEST Andy Seaborne <[email protected]> kirjoitti: > > > On 17/10/2024 10:31, [email protected] wrote: > >> You should upgrade to Jena 5.x to get security updates. > > > > The problem is that UI does not work in stain/jena-fuseki-version higher > > than 4.0.0. > > 1. stain/* is not a product of the Apache Jena project. > > 2. Are you sure? There is a 5.1.0 on dockerhub. > > Andy > > > > > Jaana > > > >> 17.10.2024 11.45 EEST Andy Seaborne <[email protected]> kirjoitti: > >> > >> > >> On 17/10/2024 03:37, [email protected] wrote: > >>> > >>> I'm running docker.io/stain/jena-fuseki:3.14.0 in podman container on > >>> linux redHat host. I a very heavy load it can happen that > >>> /var/log/messages-file receives huge amount of INFO-level messages from > >>> jena-fuseki. How can I change the log level of my container to get rid of > >>> these messages ? > >>> > >>> This is similar with > >>> https://stackoverflow.com/questions/71615972/change-jena-fuseki-logging-level > >>> > >>> https://stackoverflow.com/questions/71615972/change-jena-fuseki-logging-level > >>> , but the problem now is that I cannot find the file log4j2.properties > >>> from inside the container. > >>> > >>> Br, Jaana > >> > >> 3.14.0 used log4j1 The file will be called log4j.properties. > >> > >> If it does not exist, then the server uses a built in default. You can > >> place a logging setup in the container at the expected pl;ace and it > >> should use on start-up. > >> > >> You should upgrade to Jena 5.x to get security updates. > >> > >> Andy
