Tools

Kiwi Syslog Server NG reports file-locking errors during log archiving

First published date

10/1/2026 3:54 PM

Last published date

10/1/2026 3:54 PM

Overview

Kiwi Syslog Server NG may fail to move, delete, or compress log files during an Archive task when another process still has the files open.

Product section

Kiwi Syslog Server

Cause

The Archive task is processing files that are still being written by the Log to File action or locked by another process, such as antivirus, backup, indexing, or file-monitoring software. Invalid paths, filenames, folders, or unsupported macros can also cause the related Log to File errors.

Resolution

  1. Review the Log to File action and confirm that the full file path and filename are valid.

  2. Confirm that the destination folder exists and that the Kiwi Syslog service account has permission to access it.

  3. If the filename uses the legacy %DateISO macro, replace it with the Kiwi Syslog Server NG $Message.DateISO macro.

  4. Open Setup > Schedules and configure the Archive task to process only older files. For example, set a file-age condition of at least one day so the task does not process active log files.

  5. Check whether antivirus, backup, indexing, monitoring software, or another script is accessing the configured log folder during the archive window. Exclude the folder from scanning only according to your organization’s security policy.

  6. If ZIP archiving is enabled, temporarily disable it and test whether the files can be moved successfully without compression.

Additional Notes

Archive tasks can move or copy files and optionally compress them after processing. Configure the task to process completed, older log files rather than the file currently being written by the Log to File action.