I'm using the old version because UI is broken in the versions of stain/jena-fuseki since 4.8. But I just discoverd that I can try stain/jena-fuseki:4.0.0.
Jaana > 17.10.2024 08.33 EEST Lorenz Buehmann <[email protected]> > kirjoitti: > > > Hi, > > is there a reason for using this ancient Fuseki version 3.14.0 instead > of latest 5.1.0 available via the given Docker image? > > The problem with your old version is that the log4j properties file > wouldn't be contained in the Tarball file [1] that the Docker container > does download and extract, thus, using the latest Docker image version > 5.1.0 would be the easiest way to have the log4j config inside the > container. > > Regards, > > Lorenz > > [1] > https://archive.apache.org/dist/jena/binaries/apache-jena-fuseki-3.14.0.tar.gz > > On 17.10.24 04: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 > > -- > Lorenz Bühmann > Research Associate/Scientific Developer > > Email [email protected] > > Institute for Applied Informatics e.V. (InfAI) | Goerdelerring 9 | 04109 > Leipzig | Germany
