Hi All,

This issue was fixed and the issue in the" Remote worker" configuration file . We need to populate the "lava-Master" URL under the string "LOGGER_URL="tcp://lava-master-dns:5555: in "/etc/lava-dispatcher/lava-slave" under "Remote-Worker" server.

Basically the logs generated on the remote worker are not populating in Lava-Master web GUI. I have started debugging in that way and figured out the issue under the Remote lava-dispatcher configuration file . It started working there after(continuous rotating ball gone and logs started populated after Job logs)

Regards, Koti

On Thu, 12 Nov 2020 at 18:46, koti koti kotisoftwaretest@gmail.com wrote:

Hi,

Recently I have installed "LAVA-Master" on Server and "LAVA-Worker (On Remote location)" on Raspberrypi-4 (8GB).

Installation steps: ############################### ###############################

            Server:
             ######
                    1. #sudo install lava
             Worker (Raspberrypi-4)
             ###################
                      1. #sudo install lava-dispatcher

Add worker to Master ############################### ############################### 1. sudo lava-server manage device-types add qemu 2. sudo lava-server manage devices add --device-type qemu --worker raspberrypi qemu-02 3. Now I am able to see "raspberrypi" worker in green colour state in the master under "LAVA--->Scheduler-->workers".

Problem/issue: ############

1. My QEMU job(Health-check) is still in running state even after 2 days

(Attached the screenshot) even though it is working if my dispatcher is from the same master server. I feels something I missed here and may be extra setups to establish proper communication between "Master" and "Remote-Worker"

Please can someone suggest me as what am I missing to complete my QEMU job(Health-check) while it running in "Remote-Worker" ?

Regards, Koti