SWupdate spamming error messages after image update.

Ignacio Moya

unread,

Jun 4, 2021, 10:34:18 AM6/4/21

to swupdate

Hi, after porting my layers of my project board from Yocto Thud to Dunfell. Now swupdate is spamming error messages through the console. Since I have to admit, I'm a total newbie regarding swupdate, I'm posting here to see if anyone could point me in the right direction on at least where to look to fix the error.

This is the console output. Swupdate version is 2020.11.

/etc/rc5.d/S99variscite-bt: line 39: echo: write error: Invalid argument Swupdate v2021.04.0 Licensed under GPLv2. See source distribution for detailed copyright notices. [INFO ] : SWUPDATE running : [main] : Running on var-som-mx6 Revision 1.0 [INFO ] : SWUPDATE running : [print_registered_handlers] : Registered handlers: [INFO ] : SWUPDATE running : [print_registered_handlers] : dummy [INFO ] : SWUPDATE running : [print_registered_handlers] : archive [INFO ] : SWUPDATE running : [print_registered_handlers] : tar [INFO ] : SWUPDATE running : [print_registered_handlers] : uboot [INFO ] : SWUPDATE running : [print_registered_handlers] : bootloader [INFO ] : SWUPDATE running : [print_registered_handlers] : lua [INFO ] : SWUPDATE running : [print_registered_handlers] : raw [INFO ] : SWUPDATE running : [print_registered_handlers] : rawfile [INFO ] : SWUPDATE running : [print_registered_handlers] : rawcopy [INFO ] : SWUPDATE running : [print_registered_handlers] : remote [INFO ] : SWUPDATE running : [print_registered_handlers] : shellscript [INFO ] : SWUPDATE running : [print_registered_handlers] : preinstall [INFO ] : SWUPDATE running : [print_registered_handlers] : postinstall

[TRACE] : SWUPDATE running : [network_initializer] : Main loop daemon

[TRACE] : SWUPDATE running : [listener_create] : creating socket at /tmp/sockinstctrl [TRACE] : SWUPDATE running : [listener_create] : creating socket at /tmp/swupdateprog [TRACE] : SWUPDATE running : [start_swupdate_subprocess] : Started webserver with pid 929 and fd 8 [TRACE] : SWUPDATE running : [start_swupdate_subprocess] : Started suricatta with pid 930 and fd 9

[ERROR] : SWUPDATE failed [0] ERROR : Configuration file /etc/fw_env.config wrong or corrupted

[INFO ] : SWUPDATE running : [read_state] : Key 'none' not found in Bootloader's environment.

[ERROR] : SWUPDATE failed [0] ERROR : Cannot read stored update state.

[TRACE] : SWUPDATE running : [settings_into_dict] : Identify for configData: board --> var-som-mx6

[TRACE] : SWUPDATE running : [start_suricatta] : Server initialized, entering suricatta main loop.

[INFO ] : SWUPDATE running : [start_mongoose] : Mongoose web server version 6.18 with pid 929 started on port(s) 8080 with web root [/www]

[ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed (6): 'Couldn't resolve host name'

[TRACE] : SWUPDATE running : [server_send_target_data] : KEYVALUE= "board": "var-som-mx6" board var-som-mx6

[TRACE] : SWUPDATE running : [server_send_target_data] : CONFIGDATA= "board": "var-som-mx6"

[TRACE] : SWUPDATE running : [server_send_target_data] : URL=http://varupdate:8080/default/controller/v1/var-som-mx6/configData JSON={ "id": "", "time": "20210604T133553", "status": { "result": { "finished": "success" }, "execution": "closed", "details" : [ "" ] }, "data" : { "board": "var-som-mx6" } } Connected to SWUpdate via /tmp/swupdateprog

[ERROR] : SWUPDATE failed [0] ERROR : Channel put operation failed (6): 'Couldn't resolve host name'

[ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed (6): 'Couldn't resolve host name'

[TRACE] : SWUPDATE running : [, "details" : [ "" ] }, "data" : { "board": "var-som-mx6" } } [ERROR] : SWUPDATE failed [0] ERROR : Channel put operation failed (6): 'Couldn't resolve host name'

[ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed (6): 'Couldn't resolve host name'

[TRACE] : SWUPDATE running : [server_send_target_data] : KEYVALUE= "board": "var-som-mx6" board var-som-mx6

Thanks in advance,

Ignacio.

Jérôme Bolduc

unread,

Jun 9, 2021, 9:10:01 AM6/9/21

to swupdate

It seems I have almost the same problem on my side using Yocto Hardknott on raspberrypi4-64 platform:

Jun 09 13:01:42 raspberrypi4-64 kernel: audit: type=1334 audit(1623243702.719:8): prog-id=11 op=LOAD

Jun 09 13:01:42 raspberrypi4-64 kernel: audit: type=1334 audit(1623243702.719:9): prog-id=12 op=LOAD

Jun 09 13:01:42 raspberrypi4-64 kernel[190]: [ 12.348517] audit: type=1334 audit(1623243702.719:8): prog-id=11 op=LOAD

Jun 09 13:01:42 raspberrypi4-64 kernel[190]: [ 12.357947] audit: type=1334 audit(1623243702.719:9): prog-id=12 op=LOAD

Jun 09 13:01:42 raspberrypi4-64 systemd[1]: Started Hostname Service.

Jun 09 13:01:44 raspberrypi4-64 systemd[1]: Created slice system-sshd.slice.

Jun 09 13:01:44 raspberrypi4-64 systemd[1]: Started OpenSSH Per-Connection Daemon (10.0.0.197:58387).

Jun 09 13:01:47 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [do_get_state] : Read state=3 from persistent storage.

Jun 09 13:01:47 raspberrypi4-64 swupdate.sh[195]: [ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed (6): 'Couldn't resolve host name'

Jun 09 13:01:47 raspberrypi4-64 swupdate.sh[195]: [INFO ] : SWUPDATE running : [server_start] : Sleeping for 10s until retrying...

Jun 09 13:01:57 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [do_get_state] : Read state=3 from persistent storage.

Jun 09 13:01:57 raspberrypi4-64 swupdate.sh[195]: [ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed (6): 'Couldn't resolve host name'

Jun 09 13:01:57 raspberrypi4-64 swupdate.sh[195]: [INFO ] : SWUPDATE running : [server_start] : Sleeping for 10s until retrying...

Jun 09 13:02:07 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [do_get_state] : Read state=3 from persistent storage.

Jun 09 13:02:07 raspberrypi4-64 swupdate.sh[195]: [ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed (6): 'Couldn't resolve host name'

Jun 09 13:02:07 raspberrypi4-64 swupdate.sh[195]: [INFO ] : SWUPDATE running : [server_start] : Sleeping for 10s until retrying...

Jun 09 13:02:07 raspberrypi4-64 systemd-journald[121]: Forwarding to syslog missed 1 messages.

Jun 09 13:02:12 raspberrypi4-64 systemd[1]: systemd-hostnamed.service: Succeeded.

Jun 09 13:05:20 raspberrypi4-64 systemd-timesyncd[180]: Initial synchronization to time server 216.239.35.8:123 (time3.google.com).

Jun 09 13:05:20 raspberrypi4-64 audit: BPF prog-id=12 op=UNLOAD

Jun 09 13:05:20 raspberrypi4-64 audit: BPF prog-id=11 op=UNLOAD

Jun 09 13:05:20 raspberrypi4-64 kernel: audit: type=1334 audit(1623243920.438:10): prog-id=12 op=UNLOAD

Jun 09 13:05:20 raspberrypi4-64 kernel: audit: type=1334 audit(1623243920.438:11): prog-id=11 op=UNLOAD

Jun 09 13:05:20 raspberrypi4-64 kernel[190]: [ 42.736730] audit: type=1334 audit(1623243920.438:10): prog-id=12 op=UNLOAD

Jun 09 13:05:20 raspberrypi4-64 kernel[190]: [ 42.743867] audit: type=1334 audit(1623243920.438:11): prog-id=11 op=UNLOAD

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [network_thread] : Incoming network request: processing...

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [INFO ] : SWUPDATE started : Software Update started !

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [network_initializer] : Software update started

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [extract_file_to_tmp] : Found file

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [extract_file_to_tmp] : filename sw-description

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [extract_file_to_tmp] : size 1151

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [get_common_fields] : Version 0.1.0

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [parse_hw_compatibility] : Accepted Hw Revision : 1.0

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [_parse_images] : Found compressed Image: u-cam-image-raspberrypi4-64.ext4.gz in device : /dev/mmcblk0p2 for handler raw

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [_parse_scripts] : Found Script: emmcsetup.lua

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [_parse_bootloader] : Bootloader var: rpipart = 2

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [check_hw_compatibility] : Hardware raspberrypi4-64 Revision: 1.0

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [check_hw_compatibility] : Hardware compatibility verified

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [extract_files] : Found file

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [extract_files] : filename emmcsetup.lua

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [extract_files] : size 1692 required

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [extract_files] : Found file

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [extract_files] : filename u-cam-image-raspberrypi4-64.ext4.gz

Jun 09 13:05:21 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [extract_files] : size 80564306 required

Jun 09 13:05:25 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [do_get_state] : Read state=3 from persistent storage.

Jun 09 13:05:25 raspberrypi4-64 swupdate.sh[195]: [ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed (6): 'Couldn't resolve host name'

Jun 09 13:05:25 raspberrypi4-64 swupdate.sh[195]: [INFO ] : SWUPDATE running : [server_start] : Sleeping for 10s until retrying...

Jun 09 13:05:35 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [do_get_state] : Read state=3 from persistent storage.

Jun 09 13:05:35 raspberrypi4-64 swupdate.sh[195]: [ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed (6): 'Couldn't resolve host name'

Jun 09 13:05:35 raspberrypi4-64 swupdate.sh[195]: [INFO ] : SWUPDATE running : [server_start] : Sleeping for 10s until retrying...

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [extract_padding] : Expecting 304 padding bytes at end-of-file

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [network_initializer] : Valid image found: copying to FLASH

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [INFO ] : SWUPDATE running : Installation in progress

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [start_lua_script] : Calling Lua /tmp/scripts/emmcsetup.lua

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[243]: sh: line 1: /usr/sbin/sfdisk: No such file or directory

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] info()

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] umount()

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] error()

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] warn()

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] notify()

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] RECOVERY_STATUS: FAILURE = 4.0

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] RECOVERY_STATUS: RUN = 2.0

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] RECOVERY_STATUS: IDLE = 0.0

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] RECOVERY_STATUS: DOWNLOAD = 5.0

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] RECOVERY_STATUS: DONE = 6.0

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] RECOVERY_STATUS: SUBPROCESS = 7.0

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] RECOVERY_STATUS: PROGRESS = 7.0

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] RECOVERY_STATUS: SUCCESS = 3.0

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] RECOVERY_STATUS: START = 1.0

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] trace()

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] ROOT_DEVICE: UUID = 1.0

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] ROOT_DEVICE: PARTUUID = 2.0

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] ROOT_DEVICE: PARTLABEL = 3.0

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] ROOT_DEVICE: PATH = 0.0

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] getroot()

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] debug()

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [lua_dump_table] : (1) [table ] mount()

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [LUAstackDump] : (2) [string] /tmp/scripts/emmcsetup.lua:65: attempt to perform arithmetic on a nil value (global 'start')

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [ERROR] : SWUPDATE failed [0] ERROR : ERROR Calling Lua script /tmp/scripts/emmcsetup.lua

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [ERROR] : SWUPDATE failed [0] ERROR : execute preinstall scripts failed

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [ERROR] : SWUPDATE failed [1] Installation failed !

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [network_initializer] : Main thread sleep again !

