Telemetry and commands
Start with the server status and the command result in Activity. Fresh readings alone do not confirm that a command has been delivered.
Data updates, but commands do not run
Section titled “Data updates, but commands do not run”If the measurements are fresh but commands remain in the queue, first read the reason for the wait on the Activity tab. Besides connectivity problems, a command can be delayed by a previous operation or maintenance restrictions.
If the cause is delivery:
-
Look at the agent log:
Terminal window journalctl -u flotera-agent -n 100 --no-pager -
Check for WebSocket connection errors, authorization errors, and the service address. The proxy must allow the HTTPS connection to upgrade to WebSocket and permit a long-lived connection. A successful plain
curldoes not verify this. -
Check that the agent is up to date. If the connection does not recover, restart the agent and check its log again:
Terminal window sudo systemctl restart flotera-agent
If the command channel is unavailable, an update from the panel can also remain in the queue. Use server access and the installer after checking the network and configuration.
Commands run, but data is stale
Section titled “Commands run, but data is stale”Check the time and clock synchronization:
timedatectl statusAn incorrect clock can shift chart readings or cause data to be rejected. Fix time synchronization and update the agent. Check Activity and the agent log for Host clock is off; readings rejected.
If the time is correct, check data delivery and the account state. History recording is paused while the account is frozen.
Gaps in the charts after a connection loss
Section titled “Gaps in the charts after a connection loss”After an outage longer than five minutes, older readings cannot be recovered. The chart keeps a gap even after the connection returns. Check rental status and earnings separately on the marketplace.
Command stays in Queued
Section titled “Command stays in Queued”| Message | Meaning |
|---|---|
server is offline — queued until it reconnects |
waiting for the agent to connect |
awaiting the next delivery attempt |
waiting for a retry of delivery |
waiting for a guard or the previous command |
a restriction is in effect, or the previous command is still running |
Commands for one server run sequentially. Open the previous command and check its result.
Command ended with an error
Section titled “Command ended with an error”Open the result on the Activity tab. It contains the rejection reason or the execution error. If the power limit is outside the valid range or the agent lacks permissions, repeating the same command does not help: fix the parameter or the permissions.
Server did not appear after installation
Section titled “Server did not appear after installation”Check the installation completion, the service, and the connection following the server is offline instructions.