Test Installation ERROR: Service [/stringEchoService] is not available.

[Christopher Lester]

I have installed and have everything running, but the rosservice call fails.

Info below.

Any help is appreciated.

rosservice list returns:

$ rosservice list

/RCE_ROS_Client_4658_1390426160605/get_loggers

/RCE_ROS_Client_4658_1390426160605/set_logger_level

/rosout/get_loggers

/rosout/set_logger_level

rosservice call returns:

$ rosservice call /stringEchoService something

ERROR: Service [/stringEchoService] is not available.

Screenshots of:

rce-master

rce-robot localhost

sudo rce-container localhost

roscore

rce-ros /home/bbcloud/rce/test/debug.cfg

rosservice list

rosservice call /stringEchoService something

[Dominique Hunziker]

Hi,

So the problem is that the containers are not properly launched. You can
see this with the rce-master: There for each container a connection to
an Environment process should be logged. Only once the cloud side is
ready (ie connection between Robot process and Environment processes
established, which is initiated by the master), are the ROS interfaces
activated on the client side. (As you can see when doing rosservice list
the service /stringEchoService is not available)

Dominique

[Christopher Lester]

rce-master shows the connection to the container process.

I guess I'm missing your point.

How do I properly launch the containers?

[Dominique Hunziker]

So the container process is responsible for launching the containers. The container endpoint (ie Rapyuta's communication interface inside the container) is the environment process.

Can you check whether the containers are lauched (use sudo lxc-ls and you should see C100 ...)?

[Christopher Lester]

sudo lxc-ls returns nothing.

[Dominique Hunziker]

You can try to run the command to launch the container manually
/usr/bin/lxc-start -n {container name} -f {path to config file}
and see what happens. To use a Rapyuta config file do what you are doing now and once the rce-container prints "Start container 'C100'" and after a few seconds nothing happens run the command manually using the config file found in {path to container according to config file}/container/config/C100/config

[Christopher Lester]

Ok, I think we're getting somewhere now.

Appears to be an issue with attaching vethETacxb to the IP of the server.

$ sudo /usr/bin/lxc-start -n C100 -f /opt/rce/container/config/C100/config

lxc-start: failed to attach 'vethETacxb' to the bridge '192.168.1.110' : No such device

lxc-start: failed to create netdev

lxc-start: failed to create the network

lxc-start: failed to spawn 'C100'

[Christopher Lester]

I entered IP addresses when I ran ./setup/provision all

I ran it again, following the instructions to just press enter.

Works now.

Thanks!

[Mohamed Fouad]

I have the same exact problem , with the exception that the container is successfully created. I use 14.04 branch but I never get "Connection to Environment process established" in my logs?