Participating Frequently

Question

ColdFusion (2021 release) Update 11 Stops coldfusion-out.log

Forum|Forum|2 years ago
November 11, 2023
15 replies
7593 views

I use CF 2021 release for a long time. After installing the Update 11, when the coldfusion-out.log reaches a certain size, it's archieved as coldfusion-out.1.log but writing logs to default file stops.

All services running properly, all other logs works just fine but out log stops writing untill restarting coldfusion.

As far as I know, I've tested removing cflogging.jar, changing logging directory etc.

It's working on Ubuntu 23.04 (GNU/Linux 6.2.0-36-generic x86_64)

Anyone facing the same issue or having a solution for that problem?

Any help would be appreciated..

Show previous replies

Ali SozkesenAuthor

Participating Frequently

Update 12 is released today. Not seems relevant with the issue, seems mostly about security, but it's mentioned that "This update also removes the cf-logging.jar file and creates its backup in the updates folder."

I'm adding this comment for informational purposes. I didn't test it in the wild yet.

Charlie Arehart

Community Expert

FWIW, I've not seen this in any of my own servers (cf2021 or 2023, with either of the two latest updates). I've also not heard of anyone else reporting this beyond you all here, including my clients (several dozen on those updates) nor in the community.

That's not denying it's happening, but instead suggesting that there may be something unique to your setups (collectively) to explain things. It will be interesting to hear the ultimate resolution.

/Charlie (troubleshooter, carehart. org)

N

neochad

Inspiring

I can confirm the same problem in ColdFusion 2023

Ali SozkesenAuthor

Participating Frequently

As a temporary solution I modified neo-logging.xml / maxOutLogSize from 20 to 2000 which changes 20MB limit for coldfusion-out.log to 2 GB. (requires CF to be restarted)

Unfortunately, logs are crucial for my production and I'll be keeping an eye on the log file size until a fix releases. Hopefully!

S

Sireex

Participating Frequently

I have the same issue with update 11.

Update logs shows no errors:

Installation: Successful.

1612 Successes
0 Warnings
0 NonFatalErrors
0 FatalErrors

coldfusion-out.1.log seems normal, but after that coldfusion-out.log has only few lines and hasn't been updated in a week.

Running jdk-11.0.16.1

S

Sireex

Participating Frequently

We have an identical test server, except this instance is using jdk-11.0.19.

I did some testing with archiving current coldfusion-out.log and got these errors in the log file (coldfusion-out):

ERROR StatusConsoleListener Unable to delete file C:\ColdFusion2021\cfusion\logs\coldfusion-out.3.log: java.nio.file.FileSystemException C:\ColdFusion2021\cfusion\logs\coldfusion-out.3.log: The process cannot access the file because it is being used by another process.

ERROR StatusConsoleListener Unable to copy file C:\ColdFusion2021\cfusion\logs\coldfusion-out.2.log to C:\ColdFusion2021\cfusion\logs\coldfusion-out.3.log: java.nio.file.FileSystemException C:\ColdFusion2021\cfusion\logs\coldfusion-out.3.log: The process cannot access the file because it is being used by another process.

Ali SozkesenAuthor

Participating Frequently

I've shutdown CF server, deleted logs directory, restarted it.

logs directory and log files created again.

But still the same. When coldfusion-out.log reaches 20.4 MB, it is archived like coldfusion-out.1.log and creates a new coldfusion-out.log with zero content.

All other logs are working perfect.

Charlie Arehart

Community Expert

I've not heard of any problem of that sort caused by the update. I'd question any of many other things:

Since the error happens when the log fills (and the archival DOES happen), what is shown in any of the cf logs at that time?
Have you confirmed there are 0 fatalerrors and nonfatalerrors in the latest update log in the hf-updates folder?
Since you refer to manipulating the logging jars, have you been doing that BEFORE the update? There's no reason to still be doing that. Log4j issues were solved in past updates
While you may feel this is new since the cf update, do you know when cf had been restarted BEFORE that? It's tracked in the cf logs. If it may have been weeks or months (or even just days) before, note that something could have changed to impact this...which WOULD have started happening if you'd simply restarted cf without the update.

These are all just possibilities to consider. Keep us posted on anything you may find.

/Charlie (troubleshooter, carehart. org)

Ali SozkesenAuthor

Participating Frequently

I've not heard of any problem of that sort caused by the update. I'd question any of many other things:
Since the error happens when the log fills (and the archival DOES happen), what is shown in any of the cf logs at that time?
11/11/2023 19:38:26 is the moment of archival and init of new log file.
Server log:
"Warning","http-nio-8500-exec-6","11/11/23","19:38:32","promoManagement","Thread: http-nio-8500-exec-6, processing template: /opt/ColdFusion2021/cfusion/wwwroot/promos/syncAll.cfm, completed in 512 seconds, exceeding the 30 seco>
Exception log:
Nothing relevant the issue, or at the specific moment.
coldfusion-error.log
Nothing relevant the issue, or at the specific moment.
Have you confirmed there are 0 fatalerrors and nonfatalerrors in the latest update log in the hf-updates folder?
cfusion/hf-updates/hf-2021-00011-330247 > Adobe_ColdFusion_2021_Update_11_Install_11_08_2023_23_57_34.log
1571 Successes
0 Warnings
0 NonFatalErrors
0 FatalErrors
Since you refer to manipulating the logging jars, have you been doing that BEFORE the update? There's no reason to still be doing that. Log4j issues were solved in past updates
I did after update & facing the problem. I get back the file, restarted coldfusion several times.
While you may feel this is new since the cf update, do you know when cf had been restarted BEFORE that? It's tracked in the cf logs. If it may have been weeks or months (or even just days) before, note that something could have changed to impact this...which WOULD have started happening if you'd simply restarted cf without the update.
It's nearly restarted weekly, never faced the issue.
These are all just possibilities to consider. Keep us posted on anything you may find.

By @Charlie Arehart

Charlie Arehart

Community Expert

I'll tap out, then.

/Charlie (troubleshooter, carehart. org)

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded