Skip to main content

Troubleshooting

Use this guide to diagnose and resolve common Breeze Agent issues.

No Check‑Ins or Stale Data​

Symptoms:

  • Hosts appear stale or never‑seen in Cloudaware.
  • No recent log entries on the agent host.

Checks:

  • Verify the scheduler:
    • Linux/macOS: systemctl status breeze-agent.timer or cat /etc/cron.d/breeze-agent.
    • Windows: confirm the Breeze Agent task exists and is running on schedule.
  • Check logs:
    • Linux/macOS: /opt/breeze-agent/var/log/breeze-agent.log.
    • Windows: C:\\Program Files\\Breeze\\agent.log.
  • Confirm network access:
    • Ensure outbound TCP 443 to Breeze endpoints is allowed (and not blocked by firewalls or proxies).

If logs are empty, temporarily increase verbosity (see Logging) and rerun the agent manually to capture output.

Cloud Metadata Errors​

Symptoms:

  • Errors in logs related to cloud metadata or instance identity.
  • Missing cloud provider facts (for example, EC2, Azure, GCE, EKS/AKS identifiers).

Checks:

  • Ensure access to the cloud metadata service on instances (for example, 169.254.169.254 on many platforms).
  • Confirm NO_PROXY excludes metadata IPs so proxy interception does not block metadata requests.
  • On managed Kubernetes nodes, verify that node IAM/roles allow metadata access where required.

See Environment & Proxy for proxy and NO_PROXY examples.

TLS or Proxy Errors​

Symptoms:

  • SSL/TLS handshake failures when connecting to Breeze Server.
  • Errors mentioning certificate validation, hostname mismatch, or proxy interception.

Checks:

  • Confirm proxy configuration:
    • Linux/macOS: check /opt/breeze-agent/app.sh.
    • Windows: check C:\\Program Files\\Breeze\\app.bat.
  • Ensure the proxy’s Certificate Authority (CA) is trusted:
    • Use OS‑level trust or set HTTP_CA_FILE to a CA bundle file.
  • Verify server_url points to the correct Breeze endpoint.

If the environment uses TLS interception, coordinate with your security team to obtain the correct CA bundle.

Connectivity to Breeze Server​

Symptoms:

  • Logs show repeated connection failures to Breeze Server.

Checks:

  • From the host, test connectivity, for example:
    • Linux/macOS:
      • curl -v https://breeze-server.cloudaware.com/
    • Windows (PowerShell):
      • [System.Net.WebRequest]::Create(\"https://breeze-server.cloudaware.com/\").GetResponse() | select Status,StatusDescription,ResponseUri | fl
  • Confirm that any outbound firewall, proxy, or network appliance allows HTTPS to Breeze endpoints.

Plugin or Data Issues​

Symptoms:

  • Breeze runs, but expected data (facts or integration results) is missing.

Checks:

  • Confirm the agent is on a supported OS/architecture and meets Requirements.
  • Review logs for plugin‑related errors; some plugins may be disabled or misconfigured.
  • Ensure the relevant modules or integrations are enabled in Cloudaware Admin.

Kubernetes Pods Missing​

Symptoms:

  • Some or all Kubernetes nodes do not show Breeze data.
  • Breeze pods are missing on certain nodes.

Checks:

  • Verify the DaemonSet:
    • kubectl get ds -n <namespace> — ensure DESIRED = CURRENT = READY.
    • Check node taints/labels that might prevent scheduling.
  • Inspect pod logs:
    • kubectl logs -n <namespace> <breeze-pod> for image pull, permissions, or network errors.
  • Confirm nodes can reach Breeze endpoints (and TunHub, if used for private clusters).

For more complex issues, capture logs and environment details and contact Cloudaware support support@cloudaware.com with host IDs and timestamps.

For configuration details, see Configuration and Config reference.