IBM Support

IJ17204: ECS-EP PROCESS FAILS TO START AFTER PATCHING TO QRADAR 7.3.2 WHEN CUSTOM SNMP TRAP EVENTS WERE CONFIGURED

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

  • It has been identified that the ecs-ep service can fail to
    start after patching to QRadar 7.3.2 when custom snmp trap
    events were configured.
    Messages similar to the following might be visible in
    /var/log/qradar.log when this issue is occurring:
    [ecs-ep.ecs-ep] [ECS Runtime Thread] Caused by:
    java.io.FileNotFoundException:
    /opt/ibm/si/services/ecs-ep/current/frameworks_conf/customCRE.sn
    mp.xml (No such file or directory)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    at
    java.io.FileInputStream.open(FileInputStream.java:212)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    at
    java.io.FileInputStream.<init>(FileInputStream.java:152)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    at
    java.io.FileInputStream.<init>(FileInputStream.java:104)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    at
    sun.net.www.protocol.file.FileURLConnection.connect(FileURLConne
    ction.java:103)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    at
    sun.net.www.protocol.file.FileURLConnection.getInputStream(FileU
    RLConnection.java:201)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    at
    org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unkno
    wn Source)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    at
    org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Un
    known Source)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    at
    org.apache.xerces.parsers.XML11Configuration.parse(Unknown
    Source)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    at
    org.apache.xerces.parsers.XML11Configuration.parse(Unknown
    Source)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    at
    org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    at
    org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
    Source)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    at
    org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
    Source)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    at
    com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmars
    hal0(UnmarshallerImpl.java:211)
    [ecs-ep.ecs-ep] [ECS Runtime Thread]    ... 17 more
    

Local fix

  • Contact Support for a possible workaround that might address
    this issue in some instances.
    

Problem summary

  • This issue was fixed in QRadar QRM QVM release of 7.3.3 Patch
    1 and 7.3.2 Patch 6.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 7.3.3 Patch
    1 and 7.3.2 Patch 6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ17204

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    732

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-24

  • Closed date

    2019-12-09

  • Last modified date

    2020-01-09

  • 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

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"732","Edition":""}]

Document Information

Modified date:
09 January 2020