Server

Before you install Flopsar, make sure your environment meets a few basic requirements:

• A few gigabytes of free disk space for the collected data (size it to your retention needs).

• Your network allows TCP connections between the agents and the server.

• A 64-bit GNU/Linux host. See Supported Platforms and Requirements for details. This page covers installing the server. To attach agents to your Java applications, see the Agent page.

Starting with Flopsar 7, the Workstation web application is embedded directly in the server binary. There is no separate workstation package to install for the standard, standalone deployment — the server serves the UI and the REST API from the same port.

Install the Package

Manual Package Install

Download the package that matches your platform and architecture and install it directly.

Debian / Ubuntu

# dpkg -i flopsar-server.<arch>.deb

Red Hat / SUSE

# rpm -ih flopsar-server.<arch>.rpm
# dnf install flopsar-server.<arch>.rpm
# zypper install flopsar-server.<arch>.rpm

What the Installation Does

Regardless of the method, on the first installation the package:

• Creates a dedicated system user and group named flopsar, used to run the service.

• Installs the flopsar-server binary to /usr/sbin.

• Registers a flopsar systemd service.

• Creates the global configuration directory /etc/flopsar and generates:

  • a default configuration file, /etc/flopsar/settings.toml;

  • a self-signed TLS certificate and key in /etc/flopsar/ssl/;

  • a 256-bit master key in /etc/flopsar/ssl/master.key (used to encrypt agent tokens);

  • the service environment file /etc/flopsar/eula.env, with EULA acceptance left empty.

The auto-generated TLS certificate is self-signed. For production, replace server.crt / server.pem in /etc/flopsar/ssl/ with certificates issued by a trusted CA, and keep the file ownership and permissions intact (root:flopsar, 0640 for private material).

Accept the EULA

The server will not start until you accept the End User License Agreement. Acceptance is expressed through the FLOPSAR_EULA environment variable, which the service reads from /etc/flopsar/eula.env. Edit the file and set the value to accept:

/etc/flopsar/eula.env

# EULA acceptance (https://eula.flopsar.com):
# set the variable below to "accept" to start the server.
FLOPSAR_EULA=accept

Start the Server

Enable and start the service:

# systemctl enable --now flopsar

The service runs as the flopsar user and stores its data under /var/lib/flopsar (provided through the FLOPSAR_HOME environment variable in the unit file). On first start, the server initializes a fresh environment in that directory automatically. Check that the service is running:

# systemctl status flopsar

Sign In

Once the server is running, open the Workstation in your browser. TLS is enabled by default, so the address is:

https://<YOUR_HOST>:9443

Default credentials are admin / flopsar. Change the password immediately after your first sign-in.

File and Directory Layout

After a package installation, the relevant locations are:

• /usr/sbin/flopsar-server — the server binary.

• /etc/flopsar/settings.toml — the global server configuration.

• /etc/flopsar/ssl/ — TLS certificate (server.crt), private key (server.pem), and the master key (master.key).

• /etc/flopsar/eula.env — the service environment file, including EULA acceptance.

• /var/lib/flopsar — the server home (the environment), containing the data storage, logs, and archives.

• flopsar.service — the systemd unit for the service.

Network Ports

By default the server listens on:

• 9000 — agent connections.

• 9443 — the REST API and the Workstation (TLS).

• 4318 and 4317 — OpenTelemetry OTLP/HTTP and OTLP/gRPC ingestion. Adjust these in the server configuration and open them in your firewall as needed.

Using a Custom Environment Location

The packaged service keeps its data in /var/lib/flopsar. If you prefer a different location (for example, a dedicated data volume), you have two options:

• Point the service at another directory by overriding FLOPSAR_HOME (for example, with a systemd drop-in), or set the data option in settings.toml. Make sure the flopsar user can read and write that directory.

• Pre-create an environment explicitly and start the server against it:

$ flopsar-server create <server_home>

This creates a new, empty environment at <server_home>. See the Server page for the full list of command line operations (create, config, gencerts, genmkey, and more).

If you start the server through systemd, it runs as the flopsar user by default. Ensure that this user has read/write permissions to the environment directory.

Troubleshooting

This section covers the most common issues after installing Flopsar Server via the package and starting it with systemctl.

Where to look first

$ sudo systemctl status flopsar          # current state and last log lines
$ sudo journalctl -u flopsar -e          # full service log (most recent at the end)
$ sudo journalctl -u flopsar -f          # follow the log live

Almost every startup problem is explained in journalctl -u flopsar.

The service does not start

Symptom: systemctl status flopsar shows failed or the service exits immediately.

Most common cause — the EULA is not accepted. The log will contain a message about FLOPSAR_EULA. Fix:

$ sudo sed -i 's/^FLOPSAR_EULA=.*/FLOPSAR_EULA=accept/' /etc/flopsar/eula.env
$ sudo systemctl restart flopsar

Other causes:

• A malformed /etc/flopsar/settings.toml — the log shows a parse error and the offending field.

Restore defaults by removing the file and regenerating:

$ sudo flopsar-server config /etc/flopsar/sudo systemctl restart flopsar

Missing TLS material in /etc/flopsar/ssl/. Regenerate:

$ sudo flopsar-server gencerts /etc/flopsar/ssl/
$ sudo flopsar-server genmkey --path /etc/flopsar/ssl/
$ sudo systemctl restart flopsar

The service starts, then keeps restarting

Symptom: systemctl status shows repeated activating (auto-restart).

The unit uses Restart=on-failure, so a crash loop means the process exits with an error on each attempt. Inspect the reason:

$ sudo journalctl -u flopsar -e --no-pager | tail -n 50

Typical reasons: EULA not accepted, unreadable master.key, or a port already in use (see below).

The web interface is not reachable

Symptom: https://<host>:9443 times out or refuses the connection.

Diagnose in order:

Is the service running?

$ sudo systemctl is-active flopsar

Is it listening on the expected ports?

$ sudo ss -tlnp | grep -E '9443|9000|4318|4317'

You should see flopsar-server bound to 0.0.0.0:9443 (and the other ports).

Is a firewall blocking access? (RedHat-based / firewalld)

$ sudo firewall-cmd --list-services      # is "flopsar" listed?
$ sudo firewall-cmd --permanent --add-service=flopsar
$ sudo firewall-cmd --reload

On Debian/Ubuntu with ufw enabled: sudo ufw allow 9443/tcp.

Are you using the right port? The web UI listens on 9443 (HTTPS), not 9943 or 9000.

Browser shows a certificate warning

This is expected. Flopsar generates a self-signed certificate by default, so browsers will warn on first access. Either accept the exception, or replace /etc/flopsar/ssl/server.crt and the corresponding key with your own CA-signed certificate and restart the service.

SELinux (RedHat-based, enforcing)

Flopsar runs as an unconfined systemd service, so SELinux does not require any configuration in normal installations. If you suspect SELinux is blocking something:

$ sudo ausearch -m AVC -ts recent        # look for denials (AVC entries)
$ sudo setenforce 0                      # temporary test; if it works now, SELinux is the cause
$ sudo setenforce 1                      # re-enable

If a denial is confirmed, generate an allow rule from the audit log with audit2allow, or report it to support.

Collecting information for support

When contacting support, include:

$ flopsar-server --version
$ systemctl status flopsar --no-pager
$ journalctl -u flopsar --no-pager | tail -n 200