My CMS is stuck on debugging and it keeps bugging me. The log level is set at:
“Resting Log Level”: Error
and
“Log Level”: Error
and the “Elevated Log Until” is empty
Despite this I can constantly see API.DEBUG and XMDS.DEBUG types of messages, which bloat the log.txt. I had to empty it, because it got to over 30GB of size.
What should I do to either disable the debugging mode, or to limit the size of the log to something sensible?
Can you also check that your CMS is in “Production Mode”? It sounds like it is in test mode, which enables full debugging regardless of the log level settings.
These type of messages can be turned on/off by individual displays using the “auditing until” setting in the advanced tab of the Display edit form. You should be able to see which displays are logging those messages and check their settings.
API.DEBUG
which bloat the log.txt
Xibo doesn’t log to a file by default - have you added any custom loggers or log middle-wares?
If you have, then you may want to check what minimum log level you have set on those custom loggers. Usually the constructor takes a log level config variable.
Can confirm that this solution worked for me. Although I had two files in different directories that contained this line and the one on the previous post was not the correct file. However when I changed the line in the other directory it started working.