Issue when building with meta-mender zeus-test

General Discussions
1

Hi Mirzak,

I started integrating meta-mender (zeus-next branch) layer in my project build for Yocto Zeus.

I face some below issues, please help on this.

When I build meta-mender source for Yocto Zeus, some of the tasks are getting failed.

When I build project without meta-mender source I won’t get below errors.

Added bblayers are.

meta-mender/meta-mender-core.

meta-mender/meta-mender-demo.

Summary of some task failed, all are do_package_qa task.

Some of the build errors shown below:

./sources/oe-core/meta/recipes-extended/libmnl/libmnl_1.0.4.bb:do_package_qa

…/sources/oe-core/meta/recipes-support/libcap-ng/libcap-ng_0.7.9.bb:do_package_qa

…/sources/oe-core/meta/recipes-support/attr/attr_2.4.47.bb:do_package_qa

…/sources/oe-core/meta/recipes-extended/cracklib/cracklib_2.9.5.bb:do_package_qa

…/sources/oe-core/meta/recipes-core/expat/expat_2.2.8.bb:do_package_qa

…/sources/oe-core/meta/recipes-devtools/flex/flex_2.6.0.bb:do_package_qa

Thanks,

Vishal

2

( Moved this to a separate thread )

Please share a more complete log of the errors you are using as there is not much information to go on with what was posted.

3

meta-mender_zeus_next_build_log.yaml (12.4 KB)

Hi Mirzak,

Please find the complete bitbake build log, i am using Arago Project (Yocto project compatible) and with meta-mender (zeus-next) layer i am facing these issues.

Thanks,
Vishal

4

Unfortunately the log does not say much. The actually error messages are not printed. I do not see how the failing packages would be related to meta-mender.

Have you included the necessary configuration options required by Mender as outlined in this section,

https://docs.mender.io/2.3/artifacts/yocto-project/building#configuring-the-build-1

5

Hi Mirzak,
Thanks for your suggestion.

After including below necessary configuration options in conf/local.conf file, the build will no produce do_package_qa errors.
Mender config parameters in conf/local.conf
MENDER_ARTIFACT_NAME = “release-1”
ARTIFACTIMG_FSTYPE = “ext4”
MENDER_FEATURES_ENABLE_append = " mender-uboot"
MENDER_FEATURES_ENABLE_append = " mender-systemd"
MENDER_FEATURES_ENABLE_append = " mender-image"
MENDER_FEATURES_DISABLE_append = " mender-grub"

But the build is not able to produce rootfs tar file, however u-boot, kernel image and dtb file will produce successfully.

Build error log:

meta-mender-core
meta-mender-demo = “zeus-next:6b35e2c6f6fa6519d0baf1d8a30502b3449a5ccd”

Initialising tasks: 100% |############################################################################################| Time: 0:00:01
Sstate summary: Wanted 4 Found 1 Missed 3 Current 756 (25% match, 99% complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
ERROR: core-image-minimal-1.0-r0 do_image_tar: Execution of ‘/home/user/SVN_BWT/Code/BWT_Software_WP2_Src/Arago/tisdk/build/arago-tmp-external-arm-toolchain/work/am57xx_evm-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_tar.11943’ failed with exit code 1:
xz: Adjusted the number of threads from 4 to 3 to not exceed the memory usage limit of 3,943 MiB
md5sum: core-image-minimal-am57xx-evm-20200426181127.rootfs.tar.xz: No such file or directory
WARNING: /home/user/SVN_BWT/Code/BWT_Software_WP2_Src/Arago/tisdk/build/arago-tmp-external-arm-toolchain/work/am57xx_evm-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_tar.11943:1 exit 1 from ‘md5sum core-image-minimal-am57xx-evm-20200426181127.rootfs.tar.xz > core-image-minimal-am57xx-evm-20200426181127.rootfs.tar.xz.md5’

ERROR: Logfile of failure stored in: /home/user/SVN_BWT/Code/BWT_Software_WP2_Src/Arago/tisdk/build/arago-tmp-external-arm-toolchain/work/am57xx_evm-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_tar.11943
Log data follows:
| DEBUG: Executing python function prepare_excluded_directories
| DEBUG: Python function prepare_excluded_directories finished
| DEBUG: Executing python function set_image_size
| DEBUG: 140564.000000 = 140564 * 1.000000
| DEBUG: 434176.000000 = max(140564.000000, 430080)[430080.000000] + 4096
| DEBUG: 434176.000000 = int(434176.000000)
| DEBUG: 434176 = aligned(434176)
| DEBUG: returning 434176
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_tar
| xz: Adjusted the number of threads from 4 to 3 to not exceed the memory usage limit of 3,943 MiB
| md5sum: core-image-minimal-am57xx-evm-20200426181127.rootfs.tar.xz: No such file or directory
| WARNING: /home/user/SVN_BWT/Code/BWT_Software_WP2_Src/Arago/tisdk/build/arago-tmp-external-arm-toolchain/work/am57xx_evm-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_tar.11943:1 exit 1 from ‘md5sum core-image-minimal-am57xx-evm-20200426181127.rootfs.tar.xz > core-image-minimal-am57xx-evm-20200426181127.rootfs.tar.xz.md5’
| ERROR: Execution of ‘/home/user/SVN_BWT/Code/BWT_Software_WP2_Src/Arago/tisdk/build/arago-tmp-external-arm-toolchain/work/am57xx_evm-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_tar.11943’ failed with exit code 1:
| xz: Adjusted the number of threads from 4 to 3 to not exceed the memory usage limit of 3,943 MiB
| md5sum: core-image-minimal-am57xx-evm-20200426181127.rootfs.tar.xz: No such file or directory
| WARNING: /home/user/SVN_BWT/Code/BWT_Software_WP2_Src/Arago/tisdk/build/arago-tmp-external-arm-toolchain/work/am57xx_evm-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_tar.11943:1 exit 1 from ‘md5sum core-image-minimal-am57xx-evm-20200426181127.rootfs.tar.xz > core-image-minimal-am57xx-evm-20200426181127.rootfs.tar.xz.md5’
|
ERROR: Task (/home/user/SVN_BWT/Code/BWT_Software_WP2_Src/Arago/tisdk/sources/oe-core/meta/recipes-core/images/core-image-minimal.bb:do_image_tar) failed with exit code ‘1’
NOTE: Tasks Summary: Attempted 2568 tasks of which 2560 didn’t need to be rerun and 1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 62 seconds

Summary: 1 task failed:
/home/user/SVN_BWT/Code/BWT_Software_WP2_Src/Arago/tisdk/sources/oe-core/meta/recipes-core/images/core-image-minimal.bb:do_image_tar

Thanks
Vishal

6

Hi @Vishalkumar_1234 what happens if you add the following to local.conf?

IMAGE_FSTYPES_append = " tar.xz "

(note the spaces inside the quotes are intentional and required)

Drew

7

Hi Drew,

First of all thanks for looking into this.

I see the same below errors, even after adding image FS type to local.conf file.

Is it something related to system limitation (memory usage limit), during compressing the files, which may have with mender artifacts and mender images ?

error log:
ERROR: core-image-minimal-1.0-r0 do_image_tar: Execution of ‘/home/user/SVN_BWT/Code/BWT_Software_WP2_Src/Arago/tisdk/build/arago-tmp-external-arm-toolchain/work/am57xx_evm-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_tar.11943’ failed with exit code 1:
xz: Adjusted the number of threads from 4 to 3 to not exceed the memory usage limit of 3,943 MiB

8

I don’t really know. I’ve never see that message but it sounds like it is being careful not to use all the memory.

What does “/home/user/SVN_BWT/Code/BWT_Software_WP2_Src/Arago/tisdk/build/arago-tmp-external-arm-toolchain/work/am57xx_evm-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_tar.11943” contain?

Drew

9

Hi Drew,

It’s been a while, working on this. Again came back to Mender, and trying it out to upgrade rootfs. But same error i am getting every time.
The content of the log is below, which is your query in previous thread of this discussion.
log_content:
DEBUG: Executing python function prepare_excluded_directories
DEBUG: Python function prepare_excluded_directories finished
DEBUG: Executing python function set_image_size
DEBUG: 186960.000000 = 186960 * 1.000000
DEBUG: 221184.000000 = max(186960.000000, 217088)[217088.000000] + 4096
DEBUG: 221184.000000 = int(221184.000000)
DEBUG: 221184 = aligned(221184)
DEBUG: returning 221184
DEBUG: Python function set_image_size finished
DEBUG: Executing shell function do_image_tar
xz: Adjusted the number of threads from 4 to 3 to not exceed the memory usage limit of 3,943 MiB
md5sum: core-image-minimal-am57xx-hs-evm-20200608112838.rootfs.tar.xz: No such file or directory
WARNING: /home/user/SVN_BWT/Code/BWT_Software_WP2_Src/Arago/tisdk/build/arago-tmp-external-arm-toolchain/work/am57xx_hs_evm-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_tar.27661:1 exit 1 from ‘md5sum core-image-minimal-am57xx-hs-evm-20200608112838.rootfs.tar.xz > core-image-minimal-am57xx-hs-evm-20200608112838.rootfs.tar.xz.md5’
ERROR: Execution of ‘/home/user/SVN_BWT/Code/BWT_Software_WP2_Src/Arago/tisdk/build/arago-tmp-external-arm-toolchain/work/am57xx_hs_evm-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_tar.27661’ failed with exit code 1:
xz: Adjusted the number of threads from 4 to 3 to not exceed the memory usage limit of 3,943 MiB
md5sum: core-image-minimal-am57xx-hs-evm-20200608112838.rootfs.tar.xz: No such file or directory
WARNING: /home/user/SVN_BWT/Code/BWT_Software_WP2_Src/Arago/tisdk/build/arago-tmp-external-arm-toolchain/work/am57xx_hs_evm-linux-gnueabi/core-image-minimal/1.0-r0/temp/run.do_image_tar.27661:1 exit 1 from ‘md5sum core-image-minimal-am57xx-hs-evm-20200608112838.rootfs.tar.xz > core-image-minimal-am57xx-hs-evm-20200608112838.rootfs.tar.xz.md5’

10

Well the warnings about memory usage are a bit concerning. How much RAM do you have in the build machine? I couldn’t find an explicit statement about RAM requirements but more is always better here.

Are you able to build that MACHINE without Mender integrated?

What does the following command show?

$ bitbake -e core-image-minimal | grep '^IMAGE_FSTYPES='

11

$ bitbake -e core-image-minimal | grep ‘^IMAGE_FSTYPES=’
IMAGE_FSTYPES=" tar.xz wic.xz tar.xz.md5 mender mender.bmap "

Build machine has 8GB of RAM.

Yes I am able to build the rootfs image, without integrating Mender.
When I build separately mender-client, it will build successfully.
Issue is only during creating rootfs image and that’s with only when we integrate with Mender.

12

Hmm. It looks like you don’t have the sdimg file type. What are your settings for Mender in your local.conf? Do you inherit mender-full?