Verifying Service Health
You can verify which services have registered themselves successfully, along with their status, by running: anchorectl system status
# anchorectl system status
✔ Status system
┌─────────────────┬────────────────────┬─────────────────────────────┬──────┬────────────────┬────────────┬──────────────┐
│ SERVICE │ HOST ID │ URL │ UP │ STATUS MESSAGE │ DB VERSION │ CODE VERSION │
├─────────────────┼────────────────────┼─────────────────────────────┼──────┼────────────────┼────────────┼──────────────┤
│ analyzer │ anchore-quickstart │ http://analyzer:8228 │ true │ available │ 5130 │ 5.13.0 │
│ policy_engine │ anchore-quickstart │ http://policy-engine:8228 │ true │ available │ 5130 │ 5.13.0 │
│ apiext │ anchore-quickstart │ http://api:8228 │ true │ available │ 5130 │ 5.13.0 │
│ reports │ anchore-quickstart │ http://reports:8228 │ true │ available │ 5130 │ 5.13.0 │
│ reports_worker │ anchore-quickstart │ http://reports-worker:8228 │ true │ available │ 5130 │ 5.13.0 │
│ data_syncer │ anchore-quickstart │ http://data-syncer:8228 │ true │ available | 5130 │ 5.13.0 │
│ simplequeue │ anchore-quickstart │ http://queue:8228 │ true │ available │ 5130 │ 5.13.0 │
│ notifications │ anchore-quickstart │ http://notifications:8228 │ true │ available │ 5130 │ 5.13.0 │
│ catalog │ anchore-quickstart │ http://catalog:8228 │ true │ available │ 5130 │ 5.13.0 │
└─────────────────┴────────────────────┴─────────────────────────────┴──────┴────────────────┴────────────┴──────────────┘
Note: If specific services are down, you can investigate the logs for the services. For more information, see Viewing Logs.
The -vvv and –json options
Passing the -vvv option to AnchoreCTL can often help narrow down particular issues by displaying the client configuration and client functions as they are running:
# Example system status with -vvv
# anchorectl -vvv system status
[0000] INFO anchorectl version: 5.13.0
[0000] DEBUG application config:
url: http://localhost:8228
username: admin
password: '******'
...
[0000] DEBUG command config:
format: text
[0000] DEBUG checking if new version of anchorectl is available
[0000] TRACE worker stopped component=eventloop
[0000] TRACE bus stopped component=eventloop
┌─────────────────┬────────────────────┬─────────────────────────────┬──────┬────────────────┬────────────┬──────────────┐
│ SERVICE │ HOST ID │ URL │ UP │ STATUS MESSAGE │ DB VERSION │ CODE VERSION │
├─────────────────┼────────────────────┼─────────────────────────────┼──────┼────────────────┼────────────┼──────────────┤
│ analyzer │ anchore-quickstart │ http://analyzer:8228 │ true │ available │ 5130 │ 5.13.0 │
│ policy_engine │ anchore-quickstart │ http://policy-engine:8228 │ true │ available │ 5130 │ 5.13.0 │
│ apiext │ anchore-quickstart │ http://api:8228 │ true │ available │ 5130 │ 5.13.0 │
│ reports │ anchore-quickstart │ http://reports:8228 │ true │ available │ 5130 │ 5.13.0 │
│ reports_worker │ anchore-quickstart │ http://reports-worker:8228 │ true │ available │ 5130 │ 5.13.0 │
│ data_syncer │ anchore-quickstart │ http://data-syncer:8228 │ true │ available | 5130 │ 5.13.0 │
│ simplequeue │ anchore-quickstart │ http://queue:8228 │ true │ available │ 5130 │ 5.13.0 │
│ notifications │ anchore-quickstart │ http://notifications:8228 │ true │ available │ 5130 │ 5.13.0 │
│ catalog │ anchore-quickstart │ http://catalog:8228 │ true │ available │ 5130 │ 5.13.0 │
└─────────────────┴────────────────────┴─────────────────────────────┴──────┴────────────────┴────────────┴──────────────┘
Passing the --json option to AnchoreCTL commands will output the API response data in JSON, which often contains much more information than what the CLI outputs by default for both regular successful operations, and for operations that are resulting in an error:
# anchorectl -o json system status
✔ Status system
{
"serviceStates": [
{
"baseUrl": "http://reports_worker:8228",
"hostid": "anchore-quickstart",
"serviceDetail": {
...
...