Managerd Commands and vnetarmorctl

Start Managerd manually

Package installations normally use systemd. Manual start is useful for troubleshooting.

managerd \
  --remote 0.0.0.0:9443 \
  --local 127.0.0.1:9444 \
  --core-ipc unix:/run/vnetarmor/core.sock \
  --log-level info \
  --log-dir /var/log/vnetarmor/managerd \
  --tls_cert_path /opt/vnetarmor/certs/managerd.crt \
  --tls_key_path /opt/vnetarmor/certs/managerd.key \
  --tls_ca_path /opt/vnetarmor/certs/ca.crt

systemd commands

sudo systemctl status vnetarmor-managerd
sudo systemctl restart vnetarmor-managerd
sudo journalctl -u vnetarmor-managerd -n 100 --no-pager

vnetarmorctl status

vnetarmorctl \
  --server manager01.example.local:9443 \
  --cacert /opt/vnetarmor/certs/ca.crt \
  --cert /opt/vnetarmor/certs/operator.crt \
  --key /opt/vnetarmor/certs/operator.key \
  status

Reload Core configuration

vnetarmorctl \
  --server manager01.example.local:9443 \
  --cacert /opt/vnetarmor/certs/ca.crt \
  --cert /opt/vnetarmor/certs/operator.crt \
  --key /opt/vnetarmor/certs/operator.key \
  reload

Stream events

vnetarmorctl \
  --server manager01.example.local:9443 \
  --cacert /opt/vnetarmor/certs/ca.crt \
  --cert /opt/vnetarmor/certs/operator.crt \
  --key /opt/vnetarmor/certs/operator.key \
  events --include-allow --include-block --include-log --max-events-per-sec 25

Common errors

Error	Meaning	Fix
Core disconnected	Managerd cannot reach Core IPC socket.	Check Core service and --core-ipc path.
Permission denied	Managerd cannot read socket or cert files.	Check file ownership and permissions.
TLS handshake failed	Certificate trust or SAN problem.	Verify CA, server cert, and client cert.