Review Logs and Rule Activity

Find Proxyble, rule-agent, HAProxy, nftables, and RioDB information when operating a deployment.

Logs are the first place to look when a service fails to start, a manual rule does not apply, or an automated policy does not appear to trigger.

Start with the managed status

sudo proxyble --config-status
sudo proxyble --config-view
sudo proxyble --verbose --config-start

--verbose prints detailed action output in the terminal and writes the action log.

Key locations

/var/log/proxyble/*.log contains timestamped CLI and Proxyble action logs.
/var/log/proxyble-rule-agent/YYYY-MM-DD.log contains daily rule-agent activity and audit events.
journalctl -u proxyble-rule-agent.service shows rule-agent service output. The .path and .timer units have separate journals.
journalctl -u haproxy.service shows HAProxy service messages.
journalctl -u nftables.service shows nftables service messages; inspect the active Proxyble table with nft list table inet pmgr.
/var/log/riodb and journalctl -u riodb.service contain RioDB logs when analytics is enabled.

Quick checks

sudo ls -lt /var/log/proxyble
sudo ls -lt /var/log/proxyble-rule-agent
sudo journalctl -u proxyble-rule-agent.service -n 50 --no-pager
sudo journalctl -u haproxy.service -n 50 --no-pager
sudo journalctl -u nftables.service -n 50 --no-pager
sudo nft list table inet pmgr

For RioDB deployments, also run:

sudo journalctl -u riodb.service -n 50 --no-pager
sudo ls -lt /var/log/riodb

If these checks expose a service or routing problem, use Diagnostics to work through the likely cause.