Running nodes
Troubleshooting
Each row below starts from something that a node shows: a line in the agent’s log, a status code or a refusal. Look up the exact text you see.
Setup and connection
| Symptom | Next step |
|---|---|
Setup stops at pulling …/ankor-agent |
Check that the host can reach the image registry, then rerun setup. |
| Agent log: the controller at … refused this node’s token | The agent has stopped dialling. Restart it once the controller knows the token. |
| Agent log: the controller at … uses a protocol version incompatible with this agent’s … | The agent has stopped dialling. Update it from the host. |
| Agent log: the controller at … refused this node’s hello | The agent has stopped dialling. Its hello failed the controller’s schema (invalid_hello). Update it from the host. |
Node unavailable with code event_storage, detail says the event spool has not answered |
The disk under /srv/ankor hangs. Check the disk, and leave the agent running. Deleting /srv/ankor/events/ or restarting the agent loses the records that wait to be written. The agent takes launches again once the event spool answers. |
Node unavailable with code event_storage, any other detail |
The agent cannot open its events database, for example one that a downgrade left newer than the agent. The agent log gives the cause. Update the agent from the host, or delete /srv/ankor/events/ and restart the agent. Deleting it loses every undelivered event and server exit, including those of running servers. It also loses the record of allocations the node has launched. A running server’s later events are stored again from where its plugin resumes. |
Node unavailable with code disk_space |
The disk under /srv/ankor has less than 1024 MiB free. Check it with df -h /srv/ankor, then free space. For example, remove old demos, or remove unused Docker images with docker image prune. The agent checks every 30 seconds and accepts launches again once there is room. |
Game servers
| Symptom | Next step |
|---|---|
| CS2 missing after setup | Install it. The agent installs CS2 only when the controller requests it. |
| Node refuses launches after a CS2 release | The node updates CS2 once its running servers end. After a failed automatic attempt, update by hand. |
| Update refused for free space | Grow the disk. Update CS2 lists the thresholds. |
| Slot receives no launches, login token refused | Steam refused the slot’s login token. Replace it. |
| Missing game files or a mountpoint | Wait until the node is idle, then update CS2. |
| Stop is unconfirmed | Check Docker on the host. The slot stays occupied until Docker reports the container removed. |