IBM Support

IJ10406: ATTEMPTING TO RE-ADD A MANAGED HOST (MH) THAT ORIGINALLY FAILED TO ADD DUE TO TIMEOUT CAN LEAVE THE MH IN A STUCK STATE

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 when a Managed Host fails to add
    due to timeout, re-attempting to add it again can fail and
    cause the Managed Host to be in a stuck state, unable to
    successfully add to the deployment.
    Messages similar to the following might be visible in
    /var/log/qradar.log when this issue is occurring:
    [tomcat.tomcat] [127.0.0.1]
    com.q1labs.configservices.capabilities.CapabilitiesHandler:
    [ERROR] [NOT:0000003000][10.148.1.14/- -] [-/- -]Failed to
    inject deployment model for appliance type 1599
    [tomcat.tomcat] [127.0.0.1]
    com.q1labs.configservices.common.ConfigServicesException:
    Failed to inject deployment [default]. Managed host 10.1.227.79
    already exists in deployment model[default].
    [tomcat.tomcat] [127.0.0.1]    at
    com.q1labs.configservices.schemaext.DeploymentExtension.injectDe
    ploymentModel(DeploymentExtension.java:1320)
    [tomcat.tomcat] [127.0.0.1]    at
    com.q1labs.configservices.deployment.DeploymentHandler.injectDep
    loymentModel(DeploymentHandler.java:884)
    [tomcat.tomcat] [127.0.0.1]    at
    com.q1labs.configservices.capabilities.CapabilitiesHandler.injec
    tApplianceDeployment(CapabilitiesHandler.java:1224)
    [tomcat.tomcat] [127.0.0.1]    at
    com.q1labs.configservices.capabilities.CapabilitiesHandler.injec
    tApplicance(CapabilitiesHandler.java:362)
    [tomcat.tomcat] [127.0.0.1]    at
    com.q1labs.configservices.capabilities.CapabilitiesHandler.updat
    eHostCapabilities(CapabilitiesHandler.java:644)
    [tomcat.tomcat] [127.0.0.1]    at
    com.q1labs.configservices.core.ConfigurationServices.reportHostC
    apabilities(ConfigurationServices.java:1230)
    [tomcat.tomcat] [127.0.0.1]    at
    com.ibm.si.configservices.api.R1_2017.configservices.model.task.
    UpdateHostCapabilitiesTask.run(UpdateHostCapabilitiesTask.java:6
    5)
    [tomcat.tomcat] [127.0.0.1]
    com.q1labs.configservices.capabilities.CapabilitiesHandler:
    [ERROR] [NOT:0000003000][10.148.1.14/- -] [-/- -]Report Host
    Presence encountered an Unknown Exception.
    [tomcat.tomcat] [127.0.0.1]
    com.q1labs.configservices.common.ConfigServicesException:
    Failed to inject deployment model for appliance type 1599
    [tomcat.tomcat] [127.0.0.1]    at
    com.q1labs.configservices.capabilities.CapabilitiesHandler.injec
    tApplicance(CapabilitiesHandler.java:368)
    [tomcat.tomcat] [127.0.0.1]    at
    com.q1labs.configservices.capabilities.CapabilitiesHandler.updat
    eHostCapabilities(CapabilitiesHandler.java:644)
    [tomcat.tomcat] [127.0.0.1]    at
    com.q1labs.configservices.core.ConfigurationServices.reportHostC
    apabilities(ConfigurationServices.java:1230)
    [tomcat.tomcat] [127.0.0.1]    at
    com.ibm.si.configservices.api.R1_2017.configservices.model.task.
    UpdateHostCapabilitiesTask.run(UpdateHostCapabilitiesTask.java:6
    5)
    [tomcat.tomcat] [127.0.0.1]
    com.ibm.si.configservices.api.R1_2017.configservices.model.task.
    UpdateHostCapabilitiesTask: [ERROR]
    [NOT:0000003000][10.148.1.14/- -] [-/- -]Processing: error
    while reporting a host capabilities from 10.1.227.79 host
    [tomcat.tomcat] [127.0.0.1]
    com.q1labs.configservices.common.ConfigServicesException:
    Unknown error.
    [tomcat.tomcat] [127.0.0.1]    at
    com.q1labs.configservices.capabilities.CapabilitiesHandler.updat
    eHostCapabilities(CapabilitiesHandler.java:720)
    [tomcat.tomcat] [127.0.0.1]    at
    com.q1labs.configservices.core.ConfigurationServices.reportHostC
    apabilities(ConfigurationServices.java:1230)
    [tomcat.tomcat] [127.0.0.1]    at
    com.ibm.si.configservices.api.R1_2017.configservices.model.task.
    UpdateHostCapabilitiesTask.run(UpdateHostCapabilitiesTask.java:6
    5)
    [tomcat.tomcat] [127.0.0.1] Caused by:
    [tomcat.tomcat] [127.0.0.1]
    com.q1labs.configservices.common.ConfigServicesException:
    Failed to inject deployment model for appliance type 1599
    [tomcat.tomcat] [127.0.0.1]    at
    com.q1labs.configservices.capabilities.CapabilitiesHandler.injec
    tApplicance(CapabilitiesHandler.java:368)
    [tomcat.tomcat] [127.0.0.1]    at
    com.q1labs.configservices.capabilities.CapabilitiesHandler.updat
    eHostCapabilities(CapabilitiesHandler.java:644)
    [tomcat.tomcat] [127.0.0.1]    ... 2 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 732 FixPack 5
    and 733.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 732 FixPack 5
    and 733.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ10406

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    731

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-10

  • Closed date

    2019-11-05

  • Last modified date

    2019-11-05

  • 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":"731","Edition":""}]

Document Information

Modified date:
05 November 2019