Updates

If you are operating in a PlexTrac-hosted tenancy (either private or multi-tenant), updates occur automatically when available. The instructions here only apply to self-hosted customers.

NOTE: Customers with large amounts of data in their database may need to reference the additional procedure steps below the main update procedure.

Login to the server hosting your PlexTrac instance using an account that has been provisioned into the "docker" group. To display group memberships for the current user:

$ groups

If you do not see "docker" listed, run the following command:

$ sudo usermod -aG docker $USER

Update Procedure

1) Navigate to the folder containing the plextrac_run.sh script, normally /opt/plextrac.

2) Backup your existing database using the plextrac_backup_restore.sh script with the "backup" modifier :

$ sudo ./plextrac_backup_restore.sh backup

Note: This backup is purely cautionary in the unlikely event that any issues occur during your update.

3) Fetch and install the latest containers by running the plextrac_run.sh script:

$ ./plextrac_run.sh

4) Tail the logs for the database container with the following command:

$ docker logs -f $(docker ps -f name=plextrac_plextracdb -q)

Once you see the following, exit the tail (ctrl-Z).

/entrypoint.sh couchbase-server

5) Tail the logs for the API container with the following command:

$ docker logs -f $(docker ps -f name=plextrac_plextracapi -q)

If you see an "UnhandledPromiseRejectionWarning: Unhandled promise rejection" error, perform the "Additional Procedure Steps" below before resuming.

If you see a final message block that begins with the text below (finding count and time stamp may vary), proceed to the restore step.

Migrating 0 findings at Wed May 20 2020 22:00:33 GMT+0000 (Coordinated Universal Time)

6) Restore the database using the following command:

$ ./plextrac_backup_restore.sh restore

If you experience any issues after an update, please contact PlexTrac support to assist in troubleshooting.

Additional Procedure Steps

Customers with very large databases may experience an inability to login after an update. This may be rectified by restarting the API container using the following command:

docker-compose restart plextracapi