IBM Support

IJ10390: WINCOLLECT AGENTS DO NOT RECEIVE A CONFIGURATION UPDATE DUE TO COMMUNICATION ERROR

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 WinCollect agents are sometimes not
    able to pull the configuration updates when using QRadar 7.3.1
    patch 3 and above due to TLS communication errors.  Messages
    similar to the following might be visible in /var/log/qradar.log
     when this issue is occurring:
    [ecs-ec-ingress.ecs-ec-ingress] [Thread-133]
    com.q1labs.frameworks.crypto.TLSSecurityManager: [ERROR]
    [NOT:0000003000][xx.xx.xx.xx/- -] [-/- -]Error creating TLS
    keystore.
    [ecs-ec-ingress.ecs-ec-ingress] [Thread-133]
    java.io.IOException: Keystore was tampered with, or password
    was incorrect
    [ecs-ec-ingress.ecs-ec-ingress] [Thread-133]    at
    com.ibm.crypto.provider.JavaKeyStore.engineLoad(Unknown Source)
    [ecs-ec-ingress.ecs-ec-ingress] [Thread-133]    at
    java.security.KeyStore.load(KeyStore.java:1456)
    [ecs-ec-ingress.ecs-ec-ingress] [Thread-133]    at
    java.security.KeyStore.load(KeyStore.java:1456)
    [ecs-ec-ingress.ecs-ec-ingress] [Thread-133]    at
    com.q1labs.frameworks.crypto.TLSSecurityManager.getKeyStore(TLSS
    ecurityManager.java:234)
    [ecs-ec-ingress.ecs-ec-ingress] [Thread-133]    at
    com.q1labs.frameworks.crypto.TLSSecurityManager.getKeyStore(TLSS
    ecurityManager.java:211)
    [hostcontext.hostcontext] [main]
    com.q1labs.configservices.core.ConfigServicesClient: [INFO]
    [NOT:0000006000][xx.xx.xx.xx/- -] [-/- -]Creating key store
    file /store/tmp/hostcontext/keystore7162955284875881629q1labs
    [hostcontext.hostcontext] [main]
    com.q1labs.configservices.core.ConfigServicesClient: [INFO]
    [NOT:0000006000][xx.xx.xx.xx/- -] [-/- -]Using existing key
    /store/tmp/hostcontext/keystore7162955284875881629q1labs
    [hostcontext.hostcontext] [ConfigChangeObserver Timer[1]]
    com.q1labs.core.shared.jsonrpc.RPC: [INFO]
    [NOT:0000006000][xx.xx.xx.xx/- -] [-/- -]Using existing key
    /store/tmp/hostcontext/keystore7162955284875881629q1labs
    [hostcontext.hostcontext] [ConfigChangeObserver Timer[1]]
    com.q1labs.core.shared.jsonrpc.RPC: [INFO]
    [NOT:0000006000][xx.xx.xx.xx/- -] [-/- -]Using existing key
    /store/tmp/hostcontext/keystore7162955284875881629q1labs
    [qvmprocessor.qvmprocessor] [main]
    com.q1labs.qvm.workflow.util.DecryptPropertyConfigurer: [INFO]
    Loading properties file from URL
    [file:/opt/qvm/console/conf/qvmkeystore.properties]
    [ecs-ep.ecs-ep] [ECS Runtime Thread]
    com.q1labs.core.shared.jsonrpc.RPC: [INFO]
    [NOT:0000006000][xx.xx.xx.xx/- -] [-/- -]Creating key store
    file /store/tmp/ecs-ep/keystore60152526785599147q1labs
    [ecs-ep.ecs-ep] [ECS Runtime Thread]
    com.q1labs.core.shared.jsonrpc.RPC: [INFO]
    [NOT:0000006000][xx.xx.xx.xx/- -] [-/- -]Using existing key
    /store/tmp/ecs-ep/keystore60152526785599147q1labs
    [vis] [main] com.q1labs.core.shared.jsonrpc.RPC: [INFO]
    [NOT:0000006000][xx.xx.xx.xx/- -] [-/- -]Creating key store
    file /store/tmp/vis/keystore3810065169654787488q1labs
    [vis] [main] com.q1labs.core.shared.jsonrpc.RPC: [INFO]
    [NOT:0000006000][xx.xx.xx.xx/- -] [-/- -]Using existing key
    /store/tmp/vis/keystore3810065169654787488q1labs
    [ecs-ec.ecs-ec] [ECS Runtime Thread]
    com.q1labs.core.shared.jsonrpc.RPC: [INFO]
    [NOT:0000006000][xx.xx.xx.xx/- -] [-/- -]Creating key store
    file /store/tmp/ecs-ec/keystore1506033862275691650q1labs
    [ecs-ec.ecs-ec] [ECS Runtime Thread]
    com.q1labs.core.shared.jsonrpc.RPC: [INFO]
    [NOT:0000006000][xx.xx.xx.xx/- -] [-/- -]Using existing key
    /store/tmp/ecs-ec/keystore1506033862275691650q1labs
    ...........
    ......
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    com.q1labs.sem.semsources.wincollectconfigserver.WinCollectConfi
    gHandler: [ERROR] [NOT:0000003000][xx.xx.xx.xx/- -] [-/-
    -]Agent with ip: xx.xxx.x.xxx  hit an SSL Negotiation issue,
    most likely tried to connect with an invalid PEM
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    com.q1labs.sem.semsources.wincollectconfigserver.WinCollectConfi
    gHandler: [ERROR] [NOT:0000003000][xx.xx.xx.xx/- -] [-/-
    -]Agent with ip: xx.xxx.x.xxx  hit an SSL Negotiation issue,
    most likely tried to connect with an invalid PEM
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    com.q1labs.sem.semsources.wincollectconfigserver.WinCollectConfi
    gHandler: [ERROR] [NOT:0000003000][xx.xx.xx.xx/- -] [-/-
    -]Agent with ip: xx.xxx.x.xxx  hit an SSL Negotiation issue,
    most likely tried to connect with an invalid PEM
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    javax.net.ssl.SSLHandshakeException: no cipher suites in common
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at com.ibm.jsse2.k.a(k.java:24)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at com.ibm.jsse2.at.a(at.java:882)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at com.ibm.jsse2.D.a(D.java:98)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at com.ibm.jsse2.D.a(D.java:522)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at com.ibm.jsse2.F.b(F.java:348)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at com.ibm.jsse2.F.a(F.java:703)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at com.ibm.jsse2.F.a(F.java:782)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at com.ibm.jsse2.D.r(D.java:176)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at com.ibm.jsse2.D.a(D.java:286)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at com.ibm.jsse2.at.a(at.java:197)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at com.ibm.jsse2.at.i(at.java:509)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at com.ibm.jsse2.at.a(at.java:259)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at com.ibm.jsse2.at.startHandshake(at.java:392)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at
    com.q1labs.sem.semsources.wincollectconfigserver.WinCollectConfi
    gHandler.run(WinCollectConfigHandler.java:103)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at
    com.q1labs.sem.semsources.wincollectconfigserver.WinCollectConfi
    gHandler.run(WinCollectConfigHandler.java:103)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at
    com.q1labs.sem.semsources.wincollectconfigserver.WinCollectConfi
    gHandler.run(WinCollectConfigHandler.java:103)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at
    com.q1labs.sem.semsources.wincollectconfigserver.WinCollectConfi
    gHandler.run(WinCollectConfigHandler.java:103)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
    utor.java:1160)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
    cutor.java:635)
    [ecs-ec-ingress.ecs-ec-ingress] [WinCollectConfigHandler_1]
    at java.lang.Thread.run(Thread.java:811)
    

Local fix

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

Problem summary

  • WINCOLLECT AGENTS DO NOT RECEIVE A CONFIGURATION UPDATE DUE TO
    COMMUNICATION ERROR
    

Problem conclusion

  • This issue was fixed in WinCollect version 7.2.8 Patch 1
    (7.2.8.P1).
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ10390

  • 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

    2018-12-07

  • Last modified date

    2018-12-07

  • 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:
07 December 2018