[SWUforwarder] : Updater error if curl > 7.61.x

157 views
Skip to first unread message

TEXIER Pierre-Jean

unread,
May 16, 2019, 4:20:42 AM5/16/19
to swupdate
Hi All,

I'm playing with the SWUforwarder handler for some time now.
And it worked pretty well until the migration to the new warrior branch.

I noticed that with the curl version 7.61.0 (thud), everything works fine, but,
if I start using the curl version 7.64.x (warrior), I have an update error with the following error on the Slave part :

[TRACE] : SWUPDATE running :  [install_single_image] : Found installer for stream rootfs.img.gz raw
[ERROR] : SWUPDATE failed [0] ERROR core/cpio_utils.c : gunzip_step : 279 : inflate failed (returned -3)
[TRACE] : SWUPDATE running :  [install_single_image] : Installer for raw not successful !
[ERROR] : SWUPDATE failed [0] ERROR corelib/stream_interface.c : extract_files : 265 : Error streaming rootfs.img.gz
[ERROR] : SWUPDATE failed [1] Image invalid or corrupted. Not installing ...
[TRACE] : SWUPDATE running :  [network_initializer] : Main thread sleep again !

I tested with version 7.63.0 & 7.62.0 and I have the same problem.
Otherwise, if I downgrade the curl version to 7.61.0 on warrior, everything works again.

I will try to investigate more, but if you have any suggestions ;)

Thanks !

/Pierre-Jean

Stefano Babic

unread,
May 17, 2019, 12:23:51 PM5/17/19
to TEXIER Pierre-Jean, swupdate, Alison Chaiken
Hi Pierre,
Added Alison to CC because she has already reported such as issues. I am
investigating this, too, because I am rewriting the handler to drop some
limitations. The SWUforwarder handler strictly requires to run the
webserver on the slaves with the old and obsolete API. This forbids to
run an update on the single device simply using the Webserver because
SWUpdate should be restarted in normal mode. So I am adding Websockets
support to the handler and I reworking most of code. During that, I have
experienced corruption on data and I strongly suppose that there are
some incompatibilities in curl when using the multi interface. So I will
not let the topic falling, I am looking, too.

Best regards,
Stefano


--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=====================================================================

Alison Chaiken

unread,
May 17, 2019, 12:56:58 PM5/17/19
to Stefano Babic, TEXIER Pierre-Jean, swupdate
Thanks very much for looping me into this conversation, Stefano. I
can confirm that we are using curl version 7.64.1, which is reported
to fail by Pierre-Jean. Indeed, as you indicated, we have observed
exactly the same error pretty much irrespective of the other test
conditions. This is a promising finding, indeed! While we have put
aside this task for the moment, we would very much like to make use of
the SWUForwarder in the future.

--
Alison Chaiken
Peloton Technology
Mountain View, CA
ali...@peloton-tech.com

Pierre-Jean Texier

unread,
May 20, 2019, 12:32:29 PM5/20/19
to Stefano Babic, swupdate, Alison Chaiken
Stefano,

Thanks a lot for all this information !
Indeed, I saw "Enhance swuforward handler" in the roadmap,
and it's really good to know that the subject is progressing !
If I can help, let me know !
Anyway, I plan to investigate this week regarding curl's versions
(7.61.X vs 7.62.x) ;)

BR

Pierre-Jean


Reply all
Reply to author
Forward
0 new messages