Hi, Remi,
You said:
lava-master is receiving an invalid zmq message. I guess you are not using
encryption? Are you fuzzing it?
Sorry, I did not catch you. What does fuzzing it mean? I did not do anything special for LAVA. Meanwhile, what does "not using encryption" mean? Is this a LAVA master configure item or something else? I did not change anything related to this.
And as I said, it could work ok for some a period, then I leave the whole environment there, no touch for anything. Then severial days later, it may encountered the issue.
BTW, even such things happen, why no a exception handing in LAVA to ignore such issue? Currently it just close the zeromq connection.
------------------------------------------------------------------ Sender:lava-users-request lava-users-request@lists.lavasoftware.org Sent At:2019 Oct. 15 (Tue.) 00:25 Recipient:lava-users lava-users@lists.lavasoftware.org Subject:Lava-users Digest, Vol 14, Issue 10
Send Lava-users mailing list submissions to lava-users@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@lists.lavasoftware.org
You can reach the person managing the list at lava-users-owner@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. Re: lava job without any flashing on a real device (George Nistor) 2. Re: Unexpected crash. (Remi Duraffort) 3. Re: repeat in lava not work (Diego Russo)
----------------------------------------------------------------------
Message: 1 Date: Mon, 14 Oct 2019 13:17:55 +0000 From: George Nistor george.n@l4b-software.com To: "lava-users@lists.lavasoftware.org" lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] lava job without any flashing on a real device Message-ID: VI1PR01MB38711749B69B27E8410ABB41F0900@VI1PR01MB3871.eurprd01.prod.exchangelabs.com
Content-Type: text/plain; charset="utf-8"
Yes, In my case the only way I could make lava to see the fastboot device was via running pre-power-command, and I run a script (I customized device descriptor to run a this script as pre-power-command) which does: 1. Power Off Wait 5s 2.Power On Wait 30s 3. Login as root Wait 5s 4. echo reboot bootloader. # make it go in fastboot mode
Immediately after this script runs, the udev rule is triggered and device id added (seen from Lava).
Otherwise the reboot does not work for me. The line: nice lxc-attach -n lxc-hikey-test-186 -- fastboot -s xxxxxxx reboot gives timeout.
Because the device is not seen.
To make the job work without any flashing I removed the - deploy section which does flashing entirely
For my case: I have added to boot this section protocols: lava-lxc: - action: fastboot-boot request: pre-power-command timeout: minutes: 5
george
The full job I cannot post due to company policy with confidentiality on projects.
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: luni, 14 octombrie 2019 15:58 To: George Nistor george.n@l4b-software.com Subject: Re: lava job without any flashing on a real device
Could you send the question to ML? I don't know why adb is not enough. Maybe LAVA waits for udev event?
milosz
On Mon, 14 Oct 2019 at 13:51, George Nistor george.n@l4b-software.com wrote:
I have managed after all to do it with a job like this: My problem was to be able to run pre-power-command before boot, to make lava to see the fastboot device - trigger that python script lxc-device-add.
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: Monday, October 14, 2019 15:02 To: George Nistor george.n@l4b-software.com Subject: Re: lava job without any flashing on a real device
There was a feature called 'dummy deploy' but I can't find it any more. Did you try simply removing 'deploy' action? This should do the trick but you will need transfer_overlay in your boot section.
milosz
On Mon, 14 Oct 2019 at 12:33, George Nistor george.n@l4b-software.com wrote:
Hi Milosz,
I have a small question:
Is it possible to run a lava job without any deploy – flashing sequence on a real device?
I attach the job I’m working on.
george
------------------------------
Message: 2 Date: Mon, 14 Oct 2019 15:34:24 +0200 From: Remi Duraffort remi.duraffort@linaro.org To: cnspring2002 cnspring2002@aliyun.com Cc: lava-users lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] Unexpected crash. Message-ID: CANJfhHchH1UZOy=ScC5CUnPkZ55yi3QXrNPqqjk6wSJBFZbrzg@mail.gmail.com Content-Type: text/plain; charset="utf-8"
Hello,
lava-master is receiving an invalid zmq message. I guess you are not using encryption? Are you fuzzing it?
Le lun. 14 oct. 2019 à 11:18, cnspring2002 cnspring2002@aliyun.com a écrit :
Hi, Sometimes, lava master will show next error, then seems zemomq crash, do you know what's the potential cause?
2019-08-20 09:14:39,576 DEBUG lava-worker-1 => PING(20) 2019-08-20 09:14:39,578 DEBUG lava-worker-2 => PING(20) 2019-08-20 09:14:39,580 DEBUG lava-worker-3 => PING(20) 2019-08-20 09:14:44,467 ERROR [CLOSE] Unknown exception raised, leaving!
2019-08-20 09:14:44,467 ERROR 'utf-8' codec can't decode byte 0xc0 in position 10: invalid start byte Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 687, in handle self.main_loop(options)
File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 731, in main_loop while self.controler_socket(): # Unqueue all pending messages
File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 234, in controler_socket hostname = u(msg[0])
File "/usr/lib/python3/dist-packages/zmq/utils/strtypes.py", line 34, in cast_unicode return s.decode(encoding, errors)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc0 in position 10: invalid start byte
2019-08-20 09:14:44,467 INFO [CLOSE] Closing the controler socket and dropping messages _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Hello,
I've seen this message only once when someone was doing a security check on a private network with a non-encrypted master-slave channel.
In order to activate encryption, you have to generate a certificate for the master and the slave (/usr/share/lava-common/create_certificate.py), and update the configuration in /etc/lava-server/lava-master, /etc/lava-server/lava-logs and /etc/lava-dispatcher/lava-slave
Is the master publicly visible?
Le jeu. 17 oct. 2019 à 04:22, cnspring2002 cnspring2002@aliyun.com a écrit :
Hi, Remi,
You said:
lava-master is receiving an invalid zmq message. I guess you are not using encryption? Are you fuzzing it?
Sorry, I did not catch you. What does fuzzing it mean? I did not do anything special for LAVA. Meanwhile, what does "not using encryption" mean? Is this a LAVA master configure item or something else? I did not change anything related to this.
And as I said, it could work ok for some a period, then I leave the whole environment there, no touch for anything. Then severial days later, it may encountered the issue.
BTW, even such things happen, why no a exception handing in LAVA to ignore such issue? Currently it just close the zeromq connection.
Sender:lava-users-request lava-users-request@lists.lavasoftware.org Sent At:2019 Oct. 15 (Tue.) 00:25 Recipient:lava-users lava-users@lists.lavasoftware.org Subject:Lava-users Digest, Vol 14, Issue 10
Send Lava-users mailing list submissions to lava-users@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@lists.lavasoftware.org
You can reach the person managing the list at lava-users-owner@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:
- Re: lava job without any flashing on a real device (George Nistor)
- Re: Unexpected crash. (Remi Duraffort)
- Re: repeat in lava not work (Diego Russo)
Message: 1 Date: Mon, 14 Oct 2019 13:17:55 +0000 From: George Nistor george.n@l4b-software.com To: "lava-users@lists.lavasoftware.org" lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] lava job without any flashing on a real device Message-ID: < VI1PR01MB38711749B69B27E8410ABB41F0900@VI1PR01MB3871.eurprd01.prod.exchangelabs.com
Content-Type: text/plain; charset="utf-8"
Yes,
In my case the only way I could make lava to see the fastboot device was via
running pre-power-command, and I run a script (I customized device descriptor to run a this script as pre-power-command) which does:
- Power Off
Wait 5s 2.Power On Wait 30s 3. Login as root Wait 5s 4. echo reboot bootloader. # make it go in fastboot mode
Immediately after this script runs, the udev rule is triggered and device id added (seen from Lava).
Otherwise the reboot does not work for me. The line: nice lxc-attach -n lxc-hikey-test-186 -- fastboot -s xxxxxxx reboot gives timeout.
Because the device is not seen.
To make the job work without any flashing I removed the
- deploy section which does flashing entirely
For my case: I have added to boot this section protocols: lava-lxc: - action: fastboot-boot request: pre-power-command timeout: minutes: 5
george
The full job I cannot post due to company policy with confidentiality on projects.
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: luni, 14 octombrie 2019 15:58 To: George Nistor george.n@l4b-software.com Subject: Re: lava job without any flashing on a real device
Could you send the question to ML? I don't know why adb is not enough. Maybe LAVA waits for udev event?
milosz
On Mon, 14 Oct 2019 at 13:51, George Nistor <george.n@l4b-software.com
wrote:
I have managed after all to do it with a job like this:
My problem was to be able to run pre-power-command before boot, to make lava to see the fastboot device - trigger that python script lxc-device-add.
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: Monday, October 14, 2019 15:02 To: George Nistor george.n@l4b-software.com Subject: Re: lava job without any flashing on a real device
There was a feature called 'dummy deploy' but I can't find it any more. Did you try simply removing 'deploy' action? This should do the trick but you will need transfer_overlay in your boot section.
milosz
On Mon, 14 Oct 2019 at 12:33, George Nistor <george.n@l4b-software.com wrote:
Hi Milosz,
I have a small question:
Is it possible to run a lava job without any deploy – flashing sequence on a real device?
I attach the job I’m working on.
george
Message: 2 Date: Mon, 14 Oct 2019 15:34:24 +0200 From: Remi Duraffort remi.duraffort@linaro.org To: cnspring2002 cnspring2002@aliyun.com Cc: lava-users lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] Unexpected crash. Message-ID: CANJfhHchH1UZOy=ScC5CUnPkZ55yi3QXrNPqqjk6wSJBFZbrzg@mail.gmail.com Content-Type: text/plain; charset="utf-8"
Hello,
lava-master is receiving an invalid zmq message. I guess you are not using encryption? Are you fuzzing it?
Le lun. 14 oct. 2019 à 11:18, cnspring2002 cnspring2002@aliyun.com a écrit :
Hi, Sometimes, lava master will show next error, then seems zemomq crash, do you know what's the potential cause?
2019-08-20 09:14:39,576 DEBUG lava-worker-1 => PING(20) 2019-08-20 09:14:39,578 DEBUG lava-worker-2 => PING(20) 2019-08-20 09:14:39,580 DEBUG lava-worker-3 => PING(20)
2019-08-20 09:14:44,467 ERROR [CLOSE] Unknown exception raised, leaving!
2019-08-20 09:14:44,467 ERROR 'utf-8' codec can't decode byte 0xc0 in position 10: invalid start byte Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 687, in handle self.main_loop(options)
File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 731, in main_loop while self.controler_socket(): # Unqueue all pending messages
File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 234, in controler_socket hostname = u(msg[0])
File "/usr/lib/python3/dist-packages/zmq/utils/strtypes.py", line 34, in cast_unicode return s.decode(encoding, errors)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc0 in position 10: invalid start byte
2019-08-20 09:14:44,467 INFO [CLOSE] Closing the controler socket and dropping messages _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
-- Rémi Duraffort LAVA Tech Lead Linaro
lava-users@lists.lavasoftware.org
-
cnspring2002 -
Remi Duraffort