On 7 July 2017 at 05:46, ankit gupta ankitrtk@gmail.com wrote:

Hi All,

I am trying to setup a remote lab using Raspberry pi on my local network.

I installed lava-server and a worker on my laptop and its working fine.

I installed raspbian on R-Pi and follow the instruction given on lava site,

Raspbian is not actually a supported distribution, so you may be getting problems there. Only Debian is supported. Rasbian is sufficiently different that, like Ubuntu, there may be issues for which we cannot provide support.

I run an armv7 worker using a cubietruck but that is armhf, not armel or armv6 as in the pi. The pi may simply not be up to the job of running lava-slave. Dual core and 2Gb of RAM are generally minimal hardware for a worker. e.g. I would not recommend running lava-slave on a beaglebone-black for the same reasons, the beaglebone-black in my home lab simply acts as a serial console server using ser2net.

but when slave is trying to connect to master its not getting any response, I am able to ping master from my R-pi board and default port 3079 is open on my machine.

I used no encryption and use URL to connect master as follow.

MASTER_URL="tcp://10.42.0.24:3079" LOGGER_URL="tcp://10.42.0.24:3079"

Those need to be *different* ports, as shown in the examples.

Also, 3079 is the default port for the LAVA coordinator, so that would typically be a bad choice.

The default ports are:

# URL to the master and the logger # MASTER_URL="tcp://<lava-master-dns>:5556" # LOGGER_URL="tcp://<lava-master-dns>:5555"