Re: [openstack-dev] [nova] nova-network stuck at get semaphores lock when startup
Oops, thanks On 2014年08月07日 22:08, Ben Nemec wrote: Unfortunately this is a known issue. We're working on a fix: https://bugs.launchpad.net/oslo/+bug/1327946 On 08/07/2014 03:57 AM, Alex Xu wrote: 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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] nova-network stuck at get semaphores lock when startup
Unfortunately this is a known issue. We're working on a fix: https://bugs.launchpad.net/oslo/+bug/1327946 On 08/07/2014 03:57 AM, Alex Xu wrote: > 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@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] nova-network stuck at get semaphores lock when startup
On 2014?08?07? 17:13, Chen CH Ji wrote: 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? yes, you are right. thanks for the clarify. guess all component other than nova have this problem ? so maybe remove this [nova] can get more input ... yes Best Regards! Kevin (Chen) Ji ? ? Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com Phone: +86-10-82454158 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC Inactive hide details for Alex Xu ---08/07/2014 04:54:09 PM---When I startup nova-network, it stuck at trying get lock for ebtaAlex Xu ---08/07/2014 04:54:09 PM---When I startup nova-network, it stuck at trying get lock for ebtables. @utils.synchronized('ebtables From: Alex Xu To: OpenStack Development Mailing List , 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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] nova-network stuck at get semaphores lock when startup
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@IBMCN Internet: jiche...@cn.ibm.com Phone: +86-10-82454158 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC From: Alex Xu To: OpenStack Development Mailing List , Date: 08/07/2014 04:54 PM Subject:[openstack-dev] [nova] nova-network stuck at get semaphores lockwhen 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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev