Reopen if you encounter another case that looks like being the same issue.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #2757.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2757#event-4876200528___
Kamailio (SER) - Development Mailing List
We've made the changes for h_id_start and h_id_step and bounced everything.
Will monitor and hope that the problem is resolved. Thanks for all the help.
Will update in a week or two with results either way.
--
You are receiving this because you are subscribed to this thread.
Reply to this
You have to set `h_id_start` and `h_id_step` for all servers in the replication
group so the generated ids do not overlap:
*
https://www.kamailio.org/docs/modules/stable/modules/dialog.html#dialog.p.h_id_start
Likely the issue was caused by matching a dialog with same `h_id`, which was
[root@kamibt01 ~]# grep -iE "dialog|dmq" /etc/kamailio/kamailio.cfg
loadmodule "dmq.so"
loadmodule "dialog.so"
# -- dialog params --
modparam("dialog", "enable_dmq", 1)
modparam("dialog", "db_url", DBURL)
modparam("dialog", "db_mode", 1)
modparam("dialog", "dlg_match_mode", 1)
modparam("dialog",
If there is dialog replication via dmq, can you paste here all the modparams
you set for dialog and dmq modules (hide/replace sensitive data, such as
passwords, ips, ... if it is the case). It can be a conflict on dialog matching
due to replication.
--
You are receiving this because you are
< (gdb) p *cell
$1 = {ref = 3, next = 0x7fae15a524a8, prev = 0x0, h_id = 6059, h_entry = 3973,
state = 3, lifetime = 0, init_ts = 1622101184, start_ts = 1622542334, end_ts =
0, dflags = 513, iflags = 64, sflags = 0, toroute = 0, toroute_name = {s = 0x0,
len = 0}, from_rr_nb = 0, tl = {next =
That's a yes to the dialog replication question. Am checking the p *cell output
now. I have two core dumps so it's possible I mixed them up.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Btw, do you do dialog replication via dmq?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2757#issuecomment-853795330___
Kamailio (SER)
I got the pcap via email, the call-id matches the `bt full` output, but does
not match the output of `p *cell`. Maybe you used a different corefile, can you
get the output from the same corefile as for `bt full`? Otherwise, I cannot
correlate the data between them.
Also, the `(gdb) p
[2757_scrubbed.zip](https://github.com/kamailio/kamailio/files/6587206/2757_scrubbed.zip)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
[root@kamibh01 ~]# zgrep -h "bogus event 2 in state 5" /var/log/kamailio.log*
May 27 07:39:47 kamibh01 /usr/sbin/kamailio[11320]: CRITICAL: {2 1 INVITE
240487810-3831089987-474199...@sbc-uk-gw-th01b.uk.sdin.bt.net} dialog
[dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 5 for dlg
# zgrep -h "bogus event 2 in state 5" /var/log/kamailio.log*
Jun 1 10:12:14 kamibt01 /usr/sbin/kamailio[20001]: CRITICAL: {2 1 INVITE
6787142-3831531134-1330894...@sbc-uk-l-far07b.uk.sdin.bt.net} dialog
[dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 5 for dlg
0x7fae153d3cf0
The bogus state message may not be directly related but it's a one to one
correspondence between that message and the crash and it occurs within < 1s of
it being issued.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I don't seem to be able to add attachments here. I drag and drop and I either
get nothing at all or it inserts a file:// link pointing to my local file. I
can mail this direct to you if that would work?
--
You are receiving this because you are subscribed to this thread.
Reply to this email
And the log message `... bogus event 2 in state 5 for ...` is not directly
related to the dialog causing the crash, the print of the `*cell` shows it is
in state 3, not 5.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
The attachment was not uploaded, is only the path to it in the comment.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
file:///home/trevor/Downloads/2757_scrubbed.zip
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2757#issuecomment-85170___
Kamailio
(gdb) p *cell
$3 = {ref = 3, next = 0x7f9c302d0068, prev = 0x0, h_id = 8082, h_entry = 579,
state = 3, lifetime = 0, init_ts = 1622619237, start_ts = 1622619239, end_ts =
0, dflags = 513, iflags = 64, sflags = 0, toroute = 0, toroute_name = {s = 0x0,
len = 0}, from_rr_nb = 0, tl = {next = 0x0,
Can you get also from gdb:
```
p *cell
```
I am interested on a few other fields to see if the cell was somehow in
process of being destroyed.
Getting the pcap with all sip messages of this call would be very useful, the
time difference between packets helps to figure out if some timer
### Description
kamailio 5.4.5 crashes with a segfault shortly after producing messages in the
log like
Jun 1 10:12:14 thissystem /usr/sbin/kamailio[20001]: CRITICAL: {2 1 INVITE
6787142-3831531134-1330894187@some.telco.domain} dialog [dlg_hash.c:1182]:
next_state_dlg(): bogus event 2 in
21 matches
Mail list logo
