Re: How to change jena-fuseki logging level

[Andy Seaborne]

I would make my own using jena-fuseki-docker.

Then it has the setup for the deployment targetted. Logging, location of 
persistent database, text index, base OS, ...

Otherwise, read the descriptions and see what works for you. (most are 
forks)

    Andy

On 17/10/2024 12:49, jaa...@kolumbus.fi wrote:
Hi, which one of the possible docker images in Docker hub would you recommend 
(I just found the ones in the attachment)?

Br, Jaana


17.10.2024 14.38 EEST Andy Seaborne <a...@apache.org> kirjoitti:

  
On 17/10/2024 10:31, jaa...@kolumbus.fi 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 <a...@apache.org> kirjoitti:

   
On 17/10/2024 03:37, jaa...@kolumbus.fi 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