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?
BTW, I want to know whether multiple workers can have the same hostname ?
Thanks in advance.
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.
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.
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/
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#di...
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, My previous lava verision is 2016.12
lava@debian:~$ dpkg -l lava-dispatcher Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=============================================-===========================-===========================-=============================================================================================== ii lava-dispatcher 2016.12-1 i386 Linaro Automated Validation Architecture dispatcher
And my newly installed version is 2017.07. My versions: $ dpkg -l lava-server
Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=============================================-===========================-===========================-=============================================================================================== ii lava-server 2017.7-1~bpo9+1 all Linaro Automated Validation Architecture server
$ dpkg -l lava-dispatcher Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=============================================-===========================-===========================-=============================================================================================== ii lava-dispatcher 2017.7-1~bpo9+1 amd64 Linaro Automated Validation Architecture 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?
I want to set up one lava master and more separate workers with only pipeline devices. From the official document, the lava master needs to install both lava-server and lava-dispatcher, and lava worker only needs to install lava-dispatcher. And I just followed the instruction. Am I right? I firstly installed lava-mater with below guides. And I could not figure out why the error "ERROR [FAIL] lava-master must not be run on a remote worker!" existed.
----------------------------------------------- deb http://http.debian.net/debian stretch-backports main Remember to update your apt cache whenever add a new apt source: $ sudo apt update Then install lava-server from stretch-backports using the -t option: $ sudo apt -t stretch-backports install lava-server $ sudo a2dissite 000-default $ sudo a2enmod proxy $ sudo a2enmod proxy_http $ sudo a2ensite lava-server.conf $ sudo service apache2 restart -----------------------------------------------
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#di...
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/
On 29 August 2017 at 11:44, kingboli lijinbohehe@163.com wrote:
Neil, My previous lava verision is 2016.12
lava@debian:~$ dpkg -l lava-dispatcher Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=============================================-===========================-===========================-=============================================================================================== ii lava-dispatcher 2016.12-1 i386 Linaro Automated Validation Architecture
dispatcher
And my newly installed version is 2017.07. My versions: $ dpkg -l lava-server
Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=============================================-===========================-===========================-=============================================================================================== ii lava-server 2017.7-1~bpo9+1 all Linaro Automated Validation Architecture server
$ dpkg -l lava-dispatcher Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=============================================-===========================-===========================-=============================================================================================== ii lava-dispatcher 2017.7-1~bpo9+1 amd64 Linaro Automated Validation Architecture 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?
I want to set up one lava master and more separate workers with only pipeline devices. From the official document, the lava master needs to install both lava-server and lava-dispatcher, and lava worker only needs to install lava-dispatcher.
Correct.
And I just followed the instruction. Am I right? I firstly installed lava-mater with below guides. And I could not figure out why the error "ERROR [FAIL] lava-master must not be run on a remote worker!" existed.
It sounds like that master was previously configured as a V1 worker - check for the file /etc/lava-server/worker.conf which should not exist on a machine which runs lava-master.
deb http://http.debian.net/debian stretch-backports main Remember to update your apt cache whenever add a new apt source: $ sudo apt update Then install lava-server from stretch-backports using the -t option: $ sudo apt -t stretch-backports install lava-server $ sudo a2dissite 000-default $ sudo a2enmod proxy $ sudo a2enmod proxy_http $ sudo a2ensite lava-server.conf $ sudo service apache2 restart
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#di...
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/
-
kingboli -
Neil Williams