Hi I have an issue with Lucee not writing to log f...
# lucee
a
Hi I have an issue with Lucee not writing to log files "after a while". Is there a chance that https://luceeserver.atlassian.net/browse/LDEV-3978 will impact writing to non-standard logs eg:
Copy code
<cflog file="myLog" text="some stuff to log">
We have just noticed that one of our logs stopped logging a few days ago. Not throwing any errors about not being able to log; just: not writing to the log. if I stick a debug log entry in after the log entry above, the second log entry goes in fine:
Copy code
<cflog file="myLog" text="some stuff to log"> <!--- not writing to log file --->
<cflog file="myLog2" text="some stuff to log"> <!--- IS writing to log file --->
If I restart the container, the
myLog.log
will write the one next log entry it receives, then... no more. We're on
5.3.9.133
, from a container built with the stock Lucee
5.3.9.133-nginx
Docker image. Note:
myLog
is not configured in Lucee admin, we are just writing to it via
<cflog file="myLog">
Fuck it's this: https://luceeserver.atlassian.net/browse/LDEV-4035 If I log as fatal, the log entry goes in. Looks like we need to do another Lucee version upgrade. Excellent. The previous one took a month and went so well 😐
https://luceeserver.atlassian.net/browse/LDEV-4035 is scant on useful detail. Was there any way identified of tripping this issue, so we can test it? Also... it's scant on detail as to what the actual cause of the issue was. Looking at the changes to the source code is not particularly enlightening for me :-S