# Solving/working around devel-c Control socket request timed out daemon

**URL:** <https://dmap-community.ductus.global/t/solving-working-around-devel-c-control-socket-request-timed-out-daemon/1659>\
**Category:** CDB and CDB API\
**Created:** [November 22, 2017, 9:08am UTC](https://dmap-community.ductus.global/t/solving-working-around-devel-c-control-socket-request-timed-out-daemon/1659 "2017-11-22T09:08:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rajcse](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@rajcse](https://dmap-community.ductus.global/u/rajcse)\
**Post date:** [November 22, 2017, 9:08am UTC](https://dmap-community.ductus.global/t/solving-working-around-devel-c-control-socket-request-timed-out-daemon/1659/1 "2017-11-22T09:08:22Z")

</div>

Hi All,

I am new to CONFD. We are using confd-4.2.1 and using thirdparty database as well with cdb.

When we try to update a configuration value in cdb, sometimes we observe following log in devel.log  
devel-c Control socket request timed out daemon

After this the devel.log alwasys shows the below error (for GUI request for data)

devel-c no registration found for callpoint

The GUI is not visible after the above failure.

Could you please guide me, how to deal with this problem.

NOTE: Restarting java which has socket connection to confd, solve this issue.

Thanks in advance.  
Rajesh Kumar.

---

<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:** [November 22, 2017, 9:55am UTC](https://dmap-community.ductus.global/t/solving-working-around-devel-c-control-socket-request-timed-out-daemon/1659/2 "2017-11-22T09:55:18Z")

</div>

Hi,

See ConfD 6.5 UG Chapter 6.3. Callpoints and Callbacks and the  
examples.confd/intro/java/4-stats/  
and  
examples.confd/intro/java/6-config  
examples from the example set bundle

---

<div class="post-metadata">

**Author:** ![rajcse](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@rajcse](https://dmap-community.ductus.global/u/rajcse)\
**Post date:** [November 22, 2017, 12:50pm UTC](https://dmap-community.ductus.global/t/solving-working-around-devel-c-control-socket-request-timed-out-daemon/1659/3 "2017-11-22T12:50:23Z")

</div>

Thank you for reply. I am going through the confd user guide. Could you please suggest if there is any configuration in confd.conf which can re-establish the control socket which died.

---

<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:** [November 25, 2017, 12:36pm UTC](https://dmap-community.ductus.global/t/solving-working-around-devel-c-control-socket-request-timed-out-daemon/1659/4 "2017-11-25T12:36:44Z")

</div>

Hi, the application client initiates the connection to ConfD. So in your case your application need to reestablish the control socket