./scripts/reset-elastic.sh not working

[MilanLamote]

In order to reset the search indexes I've tried running the suggested script (./scripts/reset-elastic.sh). But the behaviour is unexpectedly fast and ends with an error in the webapp "search" page. Script output

warning this will run queries on the triplestore and delete containers, you have 5 seconds to press ctrl+c [+] Running 2/2 ✔ Container vocabserver-app-elasticsearch-1 Stopped 0.6s ✔ Container vocabserver-app-search-1 Stopped 0.4s [vocabserver-app-elasticsearch-1 vocabserver-app-search-1] Going to remove vocabserver-app-elasticsearch-1, vocabserver-app-search-1 [+] Running 2/0 ✔ Container vocabserver-app-search-1 Removed 0.0s ✔ Container vocabserver-app-elasticsearch-1 Removed 0.0s rm: cannot remove 'config/elasticsearch/update-handler.store': No such file or directory OpenLink Virtuoso Interactive SQL (Virtuoso) Version 07.20.3233 as of Nov 24 2021 Type HELP; for help and EXIT; to exit. SQL> Connected to OpenLink Virtuoso Driver: 07.20.3233 OpenLink Virtuoso ODBC Driver Done. -- 2 msec. SQL> Done. -- 87 msec. [+] Running 14/14 ✔ Container vocabserver-app-search-1 Started 2.4s ✔ Container vocabserver-app-elasticsearch-1 Started 0.9s ✔ Container vocabserver-app-database-1 Running 0.0s ✔ Container vocabserver-app-frontend-1 Running 0.0s ✔ Container vocabserver-app-content-unification-1 Running 0.0s ✔ Container vocabserver-app-delta-notifier-1 Running 0.0s ✔ Container vocabserver-app-resource-1 Running 0.0s ✔ Container vocabserver-app-triplestore-1 Running 0.0s ✔ Container vocabserver-app-vocab-fetch-1 Running 0.0s ✔ Container vocabserver-app-ldes-consumer-manager-1 Running 0.0s ✔ Container vocabserver-app-dispatcher-1 Running 0.0s ✔ Container vocabserver-app-migrations-1 Running 0.0s ✔ Container vocabserver-app-identifier-1 Running 0.0s ✔ Container vocabserver-app-uuid-generation-1 Running

Screenshot of "search" page after running script.

Rebuilding and restarting all containers fixes the error but I don't think any reindexing has happened.

Can you advice?

[nvdk]

Hi @Milan-VLIZ,

After running the reset script it takes quite some time for the index to rebuild. Could it be you checked immediately after running the script? I'd recommend running the script and following up the reindex process in the search containers logs with docker compose logs -f --tail 100 search. The process is likely to take several hours for a large dataset.

[MilanLamote]

Okay, my bad. I see things moving.

Thanks for the heads-up