generated from coop-cloud/example
This commit is contained in:
parent
c65ea6663e
commit
910958b6a8
22
README.md
22
README.md
@ -37,3 +37,25 @@ And finally, within the `app` container, create an admin account:
|
||||
```
|
||||
abra app cmd <domain> admin "<username>" "<email>"
|
||||
```
|
||||
|
||||
## Admin tips & tricks
|
||||
|
||||
### Auto-complete is not working?
|
||||
|
||||
Check the sidekiq logs (`/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 <domain> 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.
|
||||
|
Loading…
x
Reference in New Issue
Block a user