Closed leeminju531 closed 2 years ago
Hi, for everyone reading this
In my case, the problem seems to be my fault of cyclonedds.xml settings and for the ros-rmw-daemon node having its information.
if once i run some nodes after having the cyclonedds.xml settings with a typo, the ros_rmw_node has its info. even if i modify it rightly, ros cli wasn't work.
after killing daemon process and re-running, it works.
Bug report
Required Info:
I setted cyclonedds.xml settings to connect two machines (A and B) and the communication between two machines was working. But, in the machine A, 'ros2 node list' and 'ros2 topic list' didn't show anythings while the system B was working well.
Machine A ) I had run below command In the machine A 'ros2 run demo_nodes_cpp talker' 'ros2 run demo_nodes_cpp listener' and ros cli commands
Machine B ) echo ros cli commands while a talker and listener nodes were working in system A.
Expected behavior
the machine A should show the ros cli responds like the machine B
Actual behavior
didn't
Additional information
after a reboot, it's working well.
I don't know why this is happened