How to Manually Update OAS in Linux

The instructions in this guide allow you to upgrade an existing OAS Linux installation.

It is assumed that OAS was originally installed using the How to Install OAS in Linux guide.

In this guide you will:

Download and extract the OAS Engine linux release compressed in a Zip archive.
Backup OAS Engine folders
Stop the OAS Engine service
Copy the new installation files
Start the OAS Engine service
Verify that your OAS Engine version has been updated

OAS does not provide technical support for Linux operating system issues and user management.

You can find a list of operating systems where the OAS Engine has been tested on the OAS System Requirements page.

Tips

You can also remotely update your OAS Engine running in Linux using the Configure OAS application in Windows or Linux.

1 - Download OAS

In this section you will download the OAS platform for Linux and extract it.

Download the Linux version of OAS for the platform that is relevant to you.
Fully functional trial versions of the software are available for Windows, Windows IoT Core, Linux, Raspberry Pi and Docker on our downloads page.
Change directory into your user's home directory. For example:
```
cd /home/ubuntu
```
Make sure any existing oas-linux folders have been removed or renamed.
Extract the oas-linux.zip file to the current directory. This will create a new folder called oas-linux.
```
unzip oas-linux.zip
```
Tips
To unzip a zip file you might need to install the unzip utilities. In a Debain based Linux system you can do this using the following command:
sudo apt-get install unzip

2 - Save and Backup Configuration

Ensure that you have saved all your configurations.

The OAS update will only replace application files without changing the configuration files.

For extra safety, you may wish to make a backup of the following directories in the /opt/oas/oas-engine directory:

ConfigFiles
Log
OPCUA
StoreAndForward

Warning

The OAS Engine service will be stopped during this update and then restarted. If you would like to cleanly stop all connector and database communications you can first stop the Runtime by selecting Stop Runtime in the Configure OAS application.

3 - Stop the OAS Engine service

Before you can replace the application's main files you will need to stop the OAS Engine. This section assumes that you installed OAS as a systemd service and that the service is called oas-engine.

Run the following command to stop the OAS engine and wait for the command to return. This may take some time.

sudo systemctl stop oas-engine

You can check that the service has stopped using the following command.

sudo systemctl status oas-engine

You should see something like this:

○ oas-engine.service - Open Automation Software (OAS) Engine
     Loaded: loaded (/etc/systemd/system/oas-engine.service; enabled; preset: enabled)
     Active: inactive (dead) since Fri 2025-11-21 21:01:27 AWST; 2s ago
   Duration: 15.016s
    Process: 10846 ExecStart=/opt/oas/oas-engine/OASEngine (code=exited, status=0/SUCCESS)
   Main PID: 10846 (code=exited, status=0/SUCCESS)

... previous logs ...
Nov 21 21:01:24 Pylon systemd[1]: Stopping oas-engine.service - Open Automation Software (OAS) Engine...
Nov 21 21:01:24 Pylon OASEngine[10846]: OAS Engine Shutting Down...
Nov 21 21:01:27 Pylon OASEngine[10846]: OAS Engine Stopped.
Nov 21 21:01:27 Pylon systemd[1]: oas-engine.service: Deactivated successfully.
Nov 21 21:01:27 Pylon systemd[1]: Stopped oas-engine.service - Open Automation Software (OAS) Engine.

4 - Copy and Replace OAS Application Files

Once you have downloaded and extracted the OAS Linux application files you will copy and replace the existing files and then clean up the downloaded files.

Copy the contents of the oas-linux folder to the /opt/oas/oas-engine folder where the OAS Engine binaries are located. This will overwrite any of the necessary files.
```
sudo cp -rT ~/oas-linux /opt/oas/oas-engine
```
Clean up the oas-linux folder that was downloaded.
```
rm -rf oas-linux
```

5 - Start the OAS Engine service

Now that you have copied all of the updated files, you can restart the oas-engine service.

sudo systemctl start oas-engine

After a few seconds, you can check the status of the service by using the following command.

sudo systemctl status oas-engine

You should see something like this:

● oas-engine.service - Open Automation Software (OAS) Engine
     Loaded: loaded (/etc/systemd/system/oas-engine.service; enabled; preset: enabled)
     Active: active (running) since Fri 2025-11-21 21:01:09 AWST; 7s ago
   Main PID: 10846 (OASEngine)
      Tasks: 67 (limit: 38410)
     Memory: 199.9M ()
     CGroup: /system.slice/oas-engine.service
             └─10846 /opt/oas/oas-engine/OASEngine

Nov 21 21:01:09 Pylon systemd[1]: Started oas-engine.service - Open Automation Software (OAS) Engine.
Nov 21 21:01:09 Pylon OASEngine[10846]: OAS Engine Starting...
Nov 21 21:01:09 Pylon OASEngine[10846]: OAS Engine Started.
Nov 21 21:01:10 Pylon OASEngine[10846]: OAS Engine Service listening on primary port 58727
Nov 21 21:01:10 Pylon OASEngine[10846]: OAS Engine Service listening on backup port 58737

6 - Verify OAS Engine service version

You can now open the Configure OAS application on a local or remote machine and connect to the OAS instance you just updated.

Once connected you should see the version updated in the toolbar or in the Configure > System Status screen.

Windows Example:

Windows OAS Engine
Processor Type: x64
Service Version: 21.0.0.49
Service Interface Version: 315

Linux Example:

Linux OAS Engine
Processor Type: x64
Service Version: 21.0.0.45
Service Interface Version: 315