Hi All,
I am trying to understand if the architecture of ACS allows to have
multiple ACS management servers managing the same hosts. My use case is
that I need to have ACS deployed to edge and provide some UI to each edge
location and still have a central instance to manage all edge deployments.
I
Hi, All
I’ve set up an ACS 4.19.0.1 on Ubuntu 22.04, after configuring ldap, then while
add ldap user part.
The add ldap user part hang like over 10 minutes, then empty ldap user list,
then request failed pop out.
I check log in management-server.log.
Below content comes out:
2024-05-08 17:4
GitHub user Ash6990 added a comment to the discussion: Cloustack agent
(4.18.1.0) status stuck on activating
i referred to that & configured them correctly but the issue still persists
I think it is better to raise the discussion here.
Basically the questi
GitHub user weizhouapache added a comment to the discussion: Cloustack agent
(4.18.1.0) status stuck on activating
@Ash6990
can you the the log level to DEBUG and restart cloudstack-agent ?
```
sed -i "s/INFO/DEBUG/g" /etc/cloudstack/agent/log4j-cloud.xml
systemctl restart cloudstack-agent
``
I am currently running an older version of Cloudstack (4.11) on top of
CentOS 7 and using qemu-kvm-ev from the CentOS Virtualization SIG. I am
looking at migrating to Rocky Linux 8.9 and a newer version of Cloudstack,
but I'm running into issues w qemu-kvm-ev. Am I correct in stating that
qemu-kvm-
