One suggestion I'd make is to check that ElasticSearch is not out of disk space. The default setup can result in large log files that may need to be cleared, depending on usage. It is possible that restarting the container may help, but it might require manual action as well.

You can use 'docker ps' to check that the updater is running steadily and not repeatedly restarting, while tools such as 'df -h' and 'du -h -d 1' can be used to try to narrow down usage. 'docker logs --tail -n 50 (container)' may help with logs.

MediaWiki/WB 1.36 is quite old and no longer supported by Wikimedia, having both security and (I think, in Wikibase) performance deficiencies compared to the current LTS 1.39 version:

It might be worth upgrading to the current version and seeing if that improves the situation. Note that 1.40 is not yet close to ready - https://phabricator.wikimedia.org/T340939 - but the 1.39.4 security release is being prepared: https://phabricator.wikimedia.org/T332786

From: Aidan Hogan <aidhog@gmail.com>
Sent: Tuesday, September 5, 2023 3:24:01 PM
To: wikibaseug@lists.wikimedia.org <wikibaseug@lists.wikimedia.org>
Subject: [Wikibase] Wikibase: CirrusSearch not indexing new items

Hi all,

Running a Docker instance of Wikibase (wikibase:1.36.3-wmde.4), I've
noticed that CirrusSearch has stopped indexing new items. Everything
seems to be fine: the ElasticSearch container is up and running,
searches over legacy content work as expected, but searches over new
content do not yield results. Previously there was no problem.

As mentioned, I've not managed to find anything out of place, so if
there were any quick hints on where to look (in what container, log,
etc.) to debug indexing new items in CirrusSearch/ElasticSearch, I would
greatly appreciate it.

Best,
Aidan
_______________________________________________
Wikibase Community User Group mailing list -- wikibaseug@lists.wikimedia.org
To unsubscribe send an email to wikibaseug-leave@lists.wikimedia.org