Mender-connect.service not found

General Discussions
, , ,
1

I’m trying to build mender-connect version 2.3.0 on a Toradex Apalis iMX8 using the tdx-reference-multimedia-image (Yocto-based), and I’m running into an error during the do_install step:

install: cannot stat ‘/…/mender-connect-2.3.0/support/mender-connect.service’: No such file or directory

It seems like the recipe is expecting a mender-connect.service file inside the support/ directory of the source tree, but it’s not there. The build fails because it can’t install this missing systemd unit file.
Was the mender-connect.service file removed or moved in version 2.3.0?
and each bitbake mender-connect this error occured :
ERROR: mender-connect-2.3.0-r0 do_package: Didn’t find service unit ‘mender-connect.service’, specified in SYSTEMD_SERVICE:mender-connect.

2

Hi @Rani13958,

Just by looking at the 2.3.x source branches, the file seems to be available: mender-connect/support at 2.3.x · mendersoftware/mender-connect · GitHub

Can you gather a little more information, like which layer revisions are involved? Also, have you tried inspecting the actual source directory?

Greetz,
Josef

3

hi @TheYoctoJester

to be clear i cloned the meta-mender and the meta-mender-community to my build env and this is the mender configuration in my local.conf :

Enable Mender features

MENDER_FEATURES_ENABLE:append = " mender-uboot mender-image mender-image-sd"
MENDER_FEATURES_DISABLE:append = " mender-grub mender-image-uefi"

Mender Artifact info

MENDER_ARTIFACT_NAME = “scooter-v1.0”

Flash layout

MENDER_STORAGE_TOTAL_SIZE_MB = “4096”
MENDER_BOOT_PART_SIZE_MB = “64”
MENDER_DATA_PART_SIZE_MB = “256”

Mender and Toradex Tezi integration

INHERIT += “mender-toradex”
IMAGE_CLASSES += “image_type_mender_tezi”
IMAGE_FSTYPES:append = " mender_tezi"
IMAGE_FSTYPES:remove = " teziimg"

MENDER_IMAGE_BOOTLOADER_BOOTSECTOR_OFFSET = “0”
DISTRO_FEATURES:append = " systemd"
VIRTUAL-RUNTIME_init_manager = “systemd”
DISTRO_FEATURES_BACKFILL_CONSIDERED = “sysvinit”
VIRTUAL-RUNTIME_initscripts = “”

and i added this part to my bblayers.conf :
${TOPDIR}/../layers/meta-mender/meta-mender-core
${TOPDIR}/../layers/meta-mender/meta-mender-demo
${TOPDIR}/../layers/meta-mender/meta-mender-community/meta-mender-toradex-nxp \

and when i run bitbake tdx-reference-multimedia-image this error occur :
ERROR: mender-connect-2.3.0-r0 do_package: Didn’t find service unit ‘mender-connect.service’, specified in SYSTEMD_SERVICE:mender-connect.
/home/ranim/pixii_os/build/../layers/meta-mender/meta-mender-core/recipes-mender/mender-connect/mender-connect_2.3.0.bb:do_package

4

3 posts were split to a new topic: OTA binary coredump

5

Any news about this issue ?
I’ve the exact same issue.
I’ve cloned the scarthgap branch of GitHub - mendersoftware/meta-mender: Yocto Project meta layer for the Mender client
Added the bblayer :
BBLAYERS += “/opt/conga-STDA4/sources/meta-mender/meta-mender-core”

But then mender-connect can not build because the .service file is missing :

ERROR: mender-connect-2.3.0-r0 do_package: Didn’t find service unit ‘mender-connect.service’, specified in SYSTEMD_SERVICE:mender-connect.
ERROR: Logfile of failure stored in: /opt/conga-STDA4/build/arago-tmp-default-glibc/work/aarch64-oe-linux/mender-connect/2.3.0/temp/log.do_package.2224
ERROR: Task (/opt/conga-STDA4/sources/meta-mender/meta-mender-core/recipes-mender/mender-connect/mender-connect_2.3.0.bb:do_package) failed with exit code ‘1’

In my build directory (mender-connect/2.3.0/mender-connect-2.3.0/src/github.com/mendersoftware/mender-connect/), I can see the mender-connect.service file in the support directory, but it looks like Yocto/Bitbake can not see it.

Thanks for your help.

6

Hi @Damien,

Far-fetched guess - have you checked in mender-systemd is in MENDER_FEATURES? Otherwise the service file will not be installed to the root filesystem, see meta-mender/meta-mender-core/recipes-mender/mender-connect/mender-connect.inc at 033fe1f44f6f89f105f4d371a08bab6b80c8806b · mendersoftware/meta-mender · GitHub.

Greetz,
Josef

7

hi @Damien

The build issue with mender-connect version 2.3.0, where the mender-connect.service file was not found during the do_package step, has been resolved. The error stemmed from the Yocto/Bitbake build process failing to locate the systemd service file, despite its presence in the source directory (mender-connect-2.3.0/src/github.com/mendersoftware/mender-connect/support/).

To address this, the mender-connect.inc file was updated as follows:

do_install:append:mender-systemd() {
# Install systemd service
install -m 755 -d ${D}${systemd_unitdir}/system
install -m 0644 ${B}/src/${GO_IMPORT}/support/mender-connect.service ${D}${systemd_unitdir}/system/
}

Updated Configuration:

do_install:append() {
# Always install systemd service
install -d ${D}${systemd_unitdir}/system
install -m 0644 ${B}/src/github.com/mendersoftware/mender-connect/support/mender-connect.service ${D}${systemd_unitdir}/system/
}
Changes Made:

  1. Updated the source path to explicitly reference github.com/mendersoftware/mender-connect/support/mender-connect.service.

This modification ensures the mender-connect.service file is correctly installed, resolving the build error.

1 Like
8

@Rani13958 did you intentionally build without mender-systemd in MENDER_FEATURES? It should definitely be picked up otherwise.

9

The omission of mender-systemd from MENDER_FEATURES was unintentional, as it was not explicitly included in my local.conf configuration, which currently has:

MENDER_FEATURES_ENABLE:append = " mender-uboot mender-image mender-image-sd"

However, this did not cause any issues with the mender-connect build after modifying the mender-connect.inc file to unconditionally install the mender-connect.service file using do_install:append(), as shared previously. My local.conf ensures systemd is enabled as the init system via:
DISTRO_FEATURES:append = " systemd"
VIRTUAL-RUNTIME_init_manager = “systemd”
INIT_MANAGER = “systemd”
DISTRO_FEATURES_BACKFILL_CONSIDERED = “sysvinit”
VIRTUAL-RUNTIME_initscripts = “”

This configuration guaranteed systemd was present, allowing the service file installation to succeed.

Please let me know if you recommend any further adjustments.

10

Hi @Rani13958,

You’re totally right in your expectations, mender-systemd should automatically be enabled. To dig a bit further into this, can you try and run

bitbake-getvar -r core-image-minimal MENDER_FEATURES

and paste it, including the evaluation history? Thanks!

Greetz,
Josef