Troubleshooting¶
Resolve service startup, search, vector-field, and persistence problems.
A service is not active¶
Fix:
sudo cloud-init status --wait
sudo -iu ubuntu
sudo systemctl is-active typesense.service sushi-typesense-api.service
sudo journalctl -u typesense.service -u sushi-typesense-api.service --no-pager -n 50
Do not recreate the instance identity to force a retry.
Search does not return the test product¶
Cause: the query, collection name, or filter does not match the document
you inserted. The documented example searches cofee against a product
named Coffee beans with price 12 and expects found of 1.
Fix: repeat the example in
Getting started with a new collection name.
Use sushi-typesense-api. Do not print the native API key.
CLIP or a vector field is rejected¶
Cause: this build does not include CLIP embedding models.
Fix: use the string and int32 fields from the example. Do not add a vector model the package rejects.
Data is missing after reboot¶
Cause: the collection was deleted, or state was restored without
/etc/typesense and /home/ubuntu/.config/sushi/typesense.
Fix: keep the same collection for a readback. Do not re-import it to
test persistence. Restore /var/lib/typesense together with the identity
directories. See Operations.
Last updated November 1, 2026 · Suggest an improvement