Service management
Controlling the service
- Linux (systemd)
- macOS
- Windows
systemctl status wakora-agent
systemctl restart wakora-agent
journalctl -u wakora-agent -f
On OpenRC use rc-service wakora-agent ..., on sysvinit /etc/init.d/wakora-agent ....
wakora service install
wakora service uninstall
sudo launchctl kickstart -k system/io.wakora.agent
.\wakora.exe service install
.\wakora.exe service uninstall
.\wakora.exe service start
.\wakora.exe service stop
service install is idempotent: if the service already exists it fixes the image path to
the current binary and starts it, which fixes the "installed from Downloads" trap.
Logs
The agent writes its own log to /var/log/wakora/agent.log (10 MB rotation to .old),
and also to the journal on systemd. On Windows the log lives under %ProgramData%\Wakora.
One-shot commands (--key, --test, secret) log to stderr only.
tail -f /var/log/wakora/agent.log
Resource budget
The agent is built to stay light: under 1% CPU and roughly 50 to 80 MB RAM at production
cadence. In practice at a 60-second interval it measures around 0.1% CPU and single-digit
MB of RSS. It self-limits in process (GOMEMLIMIT 128 MiB, GOMAXPROCS capped at 2), and
the systemd unit adds CPUQuota=30%, MemoryHigh=160M, MemoryMax=256M, Nice=10, and
OOMScoreAdjust=500. That last one means that under host memory pressure the kernel kills
the agent before any client service.
Dry run
To see what the agent would collect without connecting:
wakora --test