On Fri, 25 Oct 2013 13:01:28 +0100 Dean Arnold <dean.arn...@arm.com> wrote:
> Hi All, > > I have recently carried out an upgrade of LAVA and I am now seeing an > issue, where I am unable to trigger any jobs. The error listed > in /srv/lava/instances/production/var/log/lava-scheduler.log can be > seen below. This could be as simple as LAVA not being fully restarted. Ensure you've run: sudo service lava restart sudo service apache2 restart Make sure lava is also restarted on any remote workers. (You should always use upgradeworker on each worker whenever you run upgrade on the server.) This is normally part of the upgrade process, so maybe something went wrong at that stage and the upgrade was incomplete. > I am not sure where the corruption happened, I presume something went > wrong in the upgrade stage. Would it be possible to give me an > example of what should be in this column and I will add the data > manually to try and resolve the problem. The queries being sent need to handle the new field, it's not missing data because the field is typically empty. -- 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
