SOLVED: Seafile 7.0.10 Search index won't update

Firstly the file search worked after updating from Seafile v6.3 to v7.0. Then I noticed (sometine between v7.0.4 und v7.0.6) that the newer Files were not being indexed and therefor could not be found. After alle the tips here in the forum (clearing index & updating etc.) it nows seems that I have a empty index.

In seafile the search results are always empty.

Even tried using a extern elasticsearch server, brings no results.

I’ve also tested:
mysql-db with ""mysqlcheck -u root -p --all-databases --auto-repair
&
REPOs with “./seaf-fsck.sh”

no errors found.

System ist a aktual Ubuntu 18.04 LTS. + Java 8.

Does anybody have a idea why i can’t update the search index?

Here ist the LOG File from “./pro//pro.py search --update”

Hey Chris.Piel,
I am sorry I would like to help you but may I ask you first for some more information? Can you please check the following, then I will most likely be capable to say what the problem is:

Here are my questions:

  • ubuntu 18.04 + java 8. How much ram did your machine has?
  • how did you start seafile? Did you start it with systemd or with seafile.sh start and seahub.sh start? If it is systemd please post your seafile.service
  • please post netstat -tulpn. Are there entries with the port 9200 and 9300?
  • here is what should happen. Please confirm what happens and what not:
  1. you start seafile
  2. after some seconds a elasticsearch.pid file is created in seafile-dir/pids
  3. watch the pid number inside this file. Is this pid always the same or does it change after a while?
  4. what is posted in seafile-dir/logs/elasticsearch.log. Can you see something like that? What happens after the initializing? Does some errors occur or does it end with
[2019-11-11T06:37:50,537][INFO ][o.e.n.Node               ] [] initializing ...
... what happens here ...
[2019-11-11T08:31:54,454][INFO ][o.e.g.GatewayService     ] [qToqAXT] recovered [2] indices into cluster_state
[2019-11-11T08:31:57,046][INFO ][o.e.c.r.a.AllocationService] [qToqAXT] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[repo_head][2]] ...]).
  1. please check ps aux | grep java. Is there only one java process or are the two or more? It should look like

root@seafile-demo:/home/seafile/logs# ps aux | grep java seafile 1626 1.3 37.1 3201428 760380 ? Sl 08:31 0:30 /usr/bin/java -Xms512m -Xmx1g -XX:-AssumeMP -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+AlwaysPreTouch -server -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -Djdk.io.permissionsUseCanonicalPath=true -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j.skipJansi=true -XX:+HeapDumpOnOutOfMemoryError -Des.path.home=/home/seafile/seafile-pro-server-7.0.10/pro/elasticsearch -cp /home/seafile/seafile-pro-server-7.0.10/pro/elasticsearch/lib/* org.elasticsearch.bootstrap.Elasticsearch -Epath.logs=/home/seafile/logs -Epath.data=/home/seafile/pro-data/search/data -Enetwork.host=127.0.0.1 -p /home/seafile/pids/elasticsearch.pid root 3921 0.0 0.0 15792 936 pts/0 S+ 09:10 0:00 grep --color=auto java

If you could answer me these questions I am quite sure I will be capable to tell you where the problem is.

Best regards
Christoph

I am testing seafile deployment on buster with the OS java jdk 11. Do we still have to stay with a very old java version for the file search to work properly?

Hello Christoph,

As I was gathering the information that you asked for and comparing the jave process options with yours, I discoverd that mine was corrupt. After I corerct the configuation und a seafile restart, I was able to update the Index with no errors. I have no Idea where or how the configutation got corrupted, it seemed to work at least, PID and java process started.

Thanks for your help.

regards
Chris