cfml

Is there a chance that work done on <https://luceeserver.atlassian.net/browse/LDEV-4035> might result in the logger's config being reloaded without being asked?

Since upgrading to 5.4.1.8, we are experiencing our logs stopping logging INFO records, after successfully logging some for a while.

All these logs are configured via `org.lucee.cfml.Administrator`'s `updateLogSettings` method, in onApplicationStart. This was to work around the issue that unless one registers the log (either via the above or in Lucee Admin), the `writeLog(file=xxx)` will not log anything lower than ERROR due to [I do not recall, but it came out in an earlier discussion on LDEV-4035 or similar].

When we start the app it's fine for a few min, but then it again ceases logging anything lower than ERROR.

This is new behaviour since we upgraded from 5.3.9.166 last week. It started *exactly* then.

"Interestingly", rerunning the `updateLogSettings`  code does _not_ fix it even temporarily.

Doing an entire container rebuild _does_, but only for a few min.

My colleague has pointed me to this: <https://dev.lucee.org/t/5-3-9-stops-logging-while-in-a-docker-container/10120/17>

So looks like it had been an issue, was "fixed" at least for a while, but has regressed?

Another consideration here. We have three identical containers; the issue only occurred on _one_ of them. It's not the heaviest traffic one, but it's the one that is doing the most logging, given the nature of its usage.

I could not replicate in our dev environment either.

NB: @ <@U070SQMD1>'s request, I have ported this to the Lucee discourse thing. <https://dev.lucee.org/t/5-4-1-8-stops-logging-while-in-a-docker-container/12888>