Managing nodes

All connected nodes are on the Nodes page. Connecting a new one is covered in Connect a node.

The node list

The list refreshes every 5 seconds. For each node it shows the state, location, agent version and resources:

• CPU and RAM — how much the limits of its servers' containers reserve, not the current load;
• disk — how much space is used.

Tabs above the list: All, Online, Attention, Offline. Next to them is a search by ID, IP, hostname, game or agent version, and a location filter. To act on several nodes at once, tick them — maintenance and removal work in bulk.

The node page

Overview:

• Resources — reserved CPU and RAM, used disk and charts of the real load;
• Host — OS, CPU, memory, swap and the data directory, as reported by the agent;
• Game servers on the node;
• Addresses — the node's IP addresses (see below);
• the games installed on the node with their settings. The set of games is changed under Games, see Game catalog.

Agent and containers — the containers the agent reports. It's a technical list for diagnostics; manage customers' servers from the server's page.

When a node hasn't been in touch for a while, its page shows a Needs attention block: commands won't reach it until it's back, and its servers may be unreachable for players. When the agent is older than the panel, the update command is shown there too.

Maintenance

Put into maintenance — the node stops taking new servers: neither the scheduler nor an admin by hand will place one there. Running servers keep running and their owners manage them as before.

Use it before working on the machine or when the node is due to be decommissioned. Take out of maintenance opens it to new servers again.

The node's location

The location is picked on the node's page (the Location field) or on the location's own page. A node without a location doesn't get servers created with a location choice. More in Locations.

Addresses

If the node has several public IPs or servers should be shown to players by a domain name, add addresses: Addresses → + Add address.

• Bind IP — the node IP the servers of this address listen on. Each IP has its own set of ports. Empty — all interfaces, and a port is taken on every IP at once. While the address has servers, the IP can't be changed.
• Public address — the IP or domain, without a port, that players see. Empty — the bind IP, or the node's IP if there is none.
• IP pool — e.g. premium for dedicated IPs. An address from a pool goes only to servers of plans that name the pool (Plans). Empty — the shared pool.
• Customer can pick — the customer sees the address when creating a server. Otherwise only an admin places servers on it.
• Default address — new servers on the node get it unless an address is picked explicitly.

Without addresses, servers listen on all interfaces and players are shown the node's IP. How ports are split between IPs is covered in Game server ports.

Removing a node

More → Remove from list… revokes the node's certificate and drops its connection at once. It can only come back by connecting again with a new token.

The containers and files on the machine itself are not removed. If you're decommissioning the node for good, first delete its servers in the panel (server's Settings tab → Delete server) while the node is online. The node then removes the containers itself and the ports are freed.

A node can't be removed while a managed database server runs on it or a database host is reached through it. The panel names that server — delete or change it first. See Databases.

A removed node frees a slot in the license's node limit.