Skip to content

Common Issues

Jump to bottom
msadministrator edited this page May 13, 2021 · 4 revisions

Common Issues

This section provides some traditional situations that may arise and how to handle them:

First Time Use

When trying to access Kibana for the first time, it may take several minutes for you to receive a response. If Kibana is working, you should see server not up yet when access the Kibana UI.

ELASTICSEARCH exited with code 137 Error

If you receive this error while on macOS you may need to do two different things:

  1. Update your Docker Desktop application resources to 4GB of memory
  2. Modify the .env ELASTICSEARCH_HEAP to 2g or more based on the allocated memory (half of it)

Run docker-compose up again and see if this resolves the issue.

Browser Access

Since we are generating self-signed certificates you may get a browser warning (especially Chrome) that the site is unsafe. If you select continue you may not be able to continue until you type thisisunsafe while the tab is selected. There is not place to enter this information, you actually just type it in and it will trust this certificate for this browser session. Please see this great blog post here

TOO_MAN_REQUEST Error

If you receive the following error:

Unexpected response code [429] from calling PUT https://0.0.0.0:9200/_security/user/apm_system/_password?pretty
Cause: index [.security-7] blocked by: [TOO_MANY_REQUESTS/12/index read-only / allow delete (api)];

It may be that you system does not have enough resources or disk space so you can run the following to fix it or increase your resources:

PUT .security-7/_settings
{
    "index": {
        "blocks": {
            "read_only_allow_delete": "false"
        }
    }
}

Upgrading

When upgrading you need to ensure that you remove all previous images and containers as well as prune network and volumes on your system or you may run into a incompatiability issues between images. To do this you can run the following commands:

Note: This remove all containers, networks, and volumes already defined on the intended system

docker-compose system prune --all
docker-compose system prune --volumes

At this point you can go through our README again and start it back up

Clone this wiki locally