Trying to install the SG plugin on 6.5.4 gives me a hang
Optimizing and caching browser bundles
I waited for 2 hours and it did not finish. Any workaround?
When asking questions, please provide the following information:
Search Guard and Elasticsearch version
Installed and used enterprise modules, if any
JVM version and operating system version
Search Guard configuration files
Elasticsearch log messages on debug level
Other installed Elasticsearch or Kibana plugins, if any
After the plugin has been installed, Kibana will run the optimization process. Depending on your system this might take a couple of minutes. This is an Kibana internal process required for each installed plugin and cannot be skipped. The Kibana optimization process is shaky and problems are typically not related to Search Guard. Most issues can be resolved by giving the process more memory by setting NODE_OPTIONS="--max-old-space-size=8192". If you are on ES 6.5.x or higher you can also try with --no-optimize (especially if you install the plugin in a Dockerfile). Kibana also currently has a bug in the optimization step if you use X-Pack, but disable reporting. Please check if your Kibana version is affected and correct your kibana.yml accordingly.
Am 25.12.2018 um 01:21 schrieb Adwait Joshi <adwait.joshi@swarganga.org>:
Trying to install the SG plugin on 6.5.4 gives me a hang
Optimizing and caching browser bundles
I waited for 2 hours and it did not finish. Any workaround?
When asking questions, please provide the following information:
* Search Guard and Elasticsearch version
* Installed and used enterprise modules, if any
* JVM version and operating system version
* Search Guard configuration files
* Elasticsearch log messages on debug level
* Other installed Elasticsearch or Kibana plugins, if any--
You received this message because you are subscribed to the Google Groups "Search Guard Community Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to search-guard+unsubscribe@googlegroups.com.
To post to this group, send email to search-guard@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/8ffe667c-d683-4da2-9fc9-c13655af573f%40googlegroups.com\.
For more options, visit https://groups.google.com/d/optout\.
I was able to get around using the no optimize. However now Kibana wont start. I have confirmed Elastisearch is running fine and secured by SG. The Kibana server just gives a message Kibana server is not ready yet. There is no errors in the log files either!
On Tuesday, December 25, 2018 at 4:39:49 AM UTC-5, Search Guard wrote:
After the plugin has been installed, Kibana will run the optimization process. Depending on your system this might take a couple of minutes. This is an Kibana internal process required for each installed plugin and cannot be skipped. The Kibana optimization process is shaky and problems are typically not related to Search Guard. Most issues can be resolved by giving the process more memory by setting NODE_OPTIONS=“–max-old-space-size=8192”. If you are on ES 6.5.x or higher you can also try with --no-optimize (especially if you install the plugin in a Dockerfile). Kibana also currently has a bug in the optimization step if you use X-Pack, but disable reporting. Please check if your Kibana version is affected and correct your kibana.yml accordingly.
https://docs.search-guard.com/latest/kibana-plugin-installation
Am 25.12.2018 um 01:21 schrieb Adwait Joshi adwait...@swarganga.org:
Trying to install the SG plugin on 6.5.4 gives me a hang
Optimizing and caching browser bundles
I waited for 2 hours and it did not finish. Any workaround?
When asking questions, please provide the following information:
- Search Guard and Elasticsearch version
- Installed and used enterprise modules, if any
- JVM version and operating system version
- Search Guard configuration files
- Elasticsearch log messages on debug level
- Other installed Elasticsearch or Kibana plugins, if any
–
You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group.To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.
To post to this group, send email to search...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/8ffe667c-d683-4da2-9fc9-c13655af573f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
As an update, I dont even see the .kibana index being created. But I am able to CURL on the elastic side just fine. All the login names and passwords work for SG.
On Tuesday, December 25, 2018 at 7:55:42 AM UTC-5, Adwait Joshi wrote:
I was able to get around using the no optimize. However now Kibana wont start. I have confirmed Elastisearch is running fine and secured by SG. The Kibana server just gives a message Kibana server is not ready yet. There is no errors in the log files either!
On Tuesday, December 25, 2018 at 4:39:49 AM UTC-5, Search Guard wrote:
After the plugin has been installed, Kibana will run the optimization process. Depending on your system this might take a couple of minutes. This is an Kibana internal process required for each installed plugin and cannot be skipped. The Kibana optimization process is shaky and problems are typically not related to Search Guard. Most issues can be resolved by giving the process more memory by setting NODE_OPTIONS=“–max-old-space-size=8192”. If you are on ES 6.5.x or higher you can also try with --no-optimize (especially if you install the plugin in a Dockerfile). Kibana also currently has a bug in the optimization step if you use X-Pack, but disable reporting. Please check if your Kibana version is affected and correct your kibana.yml accordingly.
https://docs.search-guard.com/latest/kibana-plugin-installation
Am 25.12.2018 um 01:21 schrieb Adwait Joshi adwait...@swarganga.org:
Trying to install the SG plugin on 6.5.4 gives me a hang
Optimizing and caching browser bundles
I waited for 2 hours and it did not finish. Any workaround?
When asking questions, please provide the following information:
- Search Guard and Elasticsearch version
- Installed and used enterprise modules, if any
- JVM version and operating system version
- Search Guard configuration files
- Elasticsearch log messages on debug level
- Other installed Elasticsearch or Kibana plugins, if any
–
You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group.To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.
To post to this group, send email to search...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/8ffe667c-d683-4da2-9fc9-c13655af573f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
please try
NODE_OPTIONS="--max-old-space-size=8192" bin/kibana
to start kibana.The --no-optimiuze defers the optimize step to when kibana starts.
If you still have problems (i cant reproduce the problem here on my mac) i suggest to open a issue here
Issues · elastic/kibana · GitHub or here
https://discuss.elastic.co/
Am 25.12.2018 um 15:37 schrieb Adwait Joshi <adwait.joshi@swarganga.org>:
As an update, I dont even see the .kibana index being created. But I am able to CURL on the elastic side just fine. All the login names and passwords work for SG.
On Tuesday, December 25, 2018 at 7:55:42 AM UTC-5, Adwait Joshi wrote:
I was able to get around using the no optimize. However now Kibana wont start. I have confirmed Elastisearch is running fine and secured by SG. The Kibana server just gives a message Kibana server is not ready yet. There is no errors in the log files either!On Tuesday, December 25, 2018 at 4:39:49 AM UTC-5, Search Guard wrote:
After the plugin has been installed, Kibana will run the optimization process. Depending on your system this might take a couple of minutes. This is an Kibana internal process required for each installed plugin and cannot be skipped. The Kibana optimization process is shaky and problems are typically not related to Search Guard. Most issues can be resolved by giving the process more memory by setting NODE_OPTIONS="--max-old-space-size=8192". If you are on ES 6.5.x or higher you can also try with --no-optimize (especially if you install the plugin in a Dockerfile). Kibana also currently has a bug in the optimization step if you use X-Pack, but disable reporting. Please check if your Kibana version is affected and correct your kibana.yml accordingly.Installing the Search Guard Kibana Plugin | Security for Elasticsearch | Search Guard
> Am 25.12.2018 um 01:21 schrieb Adwait Joshi <adwait...@swarganga.org>:
>
> Trying to install the SG plugin on 6.5.4 gives me a hang
>
> Optimizing and caching browser bundles
>
> I waited for 2 hours and it did not finish. Any workaround?
>
> When asking questions, please provide the following information:
>
> * Search Guard and Elasticsearch version
> * Installed and used enterprise modules, if any
> * JVM version and operating system version
> * Search Guard configuration files
> * Elasticsearch log messages on debug level
> * Other installed Elasticsearch or Kibana plugins, if any
>
> --
> You received this message because you are subscribed to the Google Groups "Search Guard Community Forum" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.
> To post to this group, send email to search...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/8ffe667c-d683-4da2-9fc9-c13655af573f%40googlegroups.com\.
> For more options, visit https://groups.google.com/d/optout\.--
You received this message because you are subscribed to the Google Groups "Search Guard Community Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to search-guard+unsubscribe@googlegroups.com.
To post to this group, send email to search-guard@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/bbace11f-046d-4b00-a2ce-b257d986f256%40googlegroups.com\.
For more options, visit https://groups.google.com/d/optout\.
Tried it, again no errors, a bunch of logs still says server not ready yet
log [13:25:45.705] [debug][legacy][proxy] “getConnections” has been called.
ops [13:25:45.724] memory: 188.5MB uptime: 0:00:14 load: [0.76 0.37 0.23] delay: 19.388
log [13:25:48.780] [debug][legacy][proxy] Event is being forwarded: connection
log [13:25:48.781] [debug][legacy][proxy] Event is being forwarded: connection
log [13:25:50.900] [debug][legacy][proxy] “getConnections” has been called.
ops [13:25:51.090] memory: 254.1MB uptime: 0:00:20 load: [0.78 0.38 0.23] delay: 190.161
log [13:25:53.163] [debug][legacy][service] Kibana server is not ready yet GET:/.
log [13:25:54.017] [debug][legacy][service] Kibana server is not ready yet GET:/favicon.ico.
log [13:25:56.073] [debug][legacy][proxy] “getConnections” has been called.
ops [13:25:56.613] memory: 355.1MB uptime: 0:00:25 load: [0.96 0.42 0.25] delay: 540.602
log [13:26:01.137] [debug][legacy][proxy] “getConnections” has been called.
ops [13:26:01.185] memory: 476.6MB uptime: 0:00:30 load: [1.52 0.55 0.29] delay: 47.801
On Tuesday, December 25, 2018 at 2:13:31 PM UTC-5, Search Guard wrote:
please try
NODE_OPTIONS=“–max-old-space-size=8192” bin/kibana
to start kibana.The --no-optimiuze defers the optimize step to when kibana starts.
If you still have problems (i cant reproduce the problem here on my mac) i suggest to open a issue here
https://github.com/elastic/kibana/issues or here
Am 25.12.2018 um 15:37 schrieb Adwait Joshi adwait...@swarganga.org:
As an update, I dont even see the .kibana index being created. But I am able to CURL on the elastic side just fine. All the login names and passwords work for SG.
On Tuesday, December 25, 2018 at 7:55:42 AM UTC-5, Adwait Joshi wrote:
I was able to get around using the no optimize. However now Kibana wont start. I have confirmed Elastisearch is running fine and secured by SG. The Kibana server just gives a message Kibana server is not ready yet. There is no errors in the log files either!
On Tuesday, December 25, 2018 at 4:39:49 AM UTC-5, Search Guard wrote:
After the plugin has been installed, Kibana will run the optimization process. Depending on your system this might take a couple of minutes. This is an Kibana internal process required for each installed plugin and cannot be skipped. The Kibana optimization process is shaky and problems are typically not related to Search Guard. Most issues can be resolved by giving the process more memory by setting NODE_OPTIONS=“–max-old-space-size=8192”. If you are on ES 6.5.x or higher you can also try with --no-optimize (especially if you install the plugin in a Dockerfile). Kibana also currently has a bug in the optimization step if you use X-Pack, but disable reporting. Please check if your Kibana version is affected and correct your kibana.yml accordingly.
https://docs.search-guard.com/latest/kibana-plugin-installation
Am 25.12.2018 um 01:21 schrieb Adwait Joshi adwait...@swarganga.org:
Trying to install the SG plugin on 6.5.4 gives me a hang
Optimizing and caching browser bundles
I waited for 2 hours and it did not finish. Any workaround?
When asking questions, please provide the following information:
- Search Guard and Elasticsearch version
- Installed and used enterprise modules, if any
- JVM version and operating system version
- Search Guard configuration files
- Elasticsearch log messages on debug level
- Other installed Elasticsearch or Kibana plugins, if any
–
You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group.
To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.
To post to this group, send email to search...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/8ffe667c-d683-4da2-9fc9-c13655af573f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group.To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.
To post to this group, send email to search...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/bbace11f-046d-4b00-a2ce-b257d986f256%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I finally see an error in the log but it doesn’t help with much
[14:02:33.443] [info][status][plugin:rollup@6.5.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [14:02:33.451] [debug][plugins] Initializing plugin input_control_vis@kibana
log [14:02:33.453] [debug][plugins] Initializing plugin inspector_views@kibana
log [14:02:33.454] [debug][plugins] Initializing plugin kbn_doc_views@kibana
log [14:02:33.456] [debug][plugins] Initializing plugin markdown_vis@kibana
log [14:02:33.459] [debug][plugins] Initializing plugin metric_vis@kibana
log [14:02:33.460] [debug][plugins] Initializing plugin region_map@kibana
log [14:02:33.462] [debug][plugins] Initializing plugin state_session_storage_redirect@kibana
log [14:02:33.465] [debug][plugins] Initializing plugin status_page@kibana
log [14:02:33.475] [debug][plugins] Initializing plugin table_vis@kibana
log [14:02:33.477] [debug][plugins] Initializing plugin tagcloud@kibana
log [14:02:33.480] [debug][plugins] Initializing plugin tile_map@kibana
log [14:02:33.482] [debug][plugins] Initializing plugin timelion@kibana
log [14:02:33.643] [info][status][plugin:timelion@6.5.4] Status changed from uninitialized to green - Ready
log [14:02:33.645] [debug][plugins] Initializing plugin graph@6.5.4
log [14:02:33.647] [info][status][plugin:graph@6.5.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [14:02:33.649] [debug][plugins] Initializing plugin monitoring@6.5.4
log [14:02:33.657] [debug][stats-collection] Initializing kibana_stats collector
log [14:02:33.661] [info][status][plugin:monitoring@6.5.4] Status changed from uninitialized to green - Ready
log [14:02:33.662] [debug][plugins] Initializing plugin grokdebugger@6.5.4
log [14:02:33.665] [info][status][plugin:grokdebugger@6.5.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [14:02:33.677] [debug][plugins] Initializing plugin dashboard_mode@6.5.4
log [14:02:33.684] [info][status][plugin:dashboard_mode@6.5.4] Status changed from uninitialized to green - Ready
log [14:02:33.686] [debug][plugins] Initializing plugin logstash@6.5.4
log [14:02:33.688] [info][status][plugin:logstash@6.5.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [14:02:33.694] [debug][plugins] Initializing plugin beats_management@6.5.4
log [14:02:33.697] [Using a default encryption key for xpack.beats.encryptionKey. It is recommended that you set xpack.beats.encryptionKey in kibana.yml with a unique token] undefined
log [14:02:33.699] [info][status][plugin:beats_management@6.5.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [14:02:33.714] [debug][plugins] Initializing plugin apm_oss@kibana
log [14:02:33.716] [debug][plugins] Initializing plugin apm@6.5.4
log [14:02:33.737] [info][status][plugin:apm@6.5.4] Status changed from uninitialized to green - Ready
log [14:02:33.738] [debug][plugins] Initializing plugin canvas@6.5.4
[BABEL] Note: The code generator has deoptimised the styling of “/usr/share/kibana/node_modules/x-pack/plugins/canvas/canvas_plugin/types/all.js” as it exceeds the max of “500KB”.
log [14:02:37.987] [server][uuid][uuid] Resuming persistent Kibana instance UUID: 726d640a-ab7e-4758-8d85-92499e32526c
log [14:02:38.095] [debug][legacy][proxy] “getConnections” has been called.
ops [14:02:38.111] memory: 149.6MB uptime: 0:00:12 load: [1.42 0.76 0.49] delay: 17.327
log [14:02:38.145] [debug][kibana-monitoring][monitoring-ui] Received Kibana Ops event data
log [14:02:38.149] [error][status][plugin:xpack_main@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.150] [error][status][plugin:searchprofiler@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.151] [error][status][plugin:ml@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.175] [error][status][plugin:tilemap@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.176] [error][status][plugin:watcher@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.176] [error][status][plugin:index_management@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.177] [error][status][plugin:rollup@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.177] [error][status][plugin:graph@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.178] [error][status][plugin:grokdebugger@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.178] [error][status][plugin:logstash@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.179] [error][status][plugin:beats_management@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.179] [error][status][plugin:elasticsearch@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.180] [debug][license][xpack] Calling [data] Elasticsearch _xpack API. Polling frequency: 30001
On Wednesday, December 26, 2018 at 8:26:41 AM UTC-5, Adwait Joshi wrote:
Tried it, again no errors, a bunch of logs still says server not ready yet
log [13:25:45.705] [debug][legacy][proxy] “getConnections” has been called.
ops [13:25:45.724] memory: 188.5MB uptime: 0:00:14 load: [0.76 0.37 0.23] delay: 19.388
log [13:25:48.780] [debug][legacy][proxy] Event is being forwarded: connection
log [13:25:48.781] [debug][legacy][proxy] Event is being forwarded: connection
log [13:25:50.900] [debug][legacy][proxy] “getConnections” has been called.
ops [13:25:51.090] memory: 254.1MB uptime: 0:00:20 load: [0.78 0.38 0.23] delay: 190.161
log [13:25:53.163] [debug][legacy][service] Kibana server is not ready yet GET:/.
log [13:25:54.017] [debug][legacy][service] Kibana server is not ready yet GET:/favicon.ico.
log [13:25:56.073] [debug][legacy][proxy] “getConnections” has been called.
ops [13:25:56.613] memory: 355.1MB uptime: 0:00:25 load: [0.96 0.42 0.25] delay: 540.602
log [13:26:01.137] [debug][legacy][proxy] “getConnections” has been called.
ops [13:26:01.185] memory: 476.6MB uptime: 0:00:30 load: [1.52 0.55 0.29] delay: 47.801
On Tuesday, December 25, 2018 at 2:13:31 PM UTC-5, Search Guard wrote:
please try
NODE_OPTIONS=“–max-old-space-size=8192” bin/kibana
to start kibana.The --no-optimiuze defers the optimize step to when kibana starts.
If you still have problems (i cant reproduce the problem here on my mac) i suggest to open a issue here
https://github.com/elastic/kibana/issues or here
Am 25.12.2018 um 15:37 schrieb Adwait Joshi adwait...@swarganga.org:
As an update, I dont even see the .kibana index being created. But I am able to CURL on the elastic side just fine. All the login names and passwords work for SG.
On Tuesday, December 25, 2018 at 7:55:42 AM UTC-5, Adwait Joshi wrote:
I was able to get around using the no optimize. However now Kibana wont start. I have confirmed Elastisearch is running fine and secured by SG. The Kibana server just gives a message Kibana server is not ready yet. There is no errors in the log files either!
On Tuesday, December 25, 2018 at 4:39:49 AM UTC-5, Search Guard wrote:
After the plugin has been installed, Kibana will run the optimization process. Depending on your system this might take a couple of minutes. This is an Kibana internal process required for each installed plugin and cannot be skipped. The Kibana optimization process is shaky and problems are typically not related to Search Guard. Most issues can be resolved by giving the process more memory by setting NODE_OPTIONS=“–max-old-space-size=8192”. If you are on ES 6.5.x or higher you can also try with --no-optimize (especially if you install the plugin in a Dockerfile). Kibana also currently has a bug in the optimization step if you use X-Pack, but disable reporting. Please check if your Kibana version is affected and correct your kibana.yml accordingly.
https://docs.search-guard.com/latest/kibana-plugin-installation
Am 25.12.2018 um 01:21 schrieb Adwait Joshi adwait...@swarganga.org:
Trying to install the SG plugin on 6.5.4 gives me a hang
Optimizing and caching browser bundles
I waited for 2 hours and it did not finish. Any workaround?
When asking questions, please provide the following information:
- Search Guard and Elasticsearch version
- Installed and used enterprise modules, if any
- JVM version and operating system version
- Search Guard configuration files
- Elasticsearch log messages on debug level
- Other installed Elasticsearch or Kibana plugins, if any
–
You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group.
To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.
To post to this group, send email to search...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/8ffe667c-d683-4da2-9fc9-c13655af573f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group.To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.
To post to this group, send email to search...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/bbace11f-046d-4b00-a2ce-b257d986f256%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Does it work with the kibana-oss version (without x-pack)?
I guess you need to file an issue here Issues · elastic/kibana · GitHub and/or https://discuss.elastic.co/ because it appears that this is not a Search Guard related problem
but affects all kibana plugins the same way.
On Wednesday, 26 December 2018 15:07:12 UTC+1, Adwait Joshi wrote:
I finally see an error in the log but it doesn’t help with much
[14:02:33.443] [info][status][plugin:rollup@6.5.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [14:02:33.451] [debug][plugins] Initializing plugin input_control_vis@kibana
log [14:02:33.453] [debug][plugins] Initializing plugin inspector_views@kibana
log [14:02:33.454] [debug][plugins] Initializing plugin kbn_doc_views@kibana
log [14:02:33.456] [debug][plugins] Initializing plugin markdown_vis@kibana
log [14:02:33.459] [debug][plugins] Initializing plugin metric_vis@kibana
log [14:02:33.460] [debug][plugins] Initializing plugin region_map@kibana
log [14:02:33.462] [debug][plugins] Initializing plugin state_session_storage_redirect@kibana
log [14:02:33.465] [debug][plugins] Initializing plugin status_page@kibana
log [14:02:33.475] [debug][plugins] Initializing plugin table_vis@kibana
log [14:02:33.477] [debug][plugins] Initializing plugin tagcloud@kibana
log [14:02:33.480] [debug][plugins] Initializing plugin tile_map@kibana
log [14:02:33.482] [debug][plugins] Initializing plugin timelion@kibana
log [14:02:33.643] [info][status][plugin:timelion@6.5.4] Status changed from uninitialized to green - Ready
log [14:02:33.645] [debug][plugins] Initializing plugin graph@6.5.4
log [14:02:33.647] [info][status][plugin:graph@6.5.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [14:02:33.649] [debug][plugins] Initializing plugin monitoring@6.5.4
log [14:02:33.657] [debug][stats-collection] Initializing kibana_stats collector
log [14:02:33.661] [info][status][plugin:monitoring@6.5.4] Status changed from uninitialized to green - Ready
log [14:02:33.662] [debug][plugins] Initializing plugin grokdebugger@6.5.4
log [14:02:33.665] [info][status][plugin:grokdebugger@6.5.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [14:02:33.677] [debug][plugins] Initializing plugin dashboard_mode@6.5.4
log [14:02:33.684] [info][status][plugin:dashboard_mode@6.5.4] Status changed from uninitialized to green - Ready
log [14:02:33.686] [debug][plugins] Initializing plugin logstash@6.5.4
log [14:02:33.688] [info][status][plugin:logstash@6.5.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [14:02:33.694] [debug][plugins] Initializing plugin beats_management@6.5.4
log [14:02:33.697] [Using a default encryption key for xpack.beats.encryptionKey. It is recommended that you set xpack.beats.encryptionKey in kibana.yml with a unique token] undefined
log [14:02:33.699] [info][status][plugin:beats_management@6.5.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [14:02:33.714] [debug][plugins] Initializing plugin apm_oss@kibana
log [14:02:33.716] [debug][plugins] Initializing plugin apm@6.5.4
log [14:02:33.737] [info][status][plugin:apm@6.5.4] Status changed from uninitialized to green - Ready
log [14:02:33.738] [debug][plugins] Initializing plugin canvas@6.5.4
[BABEL] Note: The code generator has deoptimised the styling of “/usr/share/kibana/node_modules/x-pack/plugins/canvas/canvas_plugin/types/all.js” as it exceeds the max of “500KB”.
log [14:02:37.987] [server][uuid][uuid] Resuming persistent Kibana instance UUID: 726d640a-ab7e-4758-8d85-92499e32526c
log [14:02:38.095] [debug][legacy][proxy] “getConnections” has been called.
ops [14:02:38.111] memory: 149.6MB uptime: 0:00:12 load: [1.42 0.76 0.49] delay: 17.327
log [14:02:38.145] [debug][kibana-monitoring][monitoring-ui] Received Kibana Ops event data
log [14:02:38.149] [error][status][plugin:xpack_main@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.150] [error][status][plugin:searchprofiler@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.151] [error][status][plugin:ml@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.175] [error][status][plugin:tilemap@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.176] [error][status][plugin:watcher@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.176] [error][status][plugin:index_management@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.177] [error][status][plugin:rollup@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.177] [error][status][plugin:graph@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.178] [error][status][plugin:grokdebugger@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.178] [error][status][plugin:logstash@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.179] [error][status][plugin:beats_management@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.179] [error][status][plugin:elasticsearch@6.5.4] Status changed from yellow to red - Request Timeout after 3000ms
log [14:02:38.180] [debug][license][xpack] Calling [data] Elasticsearch _xpack API. Polling frequency: 30001
On Wednesday, December 26, 2018 at 8:26:41 AM UTC-5, Adwait Joshi wrote:
Tried it, again no errors, a bunch of logs still says server not ready yet
log [13:25:45.705] [debug][legacy][proxy] “getConnections” has been called.
ops [13:25:45.724] memory: 188.5MB uptime: 0:00:14 load: [0.76 0.37 0.23] delay: 19.388
log [13:25:48.780] [debug][legacy][proxy] Event is being forwarded: connection
log [13:25:48.781] [debug][legacy][proxy] Event is being forwarded: connection
log [13:25:50.900] [debug][legacy][proxy] “getConnections” has been called.
ops [13:25:51.090] memory: 254.1MB uptime: 0:00:20 load: [0.78 0.38 0.23] delay: 190.161
log [13:25:53.163] [debug][legacy][service] Kibana server is not ready yet GET:/.
log [13:25:54.017] [debug][legacy][service] Kibana server is not ready yet GET:/favicon.ico.
log [13:25:56.073] [debug][legacy][proxy] “getConnections” has been called.
ops [13:25:56.613] memory: 355.1MB uptime: 0:00:25 load: [0.96 0.42 0.25] delay: 540.602
log [13:26:01.137] [debug][legacy][proxy] “getConnections” has been called.
ops [13:26:01.185] memory: 476.6MB uptime: 0:00:30 load: [1.52 0.55 0.29] delay: 47.801
On Tuesday, December 25, 2018 at 2:13:31 PM UTC-5, Search Guard wrote:
please try
NODE_OPTIONS=“–max-old-space-size=8192” bin/kibana
to start kibana.The --no-optimiuze defers the optimize step to when kibana starts.
If you still have problems (i cant reproduce the problem here on my mac) i suggest to open a issue here
https://github.com/elastic/kibana/issues or here
Am 25.12.2018 um 15:37 schrieb Adwait Joshi adwait...@swarganga.org:
As an update, I dont even see the .kibana index being created. But I am able to CURL on the elastic side just fine. All the login names and passwords work for SG.
On Tuesday, December 25, 2018 at 7:55:42 AM UTC-5, Adwait Joshi wrote:
I was able to get around using the no optimize. However now Kibana wont start. I have confirmed Elastisearch is running fine and secured by SG. The Kibana server just gives a message Kibana server is not ready yet. There is no errors in the log files either!
On Tuesday, December 25, 2018 at 4:39:49 AM UTC-5, Search Guard wrote:
After the plugin has been installed, Kibana will run the optimization process. Depending on your system this might take a couple of minutes. This is an Kibana internal process required for each installed plugin and cannot be skipped. The Kibana optimization process is shaky and problems are typically not related to Search Guard. Most issues can be resolved by giving the process more memory by setting NODE_OPTIONS=“–max-old-space-size=8192”. If you are on ES 6.5.x or higher you can also try with --no-optimize (especially if you install the plugin in a Dockerfile). Kibana also currently has a bug in the optimization step if you use X-Pack, but disable reporting. Please check if your Kibana version is affected and correct your kibana.yml accordingly.
https://docs.search-guard.com/latest/kibana-plugin-installation
Am 25.12.2018 um 01:21 schrieb Adwait Joshi adwait...@swarganga.org:
Trying to install the SG plugin on 6.5.4 gives me a hang
Optimizing and caching browser bundles
I waited for 2 hours and it did not finish. Any workaround?
When asking questions, please provide the following information:
- Search Guard and Elasticsearch version
- Installed and used enterprise modules, if any
- JVM version and operating system version
- Search Guard configuration files
- Elasticsearch log messages on debug level
- Other installed Elasticsearch or Kibana plugins, if any
–
You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group.
To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.
To post to this group, send email to search...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/8ffe667c-d683-4da2-9fc9-c13655af573f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google Groups “Search Guard Community Forum” group.To unsubscribe from this group and stop receiving emails from it, send an email to search-guard...@googlegroups.com.
To post to this group, send email to search...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/bbace11f-046d-4b00-a2ce-b257d986f256%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.