WinSyslog Event ID 11161: Configuration reload kept the existing log-rotation workers#

Answer#

Active log-rotation work did not finish within the reload timeout. The product keeps the current worker pool and skips replacing it so detached work retains a valid owner.

Event details#

  • Event ID: 11161

  • Severity: Warning

  • Component: Log rotation

  • Windows Event Log source: AdisconWinSyslog

  • Available since: 26.07

  • Message pattern: Configuration reload kept the existing asynchronous log rotation worker pool because active detached work did not drain before the bounded stop timeout.

Possible causes#

  • A rotation move, compression, or archive operation is slow or blocked.

  • The archive destination is unavailable or under heavy load.

  • The configured reload timeout is shorter than active rotation work requires.

Immediate checks#

  1. Inspect pending and active rotation work without terminating the service.

  2. Check archive availability, file locks, compression load, and free space.

  3. Let active work finish, then perform one controlled configuration reload.

Detailed procedures#

Verify the result#

Confirm that active rotations complete and a later reload applies the intended rotation-worker settings without Event ID 11161.

Evidence to collect#

  • The complete Windows Application Event Log entry and neighboring product events from the same time window.

  • The exact product version, affected service or action name, and event timestamp with time zone.

  • The affected configuration object and a bounded debug log covering one controlled reproduction.

  • Remove passwords, tokens, license data, private keys, message payloads, personal data, and customer-identifying names, addresses, hostnames, domains, and network addresses before sharing evidence.

Escalation#

If the event continues after the detailed procedures, collect the listed evidence and contact Adiscon Support.