Quantcast
Channel: ROS Answers: Open Source Q&A Forum - RSS feed
Viewing all articles
Browse latest Browse all 40

run_id on parameter server does not match declared run_id

$
0
0
I have set up several `roslaunch` files to be launched at system startup using `systemd`. However at the startup they show the above error and fail. When I set the `systemd` services to be restarted on failure, launch files are relaunched when failed and work fine. What might I be doing wrong here? **Declared `run_id` for each `roslaunch` seems to be different from each other at the first launch.** The error is in the following format run_id on parameter server does not match declared run_id: 686cb5dc-01cf-11e9-ab7c-b10995016401 vs 68b27f9a-01cf-11e9-ab7c-b10995016401 Here's a sample script that runs a launch file #!/bin/bash sleep 1 source /opt/ros/kinetic/setup.bash source /my/workspace/path/devel/setup.bash roslaunch /launch/file/path/myfile.launch Here's the format of the systemd services I use [Unit] Description=Unit description Wants=roscore.service BindsTo=roscore.service [Service] User=username ExecStart=/script/that/runs/the/launch/file.sh Restart=on-failure RestartSec=1 [Install] WantedBy=multi-user.target `roscore.service` starts a roscore. I am using `kinetic` on `Ubuntu 16.04`.

Viewing all articles
Browse latest Browse all 40

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>