# Weird logs on Debian 11 + OwaSys 547

**URL:** https://hub.mender.io/t/weird-logs-on-debian-11-owasys-547/7860
**Category:** Debian family
**Created:** [June 30, 2025, 5:01pm UTC](https://hub.mender.io/t/weird-logs-on-debian-11-owasys-547/7860 "2025-06-30T17:01:24Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![stefan-novaziun](https://avatars.discourse-cdn.com/v4/letter/s/2acd7d/32.png) [@stefan-novaziun](https://hub.mender.io/u/stefan-novaziun)
#### Post date: [June 30, 2025, 5:01pm UTC](https://hub.mender.io/t/weird-logs-on-debian-11-owasys-547/7860/1 "2025-06-30T17:01:25Z")

</div>

With every update check there is these 4 log entries. These spam the log and waste the limited space on the device.

What is producing these entries? Is it part of the identity process?

# System Log

```auto
Jun 30 16:08:39 HOSTNAME mender-update[1474823]: record_id=43229 severity=info time="2025-Jun-30 16:08:39.576912" name="Global" msg="No update available"
Jun 30 16:08:39 HOSTNAME mender-update[3244514]: cat: /sys/class/net/bonding_masters/address: Not a directory
Jun 30 16:08:39 HOSTNAME mender-update[3244515]: Device "bonding_masters" does not exist.
Jun 30 16:08:40 HOSTNAME mender-update[1474823]: record_id=43230 severity=info time="2025-Jun-30 16:08:40.862176" name="Global" msg="Inventory data submitted successfully"

```

---

<div class="post-metadata">

### Author: ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)
#### Post date: [July 2, 2025, 8:29am UTC](https://hub.mender.io/t/weird-logs-on-debian-11-owasys-547/7860/2 "2025-07-02T08:29:14Z")

</div>

Hi @stefan-novaziun,

Without more context, I’d guess that it is a side effect of this script: [mender/support/mender-inventory-network at master · mendersoftware/mender · GitHub](https://github.com/mendersoftware/mender/blob/master/support/mender-inventory-network)

Possibly the `bonding_masters` interface shows up but exhibits a different directory tree / file level API than expected from a standard interface. The proper way forward would probably be to extend the `mender-inventory-network` script accordingly (PRs accepted), alternatively you can try to just add a filter or such to silence it on your device.

Greetz,  
Josef