[SR-Users] DMQ problems

[Aleksandar Sosic]

Hi,

I'm now creating a dns record inside kubernetes with a headless service.
Unfortunately I must use a busybox that will start before the kamailio
nodes so the dns record will be created before kamailio starts because
otherwise it will crash as I told you before. IMHO it will be useful
to have a flag that allows me to choose if kamailio should start even
if the notification_address of the DMQ module does not resolve. That
would allow me to start nodes, populate the dns and then slowly add
nodes to the cluster without having a busybox to do that.

As you can see from the logs kamailio notices the busybox IP
(10.32.68.202) which obviously not being a kamailio node gives me this
errors:
```
17(109) ERROR: dispatcher [dispatch.c:1910]: ds_select_dst_limit(): no
destination sets
33(125) ERROR: dmq [notification_peer.c:596]:
notification_resp_callback_f(): deleting server sip:10.32.68.202:5061
because of failed request
33(125) ERROR: dmq [notification_peer.c:596]:
notification_resp_callback_f(): deleting server
sip:43.100.109.113:5061 because of failed request
```
Being a workaround for creating the DNS record before starting
kamailio nodes that's ok.
But notice the IP 43.100.109.113 which is not an IP that the DNS
record for the notification_address resolves:

```
$ nslookup dmq-proxy-service
Server: 10.96.0.10
Address: 10.96.0.10#53

Name: dmq-proxy-service.default.svc.cluster.local
Address: 172.22.5.83
Name: dmq-proxy-service.default.svc.cluster.local
Address: 172.22.5.84
Name: dmq-proxy-service.default.svc.cluster.local
Address: 10.32.68.202
Name: dmq-proxy-service.default.svc.cluster.local
Address: 172.22.5.81
Name: dmq-proxy-service.default.svc.cluster.local
Address: 172.22.5.82
```

So why is that?

Then I noticed that on one node I do have all the other IPs:
```kamcmd> dmq.list_nodes
{
host: 172.22.5.81
port: 5061
resolved_ip: 172.22.5.81
status: active
last_notification: 0
local: 0
}
{
host: 172.22.5.82
port: 5061
resolved_ip: 172.22.5.82
status: active
last_notification: 0
local: 0
}
{
host: 172.22.5.83
port: 5061
resolved_ip: 172.22.5.83
status: active
last_notification: 0
local: 0
}
{
host: 172.22.5.84
port: 5061
resolved_ip: 172.22.5.84
status: active
last_notification: 0
local: 1
}
```

But on another one:
```
kamcmd> dmq.list_nodes
{
host: 172.22.5.83
port: 5061
resolved_ip: 172.22.5.83
status: active
last_notification: 0
local: 0
}
{
host: 172.22.5.81
port: 5061
resolved_ip: 172.22.5.81
status: active
last_notification: 0
local: 0
}
{
host: 172.22.5.82
port: 5061
resolved_ip: 172.22.5.82
status: active
last_notification: 0
local: 1
}
```
I miss a node? And all the kamailio instances in this range are the
same with the same config. Also the missing node is not the ip of the
node itself but another one.
--
Aleksandar Sosic
mail: alex.sosic at evosip.cloudOn Fri, Jul 6, 2018 at 9:21 AM Aleksandar
Sosic <alex.sosic at evosip.cloud> wrote:
>
> On Thu, Jul 5, 2018 at 12:35 PM Charles Chance
> <charles.chance at sipcentric.com> wrote:
> > I'll take a look - which version are you using?
>
> 5.2.0~dev6+0~20180616010152.1138+xenial
>
> Thank you!
> --
> Aleksandar Sosic
> mail: alex.sosic at evosip.cloud