From b2c36cf7e1a3c44628b4698d4703b27740e86bde Mon Sep 17 00:00:00 2001 From: decentral1se Date: Mon, 18 Jul 2022 11:45:33 +0200 Subject: [PATCH] docs: fixing broken es for auto-complete --- README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/README.md b/README.md index 5c7f400..649569e 100644 --- a/README.md +++ b/README.md @@ -58,3 +58,20 @@ tootctl accounts create --email --confirmed --role admin Mastodon expects secrets generated by specific tools. Uou can run these commands via the scripts interface with `abra`. `abra app cmd secrets --local` + +## Tips & Tricks + +### Auto-complete is not working? + +Check the [sidekiq logs](https://social.lumbung.space/sidekiq/retries), is a bunch of stuff failing? What is the error? + +If it looks anything like `blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];` then it might mean that your elastic search service has put itself into "read-only" state. This could be due to running close to no free disk space one time. ES doesn't undo this state, even when you have more free disk space once more, so you need to handle this manually: + +``` +abra app run es bash +curl -XPUT -H "Content-Type: application/json" http://localhost:9200/_all/_settings -d '{"index.blocks.read_only_allow_delete": null}' +``` + +Then head back to the sidekiq retries panel and retry one job. You should see +the ticket of retries go down by one if if passed. Then you can "retry all" and +they should get scheduled & run.