Running Typesense Server as a Daemon via Systemd
TLDR Albert struggled with keeping a Typesense service running after terminal closure. Jason clarified that this is normal behaviour and advised running the server as a daemon via systemd, subsequently linking the documentation for correct setup, which solved Albert's issue.
Dec 02, 2021 (25 months ago)
Albert
07:05 PM
Jason
07:07 PMtypesense-server runs in the foreground, and the terminal kills all processes that were started through it when you exit. You instead want to run typesense-server as a daeomon through a process manager like systemd (at least on Linux)Jason
07:07 PMJason
07:16 PMAlbert
07:18 PMJason
07:18 PMJason
07:19 PMAlbert
10:18 PMJason
10:20 PM
Typesense
Indexed 3011 threads (79% resolved)
Similar Threads
Resolving Connection Issues on Ubuntu 21.10
Philipe faced a problem with TypeSense running on Ubuntu 21.10. After troubleshooting, Jason and Kishore Nallan suggested a binary to solve the compatibility issue, which resolved the issue.
Discussion About Typesense Nodes Not Synchronizing Correctly
Erick experienced an issue where documents weren't updated properly in a Typesense instance running on 3 nodes. Upon requesting debug logs and configs, Jason identified that these nodes weren't part of the same cluster. They couldn't resolve the nodes' failure to connect issue and recommended a fresh installation.
Problem with Loading Records on Typesense Server
Rafael had an issue with Typesense server loop during startup after loading 8M of 15M records. Kishore Nallan identified the issue as memory shortage and advised Rafael to allocate more server memory.
Installing and Running Typesense Server on Fedora 35
User Edson struggled to initiate Typesense server. Jason suggested using the RC build for Fedora 35. After troubleshooting and following instructions, Edson was finally able to start their server. They discussed the need for clearer installation documentation since it was an incompatibility issue with Fedora 35.
Debugging Typesense API Key Error
James is getting an error related to the `x-typesense-api-key` header in their Typesense project. Harrison suggests passing the API key in the HTTP header, and Jason advises checking the key via curl and possibly closing a duplicate Typesense server.