[Openstack] Unable to start neutron dhcp agent [ICEHOUSE]

Shanker Gudipati shanker_gudipati at persistent.com
Sun Apr 10 17:17:54 UTC 2016


HI Rahul ,


Thanks for the reply.


I have seen the Disc space,it is good. Talking about the dependent services metdata service and dhcp service are down. i can see these services are down by using neutron agent-list command.



DEBUG neutron.openstack.common.rpc.amqp [-] received {u'_context_roles': [u'admin'], u'_context_request_id': u'req-e94f263c-886f-4ad6-be83-9f272cf2186f', u'_context_read_deleted': u'no', u'_context_user_name': u'neutron', u'_context_project_name': u'service', u'namespace': None, u'_context_tenant_id': u'521c00a7992a4e678fe200d4ba689fb6', u'args': {u'payload': {u'port': {u'status': u'DOWN', u'binding:host_id': u'Compute3', u'name': u'', u'allowed_address_pairs': [], u'admin_state_up': True, u'network_id': u'd065ea4e-1436-4377-8d67-b68015e4aed8', u'tenant_id': u'f451e7248c1446e19f068911671652c2', u'binding:vif_details': {u'port_filter': True, u'ovs_hybrid_plug': True}, u'binding:vif_type': u'ovs', u'device_owner': u'compute:compute3', u'mac_address': u'fa:16:3e:32:bd:a9', u'fixed_ips': [{u'subnet_id': u'9d4f0b3d-e152-4f5a-895f-58ffd130f9b2', u'ip_address': u'10.35.51.114'}], u'id': u'0d61bc40-df7b-4a91-8dec-a2b0370c7985', u'security_groups': [u'6a69352a-2f50-426c-be87-8eeec6e49bc0'], u'device_id': u'1ca54fbb-1104-42ca-85c4-9ec73ef025b0'}}}, u'_context_tenant': u'521c00a7992a4e678fe200d4ba689fb6', u'_unique_id': u'd3f47c25b7d54842b1377626131dff5d', u'_context_is_admin': True, u'version': u'1.0', u'_context_timestamp': u'2016-04-10 17:09:18.146615', u'_context_tenant_name': u'service', u'_context_user': u'c38cac19d3524453b634c03ed2dba7de', u'_context_user_id': u'c38cac19d3524453b634c03ed2dba7de', u'method': u'port_create_end', u'_context_project_id': u'521c00a7992a4e678fe200d4ba689fb6'} _safe_log /usr/lib/python2.7/dist-packages/neutron/openstack/common/rpc/common.py:280
2016-04-10 12:23:17.223 13539 DEBUG neutron.openstack.common.rpc.amqp [-] unpacked context: {'project_name': u'service', 'user_id': u'c38cac19d3524453b634c03ed2dba7de', 'roles': [u'admin'], 'tenant_id': u'521c00a7992a4e678fe200d4ba689fb6', 'timestamp': u'2016-04-10 17:09:18.146615', 'is_admin': True, 'read_deleted': u'no', 'request_id': u'req-e94f263c-886f-4ad6-be83-9f272cf2186f', 'tenant_name': u'service', 'project_id': u'521c00a7992a4e678fe200d4ba689fb6', 'user_name': u'neutron', 'tenant': u'521c00a7992a4e678fe200d4ba689fb6', 'user': u'c38cac19d3524453b634c03ed2dba7de'} _safe_log /usr/lib/python2.7/dist-packages/neutron/openstack/common/rpc/common.py:280
2016-04-10 12:23:17.224 13539 DEBUG neutron.openstack.common.lockutils [req-e94f263c-886f-4ad6-be83-9f272cf2186f None] Got semaphore "dhcp-agent" lock /usr/lib/python2.7/dist-packages/neutron/openstack/common/lockutils.py:168
2016-04-10 12:23:17.224 13539 DEBUG neutron.openstack.common.lockutils [req-e94f263c-886f-4ad6-be83-9f272cf2186f None] Got semaphore / lock "port_update_end" inner /usr/lib/python2.7/dist-packages/neutron/openstack/common/lockutils.py:248
2016-04-10 12:23:17.225 13539 DEBUG neutron.agent.dhcp_agent [req-e94f263c-886f-4ad6-be83-9f272cf2186f None] Calling driver for network: d065ea4e-1436-4377-8d67-b68015e4aed8 action: reload_allocations call_driver /usr/lib/python2.7/dist-packages/neutron/agent/dhcp_agent.py:119
2016-04-10 12:23:17.239 13539 DEBUG neutron.agent.linux.dhcp [req-e94f263c-886f-4ad6-be83-9f272cf2186f None] DHCP for d065ea4e-1436-4377-8d67-b68015e4aed8 pid 4117 is stale, ignoring command disable /usr/lib/python2.7/dist-packages/neutron/agent/linux/dhcp.py:194
2016-04-10 12:23:17.287 13539 DEBUG neutron.agent.linux.dhcp [req-e94f263c-886f-4ad6-be83-9f272cf2186f None] Killing dhcpmasq for network since all subnets have turned off DHCP: d065ea4e-1436-4377-8d67-b68015e4aed8 reload_allocations /usr/lib/python2.7/dist-packages/neutron/agent/linux/dhcp.py:398
2016-04-10 12:23:17.288 13539 DEBUG neutron.openstack.common.lockutils [req-e94f263c-886f-4ad6-be83-9f272cf2186f None] Semaphore / lock released "port_update_end" inner /usr/lib/python2.7/dist-packages/neutron/openstack/common/lockutils.py:252

regards

Shanker



________________________________
From: Rahul Sharma <rahulsharmaait at gmail.com>
Sent: Saturday, April 9, 2016 11:59 PM
To: Shanker Gudipati
Cc: openstack at lists.openstack.org; Kumar Anuj
Subject: Re: [Openstack] Unable to start neutron dhcp agent [ICEHOUSE]

Check the logs in /var/log/neutron/dhcp-agent.log on the node where your neutron services are running.

DNSMASQ would be run by neutron-dhcp-agent. Since dhcp-agent is failing, hence you are not seeing any dnsmasq processes. Sometimes, such issues occur if disk is full or other dependent services are not running.

Rahul Sharma
MS in Computer Science, 2016
College of Computer and Information Science, Northeastern University
Mobile:  801-706-7860
Email: rahulsharmaait at gmail.com<mailto:rahulsharmaait at gmail.com>

On Sat, Apr 9, 2016 at 1:56 PM, Shanker Gudipati <shanker_gudipati at persistent.com<mailto:shanker_gudipati at persistent.com>> wrote:
Hi

We have OpenStack cloud setup on ICEHOUSE version.

We are facing an issue. Issue : VM is not getting the IP address released from DHCP agent.DB entry of IP address  for every instance is made. We have seen the host file of DHCP service.(Host File : where MAC address and IP address mappings are maintained). We have increased the timeout in neutron.conf and started the debug process. During debug process, we have manually killed the DNSMASQ service of DHCP agent using kill command. Now if we manually start the neutron DHCP agent, the service is not getting started.

IS this due to killing the process of DNSMASQ service manually, if so how to start DNSMASQ service explictly so neutron dhcp agent service can be started.

No logs available. If we start the DHCP service, it's not getting started. neutron agent-list shows "xx" for DHCP agent.

Thanks in advance.

regards
SHanker

DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack



DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160410/2e6431e9/attachment.html>


More information about the Openstack mailing list