During an upgrade, the upgrade file is sent to the engine server. A cron job running on the engine server checks if that file exists. The most common upgrade error is that the job is not running so the new installer does not run.
SSH to the machine.
Check the d1 service status on the engine server. It is possible that it stopped or doesn't exist.
sudo systemctl status d1
Access the installer log on the engine server and review the error.
sudo vi /tmp/demisto_install.log
Rerun the installer on the engine server using one of the following options. You can open a second window and run
watch df -h. If the problem seems to be disk space, you should resolve the disk space issue and then rerun the installer.
Download the installer from the user interface and copy it to the engine server.
sudo chmod +x installer.sh
sudo ./installer.sh -- -y
If the file exists, run the following on the engine server:
sudo chmod +x /usr/local/demisto/d1_upgrade.sh
d1_upgrade.shdoes not exist, check if
/usr/local/demisto/archived_d1_upgrade.shexists and that it was created at the time of the attempted upgrade.
If the file exists and was created at the time of the attempted upgrade, run the following on the engine server:
sudo chmod +x /usr/local/demisto/d1_upgrade_archive.sh