ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

CA Directory logs rollover gets created incorrectly when yesterday's alarm/trace log files are deleted or moved.

book

Article ID: 199653

calendar_today

Updated On:

Products

CA Directory DIRECTORY

Issue/Introduction

Questions related to the "Log Roll Over Created Incorrectly" section of the following article.
CA Directory 12.6.06 Defect Fixes: DE402024 "Log Roll Over Created Incorrectly"
CA Directory 14.1 CR01 Fixed Issues: DE402024

Q1. Is this a problem on all platforms or only on Unix/Linux?
Q2. Is the "Log Roll Over Created Incorrectly" problem completely resolved by upgrading to version '14.1 CR1'?

Cause

"Log Roll Over Created Incorrectly" issue happens when alarm and/or trace Directory logs are configured for roll-over, i.e. the settings are:
set rollover-alarm-log = true;
and/or
set rollover-trace-log = true;

If alarm and/or trace log for the previous day is deleted, DSA still holds corresponding file descriptor, and  a log file with the same name as of a deleted file is created during roll-over.

Environment

Release : 12.6.05, 14.0, 14.1

Component : CA Directory

Resolution

Question] Is this a problem on all platforms or only on Unix/Linux?
[Answer] The problem is observed on all supported platforms

[Question] Is the "Log Roll Over Created Incorrectly" problem completely resolved by upgrading to version 14.1 CR1
[Answer] Yes.
Also, another problem with logs roll over was fixed in 14.1 CR1: DE401288 - Log rollover for alarm or trace logs on DST date occurs one hour earlier.

We however recommend to upgrade to the newest available version (currently 14.1 SP1)