/lucee/cache - max size and /lucee/temp/ - max size

Have not seen this error before. When I check the directories they are empty. From the Lucee Log:

"WARN","Thread-2011779","08/19/2019","10:06:58","lucee.runtime.engine.Controler","check size of directory [/WEB-INF/lucee/temp]"
"WARN","Thread-2011779","08/19/2019","10:06:58","lucee.runtime.engine.Controler","- current size	[0]"
"WARN","Thread-2011779","08/19/2019","10:06:58","lucee.runtime.engine.Controler","- max size 	[1073741824]"
"WARN","Thread-2011779","08/19/2019","10:06:58","lucee.runtime.engine.Controler","check size of directory [/WEB-INF/lucee/cache]"
"WARN","Thread-2011779","08/19/2019","10:06:58","lucee.runtime.engine.Controler","- current size	[0]"
"WARN","Thread-2011779","08/19/2019","10:06:58","lucee.runtime.engine.Controler","- max size 	[104857600]"

That runs once an hour, purging the temp and cache dirs. Next release the logs will be a little less verbose.

1 Like

Are there any (good) news to this topic?
I’m running lucee 5.3.3.62 on a Windows Server 2012 R2 and my logfiles are growing bigger and bigger until I delete them manualy via log analyzer.
After 2 weeks of running my server hangs up because of missing place on the hard drive.

Yeah, I agree these shouldn’t be logged out by default, these are really debug entries, file a bug!

(they used to be WARN level, now they are INFO level? https://luceeserver.atlassian.net/browse/LDEV-2290)

Workaround: change your web context’s application log level from INFO to ERROR:

[host:port]/lucee/admin/web.cfm?action=server.logging