Jun 09 13:05:38 raspberrypi4-64 swupdate.sh[195]: [INFO ] : No SWUPDATE running : Waiting for requests...

Jun 09 13:05:45 raspberrypi4-64 swupdate.sh[195]: [TRACE] : SWUPDATE running : [do_get_state] : Read state=3 from persistent storage.

Jun 09 13:05:45 raspberrypi4-64 systemd-journald[121]: Forwarding to syslog missed 63 messages.

Jun 09 13:05:45 raspberrypi4-64 swupdate.sh[195]: [ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed (6): 'Couldn't resolve host name'

Jun 09 13:05:45 raspberrypi4-64 swupdate.sh[195]: [INFO ] : SWUPDATE running : [server_start] : Sleeping for 10s until retrying...

Do you know if it is curl related?

Regards,

Jerome

Stefano Babic

unread,

Jun 10, 2021, 9:18:29 AM6/10/21

to Ignacio Moya, swupdate

Hi Ignacio,

On 04.06.21 16:34, Ignacio Moya wrote:
>
> Hi, after porting my layers of my project board from Yocto Thud to
> Dunfell. Now swupdate is spamming error messages

It is not spamming, it is just telling you a list of problems that must
be solved.

> through the console.
> Since I have to admit, I'm a total newbie regarding swupdate, I'm
> posting here to see if anyone could point me in the right direction on
> at least where to look to fix the error.
>
> This is the console output. Swupdate version is 2020.11.
>
> /etc/rc5.d/S99variscite-bt: line 39: echo: write error: Invalid argument
> Swupdate v2021.04.0 Licensed under GPLv2. See source distribution for

> detailed copyright notices. *[INFO ] : SWUPDATE running : [main] :
> Running on var-som-mx6 Revision 1.0* *[INFO ] : SWUPDATE running :
> [print_registered_handlers] : Registered handlers:* *[INFO ] : SWUPDATE
> running : [print_registered_handlers] : * *dummy* *[INFO ] : SWUPDATE
> running : [print_registered_handlers] : * *archive* *[INFO ] : SWUPDATE
> running : [print_registered_handlers] : * *tar* *[INFO ] : SWUPDATE
> running : [print_registered_handlers] : * *uboot* *[INFO ] : SWUPDATE
> running : [print_registered_handlers] : * *bootloader* *[INFO ] :
> SWUPDATE running : [print_registered_handlers] : * *lua* *[INFO ] :
> SWUPDATE running : [print_registered_handlers] : * *raw* *[INFO ] :
> SWUPDATE running : [print_registered_handlers] : * *rawfile* *[INFO ] :
> SWUPDATE running : [print_registered_handlers] : * *rawcopy* *[INFO ] :
> SWUPDATE running : [print_registered_handlers] : * *remote* *[INFO ] :
> SWUPDATE running : [print_registered_handlers] : * *shellscript* *[INFO
> ] : SWUPDATE running : [print_registered_handlers] : * *preinstall*
> *[INFO ] : SWUPDATE running : [print_registered_handlers] : * *postinstall*

> [TRACE] : SWUPDATE running : [network_initializer] : Main loop daemon
> [TRACE] : SWUPDATE running : [listener_create] : creating socket at
> /tmp/sockinstctrl [TRACE] : SWUPDATE running : [listener_create] :
> creating socket at /tmp/swupdateprog [TRACE] : SWUPDATE running :
> [start_swupdate_subprocess] : Started webserver with pid 929 and fd 8
> [TRACE] : SWUPDATE running : [start_swupdate_subprocess] : Started
> suricatta with pid 930 and fd 9

> *[ERROR] : SWUPDATE failed [0] ERROR : Configuration file

> /etc/fw_env.config wrong or corrupted*

Quite clear: no configuration file or wrong, SWUpdate does not access to
U-Boot vars.

> *[INFO ] : SWUPDATE running : [read_state] : Key 'none' not found in
> Bootloader's environment.*
> *[ERROR] : SWUPDATE failed [0] ERROR : Cannot read stored update state.*

> [TRACE] : SWUPDATE running : [settings_into_dict] : Identify for
> configData: board --> var-som-mx6
> [TRACE] : SWUPDATE running : [start_suricatta] : Server initialized,
> entering suricatta main loop.

> *[INFO ] : SWUPDATE running : [start_mongoose] : Mongoose web server
> version 6.18 with pid 929 started on port(s) 8080 with web root [/www]*
> *[ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed (6):
> 'Couldn't resolve host name'*

> [TRACE] : SWUPDATE running : [server_send_target_data] : KEYVALUE=
> "board": "var-som-mx6" board var-som-mx6
> [TRACE] : SWUPDATE running : [server_send_target_data] : CONFIGDATA=
> "board": "var-som-mx6"
> [TRACE] : SWUPDATE running : [server_send_target_data] :
> URL=http://varupdate:8080/default/controller/v1/var-som-mx6/configData
> JSON={ "id": "", "time": "20210604T133553", "status": { "result": {
> "finished": "success" }, "execution": "closed", "details" : [ "" ] },
> "data" : { "board": "var-som-mx6" } } Connected to SWUpdate via
> /tmp/swupdateprog

> *[ERROR] : SWUPDATE failed [0] ERROR : Channel put operation failed (6):
> 'Couldn't resolve host name'*

This is also clear, you try to update with Hawkbit, but there is no
server whose DNS is resolved from "varupdate".

> *[ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed (6):
> 'Couldn't resolve host name'*

> [TRACE] : SWUPDATE running : [, "details" : [ "" ] }, "data" : {

> "board": "var-som-mx6" } } *[ERROR] : SWUPDATE failed [0] ERROR :
> Channel put operation failed (6): 'Couldn't resolve host name'* *

"Couldn't resolve host name'"

> *
> *[ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed (6):
> 'Couldn't resolve host name'*

> [TRACE] : SWUPDATE running : [server_send_target_data] : KEYVALUE=
> "board": "var-som-mx6" board var-som-mx6
>

Best regards,
Stefano Babic

--
=====================================================================
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
=====================================================================

Stefano Babic

unread,

Jun 10, 2021, 9:21:37 AM6/10/21

to Jérôme Bolduc, swupdate

On 09.06.21 15:10, Jérôme Bolduc wrote:
> It seems I have almost the same problem

...the only thing in common is that both are running SWUpdate.

In your case an update is started.

And the error is here. Anyway, a scripüt for partitioning is not
required anymore after switching to 2021.04. SWUpdate can partition and
format the eMMC /SD.

Best regards,
Stefano Babic

> distribution for detailed copyright notices. *[INFO ] : SWUPDATE
> running : [main] : Running on var-som-mx6 Revision 1.0* *[INFO ] :
> SWUPDATE running : [print_registered_handlers] : Registered

> handlers:* *[INFO ] : SWUPDATE running :
> [print_registered_handlers] : * *dummy* *[INFO ] : SWUPDATE running
> : [print_registered_handlers] : * *archive* *[INFO ] : SWUPDATE
> running : [print_registered_handlers] : * *tar* *[INFO ] : SWUPDATE
> running : [print_registered_handlers] : * *uboot* *[INFO ] :
> SWUPDATE running : [print_registered_handlers] : * *bootloader*
> *[INFO ] : SWUPDATE running : [print_registered_handlers] : * *lua*
> *[INFO ] : SWUPDATE running : [print_registered_handlers] : * *raw*
> *[INFO ] : SWUPDATE running : [print_registered_handlers] : *
> *rawfile* *[INFO ] : SWUPDATE running :
> [print_registered_handlers] : * *rawcopy* *[INFO ] : SWUPDATE
> running : [print_registered_handlers] : * *remote* *[INFO ] :
> SWUPDATE running : [print_registered_handlers] : * *shellscript*
> *[INFO ] : SWUPDATE running : [print_registered_handlers] : *
> *preinstall* *[INFO ] : SWUPDATE running :
> [print_registered_handlers] : * *postinstall*

> [TRACE] : SWUPDATE running : [network_initializer] : Main loop daemon
> [TRACE] : SWUPDATE running : [listener_create] : creating socket at
> /tmp/sockinstctrl [TRACE] : SWUPDATE running : [listener_create] :
> creating socket at /tmp/swupdateprog [TRACE] : SWUPDATE running :
> [start_swupdate_subprocess] : Started webserver with pid 929 and fd
> 8 [TRACE] : SWUPDATE running : [start_swupdate_subprocess] : Started
> suricatta with pid 930 and fd 9

> *[ERROR] : SWUPDATE failed [0] ERROR : Configuration file
> /etc/fw_env.config wrong or corrupted*
> *[INFO ] : SWUPDATE running : [read_state] : Key 'none' not found in
> Bootloader's environment.*
> *[ERROR] : SWUPDATE failed [0] ERROR : Cannot read stored update state.*

> [TRACE] : SWUPDATE running : [settings_into_dict] : Identify for
> configData: board --> var-som-mx6
> [TRACE] : SWUPDATE running : [start_suricatta] : Server initialized,
> entering suricatta main loop.

> *[INFO ] : SWUPDATE running : [start_mongoose] : Mongoose web server
> version 6.18 with pid 929 started on port(s) 8080 with web root [/www]*
> *[ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed
> (6): 'Couldn't resolve host name'*

> [TRACE] : SWUPDATE running : [server_send_target_data] : KEYVALUE=
> "board": "var-som-mx6" board var-som-mx6
> [TRACE] : SWUPDATE running : [server_send_target_data] : CONFIGDATA=
> "board": "var-som-mx6"
> [TRACE] : SWUPDATE running : [server_send_target_data] :
> URL=http://varupdate:8080/default/controller/v1/var-som-mx6/configData
> <http://varupdate:8080/default/controller/v1/var-som-mx6/configData>
> JSON={ "id": "", "time": "20210604T133553", "status": { "result": {
> "finished": "success" }, "execution": "closed", "details" : [ "" ]
> }, "data" : { "board": "var-som-mx6" } } Connected to SWUpdate via
> /tmp/swupdateprog

> *[ERROR] : SWUPDATE failed [0] ERROR : Channel put operation failed
> (6): 'Couldn't resolve host name'*
> *[ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed
> (6): 'Couldn't resolve host name'*

> [TRACE] : SWUPDATE running : [, "details" : [ "" ] }, "data" : {

> "board": "var-som-mx6" } } *[ERROR] : SWUPDATE failed [0] ERROR :
> Channel put operation failed (6): 'Couldn't resolve host name'* *
> *
> *[ERROR] : SWUPDATE failed [0] ERROR : Channel get operation failed
> (6): 'Couldn't resolve host name'*

> [TRACE] : SWUPDATE running : [server_send_target_data] : KEYVALUE=
> "board": "var-som-mx6" board var-som-mx6
>
> Thanks in advance,
> Ignacio.
>

> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/swupdate/38f39449-e972-4b20-8ecd-0c9d7573bdb6n%40googlegroups.com
> <https://groups.google.com/d/msgid/swupdate/38f39449-e972-4b20-8ecd-0c9d7573bdb6n%40googlegroups.com?utm_medium=email&utm_source=footer>.

Ignacio Moya

unread,

Jun 14, 2021, 2:22:13 PM6/14/21

to swupdate

Hi Stefano, thank you for replying.

Ok, now I understand a lot more about those messages. One thing I have to clarify is that I said it was spamming because this messages are written to the console repeatedly non-stop.

So quickly even that it renders the console unusable. Is this a normal behavior?

Do you know what could cause them being printed so fast? Is this another error or caused by one of those error you clarified to me, or is it some configuration that I don't know about?

Thanks a lot,

Ignacio.

Stefano Babic

unread,

Jun 14, 2021, 3:29:54 PM6/14/21

to Ignacio Moya, swupdate

Hi Ignacio,

On 14.06.21 20:22, Ignacio Moya wrote:
> Hi Stefano, thank you for replying.
>
> Ok, now I understand a lot more about those messages. One thing I have
> to clarify is that I said it was spamming because this messages are
> written to the console repeatedly non-stop.
> So quickly even that it renders the console unusable. Is this a normal
> behavior?

No.

> Do you know what could cause them being printed so fast?

I guess it tries to resolve http://varupdate, but as this cannot be
resolved, it tries again. Try replacing this (wrong) name with a fix IP
address.

> Is this another
> error or caused by one of those error you clarified to me, or is it some
> configuration that I don't know about?

Check configuration in swupdate.cfg

Best regards,
Stefano Babic

>
> Thanks a lot,
> Ignacio.
> On Thursday, June 10, 2021 at 10:21:37 AM UTC-3 Stefano Babic wrote:
>
> On 09.06.21 15:10, Jérôme Bolduc wrote:
> > It seems I have almost the same problem
>
> ...the only thing in common is that both are running SWUpdate.
>
> on my side using Yocto Hardknott
> > on raspberrypi4-64 platform:
> >
> > Jun 09 13:01:42 raspberrypi4-64 kernel: audit: type=1334
> > audit(1623243702.719:8): prog-id=11 op=LOAD
> > Jun 09 13:01:42 raspberrypi4-64 kernel: audit: type=1334
> > audit(1623243702.719:9): prog-id=12 op=LOAD
> > Jun 09 13:01:42 raspberrypi4-64 kernel[190]: [ 12.348517] audit:
> > type=1334 audit(1623243702.719:8): prog-id=11 op=LOAD
> > Jun 09 13:01:42 raspberrypi4-64 kernel[190]: [ 12.357947] audit:
> > type=1334 audit(1623243702.719:9): prog-id=12 op=LOAD
> > Jun 09 13:01:42 raspberrypi4-64 systemd[1]: Started Hostname
> Service.
> > Jun 09 13:01:44 raspberrypi4-64 systemd[1]: Created slice
> system-sshd.slice.
> > Jun 09 13:01:44 raspberrypi4-64 systemd[1]: Started OpenSSH

> > Per-Connection Daemon (10.0.0.197:58387 <http://10.0.0.197:58387>).

> <http://216.239.35.8:123> (time3.google.com <http://time3.google.com>).

> <https://groups.google.com/d/msgid/swupdate/38f39449-e972-4b20-8ecd-0c9d7573bdb6n%40googlegroups.com?utm_medium=email&utm_source=footer

> <https://groups.google.com/d/msgid/swupdate/38f39449-e972-4b20-8ecd-0c9d7573bdb6n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
>
>
> --
> =====================================================================
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

> Phone: +49-8142-66989-53 <tel:+49%208142%206698953> Fax:
> +49-8142-66989-80 <tel:+49%208142%206698980> Email: sba...@denx.de
> =====================================================================

>
> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/swupdate/e970fd78-c205-413e-8800-27bb1d2de55bn%40googlegroups.com
> <https://groups.google.com/d/msgid/swupdate/e970fd78-c205-413e-8800-27bb1d2de55bn%40googlegroups.com?utm_medium=email&utm_source=footer>.

Jean-Pierre Doyon

unread,

Aug 9, 2021, 2:09:36 PM8/9/21

to swupdate

I have the same issue where, because it can't resolve the hostname, it spams the log: