On Mon, 7 Oct 2013 15:30:16 +0100 Dean Arnold <dean.arn...@arm.com> wrote:
> Thanks for the response. Unfortunately I am still having issues. > 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: Yes. That looks correct. > > --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. Is the scheduler daemon running on the remote worker? $ ps waux|grep lava-server|grep scheduler If there is no logfile, it's quite possible that something is misconfigured and the scheduler isn't even starting on the remote worker. That would explain why jobs are not being assigned. > > 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 No. Once the process is using --loglevel=debug, then there will always be content in the scheduler log if the scheduler is running. If it's not running, try executing the command directly as root - at least that way you'll see any errors. The command on the worker will be similar to what clearly *is* running on the master, with the loglevel change. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
_______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
