From abe79038d7fc30fdc526ede04b21fe2d8170200b Mon Sep 17 00:00:00 2001 From: liza-mae Date: Thu, 4 Feb 2021 18:33:02 -0700 Subject: [PATCH 1/3] Update reporting document --- docs/user/reporting/reporting-troubleshooting.asciidoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/user/reporting/reporting-troubleshooting.asciidoc b/docs/user/reporting/reporting-troubleshooting.asciidoc index 1f07b0b57d8c7..80439383cc56b 100644 --- a/docs/user/reporting/reporting-troubleshooting.asciidoc +++ b/docs/user/reporting/reporting-troubleshooting.asciidoc @@ -55,6 +55,8 @@ if it encounters errors, logs them in the Console. Unfortunately, the error mess information about why Chromium failed to run. The most common error message is `Error: connect ECONNREFUSED`, which indicates that {kib} could not connect to the Chromium process. +Chromium is not compatible with ARM RHEL/CentOS. + To troubleshoot the problem, start the {kib} server with environment variables that tell Chromium to print verbose logs. See the <> for more information. From 553e2aef565fdc9019390b8dab0a1f799b686d3f Mon Sep 17 00:00:00 2001 From: liza-mae Date: Fri, 5 Feb 2021 10:30:10 -0700 Subject: [PATCH 2/3] Move to own section --- docs/user/reporting/reporting-troubleshooting.asciidoc | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/user/reporting/reporting-troubleshooting.asciidoc b/docs/user/reporting/reporting-troubleshooting.asciidoc index 80439383cc56b..f74ef050f4e05 100644 --- a/docs/user/reporting/reporting-troubleshooting.asciidoc +++ b/docs/user/reporting/reporting-troubleshooting.asciidoc @@ -15,6 +15,7 @@ Having trouble? Here are solutions to common problems you might encounter while * <> * <> * <> +* <> [float] [[reporting-diagnostics]] @@ -55,11 +56,10 @@ if it encounters errors, logs them in the Console. Unfortunately, the error mess information about why Chromium failed to run. The most common error message is `Error: connect ECONNREFUSED`, which indicates that {kib} could not connect to the Chromium process. -Chromium is not compatible with ARM RHEL/CentOS. - To troubleshoot the problem, start the {kib} server with environment variables that tell Chromium to print verbose logs. See the <> for more information. + [float] [[reporting-troubleshooting-text-incorrect]] === Text rendered incorrectly in generated reports @@ -158,3 +158,9 @@ requests to render. If the {kib} instance doesn't have enough memory to run the report, the report fails with an error such as `Error: Page crashed!` In this case, try increasing the memory for the {kib} instance to 2GB. + +[float] +[[reporting-troubleshooting-arm-systems]] +=== ARM systems + +Chromium is not compatible with ARM RHEL/CentOS. From f4f503b0c3072a19640b3405b415ad11a50e9ae1 Mon Sep 17 00:00:00 2001 From: liza-mae Date: Fri, 5 Feb 2021 10:31:24 -0700 Subject: [PATCH 3/3] Remove extra line --- docs/user/reporting/reporting-troubleshooting.asciidoc | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/user/reporting/reporting-troubleshooting.asciidoc b/docs/user/reporting/reporting-troubleshooting.asciidoc index f74ef050f4e05..ebe095e0881b3 100644 --- a/docs/user/reporting/reporting-troubleshooting.asciidoc +++ b/docs/user/reporting/reporting-troubleshooting.asciidoc @@ -59,7 +59,6 @@ that {kib} could not connect to the Chromium process. To troubleshoot the problem, start the {kib} server with environment variables that tell Chromium to print verbose logs. See the <> for more information. - [float] [[reporting-troubleshooting-text-incorrect]] === Text rendered incorrectly in generated reports