Launching instance. Spawning state
Hello!! When I launch an instance from my dashboard, it will be in a spawning state forever. I have looked at the logs in /var/log/nova but I have not seen any error.
[root@vmlbcatfl49 ~(keystone_admin)]# for file in $(ls /var/log/nova/); do cat /var/log/nova/$file | grep error; done
[root@vmlbcatfl49 ~(keystone_admin)]
The only weird thing I have found is that, the last line of my scheduler.log logfile:
2014-11-24 11:32:02.142 3675 INFO nova.scheduler.filter_scheduler [req-6bd0507e-69da-4d3a-99d1-4090fb94a626 a10b12add69e4199aee36cb743d73b6c a5cb7bf38ac941acbed0f569c1d1d3e6] Choosing host WeighedHost [host: vmlbcatfl49.lvtc.gsnet.corp, weight: 1.0] for instance 726289a0-1dae-479c-8868-d892085ca174
Could you help me please?
FROM 9lives answer:
[root@vmlbcatfl49 ~(keystone_admin)]# for file in $(ls /var/log/nova/); do cat /var/log/nova/$file | grep -iE 'error|warn' ; done
2014-11-24 10:53:46.675 10308 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead.
2014-11-24 10:53:46.682 10308 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead.
2014-11-24 10:53:46.891 10308 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead.
2014-11-24 11:20:40.891 3543 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead.
2014-11-24 11:20:40.896 3543 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead.
2014-11-24 11:20:41.094 3543 WARNING keystoneclient.middleware.auth_token [-] Configuring admin URI using auth fragments. This is deprecated, use 'identity_uri' instead.
2014-11-24 10:57:56.438 13621 WARNING nova.conductor.api [req-6c87d365-1407-4a09-ace4-41e4348debed None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor?
2014-11-24 10:57:56.887 13621 WARNING nova.virt.libvirt.driver [req-b8efb854-9e5b-4ec2-a13b-de1106683675 None None] Cannot update service status on host: vmlbcatfl49.lvtc.gsnet.corp,since it is not registered.
2014-11-24 11:07:46.567 13621 WARNING nova.compute.manager [-] Bandwidth usage not supported by hypervisor.
2014-11-24 11:20:50.164 3573 WARNING nova.conductor.api [req-4800e4f8-4bc6-4c6a-a388-709882687d1c None None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor?
2014-11-24 11:30:39.930 3573 WARNING nova.compute.manager [-] Bandwidth usage not supported by hypervisor.
2014-11-24 11:40:41.450 3573 ERROR oslo.messaging.rpc.dispatcher [-] Exception during message handling: Instance instance-00000001 could not be found.
2014-11-24 11:40:41.480 3573 ERROR oslo.messaging._drivers.common [-] Returning exception Instance instance-00000001 could not be found. to caller
2014-11-24 11:40:41.480 3573 ERROR oslo.messaging._drivers.common [-] ['Traceback (most recent call last):\n', ' File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 133, in _dispatch_and_reply\n incoming.message))\n', ' File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 176, in _dispatch\n return self._do_dispatch(endpoint, method, ctxt, args)\n', ' File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 122, in _do_dispatch\n result = getattr(endpoint, method ...
Pablo, look at the instance log from the dashboard. If you are using a proper OS like Fedora or Ubuntu's image to spawn instances on a QEMU compute-host, it will take like 20 minutes for it to finish booting up. please post the instance logs and nova-compute logs.
could you try this command, i really doubt there is error in nova-compute.log
First of all, thx a lot for answering me:
9lives, you were right. I will edit my question with the logs that kashyapk requestd and the output of your command because they are too long.
kashyapk: They are very large logs, what do you want me to look for on them? :) thx a lot mate!! 9lives: I have already edited my answer with the output of your command. Thx !!
9lives' command showed you the error you were looking for. You were missing the -i flag in grep command, else you would have seen the error before you even posted here :P. Ignore my requested logs.