[Openstack] Neutron crashing on controller node

kevin.breit@kevinbreit.net kevin.breit at kevinbreit.net
Wed Nov 27 17:37:34 UTC 2013


I fixed my problem. I'm not sure exactly which it was but it seems to work now.

First, I moved the auth_host and related items from [DEFAULT] to [keystone_authtoken]. Not sure if this is right. But it started working after I enabled a couple more parameters for qpid.

On November 27, 2013 at 9:48:03 AM, kevin.breit at kevinbreit.net (kevin.breit at kevinbreit.net) wrote:

Kyle,

Thanks for the response. Here is the output to the file. I also posted to a.o.o.

[ovs]
# (StrOpt) Type of network to allocate for tenant networks. The
# default value 'local' is useful only for single-box testing and
# provides no connectivity between hosts. You MUST either change this
# to 'vlan' and configure network_vlan_ranges below or change this to
# 'gre' or 'vxlan' and configure tunnel_id_ranges below in order for
# tenant networks to provide connectivity between hosts. Set to 'none'
# to disable creation of tenant networks.
#
tenant_network_type = gre
tunnel_id_ranges = 1:1000
enable_tunneling = True 
# Example: tenant_network_type = gre
# Example: tenant_network_type = vxlan

# (ListOpt) Comma-separated list of
# <physical_network>[:<vlan_min>:<vlan_max>] tuples enumerating ranges
# of VLAN IDs on named physical networks that are available for
# allocation. All physical networks listed are available for flat and
# VLAN provider network creation. Specified ranges of VLAN IDs are
# available for tenant network allocation if tenant_network_type is
# 'vlan'. If empty, only gre, vxlan and local networks may be created.
#
# network_vlan_ranges =
# Example: network_vlan_ranges = physnet1:1000:2999

# (BoolOpt) Set to True in the server and the agents to enable support
# for GRE or VXLAN networks. Requires kernel support for OVS patch ports and
# GRE or VXLAN tunneling.
#
# WARNING: This option will be deprecated in the Icehouse release, at which
#          point setting tunnel_type below will be required to enable
#          tunneling.
#
# enable_tunneling = False

# (StrOpt) The type of tunnel network, if any, supported by the plugin. If
# this is set, it will cause tunneling to be enabled. If this is not set and
# the option enable_tunneling is set, this will default to 'gre'.
#
# tunnel_type =
# Example: tunnel_type = gre
# Example: tunnel_type = vxlan

# (ListOpt) Comma-separated list of <tun_min>:<tun_max> tuples
# enumerating ranges of GRE or VXLAN tunnel IDs that are available for
# tenant network allocation if tenant_network_type is 'gre' or 'vxlan'.
#
# tunnel_id_ranges =
# Example: tunnel_id_ranges = 1:1000

# Do not change this parameter unless you have a good reason to.
# This is the name of the OVS integration bridge. There is one per hypervisor.
# The integration bridge acts as a virtual "patch bay". All VM VIFs are
# attached to this bridge and then "patched" according to their network
# connectivity.
#
# integration_bridge = br-int

# Only used for the agent if tunnel_id_ranges (above) is not empty for
# the server.  In most cases, the default value should be fine.
#
# tunnel_bridge = br-tun

# Peer patch port in integration bridge for tunnel bridge
# int_peer_patch_port = patch-tun

# Peer patch port in tunnel bridge for integration bridge
# tun_peer_patch_port = patch-int

# Uncomment this line for the agent if tunnel_id_ranges (above) is not
# empty for the server. Set local-ip to be the local IP address of
# this hypervisor.
#
# local_ip =

# (ListOpt) Comma-separated list of <physical_network>:<bridge> tuples
# mapping physical network names to the agent's node-specific OVS
# bridge names to be used for flat and VLAN networks. The length of
# bridge names should be no more than 11. Each bridge must
# exist, and should have a physical network interface configured as a
# port. All physical networks listed in network_vlan_ranges on the
# server should have mappings to appropriate bridges on each agent.
#
# bridge_mappings =
# Example: bridge_mappings = physnet1:br-eth1

[agent]
# Agent's polling interval in seconds
# polling_interval = 2

# (ListOpt) The types of tenant network tunnels supported by the agent.
# Setting this will enable tunneling support in the agent. This can be set to
# either 'gre' or 'vxlan'. If this is unset, it will default to [] and
# disable tunneling support in the agent. When running the agent with the OVS
# plugin, this value must be the same as "tunnel_type" in the "[ovs]" section.
# When running the agent with ML2, you can specify as many values here as
# your compute hosts supports.
#
# tunnel_types =
# Example: tunnel_types = gre
# Example: tunnel_types = vxlan
# Example: tunnel_types = vxlan, gre

# (IntOpt) The port number to utilize if tunnel_types includes 'vxlan'. By
# default, this will make use of the Open vSwitch default value of '4789' if
# not specified.
#
# vxlan_udp_port =
# Example: vxlan_udp_port = 8472

# (IntOpt) This is the MTU size of veth interfaces.
# Do not change unless you have a good reason to.
# The default MTU size of veth interfaces is 1500.
# veth_mtu =
# Example: veth_mtu = 1504

# (BoolOpt) Flag to enable l2-population extension. This option should only be
# used in conjunction with ml2 plugin and l2population mechanism driver. It'll
# enable plugin to populate remote ports macs and IPs (using fdb_add/remove
# RPC calbbacks instead of tunnel_sync/update) on OVS agents in order to
# optimize tunnel management.
#
# l2_population = False

[securitygroup]
# Firewall driver for realizing neutron security group function.
# firewall_driver = neutron.agent.firewall.NoopFirewallDriver
firewall-driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver

#-----------------------------------------------------------------------------
# Sample Configurations.
#-----------------------------------------------------------------------------
#
# 1. With VLANs on eth1.
# [database]
# connection = mysql://root:nova@127.0.0.1:3306/ovs_neutron
# [OVS]
# network_vlan_ranges = default:2000:3999
# tunnel_id_ranges =
# integration_bridge = br-int
# bridge_mappings = default:br-eth1
# [AGENT]
# Add the following setting, if you want to log to a file
#
# 2. With tunneling.
# [database]
# connection = mysql://root:nova@127.0.0.1:3306/ovs_neutron
# [OVS]
# network_vlan_ranges =
# tunnel_id_ranges = 1:1000
# integration_bridge = br-int
# tunnel_bridge = br-tun
# local_ip = 10.0.0.3


On November 27, 2013 at 7:40:14 AM, Kyle Mestery (kmestery) (kmestery at cisco.com) wrote:

On Nov 26, 2013, at 10:40 PM, Kevin Breit <kevin.breit at kevinbreit.net> wrote:
> I posted this on ask.openstack.org but didn't receive any responses so
> trying here.
>
> I am on CentOS 6.4 and trying to setup Neutron. Unfortunately I'm
> getting a crash when starting on this server. The snipped server.log
> file is...
>
> 2013-11-25 23:41:16.756 8105 INFO neutron.common.config [-] Logging
> enabled!
> 2013-11-25 23:41:16.757 8105 ERROR neutron.common.legacy [-] Skipping
> unknown group key: firewall_driver
> 2013-11-25 23:41:16.762 8105 INFO neutron.common.config [-] Config paste
> file: /etc/neutron/api-paste.ini
> 2013-11-25 23:41:16.822 8105 INFO neutron.manager [-] Loading Plugin:
> neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2
> 2013-11-25 23:41:16.974 8105 INFO
> neutron.plugins.openvswitch.ovs_neutron_plugin [-] Network VLAN ranges:
> {}
> 2013-11-25 23:41:17.009 8105 INFO
> neutron.plugins.openvswitch.ovs_neutron_plugin [-] Tunnel ID ranges:
> [(1, 1000)]
> 2013-11-25 23:41:17.093 8105 ERROR neutron.service [-] In serve_wsgi()
> 2013-11-25 23:41:17.093 8105 TRACE neutron.service Traceback (most
> recent call last):
> 2013-11-25 23:41:17.093 8105 TRACE neutron.service File
> "/usr/lib/python2.6/site-packages/neutron/service.py", line 96, in
> serve_wsgi
> 2013-11-25 23:41:17.093 8105 TRACE neutron.service service.start()
> 2013-11-25 23:41:17.093 8105 TRACE neutron.service File
> "/usr/lib/python2.6/site-packages/neutron/service.py", line 65, in start
> 2013-11-25 23:41:17.093 8105 TRACE neutron.service self.wsgi_app =
> _run_wsgi(self.app_name)
> 2013-11-25 23:41:17.093 8105 TRACE neutron.service File
> "/usr/lib/python2.6/site-packages/neutron/service.py", line 109, in
> _run_wsgi
> 2013-11-25 23:41:17.093 8105 TRACE neutron.service app =
> config.load_paste_app(app_name)
> 2013-11-25 23:41:17.093 8105 TRACE neutron.service File
> "/usr/lib/python2.6/site-packages/neutron/common/config.py", line 144,
> in load_paste_app
> 2013-11-25 23:41:17.093 8105 TRACE neutron.service app =
> deploy.loadapp("config:%s" % config_path, name=app_name)
> 2013-11-25 23:41:17.093 8105 TRACE neutron.service File
> "/usr/lib/python2.6/site-packages/PasteDeploy-1.5.0-py2.6.egg/paste/deploy/loadwsgi.py",
> line 247, in load
> app
> <snip>
> 2013-11-25 23:41:17.098 8105 TRACE neutron File
> "/usr/lib/python2.6/site-packages/oslo/config/cfg.py", line 1583, in
> __inner
> 2013-11-25 23:41:17.098 8105 TRACE neutron result = f(self, *args,
> **kwargs)
> 2013-11-25 23:41:17.098 8105 TRACE neutron File
> "/usr/lib/python2.6/site-packages/oslo/config/cfg.py", line 1743, in
> register_cli_opts
> 2013-11-25 23:41:17.098 8105 TRACE neutron
> self.register_cli_opt(opt, group, clear_cache=False)
> 2013-11-25 23:41:17.098 8105 TRACE neutron File
> "/usr/lib/python2.6/site-packages/oslo/config/cfg.py", line 1587, in
> __inner
> 2013-11-25 23:41:17.098 8105 TRACE neutron return f(self, *args,
> **kwargs)
> 2013-11-25 23:41:17.098 8105 TRACE neutron File
> "/usr/lib/python2.6/site-packages/oslo/config/cfg.py", line 1735, in
> register_cli_opt
> 2013-11-25 23:41:17.098 8105 TRACE neutron raise
> ArgsAlreadyParsedError("cannot register CLI option")
> 2013-11-25 23:41:17.098 8105 TRACE neutron ArgsAlreadyParsedError:
> arguments already parsed: cannot register CLI option
> 2013-11-25 23:41:17.098 8105 TRACE neutron
>
> What appears to be wrong?
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

I just replied to this on the ask site [1], can you please have
a look there and respond?

Thanks!
Kyle

[1] https://ask.openstack.org/en/question/7676/neutron-server-crashing-on-controller/?answer=7778#post-id-7778
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20131127/06522b10/attachment.html>


More information about the Openstack mailing list