[OpenSER-Devel] [ openser-Bugs-1820323 ] openser crash

[SourceForge.net]

Bugs item #1820323, was opened at 2007-10-25 15:30
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1820323&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: ver devel
Status: Open
Resolution: None
Priority: 7
Private: No
Submitted By: Dan (dan_pascu)
Assigned to: Bogdan (bogdan_iancu)
Summary: openser crash

Initial Comment:
I got this crash with trunk (svn revision 2981)

Core was generated by `/usr/sbin/openser -P /var/run/openser/openser.pid -m 128 -u openser -g openser'.
Program terminated with signal 11, Segmentation fault.
#0  0xb7f12eb4 in __libc_res_nsearch () from /lib/i686/cmov/libresolv.so.2
(gdb) bt
#0  0xb7f12eb4 in __libc_res_nsearch () from /lib/i686/cmov/libresolv.so.2
#1  0xb7f1334c in __res_nsearch () from /lib/i686/cmov/libresolv.so.2
#2  0xb7f123fa in res_search () from /lib/i686/cmov/libresolv.so.2
#3  0x08085313 in get_record (name=0x63745f2e <Address 0x63745f2e out of bounds>, type=33) at resolve.c:457
#4  0x08085b92 in do_srv_lookup (name=0xb7c21b64 "\001", port=0x63745f2e, dn=0xb7d7aff4) at resolve.c:747
#5  0x080880da in get_next_su (p=0xb03b7120, su=0xb03b9c24, add_to_bl=1) at resolve.c:1206
#6  0xb795f4ec in t_should_relay_response (Trans=0xb03b9af8, new_code=408, branch=0, should_store=0xbfc0c5a4, should_relay=0xbfc0c5a8, cancel_bitmap=0xbfc0c5f8, reply=0xffffffff) at t_reply.c:622
#7  0xb79602ad in relay_reply (t=0xb03b9af8, p_msg=0xffffffff, branch=0, msg_status=408, cancel_bitmap=0xbfc0c5f8) at t_reply.c:1024
#8  0xb7961c05 in fake_reply (t=0xb03b9af8, branch=0, code=408) at timer.c:260
#9  0xb79636ac in timer_routine (ticks=152, attr=0x0) at timer.c:396
#10 0x080ad220 in start_timer_processes () at timer.c:275
#11 0x08068416 in main (argc=11, argv=0xbfc0c884) at main.c:827


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2007-10-29 15:48

Message:
Logged In: NO 

Sorry about the reference to the dns helper process. I was thinking of
something else (there is obviously no separate process to handle dns). One
of the UDP workers was the one that died.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2007-10-29 14:36

Message:
Logged In: NO 

The domain in question is eurovoice.ro. The problem seems to happen when
my proxy encounters a SUBSCRIBE to a user in this domain. The process that
crashes seems to be the dns helper process, though it doesn't crash
immediately. It happens after a couple of such messages are processed.

Here are the relevant parts returned by DNS lookups on the domain (as you
can see NAPTR indicates tcp support but there is no tcp related SRV
record):

dawn:~$ dig NAPTR eurovoice.ro

;; ANSWER SECTION:
eurovoice.ro.           2       IN      NAPTR   0 0 "S" "SIP+D2U" ""
_sip._udp.eurovoice.ro.
eurovoice.ro.           2       IN      NAPTR   10 10 "S" "SIP+D2T" ""
_sip._tcp.eurovoice.ro.

;; ADDITIONAL SECTION:
sip.eurovoice.ro.       292     IN      A       193.231.78.10
_sip._udp.eurovoice.ro. 292     IN      SRV     0 0 5060
sip.eurovoice.ro.

dawn:~$ dig SRV _sip._udp.eurovoice.ro.

;; ANSWER SECTION:
_sip._udp.eurovoice.ro. 281     IN      SRV     0 0 5060
sip.eurovoice.ro.

dawn:~$ dig SRV _sip._tcp.eurovoice.ro.

;; AUTHORITY SECTION:
eurovoice.ro.           300     IN      SOA     ns.eurovoice.ro.
support.euroweb.ro. 2007082401 28800 7200 604800 10800



----------------------------------------------------------------------

Comment By: Bogdan (bogdan_iancu)
Date: 2007-10-29 08:15

Message:
Logged In: YES 
user_id=1275325
Originator: NO

Hi Dan,

Can you point me to such domain or post the NAPTR and SRV records you are
using - I'll try to reproduce it.

Thanks and regards,
bogdan

----------------------------------------------------------------------

Comment By: Dan (dan_pascu)
Date: 2007-10-25 15:40

Message:
Logged In: YES 
user_id=1296758
Originator: YES

This may be related to the fact that the NAPTR for the target domain
returns 2 SRV records (first with priority 0 for UDP and 2nd with priority
10 for TCP), however only the UDP SRV record actually exists in DNS, while
the TCP one is missing.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1820323&group_id=139143