IBM Support

IJ03314: WINCOLLECT AGENT STOPS SENDING EVENTS TO COLLECTOR '...COULD NOT RESTART AGENT PROCESS AFTER UNEXPECTED EXIT...' IN LOGS

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 customers with a large number of
    remote log sources (in most instances having 3 channels per log
    source: Security, System, and Application) that are being
    polled by WinCollect and with a polling interval of 1-5 seconds
    have noticed issues with config updates and/or agent restarts
    showing an error similar to the following in the WinCollect
    System logs:
    2018-01-03 11:24:32,573 ERROR System.WinCollectSvc.Service :
    Could not restart agent process after unexpected exit. Assuming
    the configuration is corrupt; waiting for next configuration
    update.
    This behavior is caused by the WinCollect agent attempting to
    poll too many remote channels in a short period of time.  It
    cannot finish before it starts again, causing it to fail.
    

Local fix

  • 1) Update all Log Sources attached to the WinCollect agent as
    follows:
    Set the polling interval to 120000 ms (2 minutes).
    Select High Event Rate Server on the Event Rate Tuning Profile.
    2) Validate the update goes to the WinCollect agent (see that
    the agentconfig.xml file is updated).
    3) Stop the WinCollect agent.
    4) Delete or archive to another location the contents of the
    \WinCollect\log folder.
    5) Delete  or archive to another location WinCollect folder
    from c:\Programdata
    6) Start WinCollect agent.
    

Problem summary

  • It has been identified that customers with a large number of
    remote log sources (in most instances having 3 channels per log
    source: Security, System, and Application) that are being
    polled by WinCollect and with a polling interval of 1-5 seconds
    have noticed issues with config updates and/or agent restarts
    showing an error similar to the following in the WinCollect
    System logs:
    2018-01-03 11:24:32,573 ERROR System.WinCollectSvc.Service :
    Could not restart agent process after unexpected exit. Assuming
    the configuration is corrupt; waiting for next configuration
    update.
    This behavior is caused by the WinCollect agent attempting to
    poll too many remote channels in a short period of time.  It
    cannot finish before it starts again, causing it to fail.
    

Problem conclusion

  • This issue was fixed in WinCollect version 7.2.8
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ03314

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    720

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-15

  • Closed date

    2018-07-10

  • Last modified date

    2018-07-10

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

Document Information

Modified date:
10 July 2018