Skip to main content Skip to footer

Update Node version

The procedure to update a Node depends on the installation environment, follow the steps in the appropriate section below.

Docker

Prerequisites

  • You have a node running a docker image
  • There is a new version of the node software available that you want to update to
  • You have remote access to the edge node you want to upgrade

1: Login to docker.crosser.io

  1. Login to your edge node using ssh and enter:
    [sudo] docker login https://docker.crosser.io
  2. When prompted, enter the username and password provided by Crosser.

2: Change node version

You have 2 options when updating to a new version:

  1. You are using the latest tag on your image specification in your docker-compose.yml file and know there is an update released. The image in this case is set to:
    image: docker.crosser.io/crosser/edgenode:latest
  2. You are using a specific version of the node software and want to update to another one
No specific version tag

To update to the latest released version:

  1. Open a terminal and enter:
    [sudo] docker-compose pull
  2. Then enter:
    [sudo] docker-compose up -d
Specific version tag set

To change from one version to another specific version:

  1. Open a terminal and enter:
    [sudo] docker-compose down
  2. Edit your docker-compose.yml to use the version you want, e.g.
    image: docker.crosser.io/crosser/edgenode:2.5.0-x64
  3. In the terminal, enter:
    [sudo] docker-compose up -d

Windows service

Prerequisites

  • You have a node running as a Windows service
  • You have a PowerShell running as Administrator

Note: If you are using the installer for version >= 2.5.0 scripting must be enabled in PowerShell for scripts downloaded from the Internet. You can check your current execution policy with:

Get-ExecutionPolicy

 

Make sure it’s one of RemoteSigned, UnRestricted or Bypass, if not use the following command to change it:

Set-ExecutionPolicy -Scope Process RemoteSigned

1: Uninstall the current version

If current version is <2.5.0:

  1. Go to the directory where you have the Crosser.EdgeNode.Service.Windows executable.

  2. Stop the edge node service using:

    Crosser.EdgeNode.Service.Windows stop
  3. Uninstall the old version with:

    Crosser.EdgeNode.Service.Windows uninstall

If current version is >= 2.5.0:

PowerShell version 6 and above

  1. Stop the edge node service with:

    Stop-Service -Name CrosserEdgeNode.Service
  2. Uninstall the previous version with:

    Remove-Service -Name Crosser-EdgeNode.Service

PowerShell version 5 and previous

  1. Stop the edge node service with:

    sc.exe stop Crosser.EdgeNode.Service
  2. Uninstall the previous version with:

    sc.exe delete Crosser.EdgeNode.Service

     

2: Download the installer for the new version

  1. Login to Crosser Control Center
  2. Download the Windows installer for the version you want to install from the Nodes->Register Nodes->Advanced Settings page and unzip it in an empty directory on your local host server.

3A: Install the Windows service for the new Node version (>=2.5.0)

  1. Open PowerShell in the directory where you stored the installer. Then run:
    .\InstallWindowsService.ps1
  2. When you are asked for the NodeId, copy the content of the 'data' folder from your previous version to the new 'data' folder created for this version.
  3. Press 'Enter' to use your existing credentials.
  4. At the prompt, type 'run' to start the new node version and any deployed Flows.

3B: Install the Windows service for the new Node version (<2.5.0)

  1. Copy the data folder from your old installation directory into your new installation directory
  2. Open PowerShell in the directory where you stored the installer. Then run:
    Crosser.EdgeNode.Service.Windows install

You will be asked to provide the nodeId and accessKey credentials, but since they have already been installed you can just answer with enter.

Start the edge node service with:

Crosser.EdgeNode.Service.Windows start

 

New version installed!

The new version should now be up and running and you should see the correct version number on the Nodes page in Crosser Control Center.