You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Client library (if applicable): both rclcpp and rclpy
Steps to reproduce issue
Two nodes are requried; a main node and a relay node.
The main node (1) launches the relay node and (2) publishes a random String message to topic input, and then kills the relay node. It remains persistent and repeats (1), (2), and (3).
The relay node simply relays the messages from the input topic to output topic, by subscribing to the input topic and publishing the same message to the output topic in the callback function registered to the subscription.
Let the main node run for several minutes. One could monitor the messages published to the output topic, but it is optional.
Expected behavior
Relay node is launched, and relays the message delivered to input topic.
Actual behavior
At one point, the relay node stops working, i.e., doesn't publish to topic output, and Fast-RTPS starts emitting the following error messages whenever the relay node is launched and a message is published to topic input:
2021-07-02 00:11:37.310 [SECURITY Error] WriterHistory cannot add the CacheChange_t -> Function exchange_participant_crypto
2021-07-02 00:11:37.310 [SECURITY Error] WriterHistory cannot add the CacheChange_t -> Function discovered_writer
2021-07-02 00:11:37.310 [RTPS_EDP Error] Security manager returns an error for writer ca.b4.f2.33.81.aa.bd.5d.96.42.1f.9|ff.0.3.c7 -> Function assignRemoteEndpoints
2021-07-02 00:11:37.310 [SECURITY Error] WriterHistory cannot add the CacheChange_t -> Function discovered_reader
2021-07-02 00:11:37.310 [RTPS_EDP Error] Security manager returns an error for writer ca.b4.f2.33.81.aa.bd.5d.96.42.1f.9|ff.0.3.c2 -> Function assignRemoteEndpoints
2021-07-02 00:11:37.310 [SECURITY Error] WriterHistory cannot add the CacheChange_t -> Function discovered_writer
2021-07-02 00:11:37.310 [RTPS_EDP Error] Security manager returns an error for writer ca.b4.f2.33.81.aa.bd.5d.96.42.1f.9|ff.0.4.c7 -> Function assignRemoteEndpoints
2021-07-02 00:11:37.310 [SECURITY Error] WriterHistory cannot add the CacheChange_t -> Function discovered_reader
2021-07-02 00:11:37.310 [RTPS_EDP Error] Security manager returns an error for writer ca.b4.f2.33.81.aa.bd.5d.96.42.1f.9|ff.0.4.c2 -> Function assignRemoteEndpoints
2021-07-02 00:11:37.310 [SECURITY Error] WriterHistory cannot add the CacheChange_t -> Function discovered_writer
2021-07-02 00:11:37.310 [RTPS_EDP Error] Security manager returns an error for reader ca.b4.f2.33.81.aa.bd.5d.96.42.1f.9|ff.2.0.c7 -> Function assignRemoteEndpoints
2021-07-02 00:11:37.310 [SECURITY Error] WriterHistory cannot add the CacheChange_t -> Function discovered_reader
2021-07-02 00:11:37.310 [RTPS_EDP Error] Security manager returns an error for writer ca.b4.f2.33.81.aa.bd.5d.96.42.1f.9|ff.2.0.c2 -> Function assignRemoteEndpoints
Even though the time required for this error to occur is random, it consistently happens across multiple runs of the main node.
The text was updated successfully, but these errors were encountered:
Bug report
Required Info:
Steps to reproduce issue
Two nodes are requried; a main node and a relay node.
String
message to topicinput
, and then kills the relay node. It remains persistent and repeats (1), (2), and (3).input
topic tooutput
topic, by subscribing to theinput
topic and publishing the same message to theoutput
topic in the callback function registered to the subscription.output
topic, but it is optional.Expected behavior
Relay node is launched, and relays the message delivered to
input
topic.Actual behavior
At one point, the relay node stops working, i.e., doesn't publish to topic
output
, and Fast-RTPS starts emitting the following error messages whenever the relay node is launched and a message is published to topicinput
:Even though the time required for this error to occur is random, it consistently happens across multiple runs of the main node.
The text was updated successfully, but these errors were encountered: