Aurva

Troubleshooting

Common issues and resolutions for Aurva deployments.

Common problems and the fastest path to resolution. If something here doesn't match your situation, contact Aurva support with the relevant log snippets.

Data Plane

Data Plane shows as offline in the Control Plane

  • Verify outbound connectivity from the Data Plane host to the Control Plane URL (typically command.aurva.io:443).
  • Check that the Aurva private registry (registry.aurva.io) is reachable for image pulls.
  • Inspect the controller pod or service logs for authentication errors.

High CPU on the Data Plane

  • Open the Monitoring Configuration page and check how many assets a single controller is handling. The recommended ceiling is 25 assets per controller.
  • Review storage policies — Store All Queries on a high-throughput database can saturate a controller. Narrow to Scope by Operation Type.

DAM Agents

eBPF agent installed but no queries appear

  • Verify kernel version meets the prerequisites (≥ 5.10 Debian, ≥ 4.10 RHEL).
  • Confirm the appropriate TRACE_* flags are set in the env file (TRACE_PSQL, TRACE_MYSQL, TRACE_MONGO, TRACE_SSL).
  • Check journalctl -u aurva-collector.service -f for runtime errors.

AIDA collector failing to authenticate

  • Confirm the company ID and controller URL match the values shown on the Monitoring Configuration page.
  • Re-run the bootstrap script with sudo.

Prevention Mode

Prevention Mode stuck at "Awaiting connection"

  • This is expected until the application connects through the new proxy port. Restart the application or its connection pool.
  • Verify the application connection string was updated to the new proxy port.

Port validation errors

Classification & Discovery

An asset has been onboarded but classification is empty

  • Initial scans run in the background and may take 30–60 minutes for small assets, longer for large ones.
  • Check the Data Plane has read permissions on the asset (sample IAM policies are in AWS IAM Permissions for the Data Plane).