IBM Support

How to enable verbose logging for drivers.log

Question & Answer


Question

In ITNCM, how do I enable verbose logging for drivers.log

Cause

You need to investigate UOW processing by ITNCM and drivers.log will only log normal interactions between device and driver at DEBUG level or lower

Answer

The logging level generated in driver.log is controlled by /opt/IBM/tivoli/netcool/ncm/config/properties/driverlog.properties at the following point in bold:

    # ITNCM Common LOG4J Properties
    #
    log4j.rootLogger=ERROR, driverlog


To enable low-level ITNCM driver logging, edit the above file and ensure that it reads:

    log4j.rootLogger=FINEST, driverlog

Then restart ITNCM for the above change to take effect. drivers.log will now contain additional logging such as the commands sent to the device and the responses from the device, e.g.

    THREAD: OperationRunner-000-worker1,[2013/09/17,15:13:26.794],FINEST,MSG:IfThen, found IF 'name:, ifStartIndex = 0 tempIfStartIndex = 0,tmpIndex: 523
    buffer:

    C
    ===================================================================
    This access is restricted and monitored. Unauthorized login
    will lead criminal prosecution.
    ===================================================================

    Username:

    THREAD: OperationRunner-000-worker1,[2013/09/17,15:13:26.795],FINEST,MSG:sending: [icosuser]

MaxBackupIndex and MaxFileSize

You may also want to consider changing the following parameters in that file so that each drivers.log may contain more data before being rolled over:

    log4j.appender.driverlog.MaxBackupIndex=10
    log4j.appender.driverlog.MaxFileSize=10MB

Above settings would mean ten drivers.log files will be kept in rotation, each file containing no more than 10Mb of logging:

    -rw-r--r--  1 icosuser icosgrp 10485975 Sep  4 13:40 drivers.log.10
    -rw-r--r--  1 icosuser icosgrp 10485775 Sep  4 13:41 drivers.log.9
    -rw-r--r--  1 icosuser icosgrp 10485854 Sep  4 15:39 drivers.log.8
    -rw-r--r--  1 icosuser icosgrp 10485785 Sep  4 15:39 drivers.log.7
    -rw-r--r--  1 icosuser icosgrp 10485781 Sep 17 09:42 drivers.log.6
    -rw-r--r--  1 icosuser icosgrp 10485777 Sep 17 09:42 drivers.log.5
    -rw-r--r--  1 icosuser icosgrp 10485775 Sep 17 10:08 drivers.log.4
    -rw-r--r--  1 icosuser icosgrp 10485854 Sep 17 15:14 drivers.log.3
    -rw-r--r--  1 icosuser icosgrp 10485821 Sep 18 08:16 drivers.log.2
    -rw-r--r--  1 icosuser icosgrp 10485795 Sep 18 08:16 drivers.log.1
    -rw-r--r--  1 icosuser icosgrp   844921 Sep 18 08:16 drivers.log

But when drivers.log is set to FINEST, 10Mb of logging may be generated by a single file alone, making data gathering cumbersome as it is much more likely the logging from a single UOW spans multiple drivers.log files.

For FINEST logging a more sensible configuration -- given that there is enough disk space available -- may be:

    log4j.appender.driverlog.MaxBackupIndex=5
    log4j.appender.driverlog.MaxFileSize=64MB

If you wish to keep more logs, subsequently increase MaxBackupIndex as increasing MaxFileSize will result in large log files that are difficult to work with in normal PC client Text Editors.

[{"Product":{"code":"SS7UH9","label":"Tivoli Netcool Configuration Manager"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Tivoli Netcool Configuration Manager","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF002","label":"AIX"}],"Version":"6.3.0;6.4;6.4.1;6.4.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21650723