subject:"\[SR\-Users\] \[Kamailio 4.2\] Crash during burn\-in test"

Re: [SR-Users] [Kamailio 4.2] Crash during burn-in test

2015-09-24 Thread Jack Wang

Hi Daniel,

Sorry for my late reply at first.

I took your suggestion and update Kamailio from 4.2.3 to 4.2.6,
then test again,
it does't crash now !  :D
Thank you very much!

2015-09-08 15:03 GMT+08:00 Daniel-Constantin Mierla :

> Hello,
>
> the first frames of the backtrace don't have the symbol table, do have
> other core files from where you can extract the bt full?
>
> Also, 4.2.3 is old in its series, newer versions in branch 4.2 were
> released. Can you update the latest version in branch 4.2 and reproduce
> again? That will rule out is not a side effect of an issue fixed after
> 4.2.3. You don't need to change anything in config or database, just grab
> the latest sources from branch 4.3 and install over the old binaries.
>
> Cheers,
> Daniel
>
>
> On 08/09/15 07:58, Jack Wang wrote:
>
> Hi,
>
> The result of 'kamailio -v' is:
>
> version: kamailio 4.2.3 (arm/linux) 87ca6e-dirty
> flags: STATS: Off, EXTRA_DEBUG, USE_TCP, USE_TLS, TLS_HOOKS,
> USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP,
> PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, USE_PTHREAD_MUTEX,
> USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST,
> HAVE_RESOLV_RES
> MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE
> 65535, DEFAULT PKG_SIZE 8MB
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
> id: 87ca6e -dirty
> compiled on 16:15:00 Sep  4 2015 with arm-marvell-linux-gnueabi-gcc
>
>
> It can be reproduced not only once, steps like wrote before.
>
> Following link is the result of `bt full` from the core file generated:
>
> https://gist.github.com/BroWater/dd759897f4b88672720a#file-gistfile1-txt
>
> FYI
>
>
>
> >Hello,
> >
> >can you give the exact version: kamailio -v?
> >
> >Also, the log message indicates that a core file was generated, sent the
> >backtrace taken from gdb:
> >
> >gdb /path/to/kamailio /path/to/corefile
> >bt full
> >
> >Could you reproduce the issue, or did it happen only once?
> >
> >Cheers,
> >Daniel
> >
> >On 03/09/15 04:50, Jack Wang wrote:
> >>
> >> [Steps]
> >>
> >> 1. one MCU call multi-endpoints
> >> 2. MCU hangup all endpoints
> >>
> >> repeatedly. And all through Kamailio proxy.
> >>
> >> [Results]
> >>
> >> For a while, Kamailio crashed.
> >>
> >> Followings are related logs:
> >>
> >>
> >> ==
> >>
> >> Sep  2 19:08:34 ./kamailio[3712]: : tm [t_fwd.c:1632]:
> >> t_send_branch(): BUG: t_send_branch: retr. already started for
> 0x41848fa0
> >> Sep  2 19:08:34 ./kamailio[3712]: ERROR: sl [sl_funcs.c:387]:
> >> sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on
> >> sending to next hop occurred (477/SL)
> >>
> >> At this point the related behavior is that Kamailio received two INFO
> >> requests simultaneously. I wonder whether this is the cause.
> >> And maybe it's related to the later crash?
> >>
> >> Sep  2 19:08:35 ./kamailio[3713]: CRITICAL:  [pass_fd.c:293]:
> >> receive_fd(): EOF on 11
> >> Sep  2 19:08:35 ./kamailio[3703]: ALERT:  [main.c:784]:
> >> handle_sigs(): child process 3704 exited by a signal 11
> >> Sep  2 19:08:35 ./kamailio[3703]: ALERT:  [main.c:787]:
> >> handle_sigs(): core was generated
> >> Sep  2 19:08:35 ./kamailio[3703]: :  [mem/f_malloc.c:586]:
> >> fm_free(): BUG: fm_free: bad pointer 0x7239b6c4 (out of memory
> >> block!), called from tm: h_table.c: free_cell(157) - aborting
> >>
> >>
> >> Any suggestions?
> >>
> >> Thanks.
> >>
> >> ==
> >>
> >>
> >> ___
> >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> >> sr-users at lists.sip-router.org
> >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
> --
> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - 
> http://www.linkedin.com/in/miconda
> Book: SIP Routing With Kamailio - http://www.asipto.com
> Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - 
> http://asipto.com/u/kat
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] [Kamailio 4.2] Crash during burn-in test

