lava-users

lava-users@lists.lavasoftware.org

1 participants
931 discussions

Job error: Invalid job data: ['Device not configured to support serial connection.', 'Device not configured to support serial connection.']

by yangjianxiang

Hi： We upgrade lava 2018 to 2021, we met the problem when we submit jobs： Job error: Invalid job data: ['Device not configured to support serial connection.', 'Device not configured to support serial connection.']

4 years, 5 months

ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)

by deffo＠gmx.de

4 years, 5 months

Job not exiting after completion

by DAS, BHARGAV

Hi Lava Users, After upgrading to LAVA 2021.01, we are facing an issue of jobs not completing/exiting (once submitted) and getting stuck in "Running" state, doesn't matter if the job is successful or unsuccessful/incomplete/fail. After sometime if we try to cancel the job it gets stuck in "Cancelling" state. Due to this the device gets blocked and subsequent jobs are sent to "Scheduled" state. Now only possible solution to free up the device, is to delete the job from LAVA administration LAVA Administration > Test jobs (under lava_scheduler_app) > {job id} > Delete . Though this way the device is recovered but the whole job gets deleted. I have tried with different boot and deploy methods like nfs, uuu, ums, and minimal. In all cases I am getting similar issue. This issue is only observed while using imx devices. Ssh based jobs are working properly and also other x86 based devices while booting through minimal method. I have attached screenshot of the jobs (Lava-job-begin.PNG and Lava-job-end.PNG). What can be the issue here ? Thanks, Bhargav

4 years, 5 months

Re: [Lava-users] LAVA master backup/restore

by Philippe Mazet (OSS)

Thanks a lot for your reply! The LAVA link you sent seems pretty outdated, and I don't think it can be applied as-is to docker-compose solution. It is for a host install on Debian (not Docker). More recent documentation seems to be here: https://lava.readthedocs.io/en/latest/admin/basic-tutorials/instance/backup/ However it tells how to create a .sql backup file (which I have), not how to restore it. About the postgres link you sent, it is for postgres running on host, not within docker I think. For Docker, it is described in https://registry.hub.docker.com/_/postgres/ (chapter "Initialization scripts"). But then when I try to place my .sql file in /docker-entrypoint-initdb.d/ folder, I get the error mentioned in my email: database "lavaserver" already exists. Thus my question: what procedure is followed by Linaro for the backup/restore of their docker-compose instances? Thanks again, Philippe From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of koti Sent: Friday, March 19, 2021 2:15 PM To: lava-users(a)lists.lavasoftware.org Subject: [Lava-users] LAVA master backup/restore Hi Philippe Mazet, Please find my comments inline. Questions: - Does Linaro's docker-compose solution modify postgres restore mechanism in any way? [Koti] --> I am not sure about this. - How do you handle backup/restore at linaro? [Koti] ----> still are you facing the backup/restore issue after following the below documentation? 1. https://docs.lavasoftware.org/lava/admin-backups.html 2. http://postgresguide.com/utilities/backup-restore.html Regards, Koti On Fri, 19 Mar 2021 at 17:30, <mailto:lava-users-request@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. LAVA master backup/restore (Philippe Mazet (OSS)) ---------------------------------------------------------------------- Message: 1 Date: Thu, 18 Mar 2021 15:22:20 +0000 From: "Philippe Mazet (OSS)" <mailto:philippe.mazet@oss.nxp.com> To: "mailto:lava-users@lists.lavasoftware.org" <mailto:lava-users@lavasoftware.org> Subject: [Lava-users] LAVA master backup/restore Message-ID: <PR3PR04MB7244B9C1456CAD918574F1218B699(a)PR3PR04MB7244.eurprd04.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Hi all, I am using the docker-compose solution to run a master: https://git.lavasoftware.org/lava/pkg/docker-compose I was wondering how to extract a backup of the DB, and re-inject it in a different instance. I found that postgres image has its own "restore" mechanism, based on initdb.d folder, as mentioned in the documentation: https://registry.hub.docker.com/_/postgres/ The entrypoint.sh script (https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh) handles the restore whenever the folder is /docker-entrypoint-initdb.d/ contains a .sql file. But when we store a backup in the container's /docker-entrypoint-initdb.d/ folder, and remove both the postgres image and its db-data volume, we get this error on next start: ERROR: database "lavaserver" already exists Full startup log attached. Questions: - Does Linaro's docker-compose solution modify postgres restore mechanism in any way? - How do you handle backup/restore at linaro? Thanks a lot in advance, Philippe Mazet NXP Semiconductors - Edge Processing Email: philippe.mazet(a)nxp.com

4 years, 6 months

LAVA master backup/restore

by koti

Hi Philippe Mazet, Please find my comments inline. Questions: - Does Linaro's docker-compose solution modify postgres restore mechanism in any way? [Koti] --> I am not sure about this. - How do you handle backup/restore at linaro? [Koti] ----> still are you facing the backup/restore issue after following the below documentation? 1. https://docs.lavasoftware.org/lava/admin-backups.html 2. http://postgresguide.com/utilities/backup-restore.html Regards, Koti On Fri, 19 Mar 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. LAVA master backup/restore (Philippe Mazet (OSS)) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 18 Mar 2021 15:22:20 +0000 > From: "Philippe Mazet (OSS)" <philippe.mazet(a)oss.nxp.com> > To: "lava-users(a)lists.lavasoftware.org" <lava-users(a)lavasoftware.org> > Subject: [Lava-users] LAVA master backup/restore > Message-ID: > < > PR3PR04MB7244B9C1456CAD918574F1218B699(a)PR3PR04MB7244.eurprd04.prod.outlook.com > > > > Content-Type: text/plain; charset="us-ascii" > > Hi all, > > I am using the docker-compose solution to run a master: > https://git.lavasoftware.org/lava/pkg/docker-compose > I was wondering how to extract a backup of the DB, and re-inject it in a > different instance. > > I found that postgres image has its own "restore" mechanism, based on > initdb.d folder, as mentioned in the documentation: > https://registry.hub.docker.com/_/postgres/ > > The entrypoint.sh script ( > https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh) > handles the restore whenever the folder is /docker-entrypoint-initdb.d/ > contains a .sql file. > > But when we store a backup in the container's > /docker-entrypoint-initdb.d/ folder, and remove both the postgres image and > its db-data volume, we get this error on next start: > ERROR: database "lavaserver" already exists > Full startup log attached. > > Questions: > - Does Linaro's docker-compose solution modify postgres restore mechanism > in any way? > - How do you handle backup/restore at linaro? > > Thanks a lot in advance, > > > Philippe Mazet > NXP Semiconductors - Edge Processing > Email: philippe.mazet(a)nxp.com > > > >

4 years, 6 months

Why the latest version of lava is 2019.11?

by cnspring2002

Hello, lava owners: I follow https://validation.linaro.org/static/docs/v2/installing_on_debian.html to install. But after add next, and apt update I found the latest lava is 2019.11 deb https://apt.lavasoftware.org/release buster main root@9486058b8151:~# apt-cache policy lava-server lava-server: Installed: (none) Candidate: 2019.11+buster Version table: 2019.11+buster 500 500 https://apt.lavasoftware.org/release buster/main amd64 Packages 2019.01-5 500 500 http://deb.debian.org/debian buster/main amd64 Packages What happened here? Or I made something wrong?

4 years, 6 months

Lava tests

by Denis HUMEAU

Hello lava users, I have to deal with a board with a very limited storage size. Overall capacity is 64 MB, with about 30 MB remaining. This is a clear limitation for Lava usage. Hence my questions: * Is there a possibility to configure Lava tests installation on an external storage, such as an USB drive? * In Lava recent versions, is it possible to optimize the overlay tests structure? * Today, assuming that tests are stored in a git repo, for each test the complete repo is copied in each overlay * A balance has to be made between one git containing all the tests and one git per test (extreme configurations) * Is there a better way to manage this? In a ideal world, that would mean copy only what is needed and not more Thanks, have a nice day

4 years, 6 months

Re: [Lava-users] lava-worker service throws error for 2021.01

by koti

Hi, I have debugged this issue a bit. Somehow I am able to register (may be work around) my lava-worker succesfully in master by update the sting as "return True" from "Return False" at " https://github.com/Linaro/lava/blob/master/lava_scheduler_app/utils.py#L339" But, I have not understand why my Lava Master "ip address"/"server name" fails while check under "def is_ip_allowed()" i.e " https://github.com/Linaro/lava/blob/master/lava_scheduler_app/utils.py#L333" appreciate any suggestions. Regards, Koti On Wed, 17 Feb 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. lava-worker service throws error for 2021.01 (koti) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 16 Feb 2021 20:20:38 +0530 > From: koti <kotisoftwaretest(a)gmail.com> > To: lava-users(a)lists.lavasoftware.org > Subject: [Lava-users] lava-worker service throws error for 2021.01 > Message-ID: > < > CAFW5HqSh8WMKaa6D-1p4DG3DRAM0agOP8UiAs0z-31Jxbfkn+A(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > 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 >

4 years, 6 months

Re: [Lava-users] lava-worker service throws error for 2021.01

by koti

Thanks Stevan. It is working by updating the UI token as per your suggetion. (netmask not yet worked . may be we need to cross check our steps for netmask method) Appreciated your support. Regards, Koti On Wed, 17 Feb 2021 at 19:13, <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: > > 2. Re: lava-worker service throws error for 2021.01 > (Stevan Radakovi?) > > > ---------------------------------------------------------------------- > > > Message: 2 > Date: Wed, 17 Feb 2021 14:43:18 +0100 > From: Stevan Radakovi? <stevan.radakovic(a)linaro.org> > To: lava-users(a)lists.lavasoftware.org > Subject: Re: [Lava-users] lava-worker service throws error for 2021.01 > Message-ID: <ab57fe22-2a1c-a6d1-f0b4-ec97763a681e(a)linaro.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hello, > > Please check out this page in the docs: > > https://lava.readthedocs.io/en/latest/admin/advanced-tutorials/deploying-rp… > You need to setup either a token for each individual worker or add the > autoregistration netmask. > > Thanks, > > > On 2/16/21 3:50 PM, koti wrote: > > Hi, > > > > We have installed the lava-worker (2021.01) as per > > > https://staging.validation.linaro.org/static/docs/v2/pipeline-server.html#i… > > < > 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 <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 > > > > _______________________________________________ > > Lava-users mailing list > > Lava-users(a)lists.lavasoftware.org > > https://lists.lavasoftware.org/mailman/listinfo/lava-users > > -- > Stevan Radakovi? | LAVA Senior Engineer > Linaro.org <www.linaro.org> ? Open source software for ARM SoCs > >

4 years, 7 months

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

4 years, 7 months

← Newer
1
...
17
18
19
20
21
22
23
...
94
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users