Kibana: Difference between revisions

From Leo's Notes
This page was last edited on 14 June 2020, at 23:58.
Created page with " == Troubleshooting == Kibana does not start. Container logs show {{highlight|lang=terminal|code= {"type":"log","@timestamp":"2019-09-03T18:12:45Z","tags":["info","optimize"..."
 
m Added categories
 
(2 intermediate revisions by the same user not shown)
Line 9: Line 9:


The first process spawns 2 additional node processes that uses a lot of CPU before eventually dying. This process starts over and over. Kibana only serves "Not Found" to any requests made to it via port 5601.
The first process spawns 2 additional node processes that uses a lot of CPU before eventually dying. This process starts over and over. Kibana only serves "Not Found" to any requests made to it via port 5601.
This occurred when processes were running as non-root. Attempting to run Kibana as a root container has the same result.
=== Solution ===
If the node process gets a SIGKILL, it most likely means it ran into a memory limitation set by the container. Raise the resource limits and try again. This fixed it for me.
{{Navbox Linux}}[[Category:Linux]]
[[Category:LinuxUtilities]]
[[Category:Containers]]

Latest revision as of 23:58, 14 June 2020


Troubleshooting

Kibana does not start. Container logs show

{"type":"log","@timestamp":"2019-09-03T18:12:45Z","tags":["info","optimize"],"pid":1,"message":"Optimizing and caching bundles for opendistro-alerting, security-login, security-customerror, security-multitenancy, security-accountinfo, security-configuration, kibana, stateSessionStorageRedirect, status_page and timelion. This may take a few minutes"}
Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist`

The first process spawns 2 additional node processes that uses a lot of CPU before eventually dying. This process starts over and over. Kibana only serves "Not Found" to any requests made to it via port 5601.

This occurred when processes were running as non-root. Attempting to run Kibana as a root container has the same result.

Solution

If the node process gets a SIGKILL, it most likely means it ran into a memory limitation set by the container. Raise the resource limits and try again. This fixed it for me.