26 Jul
2018
26 Jul
'18
12:14 p.m.
Hi Aleksandar,
The initial depopulation of the nodes (following a period of 'pending'
state) is due to no response being received from them. Are you able to
trace the messages to/from one of them to confirm what is happening there?
As for the unrecognised IP, I'm afraid I can't answer that one. It must be
coming from somewhere - it's just a case of finding out where. Following
the initial population/depopulation of the node list, DMQ simply repeats
the process over and over until it eventually connects to one or more other
nodes. Are you running on a public cloud somewhere or is it your own,
locally running Kubernetes cluster?
Cheers,
Charles
On 26 July 2018 at 15:30, Aleksandar Sosic <alex.sosic(a)evosip.cloud> wrote:
Hi Charles,
We're so glad about the improvements you just committed! Thanks!
Now I'm using the latest nightly: 5.2.0~dev6+0~20180726010431.1165+xenial
Kamailio starts even if the DNS record does not exist at first, that's
great. I'm having this nodes up and running:
```
proxy-66f79498cc-8ws6d 3/3 Running 0
4m 172.28.1.4
proxy-66f79498cc-b68dd 3/3 Running 0
4m 172.28.1.5
proxy-66f79498cc-lhbxg 3/3 Running 0
4m 172.28.1.6
proxy-66f79498cc-png6p 3/3 Running 0
4m 172.28.1.7
```
In those 4-5 minutes I've experienced a population and depopulation of
the dmq nodes.
For example:
```
kamcmd> dmq.list_nodes
{
host: 172.28.1.4
port: 5061
resolved_ip: 172.28.1.4
status: pending
last_notification: 0
local: 0
}
{
host: 172.28.1.6
port: 5061
resolved_ip: 172.28.1.6
status: pending
last_notification: 0
local: 0
}
{
host: 40.100.109.113
port: 5061
resolved_ip: 40.100.109.113
status: pending
last_notification: 0
local: 0
}
{
host: 172.28.1.5
port: 5061
resolved_ip: 172.28.1.5
status: active
last_notification: 0
local: 1
}
```
And after a few seconds only the loca node itself:
```
kamcmd> dmq.list_nodes
{
host: 172.28.1.5
port: 5061
resolved_ip: 172.28.1.5
status: active
last_notification: 0
local: 1
}
```
And then again the 3 nodes and the 40.100.109.113 which is a Microsoft
IP and I don't know what's doing that IP into my dmq server list.
The DNS record is this:
```
root@proxy-66f79498cc-b68dd:/# nslookup dmq-proxy-service
Server: 10.96.0.10
Address: 10.96.0.10#53
Non-authoritative answer:
Name: dmq-proxy-service.alex.svc.cluster.local
Address: 172.28.1.7
Name: dmq-proxy-service.alex.svc.cluster.local
Address: 172.28.1.6
Name: dmq-proxy-service.alex.svc.cluster.local
Address: 172.28.1.5
Name: dmq-proxy-service.alex.svc.cluster.local
Address: 172.28.1.4
```
Any clues why that ip is in the dmq nodes list? And why .7 is missing?
Kind regards,
--
Aleksandar Sosic
mail: alex.sosic(a)evosip.cloud
On Wed, Jul 25, 2018 at 3:06 PM Charles Chance
<charles.chance(a)sipcentric.com> wrote:
--
*Charles Chance*
Managing Director
t. 0330 120 1200 m. 07932 063 891
--
Sipcentric Ltd.
Company registered in England & Wales no.
7365592. Registered
office: Faraday Wharf, Innovation
Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB.
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
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users