Cannot initialize nav2_bringup node [closed]

asked 2020-05-02 15:43:03 -0500

ShyamGanatra gravatar image

updated 2020-05-03 02:10:25 -0500

I am trying to use navigation2 on turtlebot3(burger) in simulation.

When I run the

ros2 launch nav2_bringup nav2_bringup_launch.py map:=turtlebot3_house.yaml

I am getting an error

[map_server-2] [FATAL] [map_server]: Lifecycle node entered errorstate
[lifecycle_manager-1] [ERROR] [lifecycle_manager]: Failed to change state for node: map_server
[lifecycle_manager-1] [ERROR] [lifecycle_manager]: Failed to bring up node: map_server, aborting bringup

can anyone help me on how to solve this?

more logs:

[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [lifecycle_manager-1]: process started with pid [29469]
[INFO] [map_server-2]: process started with pid [29470]
[INFO] [amcl-3]: process started with pid [29471]
[INFO] [world_model-4]: process started with pid [29472]
[INFO] [dwb_controller-5]: process started with pid [29479]
[INFO] [navfn_planner-6]: process started with pid [29493]
[INFO] [recoveries_node-7]: process started with pid [29497]
[INFO] [bt_navigator-8]: process started with pid [29499]
[lifecycle_manager-1] [INFO] [lifecycle_manager]: Creating
[lifecycle_manager-1] [INFO] [lifecycle_manager]: Starting the system bringup...
[lifecycle_manager-1] [INFO] [lifecycle_manager]: Creating and initializing lifecycle service clients
[lifecycle_manager-1] [INFO] [lifecycle_manager]: Configuring and activating map_server
[map_server-2] [INFO] [map_server]: Creating
[amcl-3] [INFO] [amcl]: Creating
[recoveries_node-7] [WARN] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[world_model-4] [INFO] [world_model]: Creating World Model
[recoveries_node-7] [INFO] [recoveries]: Configuring Spin
[recoveries_node-7] [INFO] [recoveries]: Configuring BackUp
[dwb_controller-5] [INFO] [dwb_controller]: Creating
[bt_navigator-8] [INFO] [bt_navigator]: Creating
[world_model-4] [INFO] [global_costmap.global_costmap]: Creating Costmap
[map_server-2] [INFO] [map_server]: Configuring
[map_server-2] [INFO] [map_server]: OccGridLoader: Creating
[map_server-2] [INFO] [map_server]: OccGridLoader: Configuring
[dwb_controller-5] [INFO] [local_costmap.local_costmap]: Creating Costmap
[map_server-2] [INFO] [map_server]: Activating
[map_server-2] [INFO] [map_server]: OccGridLoader: Activating
[lifecycle_manager-1] [INFO] [lifecycle_manager]: Configuring and activating amcl
[amcl-3] [INFO] [amcl]: Configuring
[amcl-3] [INFO] [amcl]: initTransforms
[navfn_planner-6] [INFO] [navfn_planner]: Creating
[amcl-3] [WARN] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[navfn_planner-6] [WARN] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[amcl-3] [INFO] [amcl]: initPubSub
[amcl-3] [INFO] [amcl]: Subscribed to map topic.
[amcl-3] [INFO] [amcl]: Activating
[lifecycle_manager-1] [INFO] [lifecycle_manager]: Configuring and activating world_model
[world_model-4] [INFO] [world_model]: Configuring
[world_model-4] [INFO] [global_costmap.global_costmap]: Configuring
[world_model-4] [INFO] [global_costmap.global_costmap]: Using plugin "static_layer"
[world_model-4] [INFO] [global_costmap.global_costmap]: Subscribing to the map topic (/map) with transient local durability
[world_model-4] [INFO] [global_costmap.global_costmap]: Using plugin "obstacle_layer"
[world_model-4 ...
(more)
edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by ShyamGanatra
close date 2020-07-11 01:31:57.440955

Comments

Please give us more logs to look at.

stevemacenski gravatar image stevemacenski  ( 2020-05-03 00:35:39 -0500 )edit

No transition matching 1 found for current state active

Did you try to activate multiple times?

stevemacenski gravatar image stevemacenski  ( 2020-05-03 15:50:23 -0500 )edit

No, I just clicked on start once.

ShyamGanatra gravatar image ShyamGanatra  ( 2020-05-03 19:55:05 -0500 )edit

Did you modify any files?

stevemacenski gravatar image stevemacenski  ( 2020-05-03 22:31:06 -0500 )edit

No, I just cloned the git repo for dashing and was trying the tutorial.

ShyamGanatra gravatar image ShyamGanatra  ( 2020-05-03 23:21:22 -0500 )edit