tracker issue : CF-3119586

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

start.log-specific max size setting

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 02/21/2012

Components: Logging

Versions: 10.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: Public Beta / 281583

Priority/Frequency: Trivial / Unknown

Locale/System: English / Platforms All

Vote Count: 1

As mentioned by Charlie:
-----------
there may important value in the start.log being allowed to grow much larger than all the other logs. It is essentially the console log for CF [...] it would be a shame if it followed the same file size/rotation as all other logs (which are generally much smaller for a given timeframe).
-----------

Could CF Admin please permit us to specify a start.log-specific max size?  B/c start.log does actually contain much more info than the other logs, so it’d be nice if we can set its size separately.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3119586

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:

Attachments:

Comments:

Related thread: http://prerelease.adobe.com/r/?c9649d9c56af48d1a8e2c6c9df7f4377
Comment by External U.
20684 | February 21, 2012 03:45:50 PM GMT
This ER is related to bug #CF-3119583 (start.log size not checked between restarts) URL: https://bugbase.adobe.com/index.cfm?event=bug&id=CF-3119583
Comment by External U.
20685 | February 21, 2012 03:47:25 PM GMT
Yes, I hope we can cause the start log to grow larger. It's more than just the "startup log" but is really the console log for CF, so has valuable info both at startup, and during the life of an instance, and then often especially just before an instance goes down. The equivalent log in CF 9 and before (if CF was run as a Windows service) was the [cf]\runtime\*out*.logs (or in [jrun]\logs). The start.log is simply different from all the other typical CF logs, mostly because it tends to hold a lot more info over a same given timeframe. It's also so valuable with respect to troubleshooting, especially over restarts. (Yes, I do realize that the cfserver.log on Linux was the corollary to this, and was itself always in the same [cf]\logs directory as other CF logs, and it rotated/was sized like them. I suppose folks there just didn't perhaps know that we on Windows had the benefit of larger logs.) Those "out" logs did have their own configurable size, separate from the CF log file size setting in the CF Admin. You had to set the out log size separately, either with the jrunsvc command, or via a registry tweak, as I discussed in this blog entry: http://www.carehart.org/blog/client/index.cfm/2010/10/15/controlling_size_of_CF_out_logs But if you wish to be able to have a similar ability to separately control the start.log size, please vote up this bug, and spread the word. :-)
Vote by External U.
20689 | February 21, 2012 04:20:39 PM GMT
Here is a suggestion for the UI (based on our discussion in the forums): Start.log retention: [ ] Retain all start.log files [ ] Maximum combined file size (in kilobytes) [ ] Maximum number of log files to retain [ ] Maximum number of days to retain The first would permit storing all start.log files. The second would only store X kilobytes of start.log files (on server start, if total size of all start.log files was greater than this setting, then the oldest could be deleted). The third would let us say "only keep X number of start.log files. The latter would let us say, only keep start.log files logs for X days. -Aaron Neff
Comment by External U.
20686 | February 22, 2012 03:28:45 AM GMT
Added in neo-logging.xml with default value 20MB and 20 backup files.
Comment by Kiran S.
20687 | February 27, 2012 12:41:00 AM GMT
Verified this is fixed in CF10 Final (build 10,282462). It would be more useful if this setting can be edited on the Logging Settings page of CF Admin. Thanks!, -Aaron
Comment by External U.
20688 | May 27, 2012 01:35:19 AM GMT