tracker issue : CF-4199666

select a category, or use search below
(searches all categories and all time range)
Title:

New instances log folder is set to cfusion\logs instead of [instancename]\logs

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/NotABug

Reporter/Name(from Bugbase): Tyler Clendenin / Tyler Clendenin ()

Created: 09/13/2017

Components: Logging

Versions: 2016

Failure Type: Data Corruption

Found In Build/Fixed In Build: 2016.0.04.302561 / NA

Priority/Frequency: Normal / All users will encounter

Locale/System: English / Win 2012 Server x64

Vote Count: 0

Problem Description:
New instances, created using Instance Manager, continue to use the cfusion\logs folder instead of their new [intancename]\logs folder

Steps to Reproduce:
Create a new instance and look at Debugging & Logging > Logging Settings

Any Workarounds:
Edit the Log Directory

Attachments:

Comments:

We do not see this happening. Exceptions generated in the new instance, are logged in log files of the new instances. Could you please provide log files demonstrating the issue?
Comment by Immanuel N.
334 | September 14, 2017 07:00:08 AM GMT
There's not really a log file showing this, so much as it creates the follwing three files in "C:\ColdFusion2016\instance\logs", "axis2.log", "coldfusion-error.log", and "coldfusion-out.log". However these files are empty and continue to be empty until I change the setting "Log directory" in Debugging & Logging > Logging Settings from "C:\ColdFusion2016\cfusion\logs" to "C:\ColdFusion2016\instance\logs" and restart eh Coldfusion instance. During this time the logs are correctly written to the "C:\ColdFusion2016\cfusion\logs" folder (since this is the setting in the instance). The main issue I have is that the instance is created with an incorrect log directory, pointing to the root instance, instead of the newly created instance.
Comment by Tyler C.
335 | September 14, 2017 02:32:17 PM GMT
We could not repro this issue on a Windows 2012 R2 server, with 2 instances. The newly created instance had the right path listed in logging settings, and also logged correctly to the right directory.  Could you please provide the platform details, in case we have got that part wrong? Were any errors reported during instance creation? 
Comment by Immanuel N.
29560 | August 21, 2018 06:09:31 AM GMT