# Error disabling systemd

**URL:** https://hub.mender.io/t/error-disabling-systemd/3685
**Category:** General Discussions
**Created:** [May 26, 2021, 8:54pm UTC](https://hub.mender.io/t/error-disabling-systemd/3685 "2021-05-26T20:54:54Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![sjuengst](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/sjuengst/32/633_2.png) [@sjuengst](https://hub.mender.io/u/sjuengst)
#### Post date: [May 26, 2021, 8:54pm UTC](https://hub.mender.io/t/error-disabling-systemd/3685/1 "2021-05-26T20:54:54Z")

</div>

I want to run mender client in standalone mode, but when I follow the instructions to add `MENDER_FEATURES_DISABLE_append = " mender-systemd"` to local.conf, I get the following build error: `ERROR: mender-configure-1.0.0-r0 do_package: SYSTEMD_SERVICE_mender-configure value mender-configure-apply-device-config.service does not exist`. I’m using mender v2.6.0 with zeus (5.4) on i.MX6ULL.

---

<div class="post-metadata">

### Author: ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)
#### Post date: [May 26, 2021, 9:09pm UTC](https://hub.mender.io/t/error-disabling-systemd/3685/2 "2021-05-26T21:09:40Z")

</div>

Hi Stu,

To be honest I don’t know if it’s ever been tested without the dependency on systemd. I think just doing the `SYSTEMD_AUTO_ENABLE = "disable"` should be sufficient. If you find that you do need to remove `mender-systemd` we will happily take a pull request.

Drew

---

<div class="post-metadata">

### Author: ![sjuengst](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/sjuengst/32/633_2.png) [@sjuengst](https://hub.mender.io/u/sjuengst)
#### Post date: [May 27, 2021, 5:41pm UTC](https://hub.mender.io/t/error-disabling-systemd/3685/3 "2021-05-27T17:41:09Z")

</div>

I had tried `SYSTEMD_AUTO_ENABLE = "disable"` first, but found that the mender daemons were still running. Thinking that maybe bitbake didn’t pick up the change for some reason, I just did a completely clean build but they’re still there. 😕

---

<div class="post-metadata">

### Author: ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)
#### Post date: [May 27, 2021, 7:51pm UTC](https://hub.mender.io/t/error-disabling-systemd/3685/4 "2021-05-27T19:51:51Z")

</div>

That is indeed unexpected. Did you verify that `SYSTEMD_AUTO_ENABLE` was indeed being set to `DISABLE`? I wonder if maybe another layer is overriding your setting?

Drew

---

<div class="post-metadata">

### Author: ![sjuengst](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/sjuengst/32/633_2.png) [@sjuengst](https://hub.mender.io/u/sjuengst)
#### Post date: [May 27, 2021, 8:36pm UTC](https://hub.mender.io/t/error-disabling-systemd/3685/5 "2021-05-27T20:36:12Z")

</div>

First, I think the documentation has a bug: `meta-mender/meta-mender-core/recipes-mender` doesn’t contain a `mender` directory (nor `mender_%.bb`), so shouldn’t my layer contain `recipes-mender/mender-client/mender-client_%.bbappend` instead?

With this change, I did a `bitbake -e mender-client` and see this:

```auto
# $SYSTEMD_AUTO_ENABLE [4 operations]

# set /yocto-src/sources/poky/meta/conf/documentation.conf:403

# [doc] "For recipes that inherit the systemd class, this variable specifies whether the service you have specified in SYSTEMD_SERVICE should be started automatically or not."

# set? /yocto-src/sources/meta-mender/meta-mender-core/recipes-mender/mender-client/mender-client.inc:17

# "enable"

# set /yocto-src/sources/poky/meta/classes/systemd.bbclass:9

# [_defaultval] "enable"

# set /yocto-dev/layers/meta-orro/recipes-mender/mender-client/mender-client_%.bbappend:1

# "disable"

# pre-expansion value:

# "disable"

SYSTEMD_AUTO_ENABLE="disable"

#

```

but at runtime, you can see that it’s the right build (built a few minutes ago) but mender still daemonized:

```auto
root@hermes:~# uname -a
Linux hermes 5.4.24-2.1.0+gbabac008e5cf #1 SMP PREEMPT Thu May 27 15:34:35 UTC 2021 armv7l armv7l armv7l GNU/Linux
root@hermes:~# ps |grep mender
  412 root 873m S /usr/bin/mender daemon
  413 root 852m S /usr/bin/mender-connect daemon
 2667 root 2248 S grep mender

```

---

<div class="post-metadata">

### Author: ![sjuengst](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/sjuengst/32/633_2.png) [@sjuengst](https://hub.mender.io/u/sjuengst)
#### Post date: [May 27, 2021, 10:17pm UTC](https://hub.mender.io/t/error-disabling-systemd/3685/6 "2021-05-27T22:17:30Z")

</div>

Ok, making some progress here. I did a completely clean build and now the `mender-client.service` is no longer in `/etc/systemd/system/multi-user.target.wants`. Mender-client is still launched as a daemon though, because `mender-connect.service` is still in there and requires `mender-client.service`. I suspect that if I disable `mender-connect.service` in a similar .bbappend, I’ll be good.

---

<div class="post-metadata">

### Author: ![sjuengst](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/sjuengst/32/633_2.png) [@sjuengst](https://hub.mender.io/u/sjuengst)
#### Post date: [May 27, 2021, 10:58pm UTC](https://hub.mender.io/t/error-disabling-systemd/3685/7 "2021-05-27T22:58:14Z")

</div>

Confirmed … all good now.

---

<div class="post-metadata">

### Author: ![darts476](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@darts476](https://hub.mender.io/u/darts476)
#### Post date: [June 25, 2021, 10:08pm UTC](https://hub.mender.io/t/error-disabling-systemd/3685/8 "2021-06-25T22:08:19Z")

</div>

@sjuengst thanks for posting. I’ve run into the same issue. How did you disable the mender connect service?

---

<div class="post-metadata">

### Author: ![sjuengst](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/sjuengst/32/633_2.png) [@sjuengst](https://hub.mender.io/u/sjuengst)
#### Post date: [June 28, 2021, 3:52pm UTC](https://hub.mender.io/t/error-disabling-systemd/3685/9 "2021-06-28T15:52:39Z")

</div>

In my layer, created recipes-mender/mender-connect/mender-connect\_%.bbappend with content of

```auto
SYSTEMD_AUTO_ENABLE = "disable"

```

---

<div class="post-metadata">

### Author: ![darts476](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@darts476](https://hub.mender.io/u/darts476)
#### Post date: [June 30, 2021, 7:11pm UTC](https://hub.mender.io/t/error-disabling-systemd/3685/10 "2021-06-30T19:11:36Z")

</div>

@sjuengst thanks!

---

<div class="post-metadata">

### Author: ![darts476](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@darts476](https://hub.mender.io/u/darts476)
#### Post date: [June 30, 2021, 7:53pm UTC](https://hub.mender.io/t/error-disabling-systemd/3685/11 "2021-06-30T19:53:33Z")

</div>

@sjuengst hmm, well, I was hoping I could just add those disables and my errors would go away but no such luck. In my `local.conf` I have `MENDER_FEATURES_DISABLE_append = " mender-systemd "` and I see this

```auto
bitbake -e mender-configure | grep ^SYSTEMD_AUTO_ENABLE
SYSTEMD_AUTO_ENABLE="disable"

```

But, i still have the top post error

```auto
ERROR: mender-configure-1.0.0-r0 do_package: SYSTEMD_SERVICE_mender-configure value mender-configure-apply-device-config.service does not exist

```

Any thoughts?

---

<div class="post-metadata">

### Author: ![darts476](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@darts476](https://hub.mender.io/u/darts476)
#### Post date: [June 30, 2021, 8:03pm UTC](https://hub.mender.io/t/error-disabling-systemd/3685/12 "2021-06-30T20:03:14Z")

</div>

fwiw, hard overrides do work, but this seems like it would be unnecessary

```auto
SYSTEMD_SERVICE_${PN} = ""
FILES_${PN}_append_mender-systemd = ""

```
