Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Next »

If you have installed Content Gateway when offline (the gateway can’t reach the internet), it is possible that you do not have the swarmlifecycle code running correctly on your system. This code is run at midnight UTC to clean up streams that the streams' lifecycle policy may have deleted but are still showing up in your Content UI/ other S3 application. The health processor may not have visited these streams since their deletion in order to mark them as deleted. This script will mark them as deleted so they are not visible to avoid confusion.

To determine if this code was successfully installed, you can easily check for swarmlifecycle in /usr/local/bin. If it is present, then you do not need to follow these instructions as the code was installed when the gateway was installed. If you do need to install this code, please follow the instructions below.

\uD83D\uDCD8 Instructions

Installing the swarmlifecycle code offline.

  1. Download https://support.cloud.datacore.com/tools/datacore-swarmlifecycle-1.0.2-offline.tgz

  2. Transfer this tarball to your gateway(s).

  3. SSH to the gateway and unpack the tarball with tar zxvf [filename]

  4. The code should now be in a tmp subdirectory from where you unpacked it.

  5. Run: cd tmp to move to that directory.

  6. Run: pip3 install datacore-swarmlifecycle-*tgz *whl to install the code.

  7. Verify the code is installed by typing: ls /usr/local/bin/swarmlifecycle

See also: https://caringo.atlassian.net/wiki/spaces/public/pages/2931753040/Enforcement#Policy-Action

  • No labels