Updating Smart Beat Manager and Smart Beat
Smart Beat Manager must be updated first. After that, you can proceed to update Smart Beat agents. Smart Beat Manager maintains backward compatibility with previous agent versions.
Conventions:
SM_INSTALLER- the directory where theSmart Monitorinstallation package is unpackedSBM_HOME- the installation directory ofSmart Beat ManagerSB_HOME- the installation directory ofSmart Beat
Updating Smart Beat Manager
Updating Smart Beat Manager and its configurations is only available manually.
- Back up the certificates and configuration of the current installation, for example, to the
/app/backupdirectory:
mkdir -p /app/backup/$(date +%Y%m%d)/sbm/
cp -r $SBM_HOME/etc/ssl /app/backup/$(date +%Y%m%d)/sbm/
cp $SBM_HOME/etc/*.yml /app/backup/$(date +%Y%m%d)/sbm/
- Stop the service and remove the existing version of
Smart Beat Manager:
systemctl stop smartBeatManager
$SBM_HOME/smartBeatManager remove
- Delete the old files:
rm -f $SBM_HOME/smartBeatManager*
rm -f $SBM_HOME/etc/smartBeatManager.yml
rm -f $SBM_HOME/etc/config.yml
- After extracting the
Smart Monitorinstaller, copy the installation file and make it executable:
cp $SM_INSTALLER/utils/smartBeatManager/smartBeatManager-* $SBM_HOME/smartBeatManager
chmod +x $SBM_HOME/smartBeatManager
- Install
Smart Beat Manager:
$SBM_HOME/smartBeatManager install
Starting from version 4.2.0, the configuration file name has changed from smartBeatManager.yml to config.yml. If config.yml exists, it will be used. If it doesn't exist, smartBeatManager.yml might be used. The configuration syntax has changed; it is recommended to transfer the settings to the new configuration file.
Starting from version 5.1.0, installing Smart Beat Manager does not start the service; it only creates a subset of directories and files if they are missing. This allows for configuring the service before its first run.
- Compare the old configuration file
smartBeatManager.ymland the newconfig.yml:
diff /app/backup/$(date +%Y%m%d)/sbm/smartBeatManager.yml $SBM_HOME/etc/config.yml
- Transfer the necessary settings from the old file to the new one and restart the service:
systemctl start smartBeatManager
Updating Smart Beat for Linux
- Back up the certificates and configuration of the current installation, for example, to the
/app/backupdirectory:
mkdir -p /app/backup/$(date +%Y%m%d)/sb/
cp -r $SB_HOME/cert /app/backup/$(date +%Y%m%d)/sb/
cp $SB_HOME/config/*.yaml /app/backup/$(date +%Y%m%d)/sb/
- Stop the service and remove the existing version of
Smart Beat:
systemctl stop smartBeat
$SB_HOME/smartBeat remove
- Delete the old files:
rm -f $SB_HOME/smartBeat*
rm -f $SB_HOME/config/config.yaml
- After extracting the
Smart Monitorinstaller, copy the installation file and make it executable:
cp $SM_INSTALLER/utils/smartBeat/smartBeat-linux-x64-* $SB_HOME/smartBeat
chmod +x $SB_HOME/smartBeat
- Install
Smart Beat:
$SB_HOME/smartBeat install
Starting from version 5.1.0, installing Smart Beat does not start the service; it only creates a subset of directories and files if they are missing. This allows you to configure the service before its first run.
- Compare the old configuration file
config.yamland the new one:
diff /app/backup/$(date +%Y%m%d)/sb/config.yaml $SB_HOME/config/config.yaml
- Transfer the necessary settings from the old file to the new one and restart the service:
systemctl restart smartBeat
Updating Smart Beat for Windows
To update the agent on Windows, you must first uninstall it. However, uninstalling will affect the entire installation directory, so back up all necessary files beforehand. When installing from the command line or PowerShell, the installation command with the list of parameters can be left unchanged.
-
Back up the certificates (usually
C:\Program Files\smartBeat\cert\) and the configuration of the current installation (usuallyC:\Program Files\smartBeat\config\config.yaml) -
Uninstall the old agent through "Add/Remove Programs" in Windows
Control Panel -
Install
Smart Beat. Pay attention to the SSL/TLS settings window; you can specify the certificates copied before the update. If you check theGenerate self-signed certificatebox, new self-signed certificates will be generated (if none exist)