You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 14, 2022. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -509,6 +509,20 @@ When Elasticsearch is finally started:
509
509
```
510
510
Status YELLOW is expected when running Elasticsearch on a single node, as it can achieve the desired replicas. You may use Kibana Development tools or curl to get additional information.
511
511
512
+
### vm.max_map_count is too low
513
+
```
514
+
ERROR: [1] bootstrap checks failed
515
+
[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
516
+
```
517
+
Run the following to set it temporarly:
518
+
`sudo sysctl -w vm.max_map_count=262144`
519
+
Or the following:
520
+
```
521
+
1. sudo vi /etc/sysctl.conf
522
+
2. add vm.max_map_count=262144
523
+
3. sudo service sysctl restart
524
+
```
525
+
512
526
#### No results from Elasticsearch
513
527
If you don't get any results from ElasticSearch for valid queries it might be a missing template configuration for the logstash-openlog index. Elastic-Search is doing by default a dynamic template mapping that is trying to figure out field types. However, for some of the fields the mapping must be overwritten. Therefore make sure so to include the sample mapping file: `configs/openlog_index_template.json` is used by your Logstash process. See `configs/logstash.conf` as an example.
514
528
The template mapping is pre-configured when using the docker-compose configuration.
0 commit comments