# Robustness of deployments

**URL:** <https://hub.mender.io/t/robustness-of-deployments/2645>\
**Category:** General Discussions\
**Created:** [October 9, 2020, 12:58pm UTC](https://hub.mender.io/t/robustness-of-deployments/2645 "2020-10-09T12:58:39Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\
**Post date:** [October 17, 2020, 10:00pm UTC](https://hub.mender.io/t/robustness-of-deployments/2645/21 "2020-10-17T22:00:19Z")

</div>

I think you need to use the mdb\_dump tool to dump the contents of the database and then investigate the contents either with a text/hex editor or with mdb\_load

> **[mdb\_dump(1) — lmdb-utils — Debian testing — Debian Manpages](https://manpages.debian.org/testing/lmdb-utils/mdb_dump.1.en.html)**

---

<div class="post-metadata">

**Author:** ![bender](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/bender/32/847_2.png) [@bender](https://hub.mender.io/u/bender)\
**Post date:** [November 17, 2020, 3:21pm UTC](https://hub.mender.io/t/robustness-of-deployments/2645/22 "2020-11-17T15:21:05Z")

</div>

it ended up being some legacy code left behind to monitor corruption during boot ☹  
after quite some troubleshooting we found it and removed so the “issue” is gone. Thank you all.

> [@dellgreen](#):
>
> I think you need to use the mdb\_dump tool

It didn’t seem very easy through our yocto build system, so I didn’t try your suggestion after all.

[Previous page](https://hub.mender.io/t/robustness-of-deployments/2645.md?page=1)