Up to Discussions in OpenSBC

This Question is Not Answered

1 "correct" answer available (5 pts) 2 "helpful" answers available (1 pts)
2 Replies Last post: Jan 20, 2010 10:56 PM by oliverkazaam41  
Click to view oliverkazaam41's profile  
oliverkazaam41
82 posts since
Jan 31, 2009

Jan 18, 2010 9:07 PM

Constant Crashing


Hi Joegen,

I guess I am back.. :) Well been having problem with 1.1.6-9 version. It keeps on crashing. I did a back trace and all I get is this

[New process 22540]
[New process 22539]
[New process 22538]
[New process 22537]
[New process 22536]
[New process 22535]
[New process 22534]
[New process 22533]
[New process 22532]
[New process 22531]
[New process 22530]
[New process 22529]
[New process 22528]
[New process 22527]
[New process 22526]
[New process 22525]
[New process 22524]
[New process 22523]
[New process 22522]
[New process 22521]
[New process 22520]
[New process 22519]
[New process 22518]
[New process 22517]
[New process 22516]
[New process 22515]
[New process 22514]
[New process 22513]
[New process 22512]
[New process 22511]
[New process 22510]
[New process 22509]
[New process 22508]
[New process 22507]
[New process 22506]
[New process 22505]
[New process 22504]
[New process 22503]
[New process 22502]
[New process 22501]
[New process 22500]
[New process 22499]
[New process 22498]
[New process 22495]
#0 0x00f49402 in __kernel_vsyscall ()


Also the last log I got was this

2010/01/18 04:18:10.230 INF: [CID=0xa67cb13f] >>> SIP/2.0 200 OK Method(REGISTER) DST: cc.dd.ee..ff:36775:UDP SRC: aa.bb.cc.dd:5060 enc=0 bytes=360
2010/01/18 04:18:10.230 PWL: [CID=0x00000000] *** NO MATCH *** sip:cc.dd.ee..ff --> sip:64.2.17.*
2010/01/18 04:18:10.230 PWL: [CID=0x00000000] *** NO MATCH *** sip:%2A --> sip:64.2.17.*
2010/01/18 04:18:10.230 PWL: [CID=0x00000000] Using Iface: aa.bb.cc.dd to send to Dest: cc.dd.ee..ff
2010/01/18 04:18:11.332 INF: [CID=0xc5f73bfd] <<< REGISTER sip:aa.bb.cc.dd:5060 SIP/2.0 Method(REGISTER) SRC: 11.22.33.44:5060:UDP enc=0 bytes=739
2010/01/18 04:18:11.333 DTL: [CID=0xc5f73bfd] NIST(901775511) *** CREATED *** - NIST|46e2c6ce-84130369-25a0f1a8@192.168.1.132|z9hG4bKa95a2aa771B58D8E|REGISTER
2010/01/18 04:18:11.334 DTL: [CID=0xc5f73bfd] NIST(901775511) Event(SIPMessage) - REGISTER sip:aa.bb.cc.dd:5060 SIP/2.0
2010/01/18 04:18:11.334 DBG: [CID=0xc5f73bfd] TRANSACTION: (NIST) REGISTER sip:aa.bb.cc.dd:5060 SIP/2.0 State: 0
2010/01/18 04:18:11.335 DTL: [CID=0xc5f73bfd] NIST(901775511) StateIdle->StateTrying
2010/01/18 04:18:11.335 INF: [CID=0xc5f73bfd] *** LOCAL REG *** sip:8179 at aa dot bb dot cc.dd


With your deployment do you encounter such problems? Do you think it has to do with the kind of linux distro I am using? Thanks.

Click to view joegen's profile  
joegen
469 posts since
Apr 28, 2007
1. Jan 20, 2010 8:48 PM in response to: oliverkazaam41
Re: Constant Crashing

Hi Oliver,

Welcome back! I assure you that the latest bleeding edge release of OpenSBC always finds its way inproduction environment so I can assure that call handling is stable at the very least. It seems that your crash is with registration. You can suspect two things for this. I would first start with doubting the compiled binary as corrupted. Always starting with a clean build first is a good idea. If you can still reproduce the crash, allways send a level 5 log so we an see if the message format has something to do with it.

If you can replicate this fast enough, I can volunteer to tail the log for you if you give me access to the server.

Joegen

Click to view oliverkazaam41's profile  
oliverkazaam41
82 posts since
Jan 31, 2009
2. Jan 20, 2010 10:56 PM in response to: joegen
Re: Constant Crashing

Thanks for the reply Joegen. I isolated the crashes. All the crashes happend with one remote extensions doing a registration to SBC. Its been 5 days now after removing the said extension and SBC is still alive. The extension is a Polycom IP 330. I also set the logs to level 5 just in case a crash happens again. We will be able to trace the culprit.

Actions

More Like This