New Coal setup unhealth

Triton Compute
1

I have setup Coal to test out Triton on an Ubuntu laptop. It’s up and running but I’m presented with the following after the initial setup when running sdcadm health.

[root@headnode (coal-1) ~]# sdcadm health
INSTANCE SERVICE HOSTNAME ALIAS HEALTHY

  •     -        headnode  -      false

    Type: triton
    Hostname: headnode
    Error: Binder service seems to be down. Please review it before proceeding: sapi client error: No backends available in pool e0abee7c-7f5a-4e77-a28d-2989adfed64e (sapi.coal-1.example.com)
    Error: –
    Error: Triton is experiencing severe errors that prevent detailed health checks
    sdcadm health: error: Some instances appear unhealthy

I’ve looked at svcs but can’t find the binder service. How does one look for the source of this error?

2

Disregard. All appears to be health at this time.

2 Likes