Hi,
I have just pushed some changes to master - one of these allows startup to continue even if initial node resolution fails.
There are some other improvements, too, which I have been planning to push for some time and which should also help in your situation.
Can you try again with these changes applied and let me know the outcome?
Cheers,
Charles
On 6 July 2018 at 11:35, Aleksandar Sosic alex.sosic@evosip.cloud wrote:
Similar thing with a different type of nodes:
proxy-94b6ccf46-6n49v 3/3 Running 0 1m 172.22.5.99 master.alex.cloud.evox.it proxy-94b6ccf46-7jrgj 3/3 Running 0 1m 172.22.5.98 master.alex.cloud.evox.it proxy-94b6ccf46-rbskb 3/3 Running 0 1m 172.22.5.95 master.alex.cloud.evox.it proxy-94b6ccf46-rtzh9 3/3 Running 0 1m 172.22.5.96 master.alex.cloud.evox.it`root@proxy-94b6ccf46-6n49v:/# kamcmd kamcmd 1.5 Copyright 2006 iptelorg GmbH This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. kamcmd> dmq.list_nodes { host: 172.22.5.99 port: 5061 resolved_ip: 172.22.5.99 status: active last_notification: 0 local: 1 }root@proxy-94b6ccf46-7jrgj:/# kamcmd kamcmd 1.5 Copyright 2006 iptelorg GmbH This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. kamcmd> dmq.list_nodes { host: 172.22.5.95 port: 5061 resolved_ip: 172.22.5.95 status: active last_notification: 0 local: 0 } { host: 172.22.5.98 port: 5061 resolved_ip: 172.22.5.98 status: active last_notification: 0 local: 1 }root@proxy-94b6ccf46-rbskb:/# kamcmd kamcmd 1.5 Copyright 2006 iptelorg GmbH This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. kamcmd> dmq.list_nodes { host: 172.22.5.95 port: 5061 resolved_ip: 172.22.5.95 status: active last_notification: 0 local: 1 }root@proxy-94b6ccf46-rtzh9:/# kamcmd kamcmd 1.5 Copyright 2006 iptelorg GmbH This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. kamcmd> dmq.list_nodes { host: 172.22.5.96 port: 5061 resolved_ip: 172.22.5.96 status: active last_notification: 0 local: 1 }nslookup dmq-proxy-service Server: 10.96.0.10 Address: 10.96.0.10#53 Non-authoritative answer: Name: dmq-proxy-service.default.svc.cluster.local Address: 172.22.5.99 Name: dmq-proxy-service.default.svc.cluster.local Address: 172.22.5.98 Name: dmq-proxy-service.default.svc.cluster.local Address: 172.22.5.96 Name: dmq-proxy-service.default.svc.cluster.local Address: 172.22.5.95 Name: dmq-proxy-service.default.svc.cluster.local Address: 10.32.68.218What am I missing out?
Aleksandar Sosic mail: alex.sosic@evosip.cloud On Fri, Jul 6, 2018 at 12:26 PM Aleksandar Sosic alex.sosic@evosip.cloud wrote:
Here's another example:
router-0 3/3 Running 0 13m 172.22.5.94 master.alex.cloud.evox.it router-1 3/3 Running 0 13m 172.22.5.3 master.alex.cloud.evox.it router-2 3/3 Running 0 12m 172.22.5.4 master.alex.cloud.evox.it router-3 3/3 Running 0 12m 172.22.5.5 master.alex.cloud.evox.itroot@router-0:/# kamcmd kamcmd 1.5 Copyright 2006 iptelorg GmbH This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. kamcmd> dmq.list_nodes { host: 172.22.5.3 port: 5062 resolved_ip: 172.22.5.3 status: active last_notification: 0 local: 0 } { host: 172.22.5.4 port: 5062 resolved_ip: 172.22.5.4 status: active last_notification: 0 local: 0 } { host: 172.22.5.94 port: 5062 resolved_ip: 172.22.5.94 status: active last_notification: 0 local: 1 }root@router-1:/# kamcmd kamcmd 1.5 Copyright 2006 iptelorg GmbH This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. kamcmd> dmq.list_nodes { host: 172.22.5.4 port: 5062 resolved_ip: 172.22.5.4 status: active last_notification: 0 local: 0 } { host: 172.22.5.94 port: 5062 resolved_ip: 172.22.5.94 status: active last_notification: 0 local: 0 } { host: 172.22.5.3 port: 5062 resolved_ip: 172.22.5.3 status: active last_notification: 0 local: 1 }root@router-2:/# kamcmd kamcmd 1.5 Copyright 2006 iptelorg GmbH This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. kamcmd> dmq.list_nodes { host: 172.22.5.94 port: 5062 resolved_ip: 172.22.5.94 status: active last_notification: 0 local: 0 } { host: 172.22.5.3 port: 5062 resolved_ip: 172.22.5.3 status: active last_notification: 0 local: 0 } { host: 172.22.5.4 port: 5062 resolved_ip: 172.22.5.4 status: active last_notification: 0 local: 1 }root@router-3:/# kamcmd kamcmd 1.5 Copyright 2006 iptelorg GmbH This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. kamcmd> dmq.list_nodes { host: 172.22.5.5 port: 5062 resolved_ip: 172.22.5.5 status: active last_notification: 0 local: 1 }nslookup dmq-router-service Server: 10.96.0.10 Address: 10.96.0.10#53 Non-authoritative answer: Name: dmq-router-service.default.svc.cluster.local Address: 172.22.5.5 Name: dmq-router-service.default.svc.cluster.local Address: 172.22.5.4 Name: dmq-router-service.default.svc.cluster.local Address: 172.22.5.3 Name: dmq-router-service.default.svc.cluster.local Address: 10.32.68.217 Name: dmq-router-service.default.svc.cluster.local Address: 172.22.5.94There is no difference in configuration between the router nodes.
Aleksandar Sosic mail: alex.sosic@evosip.cloud On Fri, Jul 6, 2018 at 11:42 AM Aleksandar Sosic alex.sosic@evosip.cloud wrote:
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 requestBeing 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.82So why is that?
Then I noticed that on one node I do have all the other IPs:
{ 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@evosip.cloudOn Fri, Jul 6, 2018 at 9:21 AM Aleksandar Sosic alex.sosic@evosip.cloud wrote:
On Thu, Jul 5, 2018 at 12:35 PM Charles Chance charles.chance@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@evosip.cloud
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users