Re: [SR-Users] TLS problems

Hello Klaus, thank you very much! I really appreciate your help! I followed your instructions and I hope that the attached file includes

necessary informations. regards Andreas -----Ursprüngliche Nachricht----- Von: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Gesendet: Freitag, 22. Januar 2010 10:50 An: Andreas Rehbein Betreff: Re: AW: [SR-Users] TLS problems Andreas Rehbein schrieb: with the log only shows the last function call. Please start gdb again and at the gdb prompt generate a backtrace by entering bt, e.g: (gdb) bt regards klaus > regards > Andreas > > -----Ursprüngliche Nachricht----- > Von: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > Gesendet: Freitag, 22. Januar 2010 09:35 > An: Andreas Rehbein > Cc: sr-users(a)lists.sip-router.org > Betreff: Re: [SR-Users] TLS problems > > Hi Andreas! > > Maybe this is the same bug I reported yesterday. Unfortunately I can not > reproduce the crash anymore. > > Does the crash happen everytime? > > Kamailio produced a core dump: > > 0(6257) ALERT: <core> [main.c:725]: core was generated > > So please send a the backtrace: > # gdb kamailio /path/to/corefile > > bt > > Location of the core file is usually / or /tmp or the kamailio's working > directory. Use > # cat /proc/sys/kernel/core_pattern > to find the exact location of the core dump. > > Further, it might be useful to enable memory debugging: > - in Makefile.defs use -DDBG_QM_MALLOC instead of -DF_MALLOC and > rebuild/reinstall kamailio > - set higher loglevels in kamailio.cfg > memlog=3 > memdbg=3 > debug=3 > modparam("tls", "tls_log", 3) > > Note: this excessive logging makes kamailio start/stop real slow and > logfile will increase rapidly (might fill up your hard disk) > > regards > klaus > > > > Andreas Rehbein schrieb: >> Hi, >> >> >> >> I’ve installed Kamailio 3.0 on RHEL5 and activated the mysql backend and

>> tls support. Everything works fine with Soft User Agent „Phoner lite“. >> My Problem is: If I try to register a „snom 370“ Kamailio crashes >> immediatly. What is wrong? Any suggestions? >> >> Debug: >> >> 17(6290) DEBUG: <core> [ip_addr.c:116]: tcpconn_new: new tcp connection:

>> 192.168.0.222 >> >> 17(6290) DEBUG: <core> [tcp_main.c:1052]: tcpconn_new: on port 1430,

> 3 >> 17(6290) DEBUG: <core> [tcp_main.c:1351]: tcpconn_add: hashes: >> 978:1690:1400, 1 >> >> 17(6290) DEBUG: <core> [io_wait.h:361]: DBG: io_watch_add(0x8222fe0, 31,

fd=8 >> 13(6283) DEBUG: tls [tls_server.c:109]: Using TLS domain TLSs<default> >> >> 17(6290) DEBUG: <core> [tcp_main.c:2826]: DBG: handle_tcp_child: dead >> tcp child 0 (pid 6283, no 13) (shutting down?) >> >> 17(6290) DEBUG: <core> [io_wait.h:588]: DBG: io_watch_del (0x8222fe0, >> 24, -1, 0x0) fd_no=24 called >> >> 17(6290) : <core> [pass_fd.c:283]: ERROR: receive_fd: EOF on 4 >> >> 17(6290) DEBUG: <core> [tcp_main.c:3038]: DBG: handle_ser_child: dead >> child 13, pid 6283 (shutting down?) >> >> 17(6290) DEBUG: <core> [io_wait.h:588]: DBG: io_watch_del (0x8222fe0, 4,

>> -1, 0x0) fd_no=23 called >> >> 0(6257) ALERT: <core> [main.c:722]: child process 6283 exited by a >> signal 11 >> >> 0(6257) ALERT: <core> [main.c:725]: core was generated >> >> 0(6257) INFO: <core> [main.c:737]: INFO: terminating due to SIGCHLD >> >> 17(6290) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 15(6286) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 16(6289) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 12(6281) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 14(6285) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 10(6278) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 6(6269) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 2(6261) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 11(6280) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 1(6260) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 9(6276) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 8(6272) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 3(6262) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 7(6270) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 5(6267) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 4(6265) INFO: <core> [main.c:788]: INFO: signal 15 received >> >> 0(6257) DEBUG: tm [t_funcs.c:122]: DEBUG: tm_shutdown : start >> >> 0(6257) DEBUG: tm [t_funcs.c:125]: DEBUG: tm_shutdown : emptying hash > table >> 0(6257) DEBUG: tm [t_funcs.c:127]: DEBUG: tm_shutdown : removing > semaphores >> 0(6257) DEBUG: tm [t_funcs.c:129]: DEBUG: tm_shutdown : destroying tmcb

>> lists >> >> 0(6257) DEBUG: tm [t_funcs.c:132]: DEBUG: tm_shutdown : done >> >> 0(6257) DEBUG: tls [tls_init.c:621]: tls module final tls destroy >> >> 0(6257) DEBUG: <core> [mem/shm_mem.c:236]: shm_mem_destroy >> >> 0(6257) DEBUG: <core> [mem/shm_mem.c:239]: destroying the shared memory

>> lock >> >> 0(6257) DEBUG: <core> [main.c:741]: terminating due to SIGCHLD >> >> >> >> tia >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> sr-users mailing list >> sr-users(a)lists.sip-router.org >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users