Return
-
Title
How to cleanup archive share. Archiving is failing. -
Description
This article will help you cleanup the archive share.
-
Cause
Archiving fails because there isn't enough free space on the archive share. -
Resolution
Resolution:
Increase space on the archive share.
Workaround:
Before start to use the script, consider the following:
- The archive cleanup script is not supported.
- It is developed to help customers to clean up their archive share when they can not extend it.
- Do not use it on a daily basis, nor create a scheduled job.
- Make sure that no archiving is in progress.
- Use at your own risk!
- Copy the attached archive-cleanup-0.4.3.tar.gz to the core shell's root directory (/mnt/firmware/root) via SCP.
- Log in to the core shell and extract the compressed file with the following command.
tar xzf archive-cleanup-0.4.3.tar.gz
- Create a backup of archive database
cp /opt/ssb/var/sql/archive.db /root
- Enter the script's directory, execute it and follow the instructions.
cd archive-cleanup
./cleanup.sh
- Select logspace to cleanup. You can chose multiple logspaces.
- Enter the desired retention time on archive share
- Select evaluation method
- Check the result
- Check if the archive database has not become corrupt
sqlite3 /opt/ssb/var/sql/archive.db "pragma integrity_check;"
The output should be only an "ok". If the database has become corrupt please see this article.
https://support.oneidentity.com/syslog-ng-store-box/kb/310376/
-
Attachments
-
Additional Information
Feature request 383140 has been raised with our Product team for consideration of inclusion within a future release of syslog-ng Store Box.