2015-09-24 Thread Daniel-Constantin Mierla

Hello,

ok, thanks for providng the feedback, it is good to know that was
something already fixed.

Cheers,
Daniel

On 24/09/15 12:20, Jack Wang wrote:
> Hi Daniel,
>
> Sorry for my late reply at first.
>
> I took your suggestion and update Kamailio from 4.2.3 to 4.2.6,
> then test again,
> it does't crash now !  :D
> Thank you very much!
>
> 2015-09-08 15:03 GMT+08:00 Daniel-Constantin Mierla  >:
>
> Hello,
>
> the first frames of the backtrace don't have the symbol table, do
> have other core files from where you can extract the bt full?
>
> Also, 4.2.3 is old in its series, newer versions in branch 4.2
> were released. Can you update the latest version in branch 4.2 and
> reproduce again? That will rule out is not a side effect of an
> issue fixed after 4.2.3. You don't need to change anything in
> config or database, just grab the latest sources from branch 4.3
> and install over the old binaries.
>
> Cheers,
> Daniel
>
>
> On 08/09/15 07:58, Jack Wang wrote:
>> Hi,
>>
>> The result of 'kamailio -v' is:
>>
>> version: kamailio 4.2.3 (arm/linux) 87ca6e-dirty
>> flags: STATS: Off, EXTRA_DEBUG, USE_TCP, USE_TLS, TLS_HOOKS,
>> USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM,
>> SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX,
>> USE_PTHREAD_MUTEX, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR,
>> USE_DST_BLACKLIST, HAVE_RESOLV_RES
>> MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024,
>> BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
>> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
>> id: 87ca6e -dirty
>> compiled on 16:15:00 Sep  4 2015 with arm-marvell-linux-gnueabi-gcc
>>
>>
>> It can be reproduced not only once, steps like wrote before.
>>
>> Following link is the result of `bt full` from the core file
>> generated:
>>
>> https://gist.github.com/BroWater/dd759897f4b88672720a#file-gistfile1-txt
>>
>> FYI
>>
>>
>>
>> >Hello,
>> >
>> >can you give the exact version: kamailio -v?
>> >
>> >Also, the log message indicates that a core file was generated,
>> sent the
>> >backtrace taken from gdb:
>> >
>> >gdb /path/to/kamailio /path/to/corefile
>> >bt full
>> >
>> >Could you reproduce the issue, or did it happen only once?
>> >
>> >Cheers,
>> >Daniel
>> >
>> >On 03/09/15 04:50, Jack Wang wrote:
>> >>
>> >> [Steps]
>> >>
>> >> 1. one MCU call multi-endpoints 
>> >> 2. MCU hangup all endpoints
>> >>
>> >> repeatedly. And all through Kamailio proxy.
>> >>
>> >> [Results]
>> >>
>> >> For a while, Kamailio crashed.
>> >>
>> >> Followings are related logs:
>> >>
>> >>
>> >> ==
>> >>
>> >> Sep  2 19:08:34 ./kamailio[3712]: : tm [t_fwd.c:1632]:
>> >> t_send_branch(): BUG: t_send_branch: retr. already started for
>> 0x41848fa0
>> >> Sep  2 19:08:34 ./kamailio[3712]: ERROR: sl [sl_funcs.c:387]:
>> >> sl_reply_error(): ERROR: sl_reply_error used: Unfortunately
>> error on
>> >> sending to next hop occurred (477/SL)
>> >>
>> >> At this point the related behavior is that Kamailio received
>> two INFO
>> >> requests simultaneously. I wonder whether this is the cause.
>> >> And maybe it's related to the later crash?
>> >>
>> >> Sep  2 19:08:35 ./kamailio[3713]: CRITICAL: 
>> [pass_fd.c:293]:
>> >> receive_fd(): EOF on 11
>> >> Sep  2 19:08:35 ./kamailio[3703]: ALERT:  [main.c:784]:
>> >> handle_sigs(): child process 3704 exited by a signal 11
>> >> Sep  2 19:08:35 ./kamailio[3703]: ALERT:  [main.c:787]:
>> >> handle_sigs(): core was generated
>> >> Sep  2 19:08:35 ./kamailio[3703]: :  [mem/f_malloc.c:586]:
>> >> fm_free(): BUG: fm_free: bad pointer 0x7239b6c4 (out of memory
>> >> block!), called from tm: h_table.c: free_cell(157) - aborting
>> >>
>> >>
>> >> Any suggestions?
>> >>
>> >> Thanks.
>> >>
>> >> ==
>> >>
>> >>
>> >> ___
>> >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
>> mailing list
>> >> sr-users at lists.sip-router.org 
>> >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>
> -- 
> Daniel-Constantin Mierla
> http://twitter.com/#!/miconda  - 
> http://www.linkedin.com/in/miconda
> Book: SIP Routing With Kamailio - http://www.asipto.com
> Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - 
> http://asipto.com/u/kat
>
>

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced

