ROS2 foxy not seeing topics published in sudo shell
We often have problems with seeing topics from nodes started as super user. Sometimes we had this issue without sudo but I cannot reproduce it so I will focus on that point.
The easiest way for me to reproduce is starting the demo talker as super user:
open terminal -> sudo -s -> source /opt/ros/foxy/local_setup.sh -> ros2 run demo_nodes_cpp talker
Then open another terminal and source /opt/ros/foxy/local_setup.sh -> ros2 topic list
If I open the second terminal as super user I am able to see the chatter topic.
Is there anything I can do to make sure all nodes find each others topics on the same machine?
Edit: The reason my node has to run as root is we are capturing raw packages with pcap. That is also possible via specific capture capabilities but then you have issues with the path set by the setup scripts.
I tried to figure out what happens and after trying to show the ros2 topics as normal user the ros_daemon goes to 100% cpu load.
Edit2: The same issue arises when using different users where none is root but without the cpu load going up.
Perhaps an environment issue?
Did you set any env vars in the
.bashrcof the non-rootaccount? Perhaps a ROS domain ID?Edit: and you probably already know this, but running ROS nodes (whether ROS 1 or ROS 2) as
rootis not a good idea. It's also not often really needed (device access fi under Linux can often be solved using appropriate user accounts and/or capabilities).If you don't really need to run as
root, it may save time trying to figure out what's going wrong by using a different approach.Hi, we tried setting specific domain ids but that did not help. I will add some more information to my question.
I'm inclined to suspect environmental factors, as running ROS 2 nodes in Docker containers works for many users. Without configuring it differently, everything in a Docker container runs as
root.what does "but then you have issues with the path set by the setup scripts" mean?
you mean that the environment is sanatised by loading the binary?
I've seen setups with a secondary process being given the required capabilities and then the ROS node communicating with that process using IPC or some other mechanism.
Separates concerns nicely, but I can understand why that would perhaps be involved.
Basically you cannot find the shared libraries of ROS because the path is reset. Here is a description of the issue: https://stackoverflow.com/questions/9...
Yes, that's what I was referring to.
this seems like it could provide a clue.
Seeing as it's Python-based, you could see whether
pdbcan help finding out what's going on.You could also try running it not as a background process, but in a separate terminal.
@Sebastian could you elaborate on how you changed the DDS settings? I'm facing the same issue but can't figure out how to force UDP like you mention below.
We ended up using cyclone DDS which uses UDP. See here. Also in this discussion there is the description how to use fastRTPS with UDP via a config file and the environment variable FASTRTPS_DEFAULT_PROFILES_FILE.