Start order of processes
-
Trying to figure out the correct start order:
If i start first kopano-server it complains about missing kopano search.
If i start first kopano-search it complains about missing kopano-server (MAPI errors)
Both variants are flooding the logs.Kind regards,
Thomas -
@hooge change the debug level?
search - INFO - starting search
2022-01-16 11:04:49,621 - search - WARNING - could not connect to server at ‘default:’, retrying in 5 sec
2022-01-16 11:04:55,087 - search - INFO - found previous server sync state: XXX
2022-01-16 11:04:55,171 - search - INFO - starting incremental sync
2022-01-16 11:04:55,197 - query - INFO - listening on socket file:///var/run/kopano/search.sockmore it is not at each server start on search engine
my start is
search and after the
server -
Server first. Server will create the socket for Search to connect to.
I do it in this order and don’t see much noise filling up my logs, but there also isn’t that much of a delay for getting all the necessary services started. You could perhaps take a page out of some of the work that people do with docker continaners and test port/socket availability before the service starts.
-
As long all your services are able to start they will connect and get going.
Not an issue as long your server is truly able to reboot ok.
It will show in logs it can’t connect, but only for a few seconds, then it connects.
Personally I would stick to the original way the services are installed through the packages. But who knows if there’s a very good way to sort the order of startup, I’d like to try it in test.
-
In my opinion this is bad behaviour.
It’s not only “a few seconds”, loading search folders can be up to 10 minutes with our database size.
There should be some logic for server (re-)starts.
