search cancel

Data Center Security 6.5 MP1 HF6 manager.log grows out of control and is filling up disk with Titanium related messages.

book

Article ID: 163535

calendar_today

Updated On:

Products

Data Center Security Server Advanced

Issue/Introduction

Data Center Security 6.5 MP1 HF6 manager.log grows out of control and is filling up disk with Titanium related messages. The sis-server{X.EN_US}.log is showing many messages too but that log rolls-over in a controlled manner, the manager.log cannot be controlled by a configuration setting.

 

sis-server{X.EN_US}.log:

492489 2016-07-05 12:00:46.035 [INFO ] [Timer-14:42] Initializing Titanium ...
492490 2016-07-05 12:00:46.035 [INFO ] [Timer-14:42] Loaded Titanium library successfully.
492491 2016-07-05 12:00:46.135 [INFO ] [Timer-14:42] Initialized Titanium successfully.
492492 2016-07-05 12:00:46.255 [INFO ] [Timer-14:42] Initializing Titanium ...
492493 2016-07-05 12:00:46.256 [INFO ] [Timer-14:42] Loaded Titanium library successfully.
492494 2016-07-05 12:00:46.367 [INFO ] [Timer-14:42] Initialized Titanium successfully.

manager.log:

Commons Daemon procrun stdout initialized
titanium wrapper - inside titaniumload
inside initializecx library path C:\Program Files (x86)\Symantec\Critical System Protection\Server\cx_lib.dll
Successfully loaded cxLib
loaded cx library
tatinium module path :[C:\Program Files (x86)\Symantec\Critical System Protection\Server\Titanium.dll]C
Successfully loaded Titanium
loaded titanium
Starting Titanium configuration
Configured Titanium successfully
Failed when calling GetInfo, result = 1002

 

Environment

Symantec Data Center Security: Server Advanced 6.5 MP1 HF6 (6.5.0.612).

 

Cause

The server is trying to push LU package to the agent. The more the agents registered with the server the faster the logs will grow. The logs are more verbose than intended in this particular build of the manager.
 

Resolution

Upgrade to DCS 6.7 or above.

Note: The manager.log will be cleared on the (re)-start of the DCS manager service - to prevent the hard-disk from filling up, you could schedule the DCS manager service to restart periodically (and clear the log) until such time you are ready to upgrade to a newer DCS version that does not generate as many messages in the manager.log