🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
Issue in accessing the Solace Software Event Broker CLI
We are working on setting up the Solace Software Pub Sub + Event Broker of Standard Version 10.4.1.121 in lower environments.
We are observing "Access Denied"" error when trying to login to the cli using the below command.
podman exec -it solaceusqa1 /usr/sw/loads/currentload/bin/cli -A
However, we are able to login to the root of the broker and navigate to CLI but not directly to the CLI.
Can someone help on resolving the issue
Best Answer
-
The following command should work:
podman exec -it solaceusqa1 cli
If you really want to specify the full path, use:
podman exec -it solaceusqa1 /usr/bin/cli
2
Answers
-
The following command should work:
podman exec -it solaceusqa1 cli
If you really want to specify the full path, use:
podman exec -it solaceusqa1 /usr/bin/cli
2 -
Hi @Emerson Chen,
Thanks much for the commands. It worked and able to login to cli using those.
But could you please let us know why the below command didn't work which we were using it from long. Also, what is the difference between the commands you shared and we use.
podman exec -it solaceusqa1 /usr/sw/loads/currentload/bin/cli -A
Is it possible to fix this.
0 -
Hi @Dhanusri,
I don't know why that command did not work with Podman (I am currently not using Podman). I did some further testing with 10.4.1.121 and noticed that I would get the "access denied" error only during certain part of the start up (not sure exactly where). If you are getting this error all the time, please create a ticket with Support.
0 -
Hi @Emerson Chen,
Thanks much for the timely help and analysis wrt this.
We will get in touch with support for further discussion on this topic.
0