# Confd CLI agent commits the changes but the service not getting any notification

**URL:** https://dmap-community.ductus.global/t/confd-cli-agent-commits-the-changes-but-the-service-not-getting-any-notification/993
**Category:** General
**Created:** [February 2, 2017, 6:21am UTC](https://dmap-community.ductus.global/t/confd-cli-agent-commits-the-changes-but-the-service-not-getting-any-notification/993 "2017-02-02T06:21:40Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![vipbansa](https://avatars.discourse-cdn.com/v4/letter/v/a88e4f/32.png) [@vipbansa](https://dmap-community.ductus.global/u/vipbansa)
#### Post date: [February 2, 2017, 6:21am UTC](https://dmap-community.ductus.global/t/confd-cli-agent-commits-the-changes-but-the-service-not-getting-any-notification/993/1 "2017-02-02T06:21:41Z")

</div>

Hi,

I am facing this issue very frequently now that when i do some change in my config using the confd\_cli agent and do a commit. It says commit successful but i don’t get any notification or event on my service.

This happen intermittently and otherwise most of the times i get the notification and everything works fine.

Can i get some suggestions on which direction i should debug this?  
I have no idea why the communication between confd\_cli agent and service is failing intermittently.

Thanks,  
Vipin Bansal

---

<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: [February 2, 2017, 8:14am UTC](https://dmap-community.ductus.global/t/confd-cli-agent-commits-the-changes-but-the-service-not-getting-any-notification/993/2 "2017-02-02T08:14:54Z")

</div>

Hi,  
“Notification on my service”, is that a subscriber over the ConfD CDB API, or a notification over the ConfD event API, or a NETCONF notification stream, or SNMP?

---

<div class="post-metadata">

### Author: ![vipbansa](https://avatars.discourse-cdn.com/v4/letter/v/a88e4f/32.png) [@vipbansa](https://dmap-community.ductus.global/u/vipbansa)
#### Post date: [February 2, 2017, 7:29pm UTC](https://dmap-community.ductus.global/t/confd-cli-agent-commits-the-changes-but-the-service-not-getting-any-notification/993/3 "2017-02-02T19:29:53Z")

</div>

Its the subscription point notification.

The thing is when I start the service it reads all the initial config data from the confd and I have subscribed to the config change using subscription socket using cdb\_subscribe API.

This subscription point works in most of the time.  
But sometimes i am facing this inconsistency that the confd is running, and service is also running.  
And if I make any config change to that subscription point or say any config change related to my module then that trigger is not sent to the service.  
This issue happens very intermittently.

---

<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: [February 3, 2017, 7:42am UTC](https://dmap-community.ductus.global/t/confd-cli-agent-commits-the-changes-but-the-service-not-getting-any-notification/993/4 "2017-02-03T07:42:25Z")

</div>

The developer log is helpful here. For example, if a subscribing application suddenly drops the communication, crashes, etc. you will get something like this in the ConfD developer log:

`<ERR> 2-Feb-2017::21:09:01.856 tailf confd[26336]: devel-cdb subscriber ./dhcpd_conf closed unexpectedly (while delivering subscription notification)`

To get the above entry I simply killed the dhcpd\_conf process while running the `examples.confd/intro/1-2-3-start-query-model` example

To enable the developer log at trace level to a file called “devel.log”, your confd.conf need to contain something like:

```
<developerLog>
  <enabled>true</enabled>
  <file>
    <enabled>true</enabled>
    <name>./devel.log</name>
  </file>
</developerLog>
<developerLogLevel>trace</developerLogLevel>
```