Liviu, I'm still getting the stream of errors on the back up host with the
configuration I've posted on this thread and -m 2048 -M 512 on both hosts. I'm
running around 4-500 CPS at the moment. I saw some notes that this has since
been moved to TCP in opensips 2. I'm guessing the replicated
Liviu, I think I have found the problem. I ran a capture of the replicated
messages and looked at the payload. It looks to me like opensips is adding an
extra 0 to the socket port See the 50600 below?
Thanks Liviu, I'm running Opensips with the following memory allocations on
both the primary and secondary hosts. Doesn't this mean I'm allocating 2G of
shared mem and 512 Megabytes of Pkg mem? I think i'm not running more than 1000
calls per second per your last email which should take only
Hello Kneeoh,
Finally managed to replicate these errors on my own setup. In my case,
the cause was insufficient shared memory for the _primary_ OpenSIPS
instance, which MAY end up with some missing data within the dialog
module structures, and unfortunately it gets replicated that way.
I just popped up to 1.11.5 and am still getting a stream of dialog replication
failure even though the non-active host IS listening on the same socket as the
primary host. I'm banging my head on the desk, I can't figure out what this
isn't working.
Host 2 (passive host)
Jun 4 18:34:50
Kneeoh has already started an earlier thread related to this problem [1]
This should be moved to the GitHub tracker [2]. We need either a
relevant SIP trace, or a way of explaining the NULL socket behaviour /
replicating the errors ourselves.
[1]
Hi Kneeoh,
The dialog replication is done assuming that both opensips servers do
share the listening interface (via vrrp, heartbeat, etc). Do you
different listening IPs on the 2 opensips instances ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
Hi Bogdan, Both Opensips hosts are set to use corosync/heartbeat to failover
the two IPs in our config. Both hosts are set to non-localbind and opensips is
explicitly listening on both of the VIPs. This is why I'm confused. It seems
that everything is configured correctly yet I'm getting these
Hello, I've got two VIPs on two instances of opensips and am doing dialog
replication. I'm getting a steady stream of failed to replicate dialog errors
in my opensips log.
192.168.30.39192.168.30.40are the two VIPs. Both have a listen = on both
opensips configs. I'm not sure if this line in the
Hello, I'm getting a stream of errors in my log when using binary replication.
The error at log level 0 is Dialog in DB doesn't match any listening sockets.
However, opensips is infact listening on the socket. I've got non-local-bind
set to 1 and opensips is listening on the shared IP. If I
On second thoughts, the error is obvious now. The
dlg-legs[callee].bind_addr pointer is somehow NULL on the first
instance, gets replicated that way, and the second instance rejects the
dialog.
I'm guessing this does not happen for all dialogs - so it would be very
interesting if you could
Hi Kneeoh!
Your setup looks flawless. By any change, are you advertising different
ports on the two 192.168.80.2 listeners? It's the only thing that pops
up right now.
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 06.04.2015 17:38, Kneeoh wrote:
Hello,
12 matches
Mail list logo
