Administration - Installation - Core: Re (2): Lucene search problem: write lock

Thanks for the hint :) Yes, the newstart of ilserver will delete the index and if the cronjob starts again, rebuilt it. I found out that write.lock is not a problem, its normal. I was not patient enough, becaus after some minutes, it starts indexing. I think, I could resolve at least one problem:

in /etc/mysql/mysql.conf.d/mysqld.cnf I addes two values:

wait_timeout=7200

interactive_timeout=7200

After that, the indexfile became much bigger (raised from 80M to 400M). But there could the another error that I found in the log. When I look at this:

2020-12-21 20:47:40,445 WARN  Thread-33 (DocumentDefinition.java:142) - de.ilias.services.lucene.index.DocumentHandlerException: de.ilias.services.lucene.index.file.path.PathCreatorException: Cannot find file: /opt/iliasdata/iliasschoolmaster/ilFile/10/62/file_106240/B1WINA Stundentafel.pdf

2020-12-21 21:08:08,619 WARN  XML-RPC-1 (RPCSearchHandler.java:158) - org.apache.lucene.index.IndexNotFoundException: no segments* file found in MMapDirectory@/opt/iliasdata/lucene/iliasschoolmaster_8484 lockFactory=org.apache.lucene.store.NativeFSLockFactory@71c45c0c: files: [_g.fdt, _g.fdx, _h.fdt, _h.fdx, _i.fdt, _i.fdx, write.lock]

2020-12-22 08:11:05,659 WARN  XML-RPC-1 (RPCSearchHandler.java:158) - org.apache.lucene.index.IndexNotFoundException: no segments* file found in MMapDirectory@/opt/iliasdata/lucene/iliasschoolmaster_8484 lockFactory=org.apache.lucene.store.NativeFSLockFactory@71c45c0c: files: [_g.fdt, _g.fdx, _h.fdt, _h.fdx, _i.fdt, _i.fdx, write.lock]

It seems:

• There was a PDF that the indexer did not found


• Then it says: no segments* file


• And it starts indexing in the morning (should be triggert via cron) again and fails again with no segments* file

The missing file B1WINA Stundentafel.pdf was there, but in a folder 001. So I decided to copy it ohne level higher so that the indexer can find it. I am not shure if this was brilliant.