Re: [SR-Users] [Kamailio 4.2] Crash during burn-in test

2015-09-08 Thread Daniel-Constantin Mierla

Hello,

the first frames of the backtrace don't have the symbol table, do have
other core files from where you can extract the bt full?

Also, 4.2.3 is old in its series, newer versions in branch 4.2 were
released. Can you update the latest version in branch 4.2 and reproduce
again? That will rule out is not a side effect of an issue fixed after
4.2.3. You don't need to change anything in config or database, just
grab the latest sources from branch 4.3 and install over the old binaries.

Cheers,
Daniel

On 08/09/15 07:58, Jack Wang wrote:
> Hi,
>
> The result of 'kamailio -v' is:
>
> version: kamailio 4.2.3 (arm/linux) 87ca6e-dirty
> flags: STATS: Off, EXTRA_DEBUG, USE_TCP, USE_TLS, TLS_HOOKS,
> USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM,
> SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX,
> USE_PTHREAD_MUTEX, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR,
> USE_DST_BLACKLIST, HAVE_RESOLV_RES
> MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024,
> BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
> id: 87ca6e -dirty
> compiled on 16:15:00 Sep  4 2015 with arm-marvell-linux-gnueabi-gcc
>
>
> It can be reproduced not only once, steps like wrote before.
>
> Following link is the result of `bt full` from the core file generated:
>
> https://gist.github.com/BroWater/dd759897f4b88672720a#file-gistfile1-txt
>
> FYI
>
>
>
> >Hello,
> >
> >can you give the exact version: kamailio -v?
> >
> >Also, the log message indicates that a core file was generated, sent the
> >backtrace taken from gdb:
> >
> >gdb /path/to/kamailio /path/to/corefile
> >bt full
> >
> >Could you reproduce the issue, or did it happen only once?
> >
> >Cheers,
> >Daniel
> >
> >On 03/09/15 04:50, Jack Wang wrote:
> >>
> >> [Steps]
> >>
> >> 1. one MCU call multi-endpoints 
> >> 2. MCU hangup all endpoints
> >>
> >> repeatedly. And all through Kamailio proxy.
> >>
> >> [Results]
> >>
> >> For a while, Kamailio crashed.
> >>
> >> Followings are related logs:
> >>
> >>
> >> ==
> >>
> >> Sep  2 19:08:34 ./kamailio[3712]: : tm [t_fwd.c:1632]:
> >> t_send_branch(): BUG: t_send_branch: retr. already started for
> 0x41848fa0
> >> Sep  2 19:08:34 ./kamailio[3712]: ERROR: sl [sl_funcs.c:387]:
> >> sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on
> >> sending to next hop occurred (477/SL)
> >>
> >> At this point the related behavior is that Kamailio received two INFO
> >> requests simultaneously. I wonder whether this is the cause.
> >> And maybe it's related to the later crash?
> >>
> >> Sep  2 19:08:35 ./kamailio[3713]: CRITICAL:  [pass_fd.c:293]:
> >> receive_fd(): EOF on 11
> >> Sep  2 19:08:35 ./kamailio[3703]: ALERT:  [main.c:784]:
> >> handle_sigs(): child process 3704 exited by a signal 11
> >> Sep  2 19:08:35 ./kamailio[3703]: ALERT:  [main.c:787]:
> >> handle_sigs(): core was generated
> >> Sep  2 19:08:35 ./kamailio[3703]: :  [mem/f_malloc.c:586]:
> >> fm_free(): BUG: fm_free: bad pointer 0x7239b6c4 (out of memory
> >> block!), called from tm: h_table.c: free_cell(157) - aborting
> >>
> >>
> >> Any suggestions?
> >>
> >> Thanks.
> >>
> >> ==
> >>
> >>
> >> ___
> >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> >> sr-users at lists.sip-router.org 
> >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] [Kamailio 4.2] Crash during burn-in test

