yeah lots of traffic.<div>so there's no way of telling whether that particular BYE caused the crashed or not.</div><div>unless i enable debug for the server.<br><div><br></div><div>besides, you're right it might just be a simple case of receiving a BYE for an expired </div>
<div>dialog or something, doesn't seem too fishy at all. i wonder if anybody from the list</div><div>is also experiencing this?</div><div><br clear="all">Kelvin Chua<br>
<br><br><div class="gmail_quote">On Wed, Apr 21, 2010 at 5:16 PM, Iñaki Baz Castillo <span dir="ltr"><<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">2010/4/21 Kelvin Chua <<a href="mailto:kelchy@gmail.com">kelchy@gmail.com</a>>:<br>
</div><div class="im">> hi inaki,<br>
> unfortunately since i am not expecting any segfaults from kamailio, i have<br>
> very little<br>
> debug info, only those spurted out by syslog. not been using 1.5 for some<br>
> time now.<br>
> bad news, happened twice today. in a<br>
> span of 3 hours. seems like an inbound BYE. here is the other instance:<br>
<br>
> Apr 21 11:58:56 kamvm-1 /usr/local/sbin/kamailio[2526]: WARNING: dialog<br>
> [dlg_handlers.c:806]: unable to find dialog for BYE with route param<br>
> 'e34.a5ceb3d5' [1086:1564208218]<br>
<br>
</div>This just means that Kamailio has received a BYE thtat doesn't match<br>
with an existing dialog. Perhaps the dialog expired, a previous BYE<br>
from the other side was already received or kamailio was restarted and<br>
doesn't keep the dialogs info in database.<br>
<br>
Are you sure that the folowing log lines occur due to the previous BYE<br>
line? has the server lot of traffic?<br>
<div><div></div><div class="h5"><br>
<br>
> Apr 21 11:58:56 kamvm-1 /usr/local/sbin/kamailio[2526]: ERROR: dialog<br>
> [dlg_handlers.c:218]: bad sip message or missing Contact hdr<br>
> Apr 21 11:58:56 kamvm-1 /usr/local/sbin/kamailio[2526]: ERROR: dialog<br>
> [dlg_handlers.c:350]: could not add further info to the dialog<br>
> Apr 21 11:58:56 kamvm-1 kernel: kamailio[2526]: segfault at 0000000000000088<br>
> rip 00002b4a039f979a rsp 00007fff0f0472c0 error 4<br>
> Apr 21 11:59:01 kamvm-1 /usr/local/sbin/kamailio[2524]: ALERT: <core><br>
> [main.c:722]: child process 2526 exited by a signal 11<br>
> Apr 21 11:59:01 kamvm-1 /usr/local/sbin/kamailio[2524]: ALERT: <core><br>
> [main.c:725]: core was generated<br>
><br>
> Kelvin Chua<br>
><br>
><br>
> On Wed, Apr 21, 2010 at 5:06 PM, Iñaki Baz Castillo <<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>> wrote:<br>
>><br>
>> 2010/4/21 Kelvin Chua <<a href="mailto:kelchy@gmail.com">kelchy@gmail.com</a>>:<br>
>> > currently using kamailio 3.0 with around 1000 users.<br>
>> > Apr 21 10:19:57 kamvm-1 /usr/local/sbin/kamailio[28511]: ERROR: dialog<br>
>> > [dlg_handlers.c:218]: bad sip message or missing Contact hdr<br>
>> > Apr 21 10:19:57 kamvm-1 /usr/local/sbin/kamailio[28511]: ERROR: dialog<br>
>> > [dlg_handlers.c:350]: could not add further info to the dialog<br>
>> > Apr 21 10:19:57 kamvm-1 kernel: kamailio[28511]: segfault at<br>
>> > 0000000000000088 rip 00002ab61b62779a rsp 00007fffec157440 error 4<br>
>> > Apr 21 10:19:57 kamvm-1 /usr/local/sbin/kamailio[28507]: ALERT: <core><br>
>> > [main.c:722]: child process 28511 exited by a signal 11<br>
>> > Apr 21 10:19:57 kamvm-1 /usr/local/sbin/kamailio[28507]: ALERT: <core><br>
>> > [main.c:725]: core was generated<br>
>><br>
>> Oh my god!<br>
>> Let me two question:<br>
>><br>
>> - Are you able to determine if the problem occurs when handling an<br>
>> INVITE or a response?<br>
>> - Do you know if some occurs in Kamailio 1.5?<br>
>><br>
>><br>
>><br>
>> --<br>
>> Iñaki Baz Castillo<br>
>> <<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>><br>
><br>
><br>
<br>
<br>
<br>
</div></div>--<br>
<div><div></div><div class="h5">Iñaki Baz Castillo<br>
<<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>><br>
</div></div></blockquote></div><br></div></div>