IO17509: idslogmgmt does not roll logs if they are 2 GB or larger.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When using idslogmgmt to manage the ITDS logs, if a log grows
    more than 2GB the log will not be archived and will continue to
    grow.
    
    Recreate Steps:
    
    1.) Create and configure instance, and load with sample data
    
    # idsadduser -u logtest -w logtest -l /home/logtest -g idsldap
    # idsicrt    -I logtest -e passwd4eseed -g passwd4esalt \
                 -t logtest -l /home/logtest
    # idscfgdb   -I logtest -a logtest -w logtest -t logtest \
                 -l /home/logtest
    # idsdnpw    -I logtest -u cn=root -p secret -n
    # idscfgsuf  -I logtest -s o=sample
    # idsldif2db -I logtest \
                 -i /opt/ibm/ldap/V6.2/examples/sample.ldif
    
    2.) Used the Web Administration tool to configure idslogmgmt
        Server Administration -> Logs -> Modify log settings ->
        Global log settings
    
    From the ibmslapd.conf:
    
    dn: cn=Log Management, cn=Configuration
    cn: Log Management
    objectclass: top
    objectclass: container
    
    dn: cn=Default, cn=Log Management, cn=Configuration
    cn: Default
    ibm-slapdlogmaxarchives: 3
    ibm-slapdlogsizethreshold: 5
    objectclass: ibm-slapdLogConfig
    objectclass: ibm-slapdConfigEntry
    objectclass: top
    objectclass: container
    
    dn: cn=ibmslapd, cn=Log Management, cn=Configuration
    cn: ibmslapd
    ibm-slapdLog: /home/logtest/idsslapd-logtest/logs/ibmslapd.log
    ibm-slapdlogmaxarchives: 10
    #ibm-slapdLogOptions is the log level & must be one of l/m/h ...
    ibm-slapdLogOptions: m
    ibm-slapdlogsizethreshold: 10
    objectclass: ibm-slapdLogConfig
    objectclass: ibm-slapdConfigEntry
    objectclass: top
    objectclass: container
    
    3.) Grow the audit.log to 2 GB in size and start idslogmgmt tool
        it will stop rolling the log
    

Local fix

  • Option 1: Manually copy off the large file
    
    Option 2: Increase the ibm-slapdLogMaxArchives and
              ibm-slapdLogSizeThreshold values to avoid the file
              growing to 2GB.
    
    NOTE: In case of large file, there could be exception observed
    if file contains some special characters. For example:
    
      sun.io.MalformedInputException.
      at sun.io.ByteToCharUTF8.convert(...)
      at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(...)
      at sun.nio.cs.StreamDecoder$ConverterSD.implRead(...)
      at sun.nio.cs.StreamDecoder.read(...)
      at java.io.InputStreamReader.read(...)
      at java.io.BufferedReader.fill(...)
      at java.io.BufferedReader.readLine(...)
      at java.io.BufferedReader.readLine(...)
    
    Here is the technote which explains it.
    http://www-01.ibm.com/support/docview.wss?uid=swg21567375
    
    Work around to this exception ::
    
    Export the LANG to en_US from the console from before the
    logmgmt tool is being executed.
    
      $ export LANG=en_US
      $ locale
      LANG=en_US
    

Problem summary

  • Java API parseInt() is not able to hold the value of file size
    which is more than its max limit i.e. 2^31-1 (2147483647).
    
    In logmgmt code we do parsing of the file length and make a
    decision on whether we need to Archive the logs or not. In this
    case when the audit log file grows more than the max_limit it
    stops rolling. It gives the error as NaN (Not A Number).
    
    Because of NaN error, the parsing fails and further execution
    stops rolling of logs.
    
    Solution:
    Code is fixed to remove the problematic API and use public long
    length(), which returns the length of the file properly.
    

Problem conclusion

  • The fix for this APAR will be contained in the following
    maintenance packages:
    | interim fix | 6.2.0.29-ISS-ITDS-IF0029 |
    

Temporary fix

Comments

APAR Information

  • APAR number

    IO17509

  • Reported component name

    IBM TIV DIR SER

  • Reported component ID

    5724J3960

  • Reported release

    620

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-06

  • Closed date

    2013-03-27

  • Last modified date

    2013-03-27

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IO18454 IO18455

Fix information

  • Fixed component name

    IBM TIV DIR SER

  • Fixed component ID

    5724J3960

Applicable component levels

  • R620 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Security Directory Server
General

Software version:

620

Reference #:

IO17509

Modified date:

2013-03-27

Translate my page

Machine Translation

Content navigation