Yes. Actually this is just in the example below that I forgot the “s” in https.

I do have the problem with https in WS_URL.

 

 

From: Remi Duraffort <remi.duraffort@linaro.org>
Sent: Friday, November 20, 2020 10:20 AM
To: Philippe Mazet (OSS) <philippe.mazet@oss.nxp.com>
Cc: lava-users@lists.lavasoftware.org <lava-users@lavasoftware.org>
Subject: Re: [Lava-users] Problem with https and WS_URL

 

Hello,

 

have you tried to set WS_URL to "https://" and not "http://" ?

 

Le jeu. 19 nov. 2020 à 16:27, Philippe Mazet (OSS) <philippe.mazet@oss.nxp.com> a écrit :

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

_______________________________________________
Lava-users mailing list
Lava-users@lists.lavasoftware.org
https://lists.lavasoftware.org/mailman/listinfo/lava-users

 

--

Rémi Duraffort

LAVA Architect

Linaro