Skip to main content

ConfigGuardian Troubleshooting

This page covers common issues, frequently asked questions, and troubleshooting steps for ConfigGuardian.

Frequently Asked Questions​

Does ConfigGuardian work on all Axis cameras?​

ConfigGuardian works on any Axis camera that:

  • Runs AXIS OS 11.0 or later
  • Has the Anava ACAP 2.0+ installed
  • Has the native MQTT client enabled

Most modern Axis cameras (ARTPEC-7 and newer) are compatible.

What happens during a firmware update?​

During a firmware update:

  1. The ACAP may be temporarily stopped
  2. MQTT configuration may be reset to defaults
  3. When the ACAP restarts, ConfigGuardian restores the golden configuration
  4. A CONFIG_DRIFT → CONFIG_HEALED sequence is expected

No action is required. ConfigGuardian handles firmware updates automatically.

Can I temporarily disable ConfigGuardian?​

Yes, for maintenance windows you can:

Option 1: Set to Alert-Only Mode

curl -X POST "http://CAMERA_IP:8080/api/v1/config/guardian" \
  -H "Content-Type: application/json" \
  -d '{"healingPolicy": "ALERT_ONLY"}'

Option 2: Stop the ACAP

curl --digest -u root:password \
  "http://CAMERA_IP/axis-cgi/applications/control.cgi?action=stop&package=AnavaAgent"

Remember to re-enable after maintenance.

The guardian is reverting my changes. How do I make permanent changes?​

Changes made via the camera web UI or VAPIX are always reverted by ConfigGuardian. To make permanent changes:

Change TypeMethod
Broker addressContact Anava support (broker migration)
SubscriptionsUpdate via cloud profile configuration
TLS settingsNot user-configurable (security)
Client IDAutomatic (based on device serial)

How do I know if ConfigGuardian is running?​

Method 1: Health Endpoint

curl "http://CAMERA_IP:8080/api/v1/health"

Response includes ConfigGuardian status:

{
  "status": "healthy",
  "components": {
    "configGuardian": {
      "status": "running",
      "lastCheck": "2025-12-19T10:30:00Z",
      "driftCount": 0
    }
  }
}

Method 2: Dashboard

Check the device detail page. The ConfigGuardian status appears in the Device Health section.

Method 3: Logs

ssh baton@CAMERA_IP "grep ConfigGuardian /var/log/info.log | tail -10"

Does ConfigGuardian work offline?​

Yes, with limitations:

FeatureOnlineOffline
Drift detectionYesYes
HealingYesYes
Alert publishingYesQueued
Golden config updatesYesNo

When offline, alerts are queued and published when connectivity is restored.

What if the camera can't connect to the broker to heal?​

If the configuration drift prevents broker connectivity:

  1. ConfigGuardian heals the configuration via VAPIX (local)
  2. The camera reconnects with correct settings
  3. Queued alerts are published

ConfigGuardian operates locally and doesn't require broker connectivity to heal.

Common Issues​

Repeated CONFIG_CONFLICT Alerts​

Symptom: You receive multiple CONFIG_CONFLICT alerts from the same device.

Possible Causes:

  1. Conflicting ACAP: Another application is modifying MQTT settings
  2. Automation Script: A script or tool is programmatically changing settings
  3. Malicious Actor: Someone is intentionally tampering with the configuration
  4. Firmware Bug: A camera firmware issue is resetting settings

Diagnostic Steps:

# List installed ACAPs
curl --digest -u root:password \
  "http://CAMERA_IP/axis-cgi/applications/list.cgi"

# Check access logs
curl --digest -u root:password \
  "http://CAMERA_IP/axis-cgi/admin/accesslog.cgi?tail=100"

# Check system logs for MQTT changes
ssh baton@CAMERA_IP "grep -i mqtt /var/log/info.log | tail -50"

Resolution:

  1. Identify and remove conflicting software
  2. Change camera passwords if unauthorized access suspected
  3. Contact Anava support if issue persists

No Alerts Being Published​

Symptom: You know drift is occurring but don't see alerts in the dashboard.

Possible Causes:

  1. MQTT connectivity issue: Device can't reach the broker
  2. Alert publishing disabled: Configuration issue
  3. Network firewall: Outbound MQTT blocked

Diagnostic Steps:

# Check MQTT connectivity
curl "http://CAMERA_IP:8080/api/v1/health"

# Check ConfigGuardian logs
ssh baton@CAMERA_IP "grep ConfigGuardian /var/log/info.log | tail -20"

# Verify MQTT broker is reachable
ssh baton@CAMERA_IP "nc -zv mqtt.anava.ai 8883"

Golden Configuration Not Updating​

Symptom: You made a legitimate configuration change via the cloud, but ConfigGuardian reverts it.

Possible Causes:

  1. Change not propagated: The cloud config update didn't reach the device
  2. Parsing error: The configuration update was malformed
  3. Timing issue: ConfigGuardian checked before the update was applied

Resolution:

  1. Verify the configuration change in the cloud dashboard
  2. Force a configuration refresh:
curl -X POST "http://CAMERA_IP:8080/api/v1/config/refresh"
  1. Check ConfigGuardian logs for errors

High CPU Usage​

Symptom: ConfigGuardian is using more CPU than expected.

Normal Usage: < 0.1% CPU

Possible Causes:

  1. Rapid drift/heal loop: Check for CONFIG_CONFLICT
  2. VAPIX timeout: Camera web server is slow
  3. Logging overhead: Verbose logging enabled

Resolution:

  1. Check for conflict alerts
  2. Reduce logging verbosity:
curl -X POST "http://CAMERA_IP:8080/api/v1/config/logging" \
  -H "Content-Type: application/json" \
  -d '{"level": "INFO"}'

Diagnostic Commands​

Check ConfigGuardian Status​

curl "http://CAMERA_IP:8080/api/v1/config/guardian"

View Golden Configuration​

curl "http://CAMERA_IP:8080/api/v1/config/guardian/golden"

View Current Configuration​

curl "http://CAMERA_IP:8080/api/v1/config/guardian/current"

Compare Golden vs Current​

curl "http://CAMERA_IP:8080/api/v1/config/guardian/diff"

Force a Check​

curl -X POST "http://CAMERA_IP:8080/api/v1/config/guardian/check"

Reset Golden Configuration​

danger

This resets the golden configuration to the current state. Only use if you're sure the current configuration is correct.

curl -X POST "http://CAMERA_IP:8080/api/v1/config/guardian/reset-golden"

Getting Help​

If you've tried the troubleshooting steps above and still have issues:

  1. Gather Logs:

    ssh baton@CAMERA_IP "cat /var/log/info.log" > device-logs.txt

  2. Export Configuration:

    curl "http://CAMERA_IP:8080/api/v1/config/export" > device-config.json

  3. Contact Support:

    • Email: support@anava.ai
    • Include: Device serial, logs, configuration, and description of issue

Last updated: December 2025