Skip to content

Linux Server Installation

Current Status: Not Available

As of the current release, there is no validated TraceWall edition for Linux servers (headless environments).

The published .deb package is built for desktop environments with a graphical session (X11 or Wayland). It requires:

  • A running display server (X11 or Wayland)
  • A graphical desktop environment (GNOME, KDE, XFCE, etc.)
  • Electron’s browser process to initialize

The Desktop package will not function on a headless server (no GUI, no display server, SSH-only access).


What Is Required for a True Server Edition

A production-ready Linux Server edition would need:

ComponentCurrent StateRequired for Server
UI FrameworkElectron (requires GUI)Headless agent / CLI / TUI
SensorRuns in Electron main processStandalone daemon (systemd service)
ARGUS Local AIRuns in Electron renderer (loopback)Independent inference server (llama.cpp / vLLM)
ConfigurationGUI Settings + JSONCLI config + file-based / API
Packaging.deb with desktop entry.deb + .rpm with systemd units
UpdatesAuto-update via ElectronPackage manager / custom updater
Cloud SyncBuilt into Electron appSame protocol, standalone client

Planned Roadmap

MilestoneTargetNotes
Headless sensor daemonQ1 2025Rust/Go binary, systemd service, AF_PACKET / eBPF
ARGUS inference serverQ1 2025llama.cpp server mode, REST API, model management
CLI / TUI for configQ2 2025tracewallctl for enrollment, sensor control, status
Systemd integrationQ2 2025tracewall-sensor.service, tracewall-argus.service
Server packagesQ2 2025.deb (Ubuntu/Debian), .rpm (RHEL/Rocky/Alma)
ARM64 buildsQ3 2025For Ampere/Graviton instances

Why Not Use the Desktop Package on a Server?

AttemptResult
Install .deb on Ubuntu Server (no GUI)electron: symbol lookup error / Gtk: cannot open display
Install .deb + xvfb-runElectron launches but sensor misses hardware context; ARGUS fails to bind loopback cleanly; no systemd management
Run via RDP/X2Go with GUI sessionWorks but defeats “headless” purpose; session disconnect pauses sensor; not a service

If you must run TraceWall on a Linux server today:

  1. Install a minimal desktop (ubuntu-desktop-minimal or xfce4)
  2. Configure auto-login for a dedicated service account
  3. Run TraceWall at session start (autostart .desktop)
  4. Keep session alive (do not disconnect RDP/VNC)
  5. Accept limitations: no systemd management, no clean updates, manual ARGUS model handling

This is a development/test workaround only.


What You Can Do Today

NeedAlternative
Network visibility from Linux hostsDeploy Windows Desktop on a management workstation; configure SNMP/SSH/HTTPS integrations to Linux targets
Linux host telemetryUse Wazuh agent or Zabbix agent on Linux; integrate with TraceWall via Wazuh/Zabbix connectors
ARGUS analysis of Linux dataRun ARGUS on Windows Desktop; feed data via integrations

Notification Request

If you have a specific Linux server use case (distribution, kernel version, headless requirement, ARGUS need), contact soporte@trace-wall.com with:

  • Distribution and version
  • Kernel version (uname -r)
  • Whether you need sensor only, ARGUS, or both
  • Whether you can run a lightweight GUI (XFCE + auto-login) or strictly headless
  • Scale (number of servers)

This input drives prioritization.