Quick Reference
Use this page as a starting point. Match the symptom you are seeing to the most likely diagnostic path, then follow the linked page for detailed steps.
If your symptom is not represented here — or you have worked through the linked path without resolving the issue — gather a Diagnostic Bundle before contacting Anchore Customer Success.
Common Symptoms
| Symptom | Likely cause | Start here |
|---|---|---|
A service shows as down or unavailable in anchorectl system status. | The service process has crashed, the container has exited, or the readiness probe is failing. | Verifying Service Health |
A service shows as orphaned in the GUI System view. | The service can no longer reach the catalog or its database registration has lapsed. | Verifying Service Health, then inspect that service’s log. |
An image is stuck in the analyzing state for an extended period. | The analyzer cannot pull the image, registry lookup is failing, or the analyzer is overloaded. | Viewing Logs — trace the analyzer thread for that image. |
registry_lookup_failed events appear repeatedly. | Registry credentials are missing or expired, or the registry is unreachable from the catalog. | Viewing System Events |
| Vulnerability data is stale or missing for one or more feed groups. | The Data Syncer has not pulled the relevant dataset, or the upstream provider is unreachable. | Data Syncer |
| Newly-published CVEs are not appearing on existing analyses. | Feed sync completed after the image was analyzed; the analysis needs to be re-evaluated. | Data Syncer |
A policy evaluation returns an unexpected result (stop vs pass, or vice versa). | Policy or feed data has changed, or a gate is referencing data that is not yet available. | Viewing System Events and review the policy evaluation output. |
| AnchoreCTL cannot connect to Anchore Enterprise. | The URL, credentials, TLS trust, or API version are misconfigured. | Run anchorectl system status -vvvv and inspect the configuration dump along with any TLS or HTTP errors. |
| You need to validate the system end-to-end after an upgrade or configuration change. | A known-good baseline check is required. | Smoke Testing |
If Your Symptom Is Not Listed
- Re-run
anchorectl system statusand confirm every service reportsupandavailable. - Run
anchorectl event listand look for recenterror-level events tied to the affected resource. - Pull the relevant service log (see Viewing Logs) and grep for the resource identifier (image digest, image tag, or thread number).
- If you still cannot isolate the cause, prepare a Diagnostic Bundle for Anchore Customer Success.