This error is not a standard ROS output. Instead, it typically surfaces when a custom rqt plugin or a node named "Odin" (a common internal codename for autonomy stacks, custom executors, or specific robotic platforms) fails to close its ROS GUI components gracefully. The rqtclose signal indicates that the GUI was either forcibly terminated, lost a connection to the ROS master, or encountered a deadlock during shutdown.
def shutdown_plugin(self): rospy.loginfo("odin rqtclose: Starting shutdown sequence") # Disconnect callbacks self.pub.unregister() rospy.loginfo("odin rqtclose: Publishers unregistered") # Call parent super().shutdown_plugin() rospy.loginfo("odin rqtclose: Complete") If you see the first log but not the last, you’ve found a hang. Attach strace to the stuck rqt process (find PID via ps aux | grep rqt ): odin rqtclose
def shutdown_plugin(self): self._timer.stop() rospy.signal_shutdown("odin rqtclose: Plugin closing") rospy.sleep(0.5) # Give ROS time to clean up Launch rqt with a timeout: This error is not a standard ROS output
sudo strace -p <PID> -e trace=network If you see repeated poll or recvfrom calls without returning, the GUI is waiting for a dead ROS topic. Before closing rqt , run: def shutdown_plugin(self): rospy
import signal signal.signal(signal.SIGTERM, my_shutdown_handler) If that handler calls sys.exit() without cleaning up rqt , you’ll see rqtclose errors. Modify your rqt plugin’s shutdown_plugin() method: