← Back to team overview

openstack team mailing list archive

Re: dnsmasq does not start + no xapi interface -- how to solve this problem

 

2012/12/10 Vishvananda Ishaya <vishvananda@xxxxxxxxx>

> Check rabbitmqctl list_queues and see if there are queues that have
> nonzero entries. That means messages are being sent but not picked up by
> the nodes.
>

Here is the output of the command -- there some non zero values for glance
info. Is there any way to clear this queue?

rabbitmqctl list_queues
Listing queues ...
cinder-volume 0
network.computeDomU07 0
compute.computeDomU07 0
network.computeDomU05 0
compute 0
scheduler.computeDomU05 0
consoleauth.computeDomU08 0
network.controller 0
cinder-scheduler 0
compute_fanout_470aa521abf344f398dc98bf2f99b6e1 0
scheduler.computeDomU07 0
compute.controller 0
network_fanout_209e3038f3af49849c10263ab1012e37 0
cert.computeDomU07 0
scheduler.computeDomU08 0
consoleauth.computeDomU05 0
glance_notifications.warn 0
consoleauth_fanout_9f3c92a646e74f9c88cb1317379d0a6a 0
scheduler.controller 0
network_fanout_9cf790a90c2f49c781a8046d0ea91d30 0
cinder-volume_fanout_693d1211a2a4478b828acb91099a228b 0
cert_fanout_d669d273749c432d999cdfd0a7a715a9 0
network_fanout_e4cc6507e07747d093ecc59502d62018 0
consoleauth.computeDomU07 0
cert_fanout_a9734647226c4ebda2e112ece8f6f168 0
compute.computeDomU08 0
cert.computeDomU05 0
scheduler_fanout_6c29f818954243468653858252666f2a 0
cert.controller 0
cert 0
compute.computeDomU05 0
network_fanout_b511cfb6546544aa83f7920169604fbe 0
network.computeDomU08 0
consoleauth.controller 0
scheduler 0
glance_notifications.info 132
cinder-volume.controller 0
glance_notifications.error 1
network_fanout_a4dc31150bfd4fb3bf393f24a343ff76 0
cert.computeDomU08 0
cinder-scheduler_fanout_b578bf0f687c4564920f3500ae2c9b8c 0
cinder-scheduler.controller 0
network 0
compute_fanout_c1f1cd2ab9cc4c5b87fbfd72dd25a432 0
scheduler_fanout_8aa445468b5c4aa6b2a1a4412dbc09fc 0
network_fanout_693737b6acaf4ba59c3c6cd31a70951b 0
consoleauth 0
...done.




> If the nova-networks are hanging they are probably stuck waiting on a lock
> files. I believe the lock files are in /var/lock/nova by default. You could
> try deleting them and restarting nova-network.
>

However, there is no nova directory under /var/locks

Thank you,
Afef

>
> Vish
>
> On Dec 10, 2012, at 1:32 PM, Afef Mdhaffar <
> mdhaffar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>
>
> 2012/12/10 Vishvananda Ishaya <vishvananda@xxxxxxxxx>
>
>> I don't see any errors in your network log. are nova-network and
>> nova-compute running on the same host with the same config file?
>
>
> Yes, nova-network and nova-compute are running on the same node -- this is
> the compute node
>
>
>> It looks like it isn't recieving a message. Are you running another
>> nova-network that is picking up the message on another host?
>>
>
> I have another nova-network running on the cloud controller.
>
> The platform was composed of 9 nodes (1 cloud controller + 8 compute
> nodes) and was running till friday  (when one of my colleagues has
> installed some updates on our gateway). each node (including the
> controller) runs nova-network and nova-compute.
> Then (after updating the gateway), only the cloud controller and one
> compute node are still correctly running. and the rest of the nodes returns
> the same error - related in my opinion to nova-network.
>
> Any ideas how to fix that?
>
> Thank you,
> Afef
>
>>
>> Vish
>>
>> On Dec 10, 2012, at 12:18 PM, Afef MDHAFFAR <afef.mdhaffar@xxxxxxxxx>
>> wrote:
>>
>> > Hi all,
>> >
>> > I am facing an boring issue since Friday: nova-network is unable to
>> start dnsmasq. Therefore the xapi0 interface is not created.
>> > Then, it is impossible to launch VMs. nova-network does not answer
>> requests and nova-compute returns an RPC timeout.
>> > Please help me to solve this problem
>> > I am using openstack folsom release + XCP + ubuntu 12.04
>> >
>> > log file of nova-compute and nova-network are attached to this e-mail.
>> >
>> > Thank you,
>> > Afef
>> >
>> >
>> >
>> >
>> >
>> <nova-compute.txt><nova-network.log>_______________________________________________
>> > Mailing list: https://launchpad.net/~openstack
>> > Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> > Unsubscribe : https://launchpad.net/~openstack
>> > More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Afef MDHAFFAR
http://www.redcad.org/members/mdhaffar/

Follow ups

References