lava-users

lava-users@lists.lavasoftware.org

1 participants
912 discussions

lava-worker service throws error for 2021.01

by koti

Hi, We have installed the lava-worker (2021.01) as per https://staging.validation.linaro.org/static/docs/v2/pipeline-server.html#i… but noticed the below errors on "lava-worker" and "lava-master" servers as below. Lava-worker server error: (Attached the "/etc/lava-dispatcher/lava-worker" worker configuration file) ##################### pi@lavaworker-1:~ $ tail -f /var/log/lava-dispatcher/lava-worker.log 2021-02-16 19:43:08,484 ERROR [INIT] -> server error: code 403 2021-02-16 19:43:13,502 ERROR [INIT] -> server error: code 403 2021-02-16 19:43:14,896 INFO [INIT] LAVA worker has started. 2021-02-16 19:43:14,896 INFO [INIT] Name : 'lavaworker-1' 2021-02-16 19:43:14,896 INFO [INIT] Server : 'http://lavamasterserver' 2021-02-16 19:43:14,897 INFO [INIT] Version: '2021.01' 2021-02-16 19:43:14,897 INFO [INIT] Token : '<auto register>' 2021-02-16 19:43:14,897 DEBUG [INIT] Auto register as 'raspberrypi' 2021-02-16 19:43:14,909 ERROR [INIT] -> server error: code 403 2021-02-16 19:43:14,909 DEBUG [INIT] --> {"error": "Auto registration is forbidden for '192.168.1.5'"} 2021-02-16 19:43:19,914 DEBUG [INIT] Auto register as 'raspberrypi' 2021-02-16 19:43:19,927 ERROR [INIT] -> server error: code 403 2021-02-16 19:43:19,927 DEBUG [INIT] --> {"error": "Auto registration is forbidden for '192.168.1.5'"} Lava-server server error: #################### lavamasterserver@lavamasterserver:/var/log$ sudo tail -f /var/log/apache2/lava-server.log 10.138.202.62 - - [16/Feb/2021:20:09:06 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:11 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:16 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:21 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:26 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:31 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:36 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:41 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:46 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:51 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" 10.138.202.62 - - [16/Feb/2021:20:09:56 +0530] "POST /scheduler/internal/v1/workers/ HTTP/1.1" 403 348 "-" "lava-worker 2021.01" I feel that it may be an issue in lava master apache configuration . appreciate any suggestions. Regards, Koti

3 years, 10 months

Configuring Site and domain for docker-compose setup

by Westermann, Oliver

Hey, I'm hosting a lava-setup for us which is based upon the lava-docker-compose setup from here https://git.lavasoftware.org/lava/pkg/docker-compose I managed to configure Django to use a EMAIL_HOST which allows me to notify my users. However dbutils.get_domain() returns example.com and some digging lead me to the site setup from Django. I'm not entirely sure how it's intended to work but I would expect that LAVA fetches the host to use from .env, where I specified DC_LAVA_SERVER_HOSTNAME=lava.mydomain.com. Where would I set that or what did I miss? Also: I figured out a few details about the docker-compose setup by now, eg how to configure LDAP. Where would I add such documentation? A PR to the docs? Best regards, Olli

3 years, 10 months

Problem with https and WS_URL

by Philippe Mazet (OSS)

Hello, While testing 2020.10 with https enabled, we have noticed the following problem: In /etc/lava-dispatcher/lava-worker, if we set WS_URL="--ws-url http://<master's address>/ws/" (or do not this variable at all), we get the following error on worker: 2020-11-19 15:14:57,751 INFO PING => server SSL error in data received protocol: <asyncio.sslproto.SSLProtocol object at 0x7f9a0d704160> transport: <_SelectorSocketTransport fd=8 read=polling write=<idle, bufsize=0>> Traceback (most recent call last): File "/usr/lib/python3.7/asyncio/sslproto.py", line 526, in data_received ssldata, appdata = self._sslpipe.feed_ssldata(data) File "/usr/lib/python3.7/asyncio/sslproto.py", line 207, in feed_ssldata self._sslobj.unwrap() File "/usr/lib/python3.7/ssl.py", line 767, in unwrap return self._sslobj.shutdown() ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609) Still, even with those errors the worker is fully functional. Now, the only way to get rid of such errors is to explicitly specify the port, 8001: WS_URL="--ws-url http://<master's address>:8001/ws/" Have you experienced similar problems? Did we miss something on our setup? Thanks a lot, Philippe

3 years, 10 months

Sometime we met the problem blow occasionally，but it succeed when we resubmit the job

by yangjianxiang

Hey： Sometime we met the problem blow occasionally，but it succeed when we resubmit the job How can we solve the problem？ [cid:image001.png@01D6FE33.5DDDEA20]

3 years, 10 months

Lava-->Results page gives the error "500 Internal Server Error"

by koti koti

Hi Recently my LAVA results page through the below error (Attached the screenshot). Is there any way to fix this? " 500 Internal Server Error Reverse for 'lava.results.suite' with arguments '(77, '0_bin utility tests')' not found. 1 pattern(s) tried: ['results/(?P<job>[0-9]+|[0-9]+\\.[0-9]+)/(?P<pk>[-_a-zA-Z0-9.]+)$'] " Regards, Koti

3 years, 10 months

When we install lava 2021.01 in debian 10.6, we met the problem like this

by yangjianxiang

Hi： When we install lava 2021.01 in debian 10.6, we met the problem like this： [cid:image001.png@01D6F9A1.EF5DC880]

3 years, 10 months

How lava schedule jobs to devices？ Where is the code and how it works

by yangjianxiang

Hello： we want to learn more about lava, but we do not know lava very well, can you give us some tips about: 1、How lava schedule jobs to devices？ Where is the code and how it works. thanks

3 years, 10 months

Unable to change device health state without being admin

by Sebastien Haezebrouck

Hi, We used to set devices access permission using groups. So we would restrict access to a subset of devices to members of a specific group. When switching to lava 2020.10, it seems the permission to change a device does not allow to change device health state anymore. This used to be possible in previous version, and was very convenient for maintenance. With 2020.10 it seems only a lava admin is allowed to change a device health. Is it the expected behavior ? Did I miss an option somewhere ? A bit more details: All our devices are set to: * “device owner”->”Group with physical access” -> our_group. * “group device permissions”->”lava_sched_app |device | Can change device” -> “Group” -> our_group. * I intentionally did not give any specific permission to the “our_group” group, like “Can change device”, since it would allow members of this group to change any devices. Access control has to work both ways 😊 Kind regards, Seb

3 years, 10 months

Issue with DUT reboot command with uuu boot method (ssh login)

by Anand, Ravi

Hello All, I am currently facing one issue where I have to execute reboot (soft reboot) command in DUT. But after executing reboot command , target is getting rebooted and lava job get stuck at login prompt. To overcome this I have inserted boot section with auto_login (waiting for login prompt to pass username & password). But with this scenario, just after reboot command , target is getting rebooted (Hard reset) by PDU. Can somebody help me on this. I don't want DUT to get hard reset by PDU. Expectation is like just after reboot command, wait for login prompt and then proceed it with another set of commands. Attached both scenario sample pipeline definitions for reference. Regards, Ravi Anand

3 years, 11 months

Re: [Lava-users] Subject: Issue with DUT reboot command with uuu boot

by koti koti

Hi Ravi Anand, Can you try using "Method: minimal" ? Reference: https://docs.lavasoftware.org/lava/actions-boot.html#minimal) Example: ####### " actions: - boot: timeout: minutes: 2 method: minimal " Note: 1. You can mention your custom soft reboot command using the string "soft_reboot" or "{% set soft_reboot_command = 'reset' %}" in corresponding files. Regards, Koti On Fri, 8 Jan 2021 at 17:30, <lava-users-request(a)lists.lavasoftware.org> wrote: > Send Lava-users mailing list submissions to > lava-users(a)lists.lavasoftware.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.lavasoftware.org/mailman/listinfo/lava-users > or, via email, send a message with subject or body 'help' to > lava-users-request(a)lists.lavasoftware.org > > You can reach the person managing the list at > lava-users-owner(a)lists.lavasoftware.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Lava-users digest..." > > > Today's Topics: > > 1. Issue with DUT reboot command with uuu boot method (ssh > login) (Anand, Ravi) > 2. Ask android vts test link in docker test shell. (Larry Shen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 7 Jan 2021 18:12:55 +0000 > From: "Anand, Ravi" <Ravi_Anand(a)mentor.com> > To: "lava-users(a)lists.lavasoftware.org" > <lava-users(a)lists.lavasoftware.org> > Subject: [Lava-users] Issue with DUT reboot command with uuu boot > method (ssh login) > Message-ID: > <b010fbd1eff04d168a44bc3ecb661a69(a)svr-orw-mbx-03.mgc.mentorg.com> > Content-Type: text/plain; charset="us-ascii" > > Hello All, > > I am currently facing one issue where I have to execute reboot (soft > reboot) command in DUT. But after executing reboot command , target is > getting rebooted and lava job get stuck at login prompt. > To overcome this I have inserted boot section with auto_login (waiting for > login prompt to pass username & password). But with this scenario, just > after reboot command , target is getting rebooted (Hard reset) by PDU. > > Can somebody help me on this. I don't want DUT to get hard reset by PDU. > Expectation is like just after reboot command, wait for login prompt and > then proceed it with another set of commands. > > Attached both scenario sample pipeline definitions for reference. > > Regards, > Ravi Anand >

3 years, 11 months

← Newer
1
...
16
17
18
19
20
21
22
...
92
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users