No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

We can’t find the information about the VDesktop infrastructure domain virtual machine on the OMS and BMC Portal

Publication Date:  2012-11-20 Views:  45 Downloads:  0
Issue Description
There is the simplified configuration version of V100R002C00SPC200 in a site, after modifying the MCNA time, restart it, we can’t find the corresponding information about the VDesktop infrastructure domain virtual machine on the OMS Portal (SingleCLOUD operation and management system) and BMC Portal (Cloud Computing user self-service system).

Alarm Information
On the user self-service system, click the disk management, mirror image management, elastic IP management, VLAN management and VPC management in the resource manager, there always appear the dialog box “system is busy, please try a later.” As the following picture displayed:


Handling Process
1. According to the <<The time modification solution of simplified configuration>>, after modifying the MCNA time, we must restart the MCNA’s service produce and system produce, we find all the produces are in the “normal” status, but the problem is still on. The steps to restart the service produce are as followed:
1) Close the watchdog:
sh /opt/galax/gcs/watchdog/script/shell/stopwatchdog.sh
2) Restart the service produce (execute the close and restart command of the same produce at the same time):
/opt/galax/sysvolumemonitor/script/sysVolumeMonitor.sh stop
         /opt/galax/sysvolumemonitor/script/sysVolumeMonitor.sh start
         /opt/galax/sysvolumemonitor/script/sysVolumeMonitor.sh status
    # check process status
        /opt/galax/oms/bin/oms-monitor.sh gmond stop
        /opt/galax/oms/bin/oms-monitor.sh gmond start
        /opt/galax/oms/bin/oms-monitor.sh gmond status
    # check process status
        /opt/galax/oms/bin/oms-monitor.sh plugin stop
        /opt/galax/oms/bin/oms-monitor.sh plugin start
        /opt/galax/oms/bin/oms-monitor.sh plugin status
    # check process status
       /usr/bin/configframe stop
       /usr/bin/configframe start
       /usr/bin/configframe status
    # check process status
       /usr/bin/bsb stop
       /usr/bin/bsb start
       /usr/bin/bsb status
    # check process status
       /opt/eucalyptus/ecs_scripts/ecs-monitor.sh nc stop
       /opt/eucalyptus/ecs_scripts/ecs-monitor.sh nc start
       /opt/eucalyptus/ecs_scripts/ecs-monitor.sh nc status
    # check process status
3) Restart the system produce:
service cron restart
       service cron status
    # check service status
       service syslog restart
       service syslog status
    # check service status
4) Start the watchdog:
sh /opt/galax/gcs/watchdog/watchdog.sh –start
Check the watchdog’s status:
sh /opt/galax/gcs/watchdog/watchdog.sh -query
Return the status: WatchDog daemon is running.

2. Use the pgAdmin (PostgreSQL Tools) database tool to check if there is information about the VDesktop infrastructure domain virtual machine in the ESC database:
1) Login in the ESC’s floating IP via the pgAdmin tool, the port number is: 5432, the user’s name and passwords are both: galax;
2) At the left side of the pgAdmin interface, enter into the “eucalyptus -> mode -> data table -> VM_instance” catalog, at the “VM_instance”, right-click and select “view data (D) -> view all the columns (A)”, we can see the information about the system’s virtual machine, as the following picture displayed:

3) The value of “owner_id” in the above picture’s 5th row is “VDSAdmin” denotes the VDesktop infrastructure domain virtual machine, it indicates that there hasn’t lost the information about the VDesktop infrastructure domain virtual machine in the ESC.

3. There can display the MN, ESC, and CRM virtual machines’ information on the OMS Portal, but not the infrastructure domain virtual machine’s information , and there appears the dialog box “The system is busy, please try a later” on the BMS Portal, we guess the BMS Portal has some problem. Check the BMS’s status in the ESC (as the following picture), it’s normal, then we restart the BMS produce and finally settle this problem.


Root Cause
1. The MCNA service produce or system produce hasn’t been restarted.
2. There has been lost the information about the VDesktop infrastructure domain virtual machine in the ESC;
3. The problem of the OMS Portal and the BMS Portal.

Suggestions
None

END