Assistance with Loggernaut Update 2.3.0

Unfortunately, an error may occur with the Loggernaut update 2.3.0.

You can temporarily fix this manually as follows:

1. copy the script to your SIEM management server

#!/bin/bash

api=''

for i in "$@"
do
case $i in
api=*)
    api="${i##*=}"
    shift
esac
done

if [[ $EUID -ne 0 ]]; then
    print "This script must be run as root" 1>&2
    exit 1
fi

get_path="$api/v1/_/loggernaut"
file_name="ngs-loggernaut-amd64"
download_path="$get_path/latest/$file_name"
opt_path="/opt/enginsight/loggernaut"
tmp_path="/tmp/loggernaut-m47-$RANDOM"

mkdir -p "$tmp_path"
curl -# -o "$tmp_path/$file_name" "$download_path"

if [ -x "$(command -v sha512sum)" ]; then
    hash=$(curl --silent "$download_path.sha512")
    if ! echo "$hash  $tmp_path/$file_name" | sha512sum -cw > /dev/null; then
      echo "Invalid SHA512 hash!" >&2
      exit 1
    else
      echo "> Target hash: ${hash:0:16}..."
      echo "> Integrity Test passed! (SHA512)"
    fi
  fi

mv "$opt_path/ngs-loggernaut" "$opt_path/ngs-loggernaut-old"
cp "$tmp_path/$file_name" "$opt_path/ngs-loggernaut"

chmod +x "$opt_path/ngs-loggernaut"

systemctl restart ngs-loggernaut

2. make the script executable:

sudo chmod +x update.sh

3. execute the script as follows:

sudo ./update.sh api=<IhreAPiDomain>