On Thu, Sep 29, 2022 at 12:36:51PM +0530, pawanKumar wrote:

Hi Team,

I'm running Multi node testing by connecting two devices of the same type. But it results in a socket connection error. I check the lava-coordinator conf file in server and dispatcher, both contain the same configuration.

Error log is as follows: ava-dispatcher, installed at version: 2022.06 http://158.100.69.109/scheduler/job/506.0#L1start: 0 validate http://158.100.69.109/scheduler/job/506.0#L2Start time: 2022-09-28 09:25:47.384539+00:00 (UTC) http://158.100.69.109/scheduler/job/506.0#L3This MultiNode test job contains top level actions, in order, of: deploy, boot, test, finalize http://158.100.69.109/scheduler/job/506.0#L4Validating that file:///home/lava/mfgtools-01.006572-082-aio-01939v3.7z exists http://158.100.69.109/scheduler/job/506.0#L5WARNING: Using boot commands supplied in the job definition, NOT the LAVA device configuration http://158.100.69.109/scheduler/job/506.0#L6validate duration: 0.00 http://158.100.69.109/scheduler/job/506.0#results_4678case: validate case_id: 4678 definition: lava result: pass http://158.100.69.109/results/testcase/4678 http://158.100.69.109/scheduler/job/506.0#L8Initialising group c223cee3-3ef3-4a2d-9c01-7822951ac651 http://158.100.69.109/scheduler/job/506.0#L9Connecting to LAVA Coordinator on localhost:3079 timeout=90 seconds. http://158.100.69.109/scheduler/job/506.0#L10socket error on connect: 111 localhost 3079 http://158.100.69.109/scheduler/job/506.0#L11socket error on connect: 111 localhost 3079 http://158.100.69.109/scheduler/job/506.0#L12socket error on connect: 111 localhost 3079 http://158.100.69.109/scheduler/job/506.0#L13socket error on connect: 111 localhost 3079

Is lava-coordinator installed in the worker(s) connected to both devices? That's needed for using multinode.

Also, BTW please subscribe to the mailing list. Every time you send a message I need to manually approve it.