Skip to content
HyperlakeHyperlake

Troubleshooting

Command not found or stale behavior

Section titled “Command not found or stale behavior”
Terminal window
hyperlake version
npx @cerebrixos/hyperlake@0.2.6 version
python3 -m pip show hyperlake

Ensure the shell is invoking the intended binary with which hyperlake.

No clusters appear

Section titled “No clusters appear”
Terminal window
hyperlake auth whoami
hyperlake clusters list --json

Confirm the authenticated tenant and that the user has target visibility. A successful login does not imply access to every cluster.

MCP client cannot connect

Section titled “MCP client cannot connect”

Run hyperlake mcp serve --stdio directly and confirm that stdout contains only protocol traffic. Check client logs on stderr and verify that the client launches the same binary shown by which hyperlake.

Query or policy failure

Section titled “Query or policy failure”

Discover the catalog, schema, table, and grant status first. A semantic model can identify a dimension or metric without granting permission to query its source.

When reporting an issue, include command name, CLI version, request ID, status code, and redacted error text. Never include tokens, credential values, kubeconfigs, or full query results containing sensitive data.