Operations¶
Review the known issues for this version, protect your state and diagnose problems without exposing credentials or customer data.
Known issues and maintenance¶
This guide covers package version 0.1.22, a source build of Typesense 30.2. Complete unfiltered scans on 18 October 2026 retain 104 Critical and 680 High raw host matches on kernel identities, with no ignored findings. The native inventory of the 28 libraries statically linked into the server reports zero Critical and three High matches: two protobuf 21.12 advisories fixed only in later major protobuf lines and one zlib 1.3.2 advisory without a fixed release. The runtime inventory reports zero High/Critical matches. These are scanner matches, not distinct proven exploitable vulnerabilities. Libraries vendored inside those 28 components are not separately inventoried, and the full local security gate has not passed.
Compared with the upstream 30.2 release, this build links OpenSSL 3.5.9, curl 8.23.0, zlib 1.3.2, libarchive 3.8.10, protobuf 21.12 and SentencePiece 0.2.1. The upstream versions carried Critical advisories, and package 0.1.22 moves SentencePiece from 0.1.98 to 0.2.1 for CVE-2026-1260. The CLIP tokenizer is not included because its source has no published licence grant, so CLIP embedding models are rejected.
Package 0.1.22 includes the customer launch, access and hands-on instructions under /opt/sushi/docs/README.md and /opt/sushi/docs/DEMO.md. Single-instance persistence is not high availability or a backup.
4. Protect state and plan upgrades¶
Application state is under /var/lib/typesense; server configuration and private identity are under /etc/typesense. Preserve those together with /home/ubuntu/.config/sushi/typesense and any customer input/output directories. Treat backups containing credentials, documents, audio, metrics or repositories as private data. A single local EBS volume is not a redundant service or a backup.
For a consistent backup, finish active requests, stop the owning services below and take an encrypted EBS snapshot or protected file backup using your approved procedure. Preserve ownership and permissions. Start the same services afterwards and verify readback. Test restoration on a separate instance before replacing the original.
sudo systemctl stop typesense.service sushi-typesense-api.service
# Take and verify your protected backup while the services are stopped.
sudo systemctl start typesense.service sushi-typesense-api.service
A new Marketplace version does not update an existing instance. Launch the replacement separately, check state-format compatibility, restore only required customer state and verify your own read/write workflow before cutover. Keep a protected backup until the replacement is confirmed. Never erase a server identity as a routine upgrade step.
The generated self-signed TLS certificate expires after 365 days. Arrange an operator-reviewed certificate replacement before expiry, updating the client trust from the authenticated instance. Public DNS and certificate renewal automation are not included.
5. Diagnose a problem¶
sudo systemctl show typesense.service sushi-typesense-api.service -p ActiveState -p SubState -p NRestarts
sudo journalctl -u typesense.service -u sushi-typesense-api.service --no-pager -n 50
Inspect logs privately. Before sharing a support case, remove credentials, private hostnames and all customer content; include the Marketplace version, failing operation and a small invented reproduction. For connection errors, verify the correct Region/instance, Session Manager permissions, network endpoints and the active forwarding session. For input errors, check the package limits and request schema first. Do not install arbitrary replacement packages or delete customer state to force a retry.
Use the Software Sushi support contact and terms on the purchased Marketplace offer. Typesense documentation explains the upstream project; it is not a support commitment from that project for this package.
Last updated October 18, 2026 · Suggest an improvement