Hi Team, I am facing issues with typesense contai...
# community-help
v
Hi Team, I am facing issues with typesense container ,keeps on terminating after server restart. I have attached the logs , need support to start the container with existing data. 2026-04-01 103334 E20260401 050334.554198 1 store.cpp:57] If you are SURE that this is not the case, delete the LOCK file in the data db directory and try again. 2026-04-01 103336 E20260401 050336.632982 1 backward.hpp:4200] Stack trace (most recent call last): 2026-04-01 103336 E20260401 050336.633023 1 backward.hpp:4200] #7 Object "", at 0xffffffffffffffff, in 2026-04-01 103336 E20260401 050336.633028 1 backward.hpp:4200] #6 Object "/opt/typesense-server", at 0x55ff07deb02d, in _start 2026-04-01 103336 E20260401 050336.633034 1 backward.hpp:4200] #5 Object "/usr/lib/x86_64-linux-gnu/libc.so.6", at 0x7fa95b743e3f, in __libc_start_main 2026-04-01 103336 E20260401 050336.633038 1 backward.hpp:4200] #4 Object "/usr/lib/x86_64-linux-gnu/libc.so.6", at 0x7fa95b743d8f, in 2026-04-01 103336 E20260401 050336.633042 1 backward.hpp:4200] #3 Source "src/main/typesense_server.cpp", line 236, in main [0x55ff07df662d] 2026-04-01 103336 E20260401 050336.633046 1 backward.hpp:4200] #2 Source "src/typesense_server_utils.cpp", line 659, in run_server [0x55ff08311608] 2026-04-01 103336 E20260401 050336.633050 1 backward.hpp:4200] #1 Source "src/natural_language_search_model_manager.cpp", line 142, in init [0x55ff082110dd] 2026-04-01 103336 E20260401 050336.633054 1 backward.hpp:4200] #0 Source "src/store.cpp", line 144, in scan_fill [0x55ff082a2c98] 2026-04-01 103336 Segmentation fault (Address not mapped to object [(nil)]) 2026-04-01 103337 E20260401 050337.002712 1 typesense_server.cpp:171] Typesense 30.0 is terminating abruptly.
f
Hey @V Parthiban , This looks like a RocksDB lock conflict during startup. Typesense opened the code path that scans the DB, but the store had already failed to open because the db/LOCK file was present, which usually means either another Typesense process is already using the same —data-dir or a previous crash left a stale lock behind. You'll have to check the exact data directory the server is using, then confirm whether anything still has that directory open:
Copy code
ps -ef | grep typesense
Copy code
lsof +D /path/to/data-dir/db
Copy code
fuser -vm /path/to/data-dir/db
and if this is on docker:
Copy code
docker ps plus docker inspect <container> --format '{{json .Mounts}}'
to verify two containers are not sharing the same volume. If no live process is holding it, inspect the lock and DB dir with:
Copy code
ls -la /path/to/data-dir/db​
and only then remove LOCK after stopping the server completely. ​
✅ 1