bt navigator crash ?
Hello all,
Just a quick error since I compile the navigation stack from source, I just update the plugins inside the nav2_bt_navigator without touching the node source.
Here is the error I got
[bt_navigator-14] [INFO] [1642690335.156322425] [bt_navigator]: Configuring [bt_navigator-14] [bt_navigator-14] >>> [rcutils|error_handling.c:108] rcutils_set_error_state() [bt_navigator-14] This error state is being overwritten: [bt_navigator-14] [bt_navigator-14] 'invalid empty action name, at /tmp/binarydeb/ros-foxy-rcl-action-1.1.11/src/rcl_action/names.c:36' [bt_navigator-14] [bt_navigator-14] with this new error message: [bt_navigator-14] [bt_navigator-14]
'failed to get goal service name, at /tmp/binarydeb/ros-foxy-rcl-action-1.1.11/src/rcl_action/action_client.c:215' [bt_navigator-14] [bt_navigator-14] rcutils_reset_error() should be called after error handling to avoid this. [bt_navigator-14] <<< [bt_navigator-14] [ERROR] [1642690335.188702451] [bt_navigator_rclcpp_node.rclcpp_action]: Error in destruction of rcl action client handle: action client implementation is invalid, at /tmp/binarydeb/ros-foxy-rcl-action-1.1.11/src/rcl_action/action_client.c:470 [bt_navigator-14] [ERROR] [1642690335.188874993] []: Caught exception in callback for transition 10 [bt_navigator-14] [ERROR] [1642690335.188889154] []: Original error: could not initialize rcl action client: failed to get goal service name, at /tmp/binarydeb/ros-foxy-rcl-action-1.1.11/src/rcl_action/action_client.c:215 [bt_navigator-14] [WARN] [1642690335.188931476] []: Error occurred while doing error handling. [bt_navigator-14] [FATAL] [1642690335.188944149] [bt_navigator]: Lifecycle node bt_navigator does not have error state implemented
Hi @TomSon, have you reviewed this prior question #q344030. Similar error.
Thanks for your advice I try to load a simple xml and it didn't crash and it didn't display anything also, is it a correct start ?
Yes I believe that's correct as far as I know, but I am new to nav2.
me too ^^ also
Seems to be the behavior tree the issue but it has no meaningful logs telling what it doesn't like