Participating Frequently

Question

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

Forum|Forum|2 years ago
November 11, 2023
15 replies
7592 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..

A

Aaron Trice

Participating Frequently

Closing the loop on this. We finally found the root cause for our case. We had some code in our application that was calling log4j and modifying the logging level on the fly. Removing that code, resolved this issue for us.

T

Tim2842955474bi

Participating Frequently

Wow interesting... we do have code that instantiates log4j but doesn't seem to be modifying logging level... will certainly dig deeper though. One thing we noticed is logging seems fine with our code in CF2023 so far... working on migrating.

T

Tim2842955474bi

Participating Frequently

Just wanted to note here that all this time later, we are still having this problem. Adobe has been looking into it but to no avail. Clean installs of CF 2021 have the same issue. Very frustrating. Our CF2023 test servers are still logging so far, I'm considering just migrating over to that, I don't have confidence at this point in any resolution for CF2021. Hopefully CF2023 doesn't have the same problem.

A

Aaron Trice

Participating Frequently

We too are still seeing this issue. We were just discussing internally doing a clean install since we've made no progress with support. Out of curoistiy, did you perform a clean windows install as well? Or just CF? This has been going on for over a year for us.

T

Tim2842955474bi

Participating Frequently

Just CF, I haven't done a clean install of Windows on any servers. However as it's happening on all of our servers (even developer laptops), many of those have been "newly built" Windows laptops over the past year.

M

Mike - Media3

New Participant

I ran into the same issue where the ColdFusion-out.log file stopped being written to. I stopped the service, cleared the Felix-cache, and started it back up, and that resolved it. Hope this helps!

T

Tim2842955474bi

Participating Frequently

Is that still working for you? It didn't help on our end. Logs still stop within a day. We do have a ticket with Adobe, they are working on it.

A

Aaron Trice

Participating Frequently

This hasn't worked for us. We're still working with support. We found this week that when this issue occurs, the appenders are stopped. They provided an update, new bootstrap file, and a cfm to dump the logging status when the issue comes up. We uploaded logs they requested Friday for them to review.

T

Tim2842955474bi

Participating Frequently

We're having the same problem across the board on all 32 of our CF2021 servers, and also in our local dev environments (each developer has a setup). We've tried running the updater from the command line and through the CFAdmin (which is notoriously sketchy in my experience, frequently trashing CF). It makes no difference.

We do have a ticket open with Adobe and have been sending back and forth logs over a month, no fix yet. I'm tempted to roll back to update 10. This is a huge impediment.

T

Tim2842955474bi

Participating Frequently

BTW like some others mentioned, it's not just Coldfusion-out that stops, ALL of our logging stops.

A

Aaron Trice

Participating Frequently

Glad I'm not the only one. I'm still working this with support. No resolution yet. My Case is ColdFusion case# 111193 if you'd like to share it with your engineer. They're giving me the impression I'm the only person that's having this issue.

What update were you on before loading HF10? We went from HF9 to 12 and that's when this started for us.

A

Aaron Trice

Participating Frequently

The fix seems to be remove/reinstall the HF. That has worked on two of our servers, we'll be rolling out to more this week. I checked the hash of the two HF files (my original download and the new one support had me download) and they are the same. Support indicated that the HF must not have completely installed when we did the original deploy. I asked him how we can know if it was completely installed or not when the HF install log showed 100% success. I'm waiting for an answer back on that.

D

dkeith@psasys

New Participant

Aaron, Thank you for keeping up on this. We've had the same logging issue. Not only did I have to re-install HF 11 and HF 12, I had to delete our application sandbox from the CF Security Sandbox page before the logging starting working again. So there is a new permissions requirement for logging that our application is now needing. We still need an application sandbox but at least it's a way forward.

A

Aaron Trice

Participating Frequently

Following up on this thread, Even on machines I have reinstalled each patch, the logging eventually stops once the CF-Error or CF-out log hits it's max size. We don't use the sandbox in our environment. I had a call with support yesterday and they indicated that the log4j files don't seem to be getting updated correctly by the HF installer, even though the logs show 100% success. They are going to be uploading some files for me to test on a machine.

Charlie Arehart

Community Expert

To everyone in the thread, I want to repeat that whatever this problem is that you all are having, there's GOT to be some common denominator among you to explain it, other than simply updating cf 2021 or 2023 beyond the updates released in October (11 and 5, respectively). I say this because I've not seen the problem in any of several dozens of servers I help several dozen folks with, on all manner of OS versions, deployments, and architectures--all on those updates or the next.

I realize neochad reported it to Adobe and they could reproduce it. They must have hit upon whatever the exact situation that uniquely leads to this problem. What is it? Did they tell you? It doesn't seem we (any of us here) know yet. But that's what we need to determine--at least until Adobe comes out with a fix--if people want to solve it in the meantime, other than cranking up that max file size as a workaround.

It may be related to some config change made (that not everyone makes). It may be about some particular installer used (there have been different ones for each of those two cf versions). It may have something to do with a particular java version, or how it was implemented. It could be related to running the lockdown tool, or some manual lockdown step some have done. I could go on. Or it could be some combination of the above, or of course some other thing/s. I'm just throwing out ideas.

Again, if anyone connects the dots, it will be great to hear.

I don't suppose any of you have yet opened a tracker ticket (tracker.adobe.com). If you may have done it, or will, you could share that here and the others could vote it up--and they would then get notified if Adobe marks it fixed. In that case, Adobe may offer a hotfix there--before any cf update includes it.

As always, just trying to help. No offense intended toward anyone.

/Charlie (troubleshooter, carehart. org)

A

Aaron Trice

Participating Frequently

I opened a tracker yesterday https://tracker.adobe.com/#/view/CF-4220471I. Also have a support case open, not much traction on that front yet though. I'll update this thread if we find the root cause.

A

Aaron Trice

Participating Frequently

Support provided a new bootstrap.jar for us to try. That worked on some of our servers, but not all of them. Waiting for more feedback from them on what was changed in the version they provided, and any insight on what may be causing it to work on some servers but not all.

A

Aaron Trice

Participating Frequently

We're seeing the same behavior in our environment. However, we're seeing all logs stop writing, not just coldfusion-out.

D

dwaynek27338072

Participating Frequently

It's the same with us for all logs when they reach time/size for rollover.

C

carl type3

Brainiac

Tap into. Seen the same on some of the CF2021 hosts I touch. Not got a solution to add.

D

dwaynek27338072

Participating Frequently

Did you find a solution for this? We are having the same issue for all our Coldfusion 2021 instances with hotfix 12. We are using Windows server OS running on AWS EC2 instances.

D

dwaynek27338072

Participating Frequently

Sorry, forgot to post what we are seeing in the ColdFusion Exception.log:
"Error","scheduler-4","01/16/24","16:19:07","CMPRO","ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@685ebf04] unable to create manager for [L:\coldfusion\logs\session.timeout.log] with data

N

neochad

Inspiring

I have been going back and forth with Adobe CF support since I also encountered this problem after upgrading to 2023. They were able to reproduce it on their end and have esclated to product team. Thank you for making this post, I referenced this thread in my communication with them to show it was not a unique issue to our configuration.

Ali SozkesenAuthor

Participating Frequently

You are welcome. That's very kind of you.

I've allocated 20GB of out log space, by updating neo-logging xml and hopefully waiting for the permanent solution.

Show more replies

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