It sounds to me like these discovered nodes are DMQ adjacencies of
another DMQ node that _is_ properly a member of the production DMQ cluster.
On 6/3/20 2:01 PM, Henning Westerholt wrote:
Hello George,
In generally this should not happen. Have you already tried to restart
the DMQ nodes?
You are not using a DNS record to populate the cluster members?
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com <https://gilawa.com/>
*From:* sr-users <[email protected]> *On Behalf Of
*George Diamantopoulos
*Sent:* Wednesday, June 3, 2020 6:29 PM
*To:* Kamailio (SER) - Users Mailing List <[email protected]>
*Subject:* [SR-Users] Does DMQ auto-discover cluster members + how?
Hello all (again),
When running dmq.list_nodes on one of my production kamailio servers, I
get several entries corresponding to staging instances of kamailio.
These staging instances are located on separate broadcast domains
(different VLANs), and none of them are configured in the
notification_address parameter for the dmq module.
How do they end up there, and how do I get rid of them?
Thanks!
George
_______________________________________________
Kamailio (SER) - Users Mailing List
[email protected]
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
_______________________________________________
Kamailio (SER) - Users Mailing List
[email protected]
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
