Hi Neil,
Thanks for the response. Unfortunately I am still having issues.
On a fresh machine (clean Ubuntu server 64bit 12.04.3 LTS install), following your advice I used the setupworker command before installing the worker as so:
~/lava-deployment-tool/lava-deployment-tool setupworker ~/lava-deployment-tool/lava-deployment-tool installworker production
I used production as the instance, as this is the instance my master is running.
I have a single board on this remote worker. If I attempt to run a job on this board the job just stalls as mentioned before. Moving the board back to the master results in the job running though as expected. This makes me think the connection to my worker is still misconfigured.
I noticed when installing the worker I got the following error:
Remote filesystem configuration ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The remote worker needs write access to the 'media' directory on the master LAVA node so that dispatcher logs will be visible. This is managed by configuring sshfs to mount the master's media directory
Master Instance Host: 'pdsw-lava.cambridge.arm.com' Master Instance User: 'lava-production' Master Instance Directory: '/srv/lava/instances/production'
next - Use the master information as is edit - Edit the master information Please decide what to do [next]: next ./lava-deployment-tool: line 270: defaults_coordinator: command not found
Could this be what is causing my problems?
You need to now remove the lava-coordinator package - sudo apt-get purge lava-coordinator.
Then copy the coordinator configuration from the master, as described here: http://validation.linaro.org/static/docs/lava- dispatcher/multinode.html#lava-coordinator-setup
When running "sudo apt-get purge lava-coordinator" it said I didn't have this package installed.
My /etc/lava-coordinator/lava-coordinator.conf (is this the right file?) looks like this:
{ "port": 3079, "blocksize": 4096, "poll_delay": 3, "coordinator_hostname": "pdsw-lava.cambridge.arm.com" }
pdsw-lava.cambridge.arm.com is the name of my master server.
--loglevel=info => --loglevel=debug
I have enabled this and restarted lava on the remote like so:
sudo service lava restart
This all seems to start OK.
Restart lava to get the daemon to notice the config change. Cancel the pending job, if it still exists and submit a new one. Consider using a KVM device type to isolate problems with the device configuration.
More than likely the answer will be in the lava-scheduler log on the worker.
Unfortunately I don't even have a log for the scheduler. Will this only appear if the scheduler is kicked into life by the master? The only log I have is lava-uwsgi.log.
Just check you have the scheduler enabled on the worker:
e.g. in your equivalent of: /srv/lava/instances/playground/instance.conf LAVA_SCHEDULER_ENABLED='yes'
This is enabled.
Thanks Dean
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782