>Please also explain how your lab is setup, do you have a only single
>machine running LAVA or do you have one master and one or more
>separate machines acting as workers?

At 2017-08-29 18:22:56, "Neil Williams" <neil.williams@linaro.org> wrote:
>On 29 August 2017 at 11:03, kingboli <lijinbohehe@163.com> wrote:
>> Hi guys,
>>
>> I uninstalled all lava related sw and re-intall them in a clean debian
>> environment. But this time,  I met errors when visiting lava-server
>> webpages.  can you help me on the issues?
>> Attached are my installation steps, my local lava-related configurations and
>> error logs.
>
>*Never* send anyone the instance.conf - that contains the database
>password for your instance.
>
>Uninstalling the LAVA software does not purge the PostgreSql database
>if any data exists in that database - this is why you have FATAL:
>password authentication failed for user "lavaserver" in the
>django.log, lava-scheduler.log and gunicorn.log from 2017-08-29
>09:34:42
>
>In other words, you don't have a clean Debian environment because the
>original database remains.
>
>You also have other problems with your configuration:
>2017-08-29 09:28:07,013 ERROR [FAIL] lava-master must not be run on a
>remote worker!
>
>That error relates to this section of the documentation:
>https://staging.validation.linaro.org/static/docs/v2/pipeline-server.html#disabling-lava-master-on-workers
>
>If there is useful data in the database for this installation, you
>will need to go through the postgres documentation to change the
>password. If not, the database can be purged to actually get to a
>clean Debian environment.
>
>You need to follow the documentation for the version of LAVA you are
>actually installing (this is why you had the problem with lava-server
>manage workers - it's a recent addition to the software). Please
>answer these questions from the original reply:
>
>>>What version of lava are you running?
>>>
>>>Please include the output of (on all machines):
>>>
>>>dpkg -l lava-server lava-dispatcher
>
>Please also explain how your lab is setup, do you have a only single
>machine running LAVA or do you have one master and one or more
>separate machines acting as workers?
>
>With older versions of LAVA, workers can only be added using the
>Django admin interface, so you need to get the web frontend up and
>running first.
>
>>
>> Thanks.
>>
>> At 2017-08-15 16:35:09, "Neil Williams" <neil.williams@linaro.org> wrote:
>>>On 11 August 2017 at 04:37, kingboli <lijinbohehe@163.com> wrote:
>>>> Hi all,
>>>> I used LAVA V1 before and I want to migrate to LAVA V2 following the
>>>> guide "
>>>> First steps installing LAVA V2" .
>>>> I had a problem when adding pipeline workers to the master. After input
>>>> the
>>>> command " sudo lava-server manage workers add <HOSTNAME>",  I got error
>>>> "Unknown command: 'workers'" and I failed to find help by typing
>>>> "lava-server -h manage".
>>>> Can anybody help me on this step?
>>>
>>>What version of lava are you running?
>>>
>>>Please include the output of (on all machines):
>>>
>>>dpkg -l lava-server lava-dispatcher
>>>
>>>
>>>>
>>>> BTW,  I want to know whether multiple workers can have the same hostname
>>>> ?
>>>
>>>*NO* - absolutely not. The hostname is the fully qualified hostname of
>>>the worker and that needs to be unique. The master scheduler organises
>>>workers by a unique list of hostnames, as declared by the workers
>>>themselves.
>>>
>>>--
>>>
>>>Neil Williams
>>>=============
>>>neil.williams@linaro.org
>>>http://www.linux.codehelp.co.uk/
>>
>>
>>
>>
>
>
>
>-- 
>
>Neil Williams
>=============
>neil.williams@linaro.org
>http://www.linux.codehelp.co.uk/