This chapter explains how to install anynode offline on Debian, Ubuntu, and Red Hat Enterprise Linux (RHEL) systems while ensuring that all required dependencies are installed correctly.

Linux Offline

Installing anynode Offline on Debian / Ubuntu / RHEL

In environments with restricted or completely isolated networks, anynode can also be installed without internet access. For this scenario, the required anynode installation packages and all system dependencies must be downloaded beforehand on a system with internet connectivity and then transferred to the target server. This section describes how to prepare and perform an offline installation of anynode on supported Linux distributions such as Debian, Ubuntu, and Red Hat Enterprise Linux.

Overview of the Offline Installation Process

An offline installation typically consists of the following steps:

  1. Download the required anynode installation packages

  2. Download all required dependency packages on a staging system

  3. Transfer the packages to the offline server

  4. Install the packages locally

  5. Verify that all anynode services are running

For reliable dependency resolution it is recommended to use a staging system with internet access running the same operating system version as the target system.

anynode Package Download Locations

The anynode installation packages are provided on the TE-SYSTEMS Linux repository server.

Debian / Ubuntu packages

https://linux.te-systems.de/release/

This directory contains operating system specific subdirectories, for example:

  • deb11/

  • deb12/

  • deb13/

  • ub2004/

  • ub2204/

  • ub2404/

Each directory contains the installation packages for the corresponding Linux distribution.

RHEL packages

https://linux.te-systems.de/rhel/

Available directories include for example:

  • rhel8/

  • rhel9/

  • rhel10/

anynode Package Components

The anynode software consists of multiple components which are installed as separate packages:

  • anynode (Core SBC component)

  • anynodead (Administration service)

  • anynodefe (Web frontend)

  • anynodemon (Monitoring service)

All four packages must be installed on the system.

Package Naming Scheme

Debian / Ubuntu

The package naming scheme follows this format:

<component>-<version>-<distribution>-<architecture>-release.deb

Example (Debian 13):

anynode-4.14.10-debian13-x64-release.deb

anynodead-4.14.10-debian13-x64-release.deb

anynodefe-4.14.10-debian13-x64-release.deb

anynodemon-4.14.10-debian13-x64-release.deb

Example (Debian 13 arm64):

anynode-4.14.10-debian13-arm64-release.deb

anynodead-4.14.10-debian13-arm64-release.deb

anynodefe-4.14.10-debian13-arm64-release.deb

anynodemon-4.14.10-debian13-arm64-release.deb

RHEL

RHEL packages follow the RPM naming scheme:

<component>-<version>-<release>.el<major>.<architecture>.rpm

Example (RHEL 10):

anynode-4.14.10-1.el10.x86_64.rpm

anynodead-4.14.10-1.el10.x86_64.rpm

anynodefe-4.14.10-1.el10.x86_64.rpm

anynodemon-4.14.10-1.el10.x86_64.rpm