Updating the tracker from the panel

A new tracker release is installed from the panel, in Settings → Updates («Настройки → Обновления»). The tab is visible to the owner and the admin, and only the installation owner can update. Before installing, the tracker saves a copy of the data and stops receiving clicks and postbacks while copying and installing, and on an error it brings back the previous version by itself.

Where the section is and who can update

The installation owner is the owner account set when the tracker was installed, see First-run wizard. Updating is not available in log in as user mode or with an API token. Other owners and admins see the message “Updates are available only to the installation owner” («Обновления доступны только владельцу установки»).

The top of the tab shows:

• Installed version («Установленная версия») and the “Client installation” («Клиентская установка») label;
• the “Last check” («Последняя проверка») line with a date, or “Check for a new release.” («Проверьте наличие нового выпуска.») if there have been no checks yet;
• the “Installation service” («Служба установки») line — the version of the service that performs updates on the server.

With the “Development environment” («Среда разработки») label, there is no Check for updates («Проверить обновления») button: updating from the panel does not apply in such an environment.

Checking for updates

1. Open Settings → Updates.
2. Click Check for updates.
3. Wait until “Done” («Готово») appears in the “Update check” («Проверка обновлений») block.

The tracker loads the release list and checks its signature and validity period. Traffic does not stop during the check.

The result is one of two:

• a “Version … available” («Доступна версия …») card with the release description, a “Release size” («Размер выпуска») line and an Install… («Установить…») button;
• the line “The current release is installed.” («Установлен текущий выпуск.») — there is nothing to update.

If the Install… button is inactive and the message “First update the installation service on the server: bash install.sh --update-controller. The running tracker is kept.” («Сначала обновите службу установки на сервере: bash install.sh --update-controller. Работающий трекер сохраняется.») is shown above the card, follow the steps on the Updating the installation service page.

Installation

1. Click Install… in the “Version … available” card.
2. In the “Update to …?” («Обновить до …?») window, check the box “I allow receiving clicks and postbacks to be paused while copying and updating. The duration depends on the amount of data.” («На время копирования и обновления разрешаю приостановить приём кликов и постбеков. Длительность зависит от объёма данных.»)
3. Click Create a copy and update («Создать копию и обновить»).
4. Follow the stages in the “Updating to …” («Обновление до …») block.

You can leave the tab open: the update progress stays visible while the panel restarts. The line “Connection to the service is temporarily unavailable. Waiting for it to recover; this is not the result of the operation yet.” («Связь со службой временно недоступна. Ожидаем восстановления; это ещё не результат операции.») is not an error; wait for the next stage.

An error at any of the first three stages cancels the installation before the pause: the running version and traffic are not affected. The stage changes to “Not completed” («Не завершено»), and the reason appears below it — see Messages and what to do.

Check

1. Wait for the “Done” stage.
2. Make sure the Installed version field shows the new version and the line “The current release is installed.” appears below it.
3. Expand Operation history («История операций»): the row with the version number shows the “Done” result.

For the state of the services after the update, see System status.

The copy made before the update

The copy is created while the services are stopped and is stored on this same server. It is needed for the automatic return and does not replace backups on a separate storage server. After the update, the copy stays on disk and is not deleted by itself. For how to check, pin and clean up such copies, see Local update copies.

Automatic rollback

If an error occurs after the pause has started, the tracker brings back the previous version by itself:

• an error while creating the copy — the services start again and traffic opens;
• an error during installation or the startup check — the previous installation files and the data from the copy are brought back, and the previous version starts.

In the operation block, the stage changes to “Returning the previous version” («Возвращаем предыдущую версию»), then to “Previous version restored” («Предыдущая версия восстановлена») with the text “The new version failed the check. The previous version and the data have been restored.” («Новая версия не прошла проверку. Предыдущая версия и данные восстановлены.») If the server rebooted during the update, the installation service performs the return after the server starts.

The rollback applies only to an installation that has not finished. After the “Done” stage, you cannot bring back the previous version from the panel, and the tracker does not accept an older release.

Lock

If the return to the previous version fails, the operation block shows the stage “Restore by the server administrator needed” («Нужно восстановление администратором сервера») and the text “Automatic restore did not complete. Traffic remains paused. A server administrator needs to check it.” («Автоматическое восстановление не завершилось. Трафик остаётся на паузе. Нужна проверка администратором сервера.») New checks and installations do not start until the lock is removed.

From here, the server administrator takes over. The update information is saved: once the cause is fixed, restart the installation service.

sudo systemctl restart micator-updates.service

In installations made before this release, the service is called tracker-updates.service, see names in such installations.

On startup, the service repeats the return to the previous version. After a successful return, traffic opens and the lock is removed. For how to view the service state, see Installation files, ports, services and logs.

Messages and what to do