2015-09-03 Thread Daniel-Constantin Mierla

Hello,

can you give the exact version: kamailio -v?

Also, the log message indicates that a core file was generated, sent the
backtrace taken from gdb:

gdb /path/to/kamailio /path/to/corefile
bt full

Could you reproduce the issue, or did it happen only once?

Cheers,
Daniel

On 03/09/15 04:50, Jack Wang wrote:
>
> [Steps]
>
> 1. one MCU call multi-endpoints 
> 2. MCU hangup all endpoints
>
> repeatedly. And all through Kamailio proxy.
>
> [Results]
>
> For a while, Kamailio crashed.
>
> Followings are related logs:
>
>
> ==
>
> Sep  2 19:08:34 ./kamailio[3712]: : tm [t_fwd.c:1632]:
> t_send_branch(): BUG: t_send_branch: retr. already started for 0x41848fa0
> Sep  2 19:08:34 ./kamailio[3712]: ERROR: sl [sl_funcs.c:387]:
> sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on
> sending to next hop occurred (477/SL)
>
> At this point the related behavior is that Kamailio received two INFO
> requests simultaneously. I wonder whether this is the cause.
> And maybe it's related to the later crash?
>
> Sep  2 19:08:35 ./kamailio[3713]: CRITICAL:  [pass_fd.c:293]:
> receive_fd(): EOF on 11
> Sep  2 19:08:35 ./kamailio[3703]: ALERT:  [main.c:784]:
> handle_sigs(): child process 3704 exited by a signal 11
> Sep  2 19:08:35 ./kamailio[3703]: ALERT:  [main.c:787]:
> handle_sigs(): core was generated
> Sep  2 19:08:35 ./kamailio[3703]: :  [mem/f_malloc.c:586]:
> fm_free(): BUG: fm_free: bad pointer 0x7239b6c4 (out of memory
> block!), called from tm: h_table.c: free_cell(157) - aborting
>
>
> Any suggestions?
>
> Thanks.
>
> ==
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] [Kamailio 4.2] Crash during burn-in test

2015-09-02 Thread Jack Wang

[Steps]

1. one MCU call multi-endpoints
2. MCU hangup all endpoints

repeatedly. And all through Kamailio proxy.

[Results]

For a while, Kamailio crashed.

Followings are related logs:


==

Sep  2 19:08:34 ./kamailio[3712]: : tm [t_fwd.c:1632]: t_send_branch():
BUG: t_send_branch: retr. already started for 0x41848fa0
Sep  2 19:08:34 ./kamailio[3712]: ERROR: sl [sl_funcs.c:387]:
sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on
sending to next hop occurred (477/SL)

At this point the related behavior is that Kamailio received two INFO
requests simultaneously. I wonder whether this is the cause.
And maybe it's related to the later crash?

Sep  2 19:08:35 ./kamailio[3713]: CRITICAL:  [pass_fd.c:293]:
receive_fd(): EOF on 11
Sep  2 19:08:35 ./kamailio[3703]: ALERT:  [main.c:784]:
handle_sigs(): child process 3704 exited by a signal 11
Sep  2 19:08:35 ./kamailio[3703]: ALERT:  [main.c:787]:
handle_sigs(): core was generated
Sep  2 19:08:35 ./kamailio[3703]: :  [mem/f_malloc.c:586]: fm_free():
BUG: fm_free: bad pointer 0x7239b6c4 (out of memory block!), called from
tm: h_table.c: free_cell(157) - aborting


Any suggestions?

Thanks.

==
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] [Kamailio 4.2] Crash during burn-in test

Re: [SR-Users] [Kamailio 4.2] Crash during burn-in test

Re: [SR-Users] [Kamailio 4.2] Crash during burn-in test

Re: [SR-Users] [Kamailio 4.2] Crash during burn-in test

[SR-Users] [Kamailio 4.2] Crash during burn-in test

5 matches

Site Navigation

Mail list logo

Footer information