Open Stack

Just to clarify , I think your case would be run nova-network ,then ^C or
abnormally shutdown it
and it might be during  the period of holding a semaphore without releasing
it, right?

guess all component other than nova have this problem ? so maybe remove
this [nova] can get more input ...


Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM at IBMCN   Internet: jichenjc at cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:	Alex Xu <xuhj at linux.vnet.ibm.com>
To:	OpenStack Development Mailing List
            <openstack-dev at lists.openstack.org>,
Date:	08/07/2014 04:54 PM
Subject:	[openstack-dev] [nova] nova-network stuck at get semaphores
            lock	when startup



When I startup nova-network, it stuck at trying get lock for ebtables.

@utils.synchronized('ebtables', external=True)
def ensure_ebtables_rules(rules, table='filter'):
     .....

Checking the code found that invoke utils.synchronized without parameter
lock_path, the code will try to use
posix semaphore.

But posix semaphore won't release even the process crashed. Should we
fix it? I saw a lot of call for synchronized
without lock_path.

Thanks
Alex


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140807/a138734a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140807/a138734a/attachment-0001.gif>