From 525230810f6bcd63bc98e78f9bcbfbda0a9cb33b Mon Sep 17 00:00:00 2001
From: Jesse Menning <62108913+jessemenning@users.noreply.github.com>
Date: Mon, 3 Jun 2024 17:13:12 -0400
Subject: [PATCH] added some troubleshooting info (#323)
---
markdown/ep-connect-ep-broker/ep-connect-ep-broker.md | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/markdown/ep-connect-ep-broker/ep-connect-ep-broker.md b/markdown/ep-connect-ep-broker/ep-connect-ep-broker.md
index 8f0b6e37..12c38ee0 100644
--- a/markdown/ep-connect-ep-broker/ep-connect-ep-broker.md
+++ b/markdown/ep-connect-ep-broker/ep-connect-ep-broker.md
@@ -72,6 +72,11 @@ Duration: 0:10:00
1. On the next screen, click on Run Generate and populate Event Portal
1. Wait for the script to complete. Be patient, there are a lot of commands to run!
+> aside negative
+> If you get this error when running the script, you likely have not set the Event Portal Environment as the active environmental variables.
+```POST http://{{baseurl}}/api/v2/architecture/addressSpaces```
+```Error: getaddrinfo ENOTFOUND {{baseurl}}```
+
## Enable runtime configuration for your environments
Duration: 0:03:00
@@ -129,6 +134,12 @@ where ```PASSWORD_ENV_VAR_1``` is the password for your locally running broker a
```docker logs -f event-management-agent```
The last line should be: ```Started event-management agent```
+
+> aside negative
+> The following error is caused by giving an incorrect path to the EMA file in the Docker command.
+```Failed to instantiate com.solace.maas.ep.event.management.agent.plugin.manager.client.KafkaClientConfigImpl: Constructor threw exception```
+
+
5. Further confirm by going back to the Event Management Agents tab. Look to see your EMA has a green “Connected” label
