ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

How do I stop these nodes from running

asked 2023-06-06 10:04:36 -0500

koener gravatar image

updated 2023-06-06 11:10:30 -0500

gvdhoorn gravatar image

For context, I am working on a simulation for a robot and I am using an external library for pointcloud to laserscan conversion. Everything was originally working fine, but all of a sudden I have these ros2 nodes running which I can't figure out how to kill. I believe they are stopping my TF frames from registering. I have tried using the kill command and trying to find them using "htop", and I have tried finding them in my system monitor, but I can't seem to locate them anywhere to try and shut them down. These are the names of the nodes and the properties:

/vtr/boreas_odometry_feaeexyoeg
/vtr/boreas_odometry_xkzleovjry
/vtr/boreas_odometry_yvjvpzmakr

from node info:

/vtr/boreas_odometry_feaeexyoeg
  Subscribers:
    /clock: rosgraph_msgs/msg/Clock
    /parameter_events: rcl_interfaces/msg/ParameterEvent
  Publishers:
    /clock: rosgraph_msgs/msg/Clock
    /parameter_events: rcl_interfaces/msg/ParameterEvent
    /rosout: rcl_interfaces/msg/Log
    /tf: tf2_msgs/msg/TFMessage
    /tf_static: tf2_msgs/msg/TFMessage
    /vtr/boreas_2021_09_09_15_28_lidar_odometry: std_msgs/msg/String
    /vtr/filtered_point_cloud: sensor_msgs/msg/PointCloud2
    /vtr/loc_path: nav_msgs/msg/Path
    /vtr/odometry: nav_msgs/msg/Odometry
    /vtr/raw_point_cloud: sensor_msgs/msg/PointCloud2
    /vtr/submap_odo: sensor_msgs/msg/PointCloud2
    /vtr/udist_point_cloud: sensor_msgs/msg/PointCloud2
  Service Servers:
    /vtr/boreas_odometry_feaeexyoeg/describe_parameters: rcl_interfaces/srv/DescribeParameters
    /vtr/boreas_odometry_feaeexyoeg/get_parameter_types: rcl_interfaces/srv/GetParameterTypes
    /vtr/boreas_odometry_feaeexyoeg/get_parameters: rcl_interfaces/srv/GetParameters
    /vtr/boreas_odometry_feaeexyoeg/list_parameters: rcl_interfaces/srv/ListParameters
    /vtr/boreas_odometry_feaeexyoeg/set_parameters: rcl_interfaces/srv/SetParameters
    /vtr/boreas_odometry_feaeexyoeg/set_parameters_atomically: rcl_interfaces/srv/SetParametersAtomically
  Service Clients:
    /vtr/boreas_odometry_feaeexyoeg/describe_parameters: rcl_interfaces/srv/DescribeParameters
    /vtr/boreas_odometry_feaeexyoeg/get_parameter_types: rcl_interfaces/srv/GetParameterTypes
    /vtr/boreas_odometry_feaeexyoeg/get_parameters: rcl_interfaces/srv/GetParameters
    /vtr/boreas_odometry_feaeexyoeg/list_parameters: rcl_interfaces/srv/ListParameters
    /vtr/boreas_odometry_feaeexyoeg/set_parameters: rcl_interfaces/srv/SetParameters
    /vtr/boreas_odometry_feaeexyoeg/set_parameters_atomically: rcl_interfaces/srv/SetParametersAtomically
edit retag flag offensive close merge delete

Comments

Where ROS 1 was localhost by default, ROS 2 is everything-on-your-network by default.

Is someone else perhaps also running ROS 2 nodes on your network?

gvdhoorn gravatar image gvdhoorn  ( 2023-06-06 11:11:27 -0500 )edit

If @gvdhoorn's guess is correct, you need to set a unique domain id. This is a DDS config parameter.

Mike Scheutzow gravatar image Mike Scheutzow  ( 2023-06-07 10:08:32 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2023-06-07 11:52:40 -0500

koener gravatar image

Thank you for the responses. It wasn't any of these issues but I appreciate them being addressed. I am new to ROS2 and LINUX so I may have been missing something when trying to find these nodes in system manager, but what fixed it was forcing ROS2 to crash by shutting down python in terminal.

edit flag offensive delete link more

Question Tools

Stats

Asked: 2023-06-06 10:04:36 -0500

Seen: 114 times

Last updated: Jun 06 '23