<div dir="ltr"><div><div><div><div>Hello Charles,<br>2 of them were active during network failure time period and at the time of reconnection.<br><br>As the issue were noticed on Production environment i don't have enough logs to report you but i have reproduced the issue on my Lab environment that has exactly the same DMQ configurations, except the number of dmq hosts that are 3 instead of 4.<br><br>Steps to reproduce the issue:<br><br>Start all 3 kamailio nodes.<br>at this stage all of them are active in dmq.list_nodes.<br></div>Server A<br>{<br> host: 172.112.10.243<br> port: 5060<br> resolved_ip: 172.112.10.243<br> status: 2<br> last_notification: 0<br> local: 0<br>}<br>{<br> host: 172.112.10.246<br> port: 5060<br> resolved_ip: 172.112.10.246<br> status: 2<br> last_notification: 0<br> local: 0<br>}<br>{<br> host: 172.112.10.207<br> port: 5060<br> resolved_ip: 172.112.10.207<br> status: 2<br> last_notification: 0<br> local: 0<br>}<br>{<br> host: 172.112.10.206<br> port: 5060<br> resolved_ip: 172.112.10.206<br> status: 2<br> last_notification: 0<br> local: 1<br>}<br><br></div>Server B<br>{<br> host: 172.112.10.243<br> port: 5060<br> resolved_ip: 172.112.10.243<br> status: 2<br> last_notification: 0<br> local: 0<br>}<br>{<br> host: 172.112.10.206<br> port: 5060<br> resolved_ip: 172.112.10.206<br> status: 2<br> last_notification: 0<br> local: 0<br>}<br>{<br> host: 172.112.10.207<br> port: 5060<br> resolved_ip: 172.112.10.207<br> status: 2<br> last_notification: 0<br> local: 1<br>}<br><br><br></div>Server C<br><br>{<br> host: 172.112.10.246<br> port: 5060<br> resolved_ip: 172.112.10.246<br> status: 2<br> last_notification: 0<br> local: 0<br>}<br>{<br> host: 172.112.10.207<br> port: 5060<br> resolved_ip: 172.112.10.207<br> status: 2<br> last_notification: 0<br> local: 0<br>}<br>{<br> host: 172.112.10.206<br> port: 5060<br> resolved_ip: 172.112.10.206<br> status: 2<br> last_notification: 0<br> local: 0<br>}<br>{<br> host: 172.112.10.243<br> port: 5060<br> resolved_ip: 172.112.10.243<br> status: 2<br> last_notification: 0<br> local: 1<br>}<br><br><br>Then, after few minutes i inserted an IPTABLES rule on server C to drop all packages to 5060 port.<br><br>After that the Server A and Server B can see each other:<br><br>{<br> host: 172.112.10.206<br> port: 5060<br> resolved_ip: 172.112.10.206<br> status: 2<br> last_notification: 0<br> local: 0<br>}<br>{<br> host: 172.112.10.207<br> port: 5060<br> resolved_ip: 172.112.10.207<br> status: 2<br> last_notification: 0<br> local: 1<br>}<br><br>Server B only can see itself:<br><br>{<br> host: 172.112.10.243<br> port: 5060<br> resolved_ip: 172.112.10.243<br> status: 2<br> last_notification: 0<br> local: 1<br>}<br><br></div>This behavior keeps the same after the network connectivity comes up.<br><br><div><br>Please find out the log files attached on this email for each server.<br><br></div><div>Server A - 172.112.10.206</div><div>Server B - 172.112.10.207</div><div>Server C- 172.112.10.243</div><div><div><div><div><br></div><div>Let me know if do you need further information.<br><br></div><div>Regards<br></div><div>José<br></div><div><br><br><br><br></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-02-06 14:04 GMT+00:00 Charles Chance <span dir="ltr"><<a href="mailto:charles.chance@sipcentric.com" target="_blank">charles.chance@sipcentric.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>DMQ will remove nodes from its internal list if they fail to respond to its pings - with the exception of the original notification peer specified in config. This way, if the network connection is lost, DMQ will continue to try the original peer indefinitely until connectivity is restored, and rebuild its list of other nodes from there.</div><div><br></div><div>Was the original peer (or one of them if multiple defined A/SRV records) still active at the time of reconnection?</div><div><br></div><div>It would help to diagnose if you can you send your log from around the time of disconnection, and also at the time of reconnect.</div><div><br></div><div>Regards,</div><div><br></div><div>Charles</div><div><div class="h5"><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On 6 February 2017 at 10:03, José Seabra <span dir="ltr"><<a href="mailto:joseseabra4@gmail.com" target="_blank">joseseabra4@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Hello Daniel,<br><br></div>The parameters that i have configured on my kamailio server are:<br><br>#!ifdef ENABLE_REG_SYNC<br>modparam("registrar", "sock_flag", 18)<br>modparam("registrar", "sock_hdr_name", "Sock-Info")<br>####### SIP registrar replication to other nodes ######<br>loadmodule "dmq.so"<br><br>####### distributed message queue module paramenters #####<br>modparam("dmq", "server_address", "sip:MY_IP_ADDRESS:MY_PORT_ADD<wbr>RESS")<br>modparam("dmq", "notification_address", "DMQ_HOSTS")<br>modparam("dmq", "multi_notify", 1)<br>modparam("dmq", "num_workers", 4)<br><br>loadmodule "dmq_usrloc.so"<br>modparam("dmq_usrloc", "enable", 1)<br>modparam("dmq_usrloc", "sync", 1)<br>modparam("dmq_usrloc", "batch_size", DMQ_BATCH_SIZE) <br>modparam("dmq_usrloc", "batch_usleep", DMQ_BATCH_USLEEP)<br>#!endif<br><br><br></div>Let me know if do you need further information's.<br><br></div>Thank you<br></div>Regards<br></div>José Seabra<br></div><div class="gmail_extra"><div><div class="m_-8587933308111996113h5"><br><div class="gmail_quote">2017-02-06 7:01 GMT+00:00 Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Hello,</p>
<p>what are the parameters for dmq module?</p>
<p>Cheers,<br>
Daniel<br>
</p><div><div class="m_-8587933308111996113m_-5129133405889492699h5">
<br>
<div class="m_-8587933308111996113m_-5129133405889492699m_-6801905462611076241moz-cite-prefix">On 01/02/2017 11:32, José Seabra wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="m_-8587933308111996113m_-5129133405889492699h5">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Hello there,<br>
</div>
My DMQ cluster has 4 nodes and by some reason 2 of them
lost the network connectivity for long time(~ 4 hours),
after the network of these 2 nodes come back they didn't
get connected on DMQ cluster automatically, i had to
restart kamailio to get them again on DMQ list.<br>
My doubts here are:<br>
</div>
<ul>
<li>Is this an expected behavior of DMQ module?</li>
<li>Is there any way of put them again on DMQ bus
without need restart kamailio?</li>
</ul>
</div>
<br>
</div>
Thank you <br>
</div>
Best Regards<br clear="all">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div class="m_-8587933308111996113m_-5129133405889492699m_-6801905462611076241gmail_signature">
<div>José Seabra</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="m_-8587933308111996113m_-5129133405889492699m_-6801905462611076241mimeAttachmentHeader"></fieldset>
<br>
</div></div><pre>______________________________<wbr>_________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="m_-8587933308111996113m_-5129133405889492699m_-6801905462611076241moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a class="m_-8587933308111996113m_-5129133405889492699m_-6801905462611076241moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cg<wbr>i-bin/mailman/listinfo/sr-user<wbr>s</a><span class="m_-8587933308111996113m_-5129133405889492699HOEnZb"><font color="#888888">
</font></span></pre><span class="m_-8587933308111996113m_-5129133405889492699HOEnZb"><font color="#888888">
</font></span></blockquote><span class="m_-8587933308111996113m_-5129133405889492699HOEnZb"><font color="#888888">
<br>
<pre class="m_-8587933308111996113m_-5129133405889492699m_-6801905462611076241moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="m_-8587933308111996113m_-5129133405889492699m_-6801905462611076241moz-txt-link-abbreviated" href="http://www.twitter.com/miconda" target="_blank">www.twitter.com/miconda</a> -- <a class="m_-8587933308111996113m_-5129133405889492699m_-6801905462611076241moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda" target="_blank">www.linkedin.com/in/miconda</a>
Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - <a class="m_-8587933308111996113m_-5129133405889492699m_-6801905462611076241moz-txt-link-abbreviated" href="http://www.asipto.com" target="_blank">www.asipto.com</a>
Kamailio World Conference - May 8-10, 2017 - <a class="m_-8587933308111996113m_-5129133405889492699m_-6801905462611076241moz-txt-link-abbreviated" href="http://www.kamailioworld.com" target="_blank">www.kamailioworld.com</a></pre>
</font></span></div>
<br>______________________________<wbr>_________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cg<wbr>i-bin/mailman/listinfo/sr-user<wbr>s</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br></div></div><div class="m_-8587933308111996113m_-5129133405889492699gmail_signature" data-smartmail="gmail_signature">Cumprimentos<span class="m_-8587933308111996113HOEnZb"><font color="#888888"><div>José Seabra</div></font></span></div>
</div>
<br>______________________________<wbr>_________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cg<wbr>i-bin/mailman/listinfo/sr-user<wbr>s</a><br>
<br></blockquote></div><br><div><br></div>
</div></div></div></div>
<br>
<div><font style="font-size:10pt;font-family:Helvetica,Arial,sans-serif" color="gray">Sipcentric Ltd.
Company registered in England & Wales no. 7365592.</font><span style="font-size:10pt;font-family:Helvetica,Arial,sans-serif"> </span><font style="font-size:10pt;font-family:Helvetica,Arial,sans-serif" color="gray">Registered
office: Faraday Wharf, Innovation Birmingham Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB.</font></div><br>______________________________<wbr>_________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Cumprimentos<div>José Seabra</div></div>
</div>