Pular para o conteúdo principal

Updating Signer on Linux

This page shows how to update an on-premises instance of Signer installed on Linux following the Ubuntu Server installation.

info

These instructions assume you are logged in as root. If you are not, run sudo su - before continuing.

Before you update​

  1. Check the installed version:

    curl http://localhost:5001/api/system/info

    The productVersion field of the response shows the version.

  2. Read the changelog of every version between yours and the new one. Look for the versions marked as changing the database model.

  3. If you are moving from 2.x to 3.x, also follow Updating to 3.x. Version 3.0.0 requires the ASP.NET Core Runtime 10.0.

  4. Update the staging environment first. Test sending and signing documents before you update production.

  5. Pick a low-usage time. On the first startup, the application updates the database when the new version changes the model.

warning

If you have more than one server, only one of them must update the database. Stop the other servers, update one server and wait for it to start. Then update the others. Alternatively, on every server but one, set General:AutoUpdateDatabase and General:ProcessBackgroundJobs to false.

Backup​

  1. Back up the database in SQL Server.

  2. Copy the binaries folder and the configuration folder:

    tar czf /root/signer-backup-$(date +%Y%m%d).tar.gz /usr/share/lacuna-signer /etc/lacuna-signer

Update​

  1. Set the new version. See the latest version in the changelog:

    VERSION=3.0.0

  2. Download the package, stop the service, replace the binaries and start the service:

    curl -O https://cdn.lacunasoftware.com/signer/signer-$VERSION.tar.gz
    systemctl stop lacuna-signer
    rm -fR /usr/share/lacuna-signer/*
    tar xzf signer-$VERSION.tar.gz -C /usr/share/lacuna-signer
    chmod -R a=,u+rwX,go+rX /usr/share/lacuna-signer
    systemctl start lacuna-signer

The configuration lives in /etc/lacuna-signer and does not change with the update.

Check the update​

  1. Check that the service is active:

    systemctl status lacuna-signer

  2. Check that productVersion shows the new version:

    curl http://localhost:5001/api/system/info

  3. Follow the log during the first startup. The database update can take a few minutes:

    journalctl -u lacuna-signer -f

If the service does not start and the log shows PKI SDK License was not loaded successfully, the application did not load the PKI SDK license (missing, invalid or expired). Ask Lacuna for an updated license and set it in PkiSuite:SdkLicense.

If something goes wrong​

If the new version has a problem, contact Lacuna support first. If you must go back to the previous version, follow the version rollback. To restore only the binaries, extract the /usr/share/lacuna-signer folder from the backup.

See also​

View as Markdown