ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
2 runtime_manager "Failed connect to /tmp/autoware_proc_manager"

asked 2019-07-20 13:57:49 -0600

hirokawakubo gravatar image

updated 2019-07-30 23:47:04 -0600

jayess gravatar image

I installed latest version of (ver 1.12.0) and ran the ROSBAG demo described here.

From rviz, I can confirm that demo is working fine. However, in the terminal window that opened by runtime_manager is giving "Failed connect to /tmp/autoware_proc_manager".

What does this message means and is this something I should try to fix or just ignore?

The following is the entire messages on the terminal screen after I launched "Map", "Sensing", "Localization" and "Detection" launch files.

My environment: x86 ROS Kinetics Ubuntu 16.04LTS Ver 1.12.0

bash: ./../../../setup.bash: No such file or directory
mkdir: cannot create directory ‘/home/hiro/.rviz’: File exists
/home/hiro/ wxPyDeprecationWarning: Call to deprecated item. 
loading param.yaml
loading qs.yaml
Subscribe[localization] topic=/ndt_stat, key=/ndt_stat.NDTStat.exe_time
Subscribe[detection] topic=/topic2, key=/topic2
Subscribe[detection] topic=/topic1, key=/topic1
loading setup.yaml
['rosparam', 'set', 'tf_x', '1.2']
['rosparam', 'set', 'tf_y', '0.0']
['rosparam', 'set', 'tf_z', '2.0']
['rosparam', 'set', 'tf_yaw', '0.0']
['rosparam', 'set', 'tf_pitch', '0.0']
['rosparam', 'set', 'tf_roll', '0.0']
['rosparam', 'set', 'localizer', 'velodyne']
loading map.yaml
loading sensing.yaml
loading computing.yaml
loading interface.yaml
loading data.yaml
loading simulation.yaml
['rosparam', 'set', '/use_sim_time', 'false']
loading status.yaml
loading state.yaml
loading topics.yaml
['rosparam', 'set', '/use_sim_time', 'true']
['rosbag', 'play', '--start=140', '--clock', '/home/hiro/.autoware/sample_moriyama_150324.bag']
sched policy=OTHER prio=0
Failed connect to /tmp/autoware_proc_manager
['roslaunch', '/home/hiro/']
sched policy=OTHER prio=0
Failed connect to /tmp/autoware_proc_manager
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00167_-00864.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00153_-00852.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00159_-00859.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00160_-00861.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00148_-00849.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00168_-00866.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00147_-00851.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00149_-00847.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00156_-00854.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00158_-00858.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00147_-00847.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00154_-00852.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00158_-00857.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00154_-00851.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00167_-00866.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00168_-00865.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00169_-00868.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00147_-00849.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00153_-00850.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00154_-00853.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00161_-00861.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00168_-00867.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00151_-00849.pcd
load /home/hiro/.autoware/data/map/pointcloud_map/bin_Laser-00153_-00851.pcd
['roslaunch', '/home/hiro/ ...
edit retag flag offensive close merge delete

2 Answers

Sort by » oldest newest most voted

answered 2019-07-30 23:35:51 -0600

Josh Whitley gravatar image

This is OK, especially for the demo. The run_proc_manager script is called by the run script, which is called by the launch file that you run in the demo. run_proc_manager creates a file at /tmp/autoware_proc_manager which keeps track of the processes that are launched by the Runtime Manager GUI. After this, the terminal from which you launched the runtime manager tries to connect to the file to output data on the terminal about which processes are being launched. The data are just informational so not connecting to that file is fine.

edit flag offensive delete link more


Hi Josh,

Thanks for the response. It's good to know that it's not a real issue.

hirokawakubo gravatar image hirokawakubo  ( 2020-01-14 09:52:33 -0600 )edit

answered 2020-03-11 04:36:38 -0600

sneibus gravatar image

hi guys, i hvae installed ros melodic and autoware on wsl. I get this error when roslaunch and similar rosrun. can someone help please

$ roslaunch runtime_manager ... logging to /home/sneibus/.ros/log/ee337b6a-6376-11ea-b10d-708bcd595ab7/roslaunch-CLAYTEX33-419.log Checking log directory for disk usage. This may take awhile. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB.

RLException: Invalid roslaunch XML syntax: not well-formed (invalid token): line 1, column 1 The traceback for the exception was written to the log file

edit flag offensive delete link more



Please do not post questions as answers. Your question also appears to be unrelated to the topic discussed in this Q&A.

Post a new question and delete your answer here.

gvdhoorn gravatar image gvdhoorn  ( 2020-03-11 05:22:45 -0600 )edit

Question Tools


Asked: 2019-07-20 13:57:49 -0600

Seen: 2,928 times

Last updated: Mar 11 '20