Re: DMQ Status Flapping Between Active and Pending.

Henning Westerholt via sr-users <[email protected]>
Newsgroups gmane.comp.voip.ser
Message-ID <AS8PR07MB8103168F875C8EA44CDFC80FBFE3A@AS8PR07MB8103.eurprd07.prod.outlook.com>
Hello,

try to find out why it is changing its status. There should be a reason. Also activating debug log level can help to show insights.

Cheers,

Henning

From: satyaprakash ch <[email protected]>
Sent: Monday, October 6, 2025 1:56 PM
To: Henning Westerholt <[email protected]>
Cc: Kamailio (SER) - Users Mailing List <[email protected]>
Subject: Re: [SR-Users] DMQ Status Flapping Between Active and Pending.

HI,

Thanks for the reply.

Yes, I already tried using ngrep and was able to see the KDMQ and 200 OK messages.

However, when the status is active, the trace continues normally.
But when the status changes to pending, the trace stops and only resumes once the status becomes active again.

On Mon, Oct 6, 2025 at 5:19 PM Henning Westerholt <[email protected]<mailto:[email protected]>> wrote:
Hello,

first step is usually a packet trace, e.g. with ngrep. Have a look what is actually send and received for the DMQ protocol on the two Kamailio servers.

Cheers,

Henning

From: satyaprakash ch via sr-users <[email protected]<mailto:[email protected]>>
Sent: Sunday, October 5, 2025 9:15 PM
To: Kamailio (SER) - Users Mailing List <[email protected]<mailto:[email protected]>>
Cc: satyaprakash ch <[email protected]<mailto:[email protected]>>
Subject: [SR-Users] DMQ Status Flapping Between Active and Pending.

Hi,

I have two Kamailio presence servers running version 5.8.4. I am using DMQ to synchronize the active_watchers and presentity tables, but the synchronization does not seem to be occurring consistently.

During investigation, I observed that the DMQ status repeatedly toggles between active and pending, even though there is no packet loss detected.

Output of dmq_nodes:

{
    host: 192.168.18.96
    port: 5070
    proto: *
    resolved_ip:  192.168.18.96
    status: pending
    last_notification: 0
    local: 0
}
{
    host: 192.168.18.99
    port: 5070
    proto: *
    resolved_ip:  192.168.18.99
    status: active
    last_notification: 0
    local: 1
}

Any suggestions on what could cause this behavior would be greatly appreciated.

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.