ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
[moving my comment down into the answers]
Looking at the timestamps of the output you posted, the warning
[WARN] [1627469418.6436**00791**] [lc_client]: Failed to trigger transition 3
actually happens before the transition to unconfigured
[INFO] [1627469418.6436**25385**] [lc_listener]: notify callback: Transition from state errorprocessing to unconfigured
by some number of microseconds.
If the process didn't die after the warning, it could be that its just a bit of confusion due to the way the scheduler bundled the different logging processes