Troubleshooting Typesense Server Error on Docker
TLDR vikram was facing an error with Typesense Server Docker container and loss of data on restart. Kishore Nallan guided to avoid mounting tmp directory from localhost and explained stopping the Docker container.
2
Nov 01, 2022 (11 months ago)
vikram
09:39 AMI20221101 09:36:09.182243 110 raft_server.cpp:479] Loading collections from disk...
I20221101 09:36:09.182246 110 collection_manager.cpp:132] CollectionManager::load()
E20221101 09:36:09.262549 85 typesense_server.cpp:95] Typesense 0.23.1 is terminating abruptly.
Kishore Nallan
09:54 AMvikram
09:56 AMKishore Nallan
09:59 AMvikram
10:43 AME20221101 10:36:50.559542 84 backward.hpp:4199] #5 Object "", at 0xffffffffffffffff, in
E20221101 10:36:50.559551 84 backward.hpp:4199] #4 Object "/lib/x86_64-linux-gnu/libc-2.23.so", at 0x7efdfabcd51c, in __clone
E20221101 10:36:50.559557 84 backward.hpp:4199] #3 Object "/lib/x86_64-linux-gnu/libpthread-2.23.so", at 0x7efdfb5ac6b9, in start_thread
E20221101 10:36:50.559805 84 backward.hpp:4199] #2 Source "../../../../../libstdc++-v3/src/c++11/thread.cc", line 80, in execute_native_thread_routine [0x14ac6cf]
E20221101 10:36:50.559813 84 backward.hpp:4199] #1 Source "/typesense/src/batched_indexer.cpp", line 123, in run [0x50c1b6]
E20221101 10:36:50.559814 84 backward.hpp:4199] #0 Source "/typesense/include/store.h", line 169, in scan [0x512145]
Segmentation fault (Address not mapped to object [(nil)])
Kishore Nallan
10:49 AMvikram
10:49 AMvikram
10:50 AMKishore Nallan
10:50 AMKishore Nallan
10:51 AMvikram
10:51 AMvikram
10:54 AMKishore Nallan
10:58 AMvikram
10:59 AMKishore Nallan
11:16 AMvikram
11:33 AM2
Typesense
Indexed 2779 threads (79% resolved)
Similar Threads
Running Typesense in Docker Container on Windows 10
Christian had issues running Typesense in Docker due to an unrecognized data directory. Jason suggested a solution to fix the file path issue, which Christian successfully implemented using Windows Powershell.
"Resolving Startup Issue with Typesense Single Replica Set in Local `K8s` Setup"
Vishal encountered issues starting a Typesense single replica set due to directory permission issues. Kishore Nallan suggested checking if the volume was accessible for writes. Vishal resolved the problem by adjusting permissions on the host.
Trouble Running Typesense Docker Image on AMD Phenom II X4 955 Processor
Ian struggles to run Typesense on an AMD Phenom II X4 955 Processor, experiencing the docker image to shut down immediately upon startup. Jason and Kishore Nallan suggest multiple troubleshooting steps, identifying the potential issue as the processor's lack of support for MSSE4 flags.
Trouble with Typesense Memory Usage when Restarting Docker Container
Blend reports increased memory usage when restarting Docker with Typesense, information shared with Jason and Kishore Nallan. Potential data edge case identified as potential cause, although resolution undetermined.
Typesense Issues in Kubernetes Environment
siva.sunkara experienced Typesense issues in Kubernetes and shared logs. Kishore Nallan recommended stand-alone nodes and shared a Github issue thread. Sergio suggested fine-tuning Kubernetes deployment and linked to a working setup.