Shulou(Shulou.com)06/01 Report--

When you install CloudStack, three libraries, cloud, cloud_usage, and cloudbridge, are created. But after analysis, we found that only the cloud library is what we need.

Common library tables in CloudStack:

1. Vm_instance virtual machine instance table

2. Nics network card table

3. Volumes hard disk table

4. Vm_template template table

5. Configuration parameter configuration

Second, you can also look up the VM in the database; whether this template exists

Mysql > SELECT * FROM host WHERE name like'% s Murray VM%\ G / / system virtual machine information in host information

Mysql > SELECT * FROM vm_instance WHERE name like'% s Murray VM%'G / / system virtual machine information in the virtual machine instance

It seems that these two states; (state database table structure status)

Friends who know these two virtual machines all know that this is a very powerful virtual machine, which can be rebuilt after deletion. Generally, when these two virtual machines fail, they are also solved through deletion and reconstruction. Since the UI interface cannot be deleted, just modify the corresponding field in the database and set its status to Destroyed.

(it can be changed to another running according to the status; however, it is not easy to operate, because the system VM represents the current state, so it must be checked to find out where the problem is.)

UPDATE vm_instance SET state='Destroyed' WHERE name='s-1-VM'

UPDATE vm_instance SET state='Destroyed' WHERE name='v-2-VM'

A kvm host host hung up and went online again. The cloud system could not find the cloudstack-agent.

Open the database vm_instance table to check whether the running status of each virtual machine (state field) is different from the actual one (for example, if it should be Stopped, say it is Running)

Save the wrong changes and restart cloudstack-management.

Cloudstack installation

common problem

Log: (see if an exception occurs when cloudstack is enabled)

Tail-f/var/log/cloudstack/management/catalina.out

Log:

Cd / var/log/cloudstack/management

SetupManagement.log

Management-server.log

Catalina.out

3. If it is the reported permission problem:

Chown cloud / var/log/cloudstack/-R

5. If login is unable to access the pid process of the management server

[root@manage ~] # rm / var/run/cloudstack-management.pid

Restart the test login again

6. View the java process

Ps-ef | grep java

System VM is used to manage the dedicated virtual machine that comes with cloudstack; it is used to manage secondary storage and remote terminals

Modify hostname

/ etc/hosts

/ etc/sysconfig/network

1. Landing problem

Or there is an error when importing the database; (initialize data)

Cloudstack-setup-databases cloud:root@localhost-- deploy-as=root: password-I (private network IP)

2. Primary or secondary storage cannot be added

View the open ports of the / etc/sysconfig/nfs profile

8. View the virtual routing table kvm connection local address

Nat corresponds to the IP of public network and private network translation

Iptables-t nat-nL

# iptables-t nat-nL

Ssh connection linux (system virtual machine)

Connect this ip address on the host of kvm

Ssh-i / root/.ssh/id_rsa.cloud-p 3922 root@169.254.2.132 (local link address)

Execute / usr/local/cloud/systemvm/ssvm-check.sh

There will be a prompt that java is not running

And then execute

Root@v-2190-VM:/usr/local/cloud/systemvm# sh run.sh

**********

Error occurred during initialization of VM

Could not reserve enough space for objectheap

Could not create the Java virtual machine.

Check what the problem is, the hint is that there is not enough space.

The problem with my machine is that java cannot be started, because the machine does not have enough memory, so change the memory manually

Export _ JAVA_OPTIONS= "- Xmx256M"

Or export _ JAVA_OPTIONS= "- Xms256M-Xmx256M"

Then execute / usr/local/cloud/systemvm/run.sh

Unable to write to the routing table:

Resource [DataCenter:1] is unreachable:Unable to apply save password entry on router

Most likely it is the problem of the virtual routing table.

Enter the virtual routing table through the connection address; view the memory process

Or some logs take up a large amount (file view)

Du-sh * | sort-n (file size sort)

Or] # ls-lhs

Connection tracking (CONNTRACK), as the name implies, is to track and record the status of the connection

Conntrackd provides a user control daemon to track iptables connection status information. The daemon synchronizes the status information of network connections between several firewalls. Therefore, conntrackd is an indispensable component for implementing high-availability firewalls.

Global settings:

The secstorage.allowed.internal.sites is changed to 10.10.10.10.Compact 24 (actual storage network segment)

The management.network.cidr is changed to 10.10.10.10.Compact 24 (actual managed network segment)

Some other global parameters to be concerned about:

Expunge deletes parameters related to the latency of an instance

Ha.tag High availability tag

Number of ha.workers high available daemon threads

Parameters related to overallocation of overprovisioning system resources

(if the overmatch doesn't work, look at the database cluster_detail and vm_template_details tables)

Parameters related to snapshot snapshot

Kvm.snapshot.enabled uses kvm as host. This parameter must be set to true.

Allocated.capacity resource allocation threshold related parameters, more than the threshold will not be able to create and run virtual machines.

Network.throttling.rate network bandwidth. Default is 200Mbps.

Vm.network.throttling.rate network bandwidth. Default is 200Mbps.

Expunge.delay=30

Expunge.interval=30

Secstorage.allowed.internal.sites=0.0.0.0/0

/ / download the network segment where the web is located

System.vm.use.local.storage=true

/ / enable local storage

Host=172.16.0.20

/ / Host address

Management.network.cidr=172.16.0.0/24

The network segment downloaded by the template address

Hypervisor for global settings

There is a limit on the maximum number of visitors for virtual machine platforms.

Host could not join the system normally and was disconnected repeatedly

The error in the cloudstack-agent log is as follows:

Connected to 10.10.10.15:8250

Proccess agent startup answer, agent id = 0

Set agent id 0

Startup Response Received: agent id = 0

Connected to the server

Lost connection to the server. Dealing withthe remaining commands...

Note whether the host id in the manage log does not match the agent id in the cloudstack-agent log. If so, delete the host and add it again.

If it cannot be deleted, close manage and agent, clear the data corresponding to this host in host_details and host tables in the database (if prompted that other tables have associated data to be deleted as well), and restart manage and agent.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.