Skip to main content
Version: 1.x

Recovering from failure

If you run into an error when operating wasmCloud, the first step is to diagnose the problem. Typically, this will mean checking three sources of information:

Troubleshooting on Kubernetes​

When deploying wasmCloud on Kubernetes, you can access logs for wasmCloud hosts and wadm with kubectl.

To check logs for wadm:

shell
kubectl logs -f -l app.kubernetes.io/instance=wadm -c wadm

To check logs for a wasmCloud host:

shell
kubectl logs -f -l app.kubernetes.io/instance=my-wasmcloud-cluster -c wasmcloud-host

Observing NATS​

You can observe NATS activity using the NATS CLI. Installation instructions for the CLI are available on the NATS CLI GitHub repo.

To list all streams on the NATS network:

shell
nats stream list

The listed streams for a wasmCloud lattice will include:

  • wadm_commands
  • wadm_events
  • wadm_mirror
  • wadm_notify
  • wadm_status

To list all key-value buckets on the NATS instance:

shell
nats kv list

The listed key-value buckets for wasmCloud will include:

  • CONFIGDATA_default
  • wadm_manifests
  • wadm_state
  • LATTICEDATA_default