If you have installed Content Gateway on version 7.9-7.10 when offline (the gateway can’t reach the internet), it is possible that you do not have the swarmlifecycle script running correctly on your system. A message like this will be logged daily in cloudgateway_server.log if it is not set up correctly:2022-10-19 23:59:59,976 ERROR [pool-13-thread-3|] Lifecycle: Swarmlifecycle script failed with exit code 2
This script 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.
Download https://support.cloud.datacore.com/tools/datacore-swarmlifecycle-1.0.2-offline.tgz
Transfer this tarball to your gateway(s).
SSH to the gateway and unpack the tarball with
tar zxvf [filename]The code should now be in a
tmpsubdirectory from where you unpacked it.Run:
cd tmpto move to that directory.Run:
pip3 install datacore-swarmlifecycle-*tgz *whlto install the code.Run:
pip3 install /opt/caringo/cloudgateway/bin/datacore-swarmlifecycle.tar.gzto update to the latest version of the swarmlifecycle script provided by the most recent gateway installation.Verify the code is installed by typing:
ls /usr/local/bin/swarmlifecycle