[Openstack-operators] [Openstack] [openStack] instance status
Razique Mahroua
razique.mahroua at gmail.com
Tue Apr 16 13:02:48 UTC 2013
Check your nova.conf - looks like you are using a non-existing physical interface
Razique Mahroua - Nuage & Co
razique.mahroua at gmail.com
Tel : +33 9 72 37 94 15
Le 16 avr. 2013 à 10:52, Wangpan <hzwangpan at corp.netease.com> a écrit :
> Looks like all of your nova sevices are stopped runing, and what the result of 'service nova-compute status'?
>
> 2013-04-16
> Wangpan
> 发件人:Deepak A.P
> 发送时间:2013-04-16 14:36
> 主题:Re: [Openstack] Fwd: Re: [openStack] instance status
> 收件人:"Aaron Rosen"<arosen at nicira.com>
> 抄送:"openstack-operators at lists.openstack.org"<openstack-operators at lists.openstack.org>,"OpenStack Mailing List"<openstack at lists.launchpad.net>
>
> openstack at openStack:~$ sudo service ntp status
> * NTP server is running
>
>
> On Fri, Apr 12, 2013 at 11:22 AM, Aaron Rosen <arosen at nicira.com> wrote:
> 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 at gmail.com> wrote:
>
>
> ---------- Forwarded message ----------
> From: Deepak A.P <swift007.deepak at gmail.com>
> Date: Tue, Apr 9, 2013 at 2:25 PM
> Subject: Re: Re: [Openstack] [openStack] instance status
> To: Wangpan <hzwangpan at corp.netease.com>
>
>
> 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 at corp.netease.com> 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 at gmail.com>
> 抄送:"OpenStack Mailing List"<openstack at lists.launchpad.net>
>
> 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 at gmail.com> 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 at gmail.com> 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 at gmail.com> wrote:
> On Fri, Apr 5, 2013 at 4:18 AM, Deepak A.P <swift007.deepak at gmail.com> 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 at lists.launchpad.net
> 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 at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
>
>
>
> --
> Cheers,
> Deepak
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130416/0d8493cf/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NUAGECO-LOGO-Fblan_petit.jpg
Type: image/jpeg
Size: 10122 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130416/0d8493cf/attachment.jpg>
More information about the OpenStack-operators
mailing list