Hello Seafile community !
I am running Seafile Pro 7.1.7 under Debian (up to date Buster version) in a cluster configuration. We do have separated roles on different servers (Front, DB, S3 Storage, Memcached and maintenance). The server I am talking about is the maintenance server.
I am trying to be as specific as possible but I think it would be the same thing on a single server environment.
On this server, the
controller.log file keeps filling up with this :
[04/13/21 15:52:04] seafile-controller.c(130): spawned /opt/seafile/seafile-pro-server-7.1.7/pro/elasticsearch/bin/elasticsearch, pid 6029 [04/13/21 15:52:23] seafile-controller.c(585): pid file /opt/seafile/pids/elasticsearch.pid does not exist [04/13/21 15:52:23] seafile-controller.c(633): elasticsearch need restart... [04/13/21 15:52:23] seafile-controller.c(96): spawn_process: /opt/seafile/seafile-pro-server-7.1.7/pro/elasticsearch/bin/elasticsearch -Epath.logs=/opt/seafile/logs -Epath.data=/opt/seafile/pro-data/search/data -Enetwork.host=0.0.0.0 -p /opt/seafile/pids/elasticsearch.pid
I have seen this post ([SOLVED] Pid file /opt/seafile/pids/seafevents.pid does not exist [Was: 'Bad pidfile format: seafevents.pid']) and tried to install the
pyhton-redis package to solve the problem but it didn’t change anything.
The message keeps being written in the log file every 10 seconds…
Does anyone have an idea about what is happening (the log file is pretty explicit on this matter ) and more importantly how to solve it ?
Thanks for your help