
CloudStack Release Notes Documentation, Release 4.5.1
6.9 Restart management services
1. If upgrading fresh installation of 4.4.0
If you are upgrading fresh installation of CloudStack 4.4.0, the following MySQL command must be executed
before restarting the management server. If the system was running pre 4.4 and then upgraded to 4.4.0, the
MySQL command is not required. Refer to: CLOUDSTACK-7813
use cloud;
ALTER TABLE `snapshot_policy` ADD `display` TINYINT( 1 ) NOT NULL DEFAULT '1';
2. Now it’s time to start the management server
$ sudo service cloudstack-management start
3. If you use it, start the usage server
$ sudo service cloudstack-usage start
6.10 System-VMs and Virtual-Routers
Once you’ve upgraded the packages on your management servers, you’ll need to restart the system VMs. Ensure that
the admin port is set to 8096 by using the “integration.api.port” global parameter. This port is used by the cloud-
sysvmadm script at the end of the upgrade procedure. For information about how to set this parameter, see Setting
Global Configuration Parameters in the Installation Guide. Changing this parameter will require management server
restart. Also make sure port 8096 is open in your local host firewall to do this.
There is a script that will do this for you, all you need to do is run the script and supply the IP address for your MySQL
instance and your MySQL credentials:
# nohup cloudstack-sysvmadm -d IPaddress -u cloud -p password -a > sysvm.log 2>&1 &
You can monitor the log for progress. The process of restarting the system VMs can take an hour or more.
# tail -f sysvm.log
The output to sysvm.log will look something like this:
Stopping and starting 1 secondary storage vm(s)...
Done stopping and starting secondary storage vm(s)
Stopping and starting 1 console proxy vm(s)...
Done stopping and starting console proxy vm(s).
Stopping and starting 4 running routing vm(s)...
Done restarting router(s).
30 Chapter 6. Upgrade Instruction from 4.4.x
Commentaires sur ces manuels