From 5375ca90362d5e2cd067eef31de696f4c1708c47 Mon Sep 17 00:00:00 2001 From: Bobby Bissett Date: Mon, 25 Mar 2024 07:26:38 -0400 Subject: [PATCH 1/2] Add more information about efm startup log This changes adds notes in two places to tell the user to check the startup log if there is a problem starting efm. Too often the user only checks 'systemctl status' output, which does not contain the problem. (I'd like to get rid of the startup log because users forget it's there and it's not needed any more. I don't know when it will happen though: https://enterprisedb.atlassian.net/browse/EFM-1619) --- product_docs/docs/efm/4/05_using_efm.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/product_docs/docs/efm/4/05_using_efm.mdx b/product_docs/docs/efm/4/05_using_efm.mdx index 4ff307ea1f2..b7040a1dbec 100644 --- a/product_docs/docs/efm/4/05_using_efm.mdx +++ b/product_docs/docs/efm/4/05_using_efm.mdx @@ -39,6 +39,8 @@ To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/Rocky Linux/Alm `systemctl start edb-efm-4.` +!!! Note + If the agent fails to start, see the startup log `/var/log/efm-4./startup-efm.log` for more information. If the cluster properties file for the node specifies that `is.witness` is `true`, the node starts as a witness node. From f1e7d56ee886f42847c85c40ac0e01b821220827 Mon Sep 17 00:00:00 2001 From: Bobby Bissett Date: Mon, 25 Mar 2024 07:26:54 -0400 Subject: [PATCH 2/2] Add more information about efm startup log This changes adds notes in two places to tell the user to check the startup log if there is a problem starting efm. Too often the user only checks 'systemctl status' output, which does not contain the problem. (I'd like to get rid of the startup log because users forget it's there and it's not needed any more. I don't know when it will happen though: https://enterprisedb.atlassian.net/browse/EFM-1619) --- product_docs/docs/efm/4/13_troubleshooting.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/product_docs/docs/efm/4/13_troubleshooting.mdx b/product_docs/docs/efm/4/13_troubleshooting.mdx index 74fff13d648..1aab4fc531d 100644 --- a/product_docs/docs/efm/4/13_troubleshooting.mdx +++ b/product_docs/docs/efm/4/13_troubleshooting.mdx @@ -10,6 +10,10 @@ legacyRedirectsGenerated: +## The Failover Manager agent fails to start + +If an agent fails to start, see the startup log `/var/log/efm-/startup-.log` for more information. + ## Authorization file not found. Is the local agent running? If you invoke an Failover Manager cluster management command and Failover Manager isn't running on the node, the `efm` command displays an error: