# Confd master - slave sync issue

**URL:** https://dmap-community.ductus.global/t/confd-master-slave-sync-issue/2864
**Category:** General
**Created:** [January 8, 2020, 11:04am UTC](https://dmap-community.ductus.global/t/confd-master-slave-sync-issue/2864 "2020-01-08T11:04:28Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![msridhar](https://avatars.discourse-cdn.com/v4/letter/m/ba8739/32.png) [@msridhar](https://dmap-community.ductus.global/u/msridhar)
#### Post date: [January 8, 2020, 11:04am UTC](https://dmap-community.ductus.global/t/confd-master-slave-sync-issue/2864/1 "2020-01-08T11:04:28Z")

</div>

we are facing issue in slave confd where it is not able to connect to master and not syncing the data. connectivity wise we debugged and all seems working. we found some error log in the confd.err file. What could be the cause of the connectivity issue.

(process:3964): GLib-CRITICAL \*\*: 14:30:42.640: g\_source\_destroy: assertion ‘source != NULL’ failed  
CDB replacing with aaa\_merge.xml: [OK]  
Mergering aaa\_merge.xml success${CONFD} --start-phase0 -c /usr/vos/cfg/confd.conf ${CONFD\_FLAGS} --foreground

---

<div class="post-metadata">

### Author: ![greg](https://avatars.discourse-cdn.com/v4/letter/g/71c47a/32.png) [@greg](https://dmap-community.ductus.global/u/greg)
#### Post date: [January 9, 2020, 12:56am UTC](https://dmap-community.ductus.global/t/confd-master-slave-sync-issue/2864/2 "2020-01-09T00:56:54Z")

</div>

Can you give the status and cluster status from issuing ‘confd --status’ on both the master and the slave nodes?

For example, if you run the HA example in $CONFD\_DIR/examples.confd/ha/dummy, you’ll see the following near the top of the output of the ‘confd --status’ command:

status: started  
cluster status:  
mode: master  
node id: node0  
connected slaves: 2

---

<div class="post-metadata">

### Author: ![msridhar](https://avatars.discourse-cdn.com/v4/letter/m/ba8739/32.png) [@msridhar](https://dmap-community.ductus.global/u/msridhar)
#### Post date: [January 9, 2020, 8:59am UTC](https://dmap-community.ductus.global/t/confd-master-slave-sync-issue/2864/3 "2020-01-09T08:59:24Z")

</div>

is there some thing we can decode from the confderr.log

confderr.log

## node 1

nonode@nohost O hd idd ha\_serverhd mfargshd ha\_serverd  
start\_linkjhd restart\_typed permanenthd shutdownb aÐhd  
child\_typed workerjj ˜bWLAƒhk 30-Dec-2019::16:39:57.885hd error\_reportgd  
nonode@nohost hgd  
nonode@nohost J d supervisor\_reportl hd  
supervisorhd locald confd\_second\_suphd errorContextd shutdown\_errorhd reasond killedhd offenderl hd pidgd  
nonode@nohost R hd idd ha\_serverhd mfargshd ha\_serverd  
start\_linkjhd restart\_typed permanenthd shutdownb aÐhd  
child\_typed workerjj ¥bWLAƒhk 30-Dec-2019::16:42:39.025hd errorgd  
nonode@nohost hgd  
nonode@nohost H k -~w:~w: Couldn’t map ~w (~p) to server: ~p  
~p  
l d confd\_iab ðak HA sockethd errord undefinedl hd confd\_iad handle\_connectional hd filek confd\_ia.erlhd lineb ñjhd confd\_iad acceptoral hd filek confd\_ia.erlhd lineb ªjhd proc\_libd init\_pal hd filek proc\_lib.erlhd lineaájjj

## ================================================================================================================ node 2

l d confd\_iab ðak capihd errord undefinedl hd confd\_iad handle\_connectional hd filek confd\_ia.erlhd lineb ñjhd confd\_iad acceptoral hd filek confd\_ia.erlhd lineb ªjhd proc\_libd init\_pal hd filek proc\_lib.erlhd lineaájjj bWLAƒhk 30-Dec-2019::16:40:05.943hd errorgd  
nonode@nohost hgd  
nonode@nohost H k -~w:~w: Couldn’t map ~w (~p) to server: ~p  
~p  
l d confd\_iab ðak capihd errord undefinedl hd confd\_iad handle\_connectional hd filek confd\_ia.erlhd lineb ñjhd confd\_iad acceptoral hd filek confd\_ia.erlhd lineb ªjhd proc\_libd init\_pal hd filek proc\_lib.erlhd lineaájjj ˜bWLAƒhk 30-Dec-2019::16:40:06.062hd error\_reportgd  
nonode@nohost hgd  
nonode@nohost J d supervisor\_reportl hd  
supervisorhd locald confd\_second\_suphd errorContextd shutdown\_errorhd reasond killedhd offenderl hd pidgd  
nonode@nohost R hd idd ha\_serverhd mfargshd ha\_serverd  
start\_linkjhd restart\_typed permanenthd shutdownb aÐhd  
child\_typed workerjj ˜bWLAƒhk 30-Dec-2019::17:30:05.073hd error\_reportgd  
nonode@nohost hgd  
nonode@nohost K d supervisor\_reportl hd  
supervisorhd locald confd\_second\_suphd errorContextd shutdown\_errorhd reasond killedhd offenderl hd pidgd  
nonode@nohost R hd idd ha\_serverhd mfargshd ha\_serverd  
start\_linkjhd restart\_typed permanenthd shutdownb aÐhd  
child\_typed workerjj

---

<div class="post-metadata">

### Author: ![msridhar](https://avatars.discourse-cdn.com/v4/letter/m/ba8739/32.png) [@msridhar](https://dmap-community.ductus.global/u/msridhar)
#### Post date: [January 9, 2020, 9:00am UTC](https://dmap-community.ductus.global/t/confd-master-slave-sync-issue/2864/4 "2020-01-09T09:00:51Z")

</div>

confd devel.log

node 1:  
 8-Jan-2020::16:23:20.505 skl-vasn-1 confd[4030]: confd HA: Connect new slave failed: Timeout  
 8-Jan-2020::16:24:22.517 skl-vasn-1 confd[4030]: confd HA: Connect new slave failed: Timeout  
 8-Jan-2020::16:25:24.527 skl-vasn-1 confd[4030]: confd HA: Connect new slave failed: Timeout  
 8-Jan-2020::16:26:26.535 skl-vasn-1 confd[4030]: confd HA: Connect new slave failed: Timeout  
 8-Jan-2020::16:27:28.548 skl-vasn-1 confd[4030]: confd HA: Connect new slave failed: Timeout  
 8-Jan-2020::16:28:30.556 skl-vasn-1 confd[4030]: confd HA: Connect new slave failed: Timeout  
 8-Jan-2020::16:29:32.564 skl-vasn-1 confd[4030]: confd HA: Connect new slave failed: Timeout  
 8-Jan-2020::16:30:34.575 skl-vasn-1 confd[4030]: confd HA: Connect new slave failed: Timeout

## node2:

8-Jan-2020::16:28:32.560 skl-vasn-2 confd[4042]: confd New HA socket connected  
 8-Jan-2020::16:29:32.565 skl-vasn-2 confd[4042]: confd HA: Failed to synchronize with master: Closed  
 8-Jan-2020::16:29:32.565 skl-vasn-2 confd[4042]: confd HA: Requested sync with master: error  
 8-Jan-2020::16:29:34.568 skl-vasn-2 confd[4042]: confd New HA socket connected  
 8-Jan-2020::16:30:34.576 skl-vasn-2 confd[4042]: confd HA: Failed to synchronize with master: Closed  
 8-Jan-2020::16:30:34.577 skl-vasn-2 confd[4042]: confd HA: Requested sync with master: error  
 8-Jan-2020::16:30:36.580 skl-vasn-2 confd[4042]: confd New HA socket connected  
 8-Jan-2020::16:31:36.586 skl-vasn-2 confd[4042]: confd HA: Failed to synchronize with master: Closed  
 8-Jan-2020::16:31:36.587 skl-vasn-2 confd[4042]: confd HA: Requested sync with master: error  
 8-Jan-2020::16:31:38.590 skl-vasn-2 confd[4042]: confd New HA socket connected  
 8-Jan-2020::16:32:38.595 skl-vasn-2 confd[4042]: confd HA: Failed to synchronize with master: Closed  
 8-Jan-2020::16:32:38.595 skl-vasn-2 confd[4042]: confd HA: Requested sync with master: error  
 8-Jan-2020::16:32:40.599 skl-vasn-2 confd[4042]: confd New HA socket connected
