ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
1

stop: unknown instance

asked 2012-05-03 04:22:09 -0500

Ozkan gravatar image

updated 2012-05-03 05:24:39 -0500

Relatively new turtlebot user.
I had a clean Ubuntu 11.10 install to my turtlebot laptop (a HP Mini). I installed ROS electric following the instructions here:
http://ros.org/wiki/Robots/TurtleBot/Robot%20Install
I changed ROS_MASTER_URI and ROS_HOSTNAME on laptop and rebooted. I get the following when trying to stop turtlebot service

turtlebot@turtlebot1:~$ sudo service turtlebot stop
stop: Unknown instance:

Next, I started turtlebot service.
I can start as many instances as I want without any warning:

turtlebot@turtlebot1:~$ sudo service turtlebot start
turtlebot start/running, process 2089
turtlebot@turtlebot1:~$ sudo service turtlebot start
turtlebot start/running, process 2247
turtlebot@turtlebot1:~$ sudo service turtlebot start
turtlebot start/running, process 2405

Although turtlebot service is started (3 times) communication with master fails:

turtlebot@Turtlebot-WS:~$ rostopic echo /diagnostics
ERROR: Unable to communicate with master!

My problem is similar to http://answers.ros.org/question/12933/turtlebot-upstart-install-failure
That one was solved by installing daemontools. It was installed at this step:
sudo apt-get install ros-electric-turtlebot-robot
during ROS installation.

What is missing?

Before you ask, ouput of ps axuf

turtlebot@turtlebot1:~$ ps auxf
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         2  0.0  0.0      0     0 ?        S    17:42   0:00 [kthreadd]
root         3  0.2  0.0      0     0 ?        S    17:42   0:02  \_ [ksoftirqd/0]
root         6  0.0  0.0      0     0 ?        S    17:42   0:00  \_ [migration/0]
root         7  0.0  0.0      0     0 ?        S    17:42   0:00  \_ [migration/1]
root         8  0.0  0.0      0     0 ?        S    17:42   0:00  \_ [kworker/1:0]
root         9  0.0  0.0      0     0 ?        S    17:42   0:00  \_ [ksoftirqd/1]
root        11  0.0  0.0      0     0 ?        S<   17:42   0:00  \_ [cpuset]
root        12  0.0  0.0      0     0 ?        S<   17:42   0:00  \_ [khelper]
root        13  0.0  0.0      0     0 ?        S<   17:42   0:00  \_ [netns]
root        15  0.0  0.0      0     0 ?        S    17:42   0:00  \_ [sync_supers]
root        16  0.0  0.0      0     0 ?        S    17:42   0:00  \_ [bdi-default]
root        17  0.0  0.0      0     0 ?        S<   17:42   0:00  \_ [kintegrityd]
root        18  0.0  0.0      0     0 ?        S<   17:42   0:00  \_ [kblockd]
root        19  0.0  0.0      0     0 ?        S<   17:42   0:00  \_ [ata_sff]
root        20  0.0  0.0      0     0 ?        S    17:42   0:00  \_ [khubd]
root        21  0.0  0.0      0     0 ?        S<   17:42   0:00  \_ [md]
root        22  0.0  0.0      0     0 ?        S    17:42   0:00  \_ [kworker/1:1]
root        23  0.0  0.0      0     0 ?        S    17:42   0:00  \_ [khungtaskd]
root        24  0.0  0.0      0     0 ?        S    17:42   0:00  \_ [kswapd0]
root        25  0.0  0.0      0     0 ?        SN   17:42   0:00  \_ [ksmd]
root ...
(more)
edit retag flag offensive close merge delete

Comments

Did you run the "sudo ./install.bash wlan0" command? If so, does wlan0 have an IP? (If it doesn't, the service will probably not start ROS)

Ryan gravatar image Ryan  ( 2012-05-04 18:29:43 -0500 )edit

Yes. I run sudo ./install.bash wlan0 command. But that didnt help. With a clean (and more stable) installation, everything seems to work.

Ozkan gravatar image Ozkan  ( 2012-05-07 04:45:24 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2012-05-04 04:59:58 -0500

Ozkan gravatar image

I wiped clean everything.

Installed Ubuntu 10.04 LTS (Lucid) + ROS Diamondback

So far, I am not getting this error.

This is not a good solution, but it worked.

edit flag offensive delete link more

Question Tools

Stats

Asked: 2012-05-03 04:22:09 -0500

Seen: 1,130 times

Last updated: May 04 '12