sr-dev August 2018

sr-dev@lists.kamailio.org

22 participants
281 discussions

Start a nNew thread

[kamailio/kamailio] Broken Kamailio repository for CentOS 7 (#1604)

by pwakano

5 years, 4 months

[kamailio/kamailio] Segfault when calling $sel(cfg_get...) (#1159)

by Sebastian Damm

### Description I set some configuration parameters in the global section of kamailio.cfg and wanted to read them later in request_route and reply_route. But when accessing them, Kamailio segfaults. However, I can read them via kamcmd after startup. ### Troubleshooting #### Reproduction Set the following config parameter in your kamailio.cfg in the global section: ``` config.foo = "hello Daniel" ``` later, put your request and reply route in the configuration file: ``` request_route { xlog("L_INFO", "Reading config.foo into variable"); $var(configfoo) = $sel(cfg_get.config.foo); } onreply_route { xlog("L_INFO", "Reading config.foo into variable"); $var(configfoo) = $sel(cfg_get.config.foo); } ``` #### Debugging Data gdb output is the following: ``` GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/sbin/kamailio...Reading symbols from /usr/lib/debug/.build-id/94/dfffd4a243602bbd4d977202f533c3e9e613f7.debug...done. done. [New LWP 7999] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio_li_sniffer.pid -f /etc/kamaili'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f19e418e20d in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #0 0x00007f19e418e20d in ?? () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00000000006f4813 in select_cfg_var (res=0x7ffc998181d0, s=0x7f19e3965f60, msg=0x7f19e3985dd0) at core/cfg/cfg_select.c:227 group = 0x7f19e394e600 var = 0x7f19e3985958 p = 0x40 i = 32537 buf = '\000' <repeats 21 times> __FUNCTION__ = "select_cfg_var" #2 0x000000000050a6f0 in run_select (res=0x7ffc998181d0, s=0x7f19e3965f60, msg=0x7f19e3985dd0) at core/select.c:425 ret = 0 orig_level = 0 __FUNCTION__ = "run_select" #3 0x00007f19e133f089 in pv_get_select (msg=0x7f19e3985dd0, param=0x7f19e39667b8, res=0x7ffc998182d0) at pv_select.c:61 s = {s = 0x0, len = 0} sel = 0x7f19e3965f60 #4 0x00000000005b38a3 in pv_get_spec_value (msg=0x7f19e3985dd0, sp=0x7f19e39667a0, value=0x7ffc998182d0) at core/pvapi.c:1307 ret = 0 __FUNCTION__ = "pv_get_spec_value" #5 0x000000000057b007 in lval_pvar_assign (h=0x7ffc99818a80, msg=0x7f19e3985dd0, lv=0x7f19e3966690, rv=0x7f19e3966798) at core/lvalue.c:335 pvar = 0x7f19e39658d8 pval = {rs = {s = 0x0, len = 0}, ri = 0, flags = 0} r_avp = 0x417590 <syslog@plt> avp_val = {n = 7876360, s = {s = 0x782f08 "DEBUG", len = 7}, re = 0x782f08} ret = 0 v = 18987664 destroy_pval = 0 __FUNCTION__ = "lval_pvar_assign" #6 0x000000000057bd36 in lval_assign (h=0x7ffc99818a80, msg=0x7f19e3985dd0, lv=0x7f19e3966690, rve=0x7f19e3966790) at core/lvalue.c:400 rv = 0x7f19e3966798 ret = 0 __FUNCTION__ = "lval_assign" #7 0x0000000000467f60 in do_action (h=0x7ffc99818a80, a=0x7f19e3966ec0, msg=0x7f19e3985dd0) at core/action.c:1430 ret = -5 v = 6 dst = {send_sock = 0x7f19e449f300, to = {s = {sa_family = 34783, sa_data = "\201\231\374\177\000\000\220\025\031\001\000\000\000"}, sin = { sin_family = 34783, sin_port = 39297, sin_addr = {s_addr = 32764}, sin_zero = "\220\025\031\001\000\000\000"}, sin6 = {sin6_family = 34783, sin6_port = 39297, sin6_flowinfo = 32764, sin6_addr = {__in6_u = { __u6_addr8 = "\220\025\031\001\000\000\000\000@\206\201\231\374\177\000", __u6_addr16 = {5520, 281, 0, 0, 34368, 39297, 32764, 0}, __u6_addr32 = {18421136, 0, 2575402560, 32764}}}, sin6_scope_id = 8172960}}, id = 0, proto = -32 '\340', send_flags = {f = 188 '\274', blst_imask = 33 '!'}} tmp = 0x7ffc99818a90 "\220uA" new_uri = 0x2010 <error: Cannot access memory at address 0x2010> end = 0x7f19e44a1620 "" crt = 0x3939393700000015 <error: Cannot access memory at address 0x3939393700000015> cmd = 0x7f19e395d060 len = -467267128 user = 32537 uri = {user = {s = 0x7f19e44a1620 "", len = 18988272}, passwd = {s = 0x121bce0 "`\002", len = -467267135}, host = { s = 0x121bcfc "10:34:39 /usr/sbin/kamailio[7999]: DEBUG: <core> [core/select.c:412]: run_select(): Calling SELECT 0x7f19e3965f60\n", len = -464913696}, port = { s = 0x8 <error: Cannot access memory at address 0x8>, len = -467275366}, params = { s = 0x1 <error: Cannot access memory at address 0x1>, len = -468002654}, sip_params = { s = 0x3939393700000008 <error: Cannot access memory at address 0x3939393700000008>, len = 8187}, headers = {s = 0x0, len = 18987664}, port_no = 5336, proto = 125, type = ERROR_URI_T, flags = (unknown: 18988256), transport = { s = 0x2010 <error: Cannot access memory at address 0x2010>, len = -464906720}, ttl = { s = 0x121dcf0 "", len = -460542388}, user_param = { s = 0x2010 <error: Cannot access memory at address 0x2010>, len = -1472036457}, maddr = { s = 0x3 <error: Cannot access memory at address 0x3>, len = 5}, method = { s = 0x7f19e4ad7578 "\260A\256\344\031\177", len = -460539970}, lr = {s = 0x121bce0 "`\002", len = -1719564448}, r2 = {s = 0x7f19e40ffd28 "", len = -468690656}, gr = { s = 0x7ffc99818870 " Y\020\344\031\177", len = 44108294}, transport_val = { s = 0x7ffc99818860 "\377\377\377\377", len = 8180}, ttl_val = {s = 0x0, len = -458394160}, user_param_val = {s = 0x7f19e4ad7000 "", len = 4253282}, maddr_val = {s = 0x7f19e410cd78 "", len = 4209664}, method_val = { s = 0x500000000 <error: Cannot access memory at address 0x500000000>, len = 981}, lr_val = { s = 0x7f19e449f300 "\033\t&\344\031\177", len = -458394160}, r2_val = { s = 0x7ffc99818900 "@\212\201\231\374\177", len = -458341112}, gr_val = { s = 0x7ffc99818928 " Y\020\344\031\177", len = -458341968}} next_hop = {user = {s = 0x1 <error: Cannot access memory at address 0x1>, len = -460539539}, passwd = {s = 0x0, len = -458394160}, host = { s = 0x393300000005 <error: Cannot access memory at address 0x393300000005>, len = 0}, port = {s = 0x1 <error: Cannot access memory at address 0x1>, len = -458341968}, params = { s = 0x121bcf0 "<191>Jun 21 10:34:39 /usr/sbin/kamailio[7999]: DEBUG: <core> [core/select.c:412]: run_select(): Calling SELECT 0x7f19e3965f60\n", len = 0}, sip_params = { s = 0x121bcf0 "<191>Jun 21 10:34:39 /usr/sbin/kamailio[7999]: DEBUG: <core> [core/select.c:412]: run_select(): Calling SELECT 0x7f19e3965f60\n", len = -467267135}, headers = {s = 0x0, len = -458341112}, port_no = 34928, proto = 39297, type = 32764, flags = (unknown: 2575403104), transport = { s = 0xa8428197 <error: Cannot access memory at address 0xa8428197>, len = 4253282}, ttl = { s = 0xffffffff <error: Cannot access memory at address 0xffffffff>, len = -467275366}, user_param = {s = 0x7f19e4105920 "\203I", len = -458395648}, maddr = { s = 0x3939393700781a68 <error: Cannot access memory at address 0x3939393700781a68>, len = 8187}, method = {s = 0x0, len = 18987664}, lr = { s = 0x781d20 "%s: %s%s(): preparing to run routing scripts...\n", len = 18988256}, r2 = { s = 0x2010 <error: Cannot access memory at address 0x2010>, len = -464906720}, gr = { s = 0x121dcf0 "", len = 135}, transport_val = { s = 0x2010 <error: Cannot access memory at address 0x2010>, len = 10658448}, ttl_val = { s = 0x0, len = 7}, user_param_val = { s = 0xa3557a <buf+506> "13296 REGISTER\r\nMax-Forwards: 69\r\nUser-Agent: snom820/8.7.5.17\r\nContact: <sip:1016908e0@82.116.119.72:53401;line=hqwwdi0u>;reg-id=1;q=1.0;audio;mobility=\"fixed\";duplex=\"full\";description=\"snomD765\";ac"..., len = 4289936}, maddr_val = { s = 0x7ffc99818a40 "`\213\201\231\374\177", len = -460521481}, method_val = { s = 0x5 <error: Cannot access memory at address 0x5>, len = 0}, lr_val = { s = 0x100000000 <error: Cannot access memory at address 0x100000000>, len = -468690656}, r2_val = {s = 0x417590 <syslog@plt> "\377%\022.a", len = -1719563712}, gr_val = { s = 0x782f08 "DEBUG", len = -460495595}} u = 0x3000000010 port = 39297 dst_host = 0x121bce0 i = 13 flags = 2 avp = 0x7ffc99818b70 st = {flags = 3830051584, id = 32537, name = {n = -1719564353, s = {s = 0x7ffc998187bf "", len = 18421136}, re = 0x7ffc998187bf}, avp = 0x7ffc99818620} sct = 0x7f19e41aeb51 sjt = 0x2010 rve = 0x7ce8d0 mct = 0x1ff4 rv = 0x7ffc99818b50 rv1 = 0x7ffc99818ab0 c1 = {cache_type = 8208, val_type = 14643, c = {avp_val = {n = -464906720, s = { s = 0x7f19e44a1620 "", len = 18996464}, re = 0x7f19e44a1620}, pval = {rs = { s = 0x7f19e44a1620 "", len = 18996464}, ri = 150, flags = 0}}, i2s = "\020 \000\000\063\071\000\000\254u\027\344\031\177\000\000\020\207\201\231\374\177"} s = {s = 0x6 <error: Cannot access memory at address 0x6>, len = -467997871} srevp = {0x7ffc99818830, 0x7ffc99818600} mod_f_params = {{type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = { number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, { type = NOSUBTYPE, u = {number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = {number = 0, string = 0x0, str = { s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}, {type = NOSUBTYPE, u = { number = 0, string = 0x0, str = {s = 0x0, len = 0}, data = 0x0, attr = 0x0, select = 0x0}}} __FUNCTION__ = "do_action" #8 0x00000000004699fa in run_actions (h=0x7ffc99818a80, a=0x7f19e3965510, msg=0x7f19e3985dd0) at core/action.c:1552 t = 0x7f19e3966ec0 ret = 1 mod = 0xab00000003 ms = 0 __FUNCTION__ = "run_actions" #9 0x000000000046a1bd in run_top_route (a=0x7f19e3965510, msg=0x7f19e3985dd0, c=0x0) at core/action.c:1641 ctx = {rec_lev = 1, run_flags = 0, last_retcode = 1, jmp_env = {{__jmpbuf = {4289936, -8039283903424375778, 7876360, 7, 10704250, 4289936, -8039283903554399202, 8041047856258208798}, __mask_was_saved = 0, __saved_mask = {__val = {139749141390273, 4294967416, 20, 20, 18446744073709551615, 140722883889968, 139749141390764, 7876360, 0, 4611686022733059450, 139749169323472, 140722883890016, 5295428, 4302843656, 139749169323472, 4611686022733059450}}}}} p = 0x7ffc99818a80 ret = 0 sfbk = 0 #10 0x000000000057f2fc in receive_msg ( buf=0xa353f7 <buf+119> "REGISTER sip:sipgate.de SIP/2.0\r\nVia: SIP/2.0/UDP 217.116.120.247;branch=z9hG4bK0333.dae22993f9315bf8290cb153c6c2a81a.0\r\nVia: SIP/2.0/UDP 82.116.119.72:53401;received=82.116.119.72;branch=z9hG4bK-5hxr"..., len=1051, rcv_info=0x7ffc99818e80) at core/receive.c:264 msg = 0x7f19e3985dd0 ctx = {rec_lev = 248976, run_flags = 0, last_retcode = 568056, jmp_env = {{__jmpbuf = {568056, 8, 25, -8487096721362804224, 170079128784, 139749117125472, 139749169323120, 21482915456}, __mask_was_saved = 11, __saved_mask = {__val = {139749169100840, 7876360, 7, 140722883890512, 139749114876551, 139749114945152, 171331424705, 140722883890600, 98307693672, 11401280, 0, 8834747727873, 139745350909968, 7876360, 139749169100840, 7876360}}}}} bctx = 0x661d2b <qm_info+46> ret = 103 stats_on = 0 tvb = {tv_sec = 1498034079, tv_usec = 444700} tve = {tv_sec = 139749169323416, tv_usec = 139749168754704} tz = {tz_minuteswest = 0, tz_dsttime = 0} diff = 0 inb = { s = 0xa353f7 <buf+119> "REGISTER sip:sipgate.de SIP/2.0\r\nVia: SIP/2.0/UDP 217.116.120.247;branch=z9hG4bK0333.dae22993f9315bf8290cb153c6c2a81a.0\r\nVia: SIP/2.0/UDP 82.116.119.72:53401;received=82.116.119.72;branch=z9hG4bK-5hxr"..., len = 1051} netinfo = {data = {s = 0x7f19e3933440 "", len = 0}, dst = 0x800000 <yytable+6400>, rcv = 0x775508} keng = 0x0 __FUNCTION__ = "receive_msg" #11 0x00007f19e059ccdf in parsing_hepv3_message (buf=0xa35380 <buf> "HEP3\004\222", len=1170) at hep.c:499 from = {s = {sa_family = 2, sa_data = "\023\304\331tx\367\000\000\000\000\000\000\000"}, sin = { sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 4151866585}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 4151866585, sin6_addr = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}} to = {s = {sa_family = 2, sa_data = "\023\304\254\024\025\004\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 68490412}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 68490412, sin6_addr = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}} ri = {src_ip = {af = 2, len = 4, u = {addrl = {139749502776537, 1}, addr32 = {4151866585, 32537, 1, 0}, addr16 = {29913, 63352, 32537, 0, 1, 0, 0, 0}, addr = "\331tx\367\031\177\000\000\001\000\000\000\000\000\000"}}, dst_ip = {af = 2, len = 4, u = {addrl = {68490412, 139749187483088}, addr32 = {68490412, 0, 3836573136, 32537}, addr16 = {5292, 1045, 0, 0, 30160, 58541, 32537, 0}, addr = "\254\024\025\004\000\000\000\000\320u\255\344\031\177\000"}}, src_port = 5060, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 2, sa_data = "\023\304\331tx\367\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 4151866585}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 4151866585, sin6_addr = {__in6_u = { __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, bind_address = 0x7f19e3985c50, proto = 1 '\001'} tmp = 0xa353f1 <buf+113> "" dst_ip = {af = 2, len = 4, u = {addrl = {68490412, 140722883890976}, addr32 = {68490412, 0, 2575404832, 32764}, addr16 = {5292, 1045, 0, 0, 36640, 39297, 32764, 0}, addr = "\254\024\025\004\000\000\000\000 \217\201\231\374\177\000"}} src_ip = {af = 2, len = 4, u = {addrl = {139749502776537, 139749187481600}, addr32 = { 4151866585, 32537, 3836571648, 32537}, addr16 = {29913, 63352, 32537, 0, 28672, 58541, 32537, 0}, addr = "\331tx\367\031\177\000\000\000p\255\344\031\177\000"}} si = 0x7f19e3985c50 tmp_len = 4 i = 1170 payload = 0xa353f7 <buf+119> "REGISTER sip:sipgate.de SIP/2.0\r\nVia: SIP/2.0/UDP 217.116.120.247;branch=z9hG4bK0333.dae22993f9315bf8290cb153c6c2a81a.0\r\nVia: SIP/2.0/UDP 82.116.119.72:53401;received=82.116.119.72;branch=z9hG4bK-5hxr"... payload_len = 1051 chunk = 0xa353f1 <buf+113> hg = 0x7f19e3985b60 totelem = 11 chunk_vendor = 0 chunk_type = 15 chunk_length = 1057 total_length = 1170 __FUNCTION__ = "parsing_hepv3_message" #12 0x00007f19e059b264 in hepv3_received (buf=0xa35380 <buf> "HEP3\004\222", len=1170, ri=0x7ffc998190c0) at hep.c:231 __FUNCTION__ = "hepv3_received" #13 0x00007f19e05999cb in hep_msg_received (data=0x7ffc998190a0) at hep.c:85 srevp = 0x7ffc998190a0 buf = 0xa35380 <buf> "HEP3\004\222" len = 0x7ffc99819074 ri = 0x7ffc998190c0 __FUNCTION__ = "hep_msg_received" heph = 0xa35380 <buf> #14 0x000000000049e3e1 in sr_event_exec (type=7, data=0x7ffc998190a0) at core/events.c:263 ret = 0 i = 7 #15 0x000000000048721a in udp_rcv_loop () at core/udp_server.c:466 sredp = {0xa35380 <buf>, 0x7ffc99819074, 0x7ffc998190c0} len = 1170 buf = "HEP3\004\222\000\000\000\001\000\a\002\000\000\000\002\000\a\021\000\000\000\a\000\b\023\304\000\000\000\b\000\b\023\304\000\000\000\t\000\n\237/JY\000\000\000\n\000\n}\354\005\000\000\000\000\v\000\a\001\000\000\000\f\000\n\000\000\000\000\000\000\000\003\000\n\331tx\367\000\000\000\004\000\n\254\024\025\004\000\000\000\016\000\024buschMyHep2001\000\000\000\017\004!REGISTER sip:sipgate.de SIP/2.0\r\nVia: SIP/2.0/UDP 217.116.120.247;branch=z9hG4bK0"... tmp = 0x52f3ea <init_child+52> "\311\303UH\211\345AWAVAUATSH\203\354\070H\211}\270H\203}\270" from = 0x7f19e3968030 fromlen = 16 ri = {src_ip = {af = 2, len = 4, u = {addrl = {16777343, 139749169093632}, addr32 = {16777343, 0, 3818183680, 32537}, addr16 = {127, 256, 0, 0, 56320, 58260, 32537, 0}, addr = "\177\000\000\001\000\000\000\000\000\334\224\343\031\177\000"}}, dst_ip = { af = 2, len = 4, u = {addrl = {0, 0}, addr32 = {0, 0, 0, 0}, addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, addr = '\000' <repeats 15 times>}}, src_port = 42940, dst_port = 9060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 2, sa_data = "\247\274\177\000\000\001\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 48295, sin_addr = {s_addr = 16777343}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 48295, sin6_flowinfo = 16777343, sin6_addr = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, bind_address = 0x7f19e394da80, proto = 1 '\001'} __FUNCTION__ = "udp_rcv_loop" #16 0x0000000000422c08 in main_loop () at main.c:1625 i = 1 pid = 0 si = 0x7f19e394da80 si_desc = "udp receiver child=1 sock=0.0.0.0:9060\000\000\276\250s\000\000\000\000\000Z\261s\000\000\000\000\000\000\242\311\234\177\306\067\212\004\000\000\000\000\000\000\000\220uA\000\000\000\000\000\b/x\000\000\000\000\000\a\000\000\000\000\000\000\000\017", '\000' <repeats 15 times>, "\220\222\201\231\374\177\000\000i$_\000\000\000\000" nrprocs = 4 woneinit = 1 __FUNCTION__ = "main_loop" #17 0x000000000042a308 in main (argc=13, argv=0x7ffc99819568) at main.c:2646 cfg_stream = 0x118b010 c = -1 r = 0 tmp = 0x7ffc99819f00 "" tmp_len = -468663896 port = 32537 proto = -1719561184 options = 0x738938 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 2544599327 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x0 p = 0x1 <error: Cannot access memory at address 0x1> st = {st_dev = 15, st_ino = 11439, st_nlink = 2, st_mode = 16832, st_uid = 118, st_gid = 301, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = { tv_sec = 1495618022, tv_nsec = 508564058}, st_mtim = {tv_sec = 1498034038, tv_nsec = 560355778}, st_ctim = {tv_sec = 1498034038, tv_nsec = 560355778}, __glibc_reserved = {0, 0, 0}} __FUNCTION__ = "main" No symbol table info available. 1829 main.c: No such file or directory. ``` #### Log Messages This is what debug log says (trimmed down to the essential lines): ``` root@busch:/var/cores# systemctl restart kamailio_li_sniffer.service && kamcmd cfg.get config foo && tail -f /var/log/kamailio/proxy.log hello Daniel [..] Jun 21 10:34:39 busch /usr/sbin/kamailio[7998]: DEBUG: <core> [core/parser/msg_parser.c:600]: parse_msg(): SIP Request: Jun 21 10:34:39 busch /usr/sbin/kamailio[7998]: DEBUG: <core> [core/parser/msg_parser.c:602]: parse_msg(): method: <REGISTER> Jun 21 10:34:39 busch /usr/sbin/kamailio[7998]: DEBUG: <core> [core/parser/msg_parser.c:604]: parse_msg(): uri: <sip:sipgate.de> Jun 21 10:34:39 busch /usr/sbin/kamailio[7998]: DEBUG: <core> [core/parser/msg_parser.c:606]: parse_msg(): version: <SIP/2.0> [..] Jun 21 10:34:39 busch /usr/sbin/kamailio[7999]: DEBUG: <core> [core/receive.c:234]: receive_msg(): preparing to run routing scripts... Jun 21 10:34:39 busch /usr/sbin/kamailio[8001]: INFO: <script>: Reading config.foo into variable Jun 21 10:34:39 busch /usr/sbin/kamailio[8000]: INFO: <script>: Reading config.foo into variable Jun 21 10:34:39 busch /usr/sbin/kamailio[7999]: INFO: <script>: Reading config.foo into variable Jun 21 10:34:39 busch /usr/sbin/kamailio[8001]: DEBUG: <core> [core/select.c:412]: run_select(): Calling SELECT 0x7f19e3965f60 Jun 21 10:34:39 busch /usr/sbin/kamailio[7999]: DEBUG: <core> [core/select.c:412]: run_select(): Calling SELECT 0x7f19e3965f60 Jun 21 10:34:39 busch /usr/sbin/kamailio[8000]: DEBUG: <core> [core/select.c:412]: run_select(): Calling SELECT 0x7f19e3965f60 Jun 21 10:34:39 busch /usr/sbin/kamailio[8010]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 11 Jun 21 10:34:39 busch /usr/sbin/kamailio[8010]: DEBUG: <core> [core/tcp_main.c:3456]: handle_ser_child(): dead child 1, pid 7998 (shutting down?) Jun 21 10:34:39 busch /usr/sbin/kamailio[8010]: DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa4c100, 11, -1, 0x0) fd_no=18 called Jun 21 10:34:39 busch /usr/sbin/kamailio[8010]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 14 Jun 21 10:34:39 busch /usr/sbin/kamailio[8010]: DEBUG: <core> [core/tcp_main.c:3456]: handle_ser_child(): dead child 4, pid 8001 (shutting down?) Jun 21 10:34:39 busch /usr/sbin/kamailio[8010]: DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa4c100, 14, -1, 0x0) fd_no=17 called Jun 21 10:34:39 busch /usr/sbin/kamailio[7996]: ALERT: <core> [main.c:743]: handle_sigs(): child process 7998 exited by a signal 11 Jun 21 10:34:39 busch /usr/sbin/kamailio[7996]: ALERT: <core> [main.c:746]: handle_sigs(): core was generated Jun 21 10:34:39 busch /usr/sbin/kamailio[7996]: INFO: <core> [main.c:768]: handle_sigs(): terminating due to SIGCHLD Jun 21 10:34:39 busch /usr/sbin/kamailio[7996]: DEBUG: <core> [main.c:770]: handle_sigs(): terminating due to SIGCHLD Jun 21 10:34:39 busch /usr/sbin/kamailio[8010]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Jun 21 10:34:39 busch /usr/sbin/kamailio[8009]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Jun 21 10:34:39 busch /usr/sbin/kamailio[8008]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Jun 21 10:34:39 busch /usr/sbin/kamailio[8007]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Jun 21 10:34:39 busch /usr/sbin/kamailio[8006]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Jun 21 10:34:39 busch /usr/sbin/kamailio[8005]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Jun 21 10:34:39 busch /usr/sbin/kamailio[8002]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Jun 21 10:34:39 busch /usr/sbin/kamailio[8003]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Jun 21 10:34:39 busch /usr/sbin/kamailio[8004]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received [..] ``` #### SIP Traffic The SIP traffic doesn't matter. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.0.2 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, 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: unknown compiled with gcc 4.9.2 ``` * **Operating System**: ``` Debian Jessie Linux busch.dev.sipgate.net 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u1 (2017-02-22) x86_64 GNU/Linux ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1159

5 years, 4 months

[kamailio/kamailio] tr_lookup(): error parsing [{param.count, , }] (#1041)

by Sergey Lavrov

Kamailio can't parse construction like $(hdr(History-Info)[*]{param.count,,}) where delimiter is comma. I tried to use delimiter as , / ',' / "," wuthout success. ERROR: pv [pv_trans.c:2631]: tr_parse_paramlist(): invalid separator in transformation: count,,} ERROR: <core> [pvapi.c:1629]: tr_lookup(): error parsing [{param.count,,}] ERROR: <core> [pvapi.c:1010]: pv_parse_spec2(): bad tr in pvar name "hdr" ERROR: <core> [pvapi.c:1036]: pv_parse_spec2(): invalid parsing in [$(hdr(History-Info)[*]{param.count,,})] at (4) ERROR: pv [pv_trans.c:2639]: tr_parse_paramlist(): invalid name transformation: count,','}! ERROR: <core> [pvapi.c:1629]: tr_lookup(): error parsing [{param.count,','}] ERROR: <core> [pvapi.c:1010]: pv_parse_spec2(): bad tr in pvar name "hdr" ERROR: <core> [pvapi.c:1036]: pv_parse_spec2(): invalid parsing in [$(hdr(History-Info)[*]{param.count,','})] at (4) ERROR: bad config file (1 errors) ERROR: pv [pv_trans.c:2639]: tr_parse_paramlist(): invalid name transformation: count,","}! ERROR: <core> [pvapi.c:1629]: tr_lookup(): error parsing [{param.count,","}] ERROR: <core> [pvapi.c:1010]: pv_parse_spec2(): bad tr in pvar name "hdr" ERROR: <core> [pvapi.c:1036]: pv_parse_spec2(): invalid parsing in [$(hdr(History-Info)[*]{param.count,","})] at (4) kamailio -v version: kamailio 4.4.5 (x86_64/linux) f98162 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, 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: f98162 compiled on 03:47:31 Feb 27 2017 with gcc 4.8.5 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1041

5 years, 4 months

[kamailio/kamailio] erlang: build fails on alpha (#1373)

by Victor Seva

>From 5.1.0 official Debian build ``` /usr/bin/make every-module group_include="kerlang" quiet=verbose make[1]: Entering directory '/<<PKGBUILDDIR>>' /usr/bin/make -C src/ every-module make[2]: Entering directory '/<<PKGBUILDDIR>>/src' config.mak loaded Makefile.defs defs skipped Makefile.defs defs skipped Makefile.defs defs skipped beam.smp: allocatestack.c:480: allocate_stack: Assertion `size != 0' failed. Aborted beam.smp: allocatestack.c:480: allocate_stack: Assertion `size != 0' failed. Aborted Makefile:16: *** Not found Erlang. Stop. ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1373

5 years, 5 months

error in Makefile.modules

by Juha Heinanen

When building debian package from master, I noticed this kind of error message: s ../../../doc/stylesheets/serdoc2man.xsl auth.xml make[3]: s: Command not found ../../Makefile.modules:283: recipe for target 'auth.7' failed The line in Makefile.modules is here: $(MOD_NAME).7: $(MOD_NAME).xml $(DOCBOOK) -s ../../../doc/stylesheets/serdoc2man.xsl $< Could it be that variable $(DOCBOOK) has not been defined? -- Juha

5 years, 5 months

[kamailio/kamailio] Crash on receiving incorrect REGISTER request? (#1420)

by kbdfck

### Description Periodically Kamailio crashes, log shows that it happens on REGISTER request with incorrect params. I don't know if it is a network problem or somebody sends incorrect request, but there are records in logs: #### Log Messages Jan 30 03:49:29 kam /usr/sbin/kamailio[20718]: ERROR: <core> [core/parser/parse_from.c:53]: parse_from_header(): bad msg or missing FROM header Jan 30 03:49:29 kam /usr/sbin/kamailio[20718]: ERROR: dialog [dlg_cseq.c:93]: dlg_cseq_prepare_msg(): cannot parse FROM header Jan 30 03:49:29 kam /usr/sbin/kamailio[20718]: ERROR: pv [pv_core.c:664]: pv_get_callid(): cannot parse Call-Id header Jan 30 03:49:29 kam /usr/sbin/kamailio[20718]: {1 <null> <null>} ERROR: <core> [core/parser/parse_from.c:53]: parse_from_header(): bad msg or missing FROM header Jan 30 03:49:29 kam /usr/sbin/kamailio[20718]: {1 <null> <null>} ERROR: pv [pv_core.c:468]: pv_get_from_attr(): cannot parse From header Jan 30 03:49:29 kam /usr/sbin/kamailio[20718]: {1 <null> <null>} ERROR: pv [pv_core.c:664]: pv_get_callid(): cannot parse Call-Id header Jan 30 03:49:29 kam /usr/sbin/kamailio[20718]: {1 <null> <null>} NOTICE: <script>: REQ: M='REGISTER sip:1.2.3.208:5060' F='<null>' T='<null>' CI='<null>' SRC='113.128.105.127:49556' AU='<null>' Jan 30 03:49:29 kam /usr/sbin/kamailio[20736]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 15 Jan 30 03:49:29 kam /usr/sbin/kamailio[20713]: ALERT: <core> [main.c:746]: handle_sigs(): child process 20718 exited by a signal 11 Jan 30 03:49:29 kam /usr/sbin/kamailio[20713]: ALERT: <core> [main.c:749]: handle_sigs(): core was not generated Jan 30 03:49:29 kam /usr/sbin/kamailio[20713]: INFO: <core> [main.c:771]: handle_sigs(): terminating due to SIGCHLD ### Additional Information version: kamailio 5.2.0-dev2 (i386/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, 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: unknown compiled with gcc 4.9.2 * **Operating System**: Linux kam 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1420

5 years, 6 months

[kamailio/kamailio] cfg_rpc updates changing variable values to large random numbers (#1583)

by vinesinha

I was trying to do a cfg_rpc update on a variable and some of the times, the variable would take on randomly large values or negative values. The -1 here is probably causing issues. https://github.com/kamailio/kamailio/blob/1d53ea3dba4e59b05b2e92ecc973c4415… Here's an explanation of what's going on (debugged using gdb). In cfg_struc.c if you put a breakpoint in the following line in cfg_clone_global https://github.com/kamailio/kamailio/blob/1d53ea3dba4e59b05b2e92ecc973c4415… checking variable values: ``` --- Old (correct) value --- (gdb) print sizeof(*(int *)(((unsigned char *)((*cfg_global)->vars + 984)) + 172)) $33 = 4 (gdb) print *((unsigned char *)&(*(int *)(((unsigned char *)((*cfg_global)->vars + 984)) + 172)) + 0) $34 = 99 'c' (gdb) print *((unsigned char *)&(*(int *)(((unsigned char *)((*cfg_global)->vars + 984)) + 172)) + 1) $35 = 0 '\000' (gdb) print *((unsigned char *)&(*(int *)(((unsigned char *)((*cfg_global)->vars + 984)) + 172)) + 2) $36 = 0 '\000' (gdb) print *((unsigned char *)&(*(int *)(((unsigned char *)((*cfg_global)->vars + 984)) + 172)) + 3) $37 = 0 '\000' --- new (corrupt) value --- (gdb) print sizeof(*(int *)(((unsigned char *)((block)->vars + 984)) + 172)) $28 = 4 (gdb) print *((unsigned char *)&(*(int *)(((unsigned char *)((block)->vars + 984)) + 172)) + 0) $29 = 99 'c' (gdb) print *((unsigned char *)&(*(int *)(((unsigned char *)((block)->vars + 984)) + 172)) + 1) $30 = 0 '\000' (gdb) print *((unsigned char *)&(*(int *)(((unsigned char *)((block)->vars + 984)) + 172)) + 2) $31 = 0 '\000' (gdb) print *((unsigned char *)&(*(int *)(((unsigned char *)((block)->vars + 984)) + 172)) + 3) $32 = 130 '\202' ``` As visible, the last byte is getting corrupted. I checked the memory allocation variables: ``` --> cfg_block_size (gdb) print cfg_block_size $2 = 1156 --> sizeof(cfg_block_t) print sizeof(cfg_block_t) $15 = 8 ``` This means that total memory assigned = 8 + 1156 -(1) = 1163 ``` --> address of new block (gdb) print (void *) block $12 = (void *) 0x7f63086b6758 --> address of the corrupted variable in the new block (gdb) print (void *)(((unsigned char *)((block)->vars + 984)) + 172) $13 = (void *) 0x7f63086b6be0 --> offset of the variable from the block start (gdb) print 0x7f63086b6be0 - 0x7f63086b6758 $14 = 1160 ``` since the variable is an integer, memory that should be assigned = 1160 + 4 = 1164 However, we're assigning 1163. Therefore the last byte is getting corrupted. Does it make sense to remove the -1 from all the memory allocation in cfg_struct ? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1583

5 years, 6 months

[kamailio/kamailio] MemoryUtilization getting increase with lua routing (#1577)

by Surendra Tiwari

### Description  We are using lua base routing with app_lua. We are seeing that our memory-utilization on that system continuously getting increase. our route.lua will have all routing logic same as https://github.com/kamailio/kamailio/blob/master/misc/examples/kemi/kamaili… we are using following set of modules loadmodule "tm.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "maxfwd.so" loadmodule "nathelper.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "path.so" loadmodule "jsonrpcs.so" loadmodule "app_lua.so" loadmodule "dispatcher.so" loadmodule "json.so" loadmodule "cfg_rpc.so" loadmodule "ctl.so" loadmodule "ipops.so" loadmodule "http_async_client.so" loadmodule "dialog.so" # ----------------- setting module-specific parameters --------------- # ----- rr params ----- # set next param to 1 to add value to ;lr param (helps with some UAs) modparam("rr", "enable_full_lr", 0) # do not append from tag to the RR (no need for this script) modparam("rr", "append_fromtag", 1) # ----- dispatcher params ----- modparam("dispatcher", "list_file", DISPATCHER_FILE) modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "flags", 2) modparam("dispatcher", "ds_ping_interval", 10) modparam("dispatcher", "ds_ping_from", "sip:ping@test.com") # ----- nathelper params ---- modparam("nathelper", "received_avp", "$avp(s:rcv)") # ----- http_async_client ------- # ---- number of worker process for async req and res modparam("http_async_client", "workers", 4) # ----- ctl ------ modparam("ctl", "binrpc", "tcp:MY_IP_ADDR:2086") # ----- app_lua params ---- modparam("app_lua", "reload", 1) modparam("app_lua", "load", ROUTE_LUA) # ---- dialog params ---- modparam("dialog", "enable_stats", 1) modparam("dialog", "dlg_flag", 4) modparam("dialog", "event_callback", "ksr_dialog_event") cfgengine "lua" ### Troubleshooting #### Reproduction We can easily reproduce by loading app_lua with kamailio-basic-kemi-lua.lua https://github.com/kamailio/kamailio/blob/master/misc/examples/kemi/kamaili…  #### Debugging Data root@ip-172-31-4-160:~# kamcmd -s tcp:172.31.4.160:2046 tm.stats { current: 2220 waiting: 2198 total: 6113169 total_local: 1371 rpl_received: 11958486 rpl_generated: 6111711 rpl_sent: 12224635 6xx: 0 5xx: 6104789 4xx: 6831 3xx: 0 2xx: 1483 created: 6113169 freed: 6110949 delayed_free: 0 } transaction are getting free as they are created so no transaction memory leak.  ``` U 54.183.198.87:5060 -> 172.31.4.160:5060 INVITE sip:919980950111@13.57.122.212:5060 SIP/2.0. Record-Route: <sip:54.183.198.87;lr;ftag=2186327>. Via: SIP/2.0/UDP 54.183.198.87:5060;branch=z9hG4bK62f3.22dfb9a43503cc12dafdcdbc9ab1e17d.0. Via: SIP/2.0/UDP 172.31.13.202:5060;rport=5060;received=13.232.78.75;branch=z9hG4bK-20254-2186327-0. From: <sip:919980950111@21979254854757081.zt.plivo.com>;tag=2186327. To: <sip:919980950111@21979254854757081.zt.plivo.com>. Call-ID: 2186327-20254(a)172.31.13.202. CSeq: 1 INVITE. Contact: <sip:sipp@13.126.252.148:5060;transport=UDP;alias=13.232.78.75~5060~1>. Max-Forwards: 69. User-Agent: Sipp/Linux. Supported: replaces, outbound. Content-Type: application/sdp. Content-Length: 139. X-ZT-Cust-IP: 13.232.78.75. X-ZT-Trunk: 21979254854757081.zt.plivo.com. . v=0. o=user1 53655765 2353687637 IN IP4 13.126.252.148. s=-. c=IN IP4 13.126.252.148. t=0 0. m=audio 6000 RTP/AVP 0. a=rtpmap:0 PCMU/8000. # U 172.31.4.160:5060 -> 54.183.198.87:5060 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 54.183.198.87:5060;branch=z9hG4bK62f3.22dfb9a43503cc12dafdcdbc9ab1e17d.0;rport=5060. Via: SIP/2.0/UDP 172.31.13.202:5060;rport=5060;received=13.232.78.75;branch=z9hG4bK-20254-2186327-0. From: <sip:919980950111@21979254854757081.zt.plivo.com>;tag=2186327. To: <sip:919980950111@21979254854757081.zt.plivo.com>. Call-ID: 2186327-20254(a)172.31.13.202. CSeq: 1 INVITE. Server: kamailio (5.1.3 (x86_64/linux)). Content-Length: 0. . # U 172.31.4.160:5060 -> 54.183.198.87:5060 SIP/2.0 408 Request Timeout. Via: SIP/2.0/UDP 54.183.198.87:5060;branch=z9hG4bK223b.cd9c3cb1d2dc6adc346e6fb7acdee708.0;rport=5060. Via: SIP/2.0/UDP 172.31.13.202:5060;rport=5060;received=13.232.78.75;branch=z9hG4bK-20254-2185727-0. From: <sip:919980950111@21979254854757081.zt.plivo.com>;tag=2185727. To: <sip:919980950111@21979254854757081.zt.plivo.com>;tag=c99e9820d9036d36e5541ff825b95248-8c22. Call-ID: 2185727-20254(a)172.31.13.202. CSeq: 1 INVITE. Server: kamailio (5.1.3 (x86_64/linux)). Content-Length: 0. . ``` #### Log Messages  ``` Jun 29 19:18:14 ip-172-31-4-160 kamailio[8119]: ERROR: <core> [core/mem/q_malloc.c:287]: qm_find_free(): qm_find_free(0x7fe974b24000, 35992); Free fragment not found! Jun 29 19:18:14 ip-172-31-4-160 kamailio[8119]: ERROR: <core> [core/mem/q_malloc.c:421]: qm_malloc(): qm_malloc(0x7fe974b24000, 35992) called from http_async_client: http_multi.c: curl_shm_calloc(346), module: http_async_client; Free fragment not found! Jun 29 19:18:14 ip-172-31-4-160 kamailio[8119]: ERROR: http_async_client [http_multi.c:437]: new_request(): curl_easy_init() failed! ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (paste your output here) ``` * **Operating System**:  ``` root@ip-172-31-4-160:/etc/kamailio# uname -a Linux ip-172-31-4-160 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27 10:45:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1577

5 years, 6 months

[kamailio/kamailio] pkg/kamailio: Fix of ticket 1085 (#1086)

by sergey-safarov

You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1086 -- Commit Summary -- * pkg/kamailio: Fix of ticket 1085 -- File Changes -- M pkg/kamailio/centos/7/kamailio.service (2) M pkg/kamailio/deb/debian/kamailio.service (2) M pkg/kamailio/deb/jessie/kamailio.service (2) M pkg/kamailio/deb/sid/kamailio.service (2) M pkg/kamailio/deb/stretch/kamailio.service (2) M pkg/kamailio/deb/xenial/kamailio.service (2) M pkg/kamailio/fedora/17/kamailio.service (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1086.patch https://github.com/kamailio/kamailio/pull/1086.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/1086

5 years, 6 months

[kamailio] recover htable replication through dmq after kamailio restart (#260)

by José Seabra

(Feature request) be able to recover data from htable variable when kamailio starts, from another kamailio instances through dmq module. --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/260

5 years, 6 months

← Newer
1
2
3
4
5
6
7
8
9
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev August 2018