GitHub user arpanbht added a comment to the discussion: Cloudstack multiple 
management server connection across different networks

@weizhouapache
I only stopped the cloudstack-management service.

But the thing is I am trying to install the management server again by 
following the steps in our 1st mgmt server same as it which are listed below

```
    2  hostnamectl
    3  clear
    4  apt install openjdk-11-jre-headless -y
    5  clear
    6  java -version
    7  apt install chrony -y
    8  nano /etc/apt/sources.list.d/cloudstack.list
    9  cat /etc/os-release
   10  clear
   11  nano /etc/apt/sources.list.d/cloudstack.list
   12  wget -O - https://download.cloudstack.org/release.asc |sudo tee 
/etc/apt/trusted.gpg.d/cloudstack.asc
   13  sudo apt update
   14  sudo apt install cloudstack-management
   15  sudo apt install mysql-server
   16  clear
   17  nano /etc/mysql/mysql.cnf
   18  nano /etc/mysql/my.cnf
   19  nano /etc/mysql/mysql.cnf
   20  sudo systemctl restart mysql
   21  clear
   22  sudo cloudstack-setup-databases cloud:cloud@localhost --deploy-as=root
   23  ufw allow mysql
   24  ufw allow 8080/tcp
   25  ufw allow 8250/tcp
   26  ufw allow 8443/tcp
   27  ufw allow 9090/tcp
   28  ufw enable
   29  ufw reload
   30  cloudstack-setup-management
   31  ufw allow 8080/tcp
   32  ufw allow 8250/tcp
   33  ufw allow 8443/tcp
   34  ufw allow 9090/tcp
   35  ufw enable
   36  ufw reload
   37  sudo systemctl start cloudstack-management
   38  sudo systemctl enable cloudstack-management
   39  sudo systemctl status cloudstack-management
```

the management-server 1 is running fine with this setup after I installed the 
new server with this it is giving the same **spring bean error**.

In the dpkg list the mgmt1 shows the cloudstack version as **4.22.1.0** but in 
the mgmt2 its getting upgraded to **4.22.1.1** on its own.

GitHub link: 
https://github.com/apache/cloudstack/discussions/13919#discussioncomment-18092116

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to