DSpace Log File Does Not Populate With INFO or DEBUG Messages.

[Braxton Van Gundy]

Hello,

I'm trying to get DSpace to output DEBUG and INFO messages to the dspace.log file, it creates the log file however most of the time it does not write anything to it. Sometimes it will write a few info / debug messages and then stop writing to the log file for the rest of the day. I have another test server and it will write thousands of debug / info messages to the log throughout the day which is what i'm looking for. I'm not sure where I am going wrong with this other server, i've compared their configurations and they look the same. I'm thinking it might be the way I am making the changes to the "/usr/local/dspace/config/log4j.properties" file, here is the process I am following, I have attached the file for reference:

1. Edit the "/usr/local/dspace/config/log4j.properties", changing INFO to DEBUG on lines 25 and 31.

2. restart tomcat using "sudo systemctl stop tomcat" and then "sudo systemctl start tomcat"

3. Navigate to my DSpace site and produce some internal server errors to populate the logs

4. Go to today's DSpace log file found at "/usr/local/dspace/log/dspace.log.2020-06-16"

The log file is empty, even though I performed some searches and ran into some internal server errors.  I've spent a couple hours trying to figure out what the difference is / what I might be doing wrong.  Any suggestions here? There's also a DSpace page that mentions doing this in the src directory and then running "ant init_configs", however I tried this and it made no difference. 

[Braxton Van Gundy]

For anyone with the same issue.  I found that I had to do a full DSpace rebuild ("mvn package" and then "ant update").  If that still doesn't work, also check your log4j-console.properties file and try setting "log4j.rootCategory" to INFO and then rebuild.