Ask Your Question
0

Failed to start Neutron-l3-agent in Network node

asked 2019-08-12 07:25:03 -0500

Harry996 gravatar image

Hello, I am trying to add Network Node by installing it manually. But unfortunately, the neutron-l3-agent did not start successfully. I checked the log but it did not provide any useful information for me to debug. Anyone can help me this? Thank you!

 root@networknode:/home/networknode# journalctl -u neutron-l3-agent.service
-- Logs begin at Sat 2019-07-20 00:56:13 UTC, end at Mon 2019-08-12 12:17:01 UTC. --
Aug 12 06:56:07 networknode systemd[1]: Started OpenStack Neutron L3 agent.
Aug 12 06:56:09 networknode systemd[1]: neutron-l3-agent.service: Main process exited, code=exited, sta
Aug 12 06:56:09 networknode systemd[1]: neutron-l3-agent.service: Failed with result 'exit-code'.
Aug 12 06:56:10 networknode systemd[1]: neutron-l3-agent.service: Service hold-off time over, schedulin
Aug 12 06:56:10 networknode systemd[1]: neutron-l3-agent.service: Scheduled restart job, restart counte
Aug 12 06:56:10 networknode systemd[1]: Stopped OpenStack Neutron L3 agent.
Aug 12 06:56:10 networknode systemd[1]: Started OpenStack Neutron L3 agent.
Aug 12 06:56:12 networknode systemd[1]: neutron-l3-agent.service: Main process exited, code=exited, sta
Aug 12 06:56:12 networknode systemd[1]: neutron-l3-agent.service: Failed with result 'exit-code'.
Aug 12 06:56:12 networknode systemd[1]: neutron-l3-agent.service: Service hold-off time over, schedulin
Aug 12 06:56:12 networknode systemd[1]: neutron-l3-agent.service: Scheduled restart job, restart counte
Aug 12 06:56:12 networknode systemd[1]: Stopped OpenStack Neutron L3 agent.
Aug 12 06:56:12 networknode systemd[1]: Started OpenStack Neutron L3 agent.
Aug 12 06:56:15 networknode systemd[1]: neutron-l3-agent.service: Main process exited, code=exited, sta
Aug 12 06:56:15 networknode systemd[1]: neutron-l3-agent.service: Failed with result 'exit-code'.
Aug 12 06:56:15 networknode systemd[1]: neutron-l3-agent.service: Service hold-off time over, schedulin
Aug 12 06:56:15 networknode systemd[1]: neutron-l3-agent.service: Scheduled restart job, restart counte
Aug 12 06:56:15 networknode systemd[1]: Stopped OpenStack Neutron L3 agent.
Aug 12 06:56:15 networknode systemd[1]: Started OpenStack Neutron L3 agent.
Aug 12 06:56:16 networknode systemd[1]: neutron-l3-agent.service: Main process exited, code=exited, sta
Aug 12 06:56:16 networknode systemd[1]: neutron-l3-agent.service: Failed with result 'exit-code'.
Aug 12 06:56:16 networknode systemd[1]: neutron-l3-agent.service: Service hold-off time over, schedulin
Aug 12 06:56:16 networknode systemd[1]: neutron-l3-agent.service: Scheduled restart job, restart counte
Aug 12 06:56:16 networknode systemd[1]: Stopped OpenStack Neutron L3 agent.
Aug 12 06:56:16 networknode systemd[1]: Started OpenStack Neutron L3 agent.
Aug 12 06:56:17 networknode systemd[1]: neutron-l3-agent.service: Main process exited, code=exited, sta
Aug 12 06:56:17 networknode systemd[1]: neutron-l3-agent.service: Failed with result 'exit-code'.
Aug 12 06:56:17 networknode systemd[1]: neutron-l3-agent.service: Service hold-off time over, schedulin
Aug 12 06:56:17 networknode systemd[1]: neutron-l3-agent.service: Scheduled restart job, restart counte
Aug 12 06:56:17 networknode systemd[1]: Stopped OpenStack Neutron L3 agent.
Aug 12 ...
(more)
edit retag flag offensive close merge delete

Comments

1

Is there an L3 log file under /var/log/neutron? If yes, it should contain messages that help understand the error.

Bernd Bausch gravatar imageBernd Bausch ( 2019-08-12 10:07:29 -0500 )edit

You are right! Thank you!

Harry996 gravatar imageHarry996 ( 2019-08-12 18:43:21 -0500 )edit

Here is the log file, Could you tell me what is the problem here? https://pastebin.com/raw/w5AbEaJZ

Harry996 gravatar imageHarry996 ( 2019-08-12 18:49:00 -0500 )edit

Hi @Bernd, What if there is no error in log file but I couldnt start the neutron-l3-agent service?

sakiraa gravatar imagesakiraa ( 2019-08-20 10:53:51 -0500 )edit

In this case I would start it on the command line and see what output it generates.

Bernd Bausch gravatar imageBernd Bausch ( 2019-08-20 10:58:23 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
1

answered 2019-08-12 22:44:26 -0500

updated 2019-08-12 22:44:59 -0500

You misspelled "linuxbrige" in the configuration. The L3 agent tries to find a "linuxbrige" driver that doesn't exist.

edit flag offensive delete link more

Comments

Could you tell me how to solve this issue? I am very new to this so.

Harry996 gravatar imageHarry996 ( 2019-08-13 07:14:44 -0500 )edit

Replace "linuxbrige" with "linuxbridge" in your configuration files, then restart Neutron.

Bernd Bausch gravatar imageBernd Bausch ( 2019-08-13 08:51:33 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

Stats

Asked: 2019-08-12 07:25:03 -0500

Seen: 28 times

Last updated: Aug 12