openstack team mailing list archive

[Aaron Rosen <arosen@xxxxxxxxxx>]

Do you have NTP configured? If the nodes running nova-compute have clocks
that differ from each other the status shows XXX . (Not sure why it's done
this way though).

Aaron


On Thu, Apr 11, 2013 at 10:44 PM, Deepak A.P <swift007.deepak@xxxxxxxxx>wrote:

>
>
> ---------- Forwarded message ----------
> From: Deepak A.P <swift007.deepak@xxxxxxxxx>
> Date: Tue, Apr 9, 2013 at 2:25 PM
> Subject: Re: Re: [Openstack] [openStack] instance status
> To: Wangpan <hzwangpan@xxxxxxxxxxxxxxxx>
>
>
> Hello,
>
>         The output of 'nova-manage service list'    command is
>
>
>
>         * Binary                   Host                  Zone
>           Status                    State                      Updated_At*
>
>         nova-compute        openStack           nova
>  Enabled                   XXX                       2012-04-03
>
>         nova-network         openStack           nova
>    Enabled                   XXX                      2012-04-03
>
>         nova-scheduler       openStack          nova
>  Enabled                  XXX                        2012-04-05
>
>          nova-cert              openStack           nova
>      Enabled                   XXX                       2012-04-05
>
>
>
>
>
>
> On Tue, Apr 9, 2013 at 12:21 PM, Wangpan <hzwangpan@xxxxxxxxxxxxxxxx>wrote:
>
>> **
>> What the result of running 'nova-manage service list'， 'sudo' may be
>> needed by non-root user.
>>
>> 2013-04-09
>>  ------------------------------
>>  Wangpan
>>  ------------------------------
>>  *发件人：*Deepak A.P
>> *发送时间：*2013-04-09 13:54
>> *主题：*Re: [Openstack] [openStack] instance status
>> *收件人：*"sachin tripathi"<sachinkuber@xxxxxxxxx>
>> *抄送：*"OpenStack Mailing List"<openstack@xxxxxxxxxxxxxxxxxxx>
>>
>>  Below is output which i got on running '*nova console-log*'
>>
>> nova console-log *d46530e2-.....*
>>
>> Error: The server has either erred or either incapable of performing the
>> requested operation. HTTP(500) (Request-ID: req-be41c539.......)
>>
>> i tried the other nova commands like 'nova reboot' , ' nova reload' but
>> got the similar error,
>>
>> and logs are not created under '/var/log/nova/'
>>
>> stuck with the above issue
>>
>>
>>
>> On Tue, Apr 9, 2013 at 10:32 AM, sachin tripathi <sachinkuber@xxxxxxxxx>wrote:
>>
>>>    Hello,
>>> You can check the console logs
>>> nova console-log <instance_id>
>>>
>>> On the api node, you can find /var/log/nova/nova-*.log,
>>>
>>> And from "nova  show <instance_id> " get the hypervisor hostname and
>>> check the hypervisor compute-log too.
>>>
>>> Hope, this will give some info to start troubleshoot.
>>>
>>> +Sachin
>>>
>>>
>>>
>>>  On Tue, Apr 9, 2013 at 10:03 AM, Deepak A.P <swift007.deepak@xxxxxxxxx>wrote:
>>>
>>>>  Hello,
>>>>
>>>>         After launching the instance i waited for long time , but still
>>>> the status of the instance  shows 'BUILD' , the flavor of the image is
>>>> 'm1.small' . Is there any work around to know what's happening with the
>>>>
>>>>         instance ?. Are there any logs where i can check the instance
>>>> launch status ?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, Apr 6, 2013 at 12:01 AM, Lloyd Dewolf <lloydostack@xxxxxxxxx>wrote:
>>>>
>>>>>  On Fri, Apr 5, 2013 at 4:18 AM, Deepak A.P <swift007.deepak@xxxxxxxxx
>>>>> > wrote:
>>>>>
>>>>>>
>>>>>> Hi ,
>>>>>>
>>>>>>      i have a list of instances created using the below command
>>>>>>
>>>>>>      nova boot myInstance --image
>>>>>> 0e2f43a8-e614-48ff-92bd-be0c68da19f4
>>>>>>
>>>>>>        --flavor 2 --key_name openstack
>>>>>>
>>>>>>
>>>>>>        i ran the below command to check the status of instances
>>>>>>
>>>>>>
>>>>>>     nova list
>>>>>>
>>>>>>
>>>>>> all the instances show status as  "*BUILD*" , how to se the status of the image to
>>>>>>
>>>>>> "ACTIVE " , i tried rebooting the instance am getting the below error
>>>>>>
>>>>>>
>>>>> Once the instance finishes building then it will be in the "active"
>>>>> state. Depending on the image, flavor and configuration starting an
>>>>> instance can take a long time. I would suggest first trying with a small
>>>>> image like Cirrus and using a "tiny" flavor.
>>>>>
>>>>> http://docs.openstack.org/trunk/openstack-compute/admin/content/starting-images.html
>>>>>
>>>>> Hope that helps,
>>>>> --
>>>>> @lloyddewolf
>>>>> http://www.pistoncloud.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Cheers,
>>>> Deepak
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>
>>
>> --
>> Cheers,
>> Deepak
>>
>
>
>
> --
> Cheers,
> Deepak
>
>
>
> --
> Cheers,
> Deepak
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>