Local Cluster - Update

Update each Windows host in an existing Flowgear local Cluster by running the latest installer. The installer performs an in-place upgrade: you do not need to uninstall the current version first.

Prerequisites

You have administrator privileges on each local Cluster host.
The local Cluster is already configured and appears in Local Clusters in the Flowgear Console.
You have downloaded the latest installer from Local Clusters in the Flowgear Console.
You have planned for the short service interruption described below.

Important: The upgrade retains the existing local Cluster configuration and certificate. Install the new version in the same location. You do not need to run the setup tool again unless the configuration is missing or must be changed.

During the upgrade, the installer stops the FlowgearLocalRuntime Windows service and replaces the program files. The service is registered to start automatically, but the installer does not start it, so confirm that it is running after the upgrade and start it if needed. Workflows cannot run on that host while the service is stopped.

If the local Cluster has one host, plan for a short downtime. If it has multiple hosts, update one host at a time and confirm that it is online before updating the next host. Ensure that the remaining hosts have enough capacity for the Workflows that run during the update.

Step 1: Record the current state

Open Local Clusters in the Flowgear Console.
Open the local Cluster that you want to update.
Record the version and online status of each host.

Step 2: Run the latest installer

Run the latest local Cluster installer as an administrator.
Allow the installer to make changes when Windows User Account Control prompts you.
Use the same installation location as the current version.
Complete the installation wizard.

The installer upgrades the existing installation in place. It stops the FlowgearLocalRuntime service and updates the files. The existing configuration and certificate remain available to the new version, so you do not need to run the setup tool again unless the configuration is missing or you need to change it.

Step 3: Start the service

The installer does not start the service after the upgrade.

Open the Windows Services app.
Find Flowgear Local Runtime.
Confirm that its startup type is Automatic.
If the service is not running, click Start.

Step 4: Verify the update

Return to Local Clusters in the Flowgear Console, and then refresh the local Cluster.
Confirm that the updated host shows as online.
Confirm that the host shows the new version.
If the Cluster has multiple hosts, confirm that all hosts show the intended version after you update them.
Run a suitable Workflow assigned to the local Cluster and confirm that it completes successfully.

If the host remains offline, check that the Flowgear Local Runtime service is running. Review Windows Event Viewer and the local Cluster log files for errors.

Troubleshooting

The installer stops responding at "Validating install"

If progress stops at Validating install for several minutes and nothing else happens, the FlowgearLocalRuntime service is still running and holding its program files open. This prevents the installer from replacing those files, so it waits.

This occurs when Windows cannot close the running service on your behalf during installation. The Flowgear Local Runtime service runs in the background with no window, and on some machines the Windows Restart Manager (the component that would normally stop the service for the installer) is turned off by a group policy. When that happens, the installer has no way to close the service and appears to hang.

To let a stuck upgrade continue:

Leave the installer window open.
Open the Windows Services app.
Find Flowgear Local Runtime, and then click Stop.
Wait for the service to stop. The installer then continues automatically.

To avoid the problem, stop the service before you start:

Open the Windows Services app.
Find Flowgear Local Runtime, and then click Stop.
Run the installer.

Note for administrators: This is most likely on hardened machines where the DisableAutomaticApplicationShutdown policy is enabled under HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer. Setting that value to 0 re-enables the Windows Restart Manager, which allows the installer to stop and restart the service automatically without manual intervention.