Merge pull request #5437 from EnterpriseDB/efm/startup-log-knows-all

Add more information about efm startup log
EnterpriseDB · Mar 25, 2024 · f1a9c78 · f1a9c78 · github-actions · Mar 25, 2024
2 parents d13f5ad + f1e7d56
commit f1a9c78
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git 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.<x>`
 
+!!! Note
+    If the agent fails to start, see the startup log `/var/log/efm-4.<x>/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.
 

diff --git a/product_docs/docs/efm/4/13_troubleshooting.mdx b/product_docs/docs/efm/4/13_troubleshooting.mdx
@@ -10,6 +10,10 @@ legacyRedirectsGenerated:
 
 <div id="troubleshooting" class="registered_link"></div>
 
+## The Failover Manager agent fails to start
+
+If an agent fails to start, see the startup log `/var/log/efm-<version>/startup-<cluster>.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: