# Confd Exited Over long run

**URL:** <https://dmap-community.ductus.global/t/confd-exited-over-long-run/4715>\
**Category:** CDB and CDB API\
**Created:** [July 3, 2024, 9:48am UTC](https://dmap-community.ductus.global/t/confd-exited-over-long-run/4715 "2024-07-03T09:48:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kamala.V](https://avatars.discourse-cdn.com/v4/letter/k/e56c9b/32.png) [@Kamala.V](https://dmap-community.ductus.global/u/Kamala.V)\
**Post date:** [July 3, 2024, 9:48am UTC](https://dmap-community.ductus.global/t/confd-exited-over-long-run/4715/1 "2024-07-03T09:48:25Z")

</div>

Hi all,

In our testing environment, we have seen sometimes confd is exited over long run, and below are the logs found,

 ![image](https://canada1.discourse-cdn.com/flex010/uploads/ductus_dmap/original/1X/a547f54f5cf84ff819feb39403c391bccf8e191b.png)

 ![image](https://canada1.discourse-cdn.com/flex010/uploads/ductus_dmap/original/1X/7d5d49ae9a3903f47bd1be3cbbdb506d2d01715c.png)

as per logs it seems due memory exhaust confd exited. kindly confirm what might be the reason here.

Thanks

---

<div class="post-metadata">

**Author:** ![cohult](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/cohult/32/221_2.png) [@cohult](https://dmap-community.ductus.global/u/cohult)\
**Post date:** [July 3, 2024, 3:11pm UTC](https://dmap-community.ductus.global/t/confd-exited-over-long-run/4715/2 "2024-07-03T15:11:48Z")

</div>

What ConfD version are you using?

---

<div class="post-metadata">

**Author:** ![Kamala.V](https://avatars.discourse-cdn.com/v4/letter/k/e56c9b/32.png) [@Kamala.V](https://dmap-community.ductus.global/u/Kamala.V)\
**Post date:** [July 4, 2024, 5:27am UTC](https://dmap-community.ductus.global/t/confd-exited-over-long-run/4715/3 "2024-07-04T05:27:50Z")

</div>

we are using confd version 7.6

---

<div class="post-metadata">

**Author:** ![cohult](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/cohult/32/221_2.png) [@cohult](https://dmap-community.ductus.global/u/cohult)\
**Post date:** [July 4, 2024, 8:41pm UTC](https://dmap-community.ductus.global/t/confd-exited-over-long-run/4715/4 "2024-07-04T20:41:04Z")

</div>

Regarding the “Too many processes” error message, you are likely hitting this issue: ENG-29307 “an issue was fixed where internal Erlang processes remained and kept consuming memory after subscriber diff iteration”.  
Fixed in ConfD version 8.0 (and 7.6.8, 7.7.6)

---

<div class="post-metadata">

**Author:** ![khan](https://avatars.discourse-cdn.com/v4/letter/k/3ab097/32.png) [@khan](https://dmap-community.ductus.global/u/khan)\
**Post date:** [December 12, 2024, 11:47am UTC](https://dmap-community.ductus.global/t/confd-exited-over-long-run/4715/5 "2024-12-12T11:47:30Z")

</div>

Hi @cohult,  
is there any work around for this issue any limit which can be configured ?  
we are on version 7.8.1 and seeing this issue over continuous config commit.

---

<div class="post-metadata">

**Author:** ![cohult](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/cohult/32/221_2.png) [@cohult](https://dmap-community.ductus.global/u/cohult)\
**Post date:** [December 19, 2024, 6:28pm UTC](https://dmap-community.ductus.global/t/confd-exited-over-long-run/4715/6 "2024-12-19T18:28:55Z")

</div>

The workaround is to upgrade from 7.8.1 to at least 7.8.3.