In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-30 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)05/31 Report--
This article will explain in detail how to create a CVM failure error report Exceeded maximum number of retries. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.
1. Error message
When doing the test, I found that the creation of the CVM failed. Click on the overview to see
two。 Check the log
On the error message, check the log of neutron, check server.log, and see the following information:
2017-06-08 17 90b1-e46c9898d1a4 7a969cf8b5f04efdbe1af5e8ac690698 73948300ef77444cbdcf96fa60e0158f 22 ERROR neutron.plugins.ml2.managers 52.103 1434130 [req-1ace1476-a027-4409-90b1-e46c9898d1a4 7a969cf8b5f04efdbe1af5e8ac690698 73948300ef77444cbdcf96fa60e0158f -] Failed to bind port f8d9b6f2-b8ba-4351-ba51-28321be3dd85 on host dlw2 for vnic_type normal using segments [{'segmentation_id': 78,' physical_network': None, 'id': u'e6bc5f71-03c3-4453-bee8-0933096bf682' 2017-06-08 1722 90b1-e46c9898d1a4 7a969cf8b5f04efdbe1af5e8ac690698 73948300ef77444cbdcf96fa60e0158f 52.103 1434130 INFO neutron.plugins.ml2.plugin [req-1ace1476-a027-4409-90b1-e46c9898d1a4 7a969cf8b5f04efdbe1af5e8ac690698 73948300ef77444cbdcf96fa60e0158f -] Attempt 10 to bind port f8d9b6f2-b8ba-4351-ba51-28321be3dd852017-06-08 1722 Attempt 52.116 1434130 WARNING neutron.plugins.ml2.drivers.mech_agent [req-1ace1476-a027-4409-90b1-e46c9898d1a4 7a969cf8b5f04efdbe1af5e8ac690698 73948300ef77444cbdcf96fa60e0158f -] Refusing to bind port f8d9b6f2lue b8ba- 4351-ba51-28321be3dd85 to dead agent: {'binary': upright bridges:' linuxbridgeway.' 'description': None,' admin_state_up': True, 'heartbeat_timestamp': datetime.datetime (2017, 6, 8, 8, 48, 20),' availability_zone': None, 'alive': False,' topic': uplink, 'host': utilisation dlw2,' agent_type': u'Linux bridge agent', 'resource_versions': {upright SubPortals: upright 1.0, upright QosPolicing: upright 1.3' Created_at': datetime.datetime (2017, 6, 2, 9, 1, 38), 'started_at': datetime.datetime (2017, 6, 2, 9, 8, 15),' id': u'a4c3d014-531f-4f08-aea8-3f2a36e08d43), 'configurations': {upright tunneling mapping: upright 172.16.40.2, upright deviceship: 5, upright interfacemapping: {upright provisioning: upright eno2'} Upright extension: [], upright extension: [], ubiquitous tunneling 90b1-e46c9898d1a4 7a969cf8b5f04efdbe1af5e8ac690698 73948300ef77444cbdcf96fa60e0158f populationalization: True, ubiquitous tunneling mapping: [upright vxlan'], ubiquitous bridgeable mapping: {}} 2017-06-08 17 90b1-e46c9898d1a4 7a969cf8b5f04efdbe1af5e8ac690698 73948300ef77444cbdcf96fa60e0158f 22 1434130 ERROR neutron.plugins.ml2.managers [req-1ace1476-a027-4409-90b1-e46c9898d1a4 7a969cf8b5f04efdbe1af5e8ac690698 73948300ef77444cbdcf96fa60e0158f -] Failed to bind port f8d9b6f2-b8ba-4351-ba51-28321be3dd85 on host dlw2 for vnic_type normal using segments [{'segmentation_id': 78,' physical_network': None] 'id': u'e6bc5f71-03c3-4453-bee8-0933096bf682,' network_type': uplift vxlan'}] 3. Log analysis
Seeing {upright tunneling ipsilateral: upright 172.16.40.2, upright deviceschecking, I found tunneling_ip, thought of Linux bridge agent service, and checked the neutron service.
# neutron agent-list | grep Linux | a4c3d014-531f-4f08-aea8-3f2a36e08d43 | Linux bridge agent | dlw2 | | xxx | True | neutron-linuxbridge-agent | | df626dfb-a874-44d6-9ce2-a5e7d8157500 | Linux bridge agent | dlw1 | | xxx | True | neutron-linuxbridge-agent | | e04db880-1e77-4bf6-9321-dea7791d1eaf | Linux bridge agent | dlw3 | | xxx | True | neutron-linuxbridge-agent |
It is found that all three linuxbridgeagent are xxx for down.
[root@dlw1 openrc] # for i in `neutron agent-list | grep Li | awk-F'|'{print $2}'`; do neutron agent-show $I Done+-+--+ | Field | Value | +-+- -- + | admin_state_up | True | | agent_type | Linux bridge agent | | alive | False | | availability_zone | | | binary | neutron-linuxbridge-agent | | configurations | {| | "tunneling_ip": "172.16.40.2" | "devices": 5, | "interface_mappings": {| | "provider": "eno2" |} | | "extensions": [], | | "l2_population": true | | "tunnel_types": [| "vxlan" | | "bridge_mappings": {} |} | | created_at | 2017-06-02 09:01:38 | | description | | | heartbeat_timestamp | 2017-06-08 08:48:20 | | host | dlw2 | | id | a4c3d014-531f-4f08-aea8-3f2a36e08d43 | | started_at | 2017-06-02 09:08:15 | | topic | NambiA | | | +-+-- + + -+ | Field | Value | +-+-- + | admin_state_up | True | | agent_type | Linux bridge agent | | alive | False | | availability_zone | | binary | neutron-linuxbridge-agent | | configurations | { | "tunneling_ip": "172.16.40.1" | "devices": 5, | "interface_mappings": {| | "provider": "eno2" |} | | "extensions": [], | | "l2_population": true | | "tunnel_types": [| "vxlan" | | "bridge_mappings": {} |} | | created_at | 2017-06-02 09:01:39 | | description | | | heartbeat_timestamp | 2017-06-08 08:46:50 | | host | dlw1 | | id | df626dfb-a874-44d6-9ce2-a5e7d8157500 | | started_at | 2017-06-02 09:08:18 | | topic | NambiA | | | +-+-- + + -+ | Field | Value | +-+-- + | admin_state_up | True | | agent_type | Linux bridge agent | | alive | False | | availability_zone | | binary | neutron-linuxbridge-agent | | configurations | { | "tunneling_ip": "172.16.40.3" | "devices": 3, | "interface_mappings": {| | "provider": "eno2" |} | | "extensions": [], | | "l2_population": true | | "tunnel_types": [| "vxlan" | | "bridge_mappings": {} |} | | created_at | 2017-06-02 09:02:37 | | description | | | heartbeat_timestamp | 2017-06-08 08:48:17 | | host | dlw3 | | id | e04db880-1e77-4bf6-9321-dea7791d1eaf | | started_at | 2017-06-02 09:08:11 | | topic | NambiA | | +-+-- + 4. Start the service
It may have caused the down of the neutron service when restarting the linuxbridgeagent service before, so it should be no problem to restart the service if there is an error above.
# systemctl restart neutron-linuxbridge-agent.service
Recreate the CVM and find that the CVM has been created successfully.
This is the end of the article on "what to do if you failed to create a CVM and report an error Exceeded maximum number of retries". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.