IBM Support

IJ29518: SMBTAILPROTOCOL LOG SOURCES CAN FUNCTION NORMALLY BUT DISPLAY IN 'ERROR' STATE WHEN A JNQEXCEPTION OCCURS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Log Sources using the SMBTail Protocol display in an error
    state when a jNQ exception is thrown, but the Log Source
    continues to function as expected.
    Messages similar to the following might be visible in
    /var/log/qradar.log when this issue occurs:
    [ecs-ec-ingress.ecs-ec-ingress] [Folder Monitor
    [127.0.0.1][smb://127.0.0.1/dhcplog/]]
    com.q1labs.semsources.sources.smbtail.io.jnq.JNQException:
    Unable to create/open - j50.log status = -1073741757
    (0xc0000043) (0xC0000043)
    [ecs-ec-ingress.ecs-ec-ingress] [Folder Monitor
    [127.0.0.1][smb://127.0.0.1/dhcplog/]]
    com.q1labs.semsources.sources.windowsdhcp.WindowsDHCPTailProvide
    r: [ERROR] [NOT:0000003000][10.42.165.13/- -] [-/-
    -]TailingException: Unable to create/open - j50.log status =
    -1073741757 (0xc0000043) (0xC0000043)
    

Local fix

  • No workaround available.
    APARs identified with no workaround may require a software
    delivery to resolve. This reported issue will be considered for
    a future release and administrators can subscribe to the APAR
    to get updates by clicking on the Subscribe button on the right
    side of this page or ask a question about this APAR in our
    Support Forums.
    https://ibm.biz/qradarforums
    

Problem summary

  • This fix is dependent upon the QRadar version and is available
    in the following RPMs on IBM Fix Central:
    
    Version 7.3.x:
    PROTOCOL-SmbTailProtocol-7.3-20210329122540.noarch.rpm
    PROTOCOL-WindowsDHCPProtocol-7.3-20210315133009.noarch.rpm
    PROTOCOL-WindowsExchangeProtocol-7.3-20210315133009.noarch.rpm
    PROTOCOL-WindowsIISProtocol-7.3-20210315133009.noarch.rpm
    PROTOCOL-OracleDatabaseListener-7.3-20210315133009.noarch.rpm
    PROTOCOL-WindowsEventRPC-7.3-20210315133009.noarch.rpm
    
    Version 7.4.x:
    PROTOCOL-SmbTailProtocol-7.4-20210329122529.noarch.rpm
    

Problem conclusion

  • This fix is dependent upon the QRadar version and is available
    in the following RPMs on IBM Fix Central:
    
    Version 7.3.x:
    PROTOCOL-SmbTailProtocol-7.3-20210329122540.noarch.rpm
    PROTOCOL-WindowsDHCPProtocol-7.3-20210315133009.noarch.rpm
    PROTOCOL-WindowsExchangeProtocol-7.3-20210315133009.noarch.rpm
    PROTOCOL-WindowsIISProtocol-7.3-20210315133009.noarch.rpm
    PROTOCOL-OracleDatabaseListener-7.3-20210315133009.noarch.rpm
    PROTOCOL-WindowsEventRPC-7.3-20210315133009.noarch.rpm
    
    Version 7.4.x:
    PROTOCOL-SmbTailProtocol-7.4-20210329122529.noarch.rpm
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ29518

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    730

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-12-01

  • Closed date

    2021-04-28

  • Last modified date

    2021-04-28

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

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

Fix information

  • Fixed component name

    QRADAR SOFTWARE

  • Fixed component ID

    5725QRDSW

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSBQAC","label":"IBM QRadar SIEM"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"730"}]

Document Information

Modified date:
29 April 2021