Kopano-search running for couple of hours then kopano-server crashes

fbartels

@ckruijntjens said in Kopano-search running for couple of hours then kopano-server crashes:

A question can we see how far indexing is somehow??

No, that is not possible.

Hi is there Some wat then to tell when indexing is finishes? When i gestart my server Will iT pick up where iT is left or is iT starting from the begining?

fbartels

Once indexing has finished kopano-search will create the search socket. if you stop search during indexing it will continue from where it stopped.

@fbartels

hi and thank you for your reply. where should this file be created?

fbartels

By default /var/run/kopano/search.sock

fbartels

@ckruijntjens said in Kopano-search running for couple of hours then kopano-server crashes:

kopano-server-8.6.82.110-117.1.x86_64
kopano-search-8.6.82.110-117.1.x86_64

this version is already more than a week old. Can you check if you also have the same issue with the most recent build?

mark dufour

would it be possible to try and run valgrind on kopano-server, for a few minutes (note that it will become like 10 times slower)? we use valgrind internally to look for leaks, but unfortunately we can’t cover every possible situation, so it would be much appreciated if you could give this a try. usually if there’s any leak (not “unbounded allocation”), valgrind will find it.

@mark-dufour

Hi i Will try this and report the outcome. Wat is best for performance attachments inside database or outside?

fbartels

Definitely outside the database

@fbartels

Hi can i stil switch to outside database? Without losing everything?

fbartels

https://documentation.kopano.io/kopanocore_administrator_manual/upgrading.html#migrating-database-attachments-to-files