on my machine, ser 0.9.3 crashes as soon as a UA sends REGISTER message
on doing gdb ser corefile i get the following when calling 'bt'
(gdb) bt #0 qm_malloc (qm=0x8107e00, size=760) at mem/q_malloc.c:290 #1 0x0806ce0e in receive_msg ( buf=0x80d6560 "REGISTER sip:194.255.1.199:5060 SIP/2.0\r\nFrom: sip:88515356@194.255.1.199;tag=ccd4c5cb-13c4-2838-9d1b45-6d9e\r\nTo: sip:88515356@194.255.1.199\r\nCall-ID: ccd4c5cb-13c4-2838-9d1b45-7a20\r\nCSeq: 1 REGIS"..., len=437, rcv_info=0xbfed0fe0) at receive.c:92 #2 0x0808421c in udp_rcv_loop () at udp_server.c:458 #3 0x0805ceaf in main_loop () at main.c:1032
#4 0x0805e50b in main (argc=2, argv=0xbfed11a4) at main.c:1568
(gdb) print h $9 = 0
please help,
note that a similar setup on another machine works just fine.
tulika
When was the last time you updated from CVS? This problem is almost exactly what I was experiencing but this has been fixed for several weeks now.
_Steve
Tulika Pradhan wrote:
on my machine, ser 0.9.3 crashes as soon as a UA sends REGISTER message
on doing gdb ser corefile i get the following when calling 'bt'
(gdb) bt #0 qm_malloc (qm=0x8107e00, size=760) at mem/q_malloc.c:290 #1 0x0806ce0e in receive_msg ( buf=0x80d6560 "REGISTER sip:194.255.1.199:5060 SIP/2.0\r\nFrom: sip:88515356@194.255.1.199;tag=ccd4c5cb-13c4-2838-9d1b45-6d9e\r\nTo: sip:88515356@194.255.1.199\r\nCall-ID: ccd4c5cb-13c4-2838-9d1b45-7a20\r\nCSeq: 1 REGIS"..., len=437, rcv_info=0xbfed0fe0) at receive.c:92 #2 0x0808421c in udp_rcv_loop () at udp_server.c:458 #3 0x0805ceaf in main_loop () at main.c:1032
#4 0x0805e50b in main (argc=2, argv=0xbfed11a4) at main.c:1568
(gdb) print h $9 = 0
please help,
note that a similar setup on another machine works just fine.
tulika
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
i did not take the release from CVS but from the stable release 0.9.3 link.
can this be a problem ?
regards,
tulika
From: Steve Blair blairs@isc.upenn.edu To: Tulika Pradhan tulikapradhan@hotmail.com CC: serusers@lists.iptel.org Subject: Re: [Serusers] ser 0.9.3 crash Date: Wed, 14 Sep 2005 14:11:48 -0400
When was the last time you updated from CVS? This problem is almost exactly what I was experiencing but this has been fixed for several weeks now.
_Steve
Tulika Pradhan wrote:
on my machine, ser 0.9.3 crashes as soon as a UA sends REGISTER message
on doing gdb ser corefile i get the following when calling 'bt'
(gdb) bt #0 qm_malloc (qm=0x8107e00, size=760) at mem/q_malloc.c:290 #1 0x0806ce0e in receive_msg ( buf=0x80d6560 "REGISTER sip:194.255.1.199:5060 SIP/2.0\r\nFrom: sip:88515356@194.255.1.199;tag=ccd4c5cb-13c4-2838-9d1b45-6d9e\r\nTo: sip:88515356@194.255.1.199\r\nCall-ID: ccd4c5cb-13c4-2838-9d1b45-7a20\r\nCSeq: 1 REGIS"..., len=437, rcv_info=0xbfed0fe0) at receive.c:92 #2 0x0808421c in udp_rcv_loop () at udp_server.c:458 #3 0x0805ceaf in main_loop () at main.c:1032
#4 0x0805e50b in main (argc=2, argv=0xbfed11a4) at main.c:1568
(gdb) print h $9 = 0
please help,
note that a similar setup on another machine works just fine.
tulika
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- ISC Network Engineering The University of Pennsylvania 3401 Walnut Street, Suite 221A Philadelphia, PA 19104
voice: 215-573-8396
215-746-8001
fax: 215-898-9348
sip:blairs@upenn.edu
now, i am trying the 0.9.4 release and sometimes ser starts up ok. other times it crashes. here is the 'bt' results.
Loaded symbols for /lib/libnss_dns.so.2 #0 0x00b4eec3 in preload_udomain (_c=0x810c898, _d=0xb6178ce8) at udomain.c:302 302 ua.len = strlen(ua.s); (gdb) bt #0 0x00b4eec3 in preload_udomain (_c=0x810c898, _d=0xb6178ce8) at udomain.c:302 #1 0x00b4ab76 in register_udomain (_n=0x0, _d=0xbfedf6ec) at dlist.c:249 #2 0x00133795 in domain_fixup (param=0x810d834, param_no=1) at reg_mod.c:207 #3 0x08070723 in fix_actions (a=0x0) at route.c:238 #4 0x08070845 in fix_actions (a=0x0) at route.c:225 #5 0x080744e4 in fix_rls () at route.c:726 #6 0x0805e33d in main (argc=2, argv=0xbfedf9c4) at main.c:1582 (gdb)
any help would be greatly appreciated.
regards,
tulika
From: "Tulika Pradhan" tulikapradhan@hotmail.com To: blairs@isc.upenn.edu CC: serusers@lists.iptel.org Subject: Re: [Serusers] ser 0.9.3 crash Date: Wed, 14 Sep 2005 18:36:40 +0000
i did not take the release from CVS but from the stable release 0.9.3 link.
can this be a problem ?
regards,
tulika
From: Steve Blair blairs@isc.upenn.edu To: Tulika Pradhan tulikapradhan@hotmail.com CC: serusers@lists.iptel.org Subject: Re: [Serusers] ser 0.9.3 crash Date: Wed, 14 Sep 2005 14:11:48 -0400
When was the last time you updated from CVS? This problem is almost exactly what I was experiencing but this has been fixed for several weeks now.
_Steve
Tulika Pradhan wrote:
on my machine, ser 0.9.3 crashes as soon as a UA sends REGISTER message
on doing gdb ser corefile i get the following when calling 'bt'
(gdb) bt #0 qm_malloc (qm=0x8107e00, size=760) at mem/q_malloc.c:290 #1 0x0806ce0e in receive_msg ( buf=0x80d6560 "REGISTER sip:194.255.1.199:5060 SIP/2.0\r\nFrom: sip:88515356@194.255.1.199;tag=ccd4c5cb-13c4-2838-9d1b45-6d9e\r\nTo: sip:88515356@194.255.1.199\r\nCall-ID: ccd4c5cb-13c4-2838-9d1b45-7a20\r\nCSeq: 1 REGIS"..., len=437, rcv_info=0xbfed0fe0) at receive.c:92 #2 0x0808421c in udp_rcv_loop () at udp_server.c:458 #3 0x0805ceaf in main_loop () at main.c:1032
#4 0x0805e50b in main (argc=2, argv=0xbfed11a4) at main.c:1568
(gdb) print h $9 = 0
please help,
note that a similar setup on another machine works just fine.
tulika
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- ISC Network Engineering The University of Pennsylvania 3401 Walnut Street, Suite 221A Philadelphia, PA 19104
voice: 215-573-8396
215-746-8001
fax: 215-898-9348
sip:blairs@upenn.edu
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
hi,
what is the maximum number of users that can be registered on SER at one time. is there any such limitation ? i need to register about 250,000 users on a SER. apart from RAM and hard disk are there any other factors preventing this ?
regards,
tulika