sr-dev March 2019

sr-dev@lists.kamailio.org

28 participants
323 discussions

[kamailio/kamailio] Siptrace (#1912)
by Ionut Ionita 09 Apr '19

09 Apr '19

#### Pre-Submission Checklist    - [ ] Commit message has the format required by CONTRIBUTING guide - [ ] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] Each component has a single commit (if not, squash them into one commit) - [ ] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [ ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  Siptrace module has two different tracing concepts which do mostly the same thing. It has sip_trace function and it has trace_flag parameter which traces messages in a transaction. This pull request aims to have a single point of trace activation, that is when the user calls sip_trace() function from the script. Moreover, it adds 3 levels of tracing: message, transaction and dialog level tracing. This option is added as a parameter to sip_trace(), therefore the user can now summon sip_trace(duri, correlation_id, "m/t/d") where "m" stands for message, "t" for transaction and "d" for dialog. The patch has been tested both locally and in our company's test system. Locally I've tested it using a few scenarios generated using sipp: successful call, negative reply(491 answer - hop-by-hop ACK), UAC CANCEL and dual bye scenario generated by Kamailio(dialog timeout). The only issue with current patch is it doesn't trace internally generated BYEs that is because they are only a buffer in Kamailio, not a parsed SIP message, therefore, after a few days of searching for solutions I didn't find any valid one. Parsing a SIP message for tracing didn't seem worth the processing time to me, but of course it can be added in the future. Looking forward to your opinion or suggestions regarding the current patch. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1912 -- Commit Summary -- * siptrace: add basic transaction and dialog level tracing * siptrace: trace negative ACKs * siptrace: check if a request is set to avoid local transaction crash * siptrace: Add code to trace incoming CANCEL transcations * siptrace: Minor code fixes; remove useless error logs * siptrace: store sip_trace destination parameter for the entire dialog * siptrace: remove unused trace flag * siptrace: update README -- File Changes -- M src/core/parser/msg_parser.h (1) M src/modules/siptrace/README (562) M src/modules/siptrace/doc/siptrace_admin.xml (33) M src/modules/siptrace/siptrace.c (864) M src/modules/siptrace/siptrace_data.h (14) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1912.patch https://github.com/kamailio/kamailio/pull/1912.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/1912

6 28

[kamailio/kamailio] crash in slow timer (#1897)
by lazedo 08 Apr '19

08 Apr '19

### Description slow_timer proc exited with crash, kamailio kept running but tm transaction kept accumulating which will lead to shared memory exhaustion and crash. in line 1131 `ret=tl->f(*ticks, tl, tl->data);` f is null, reason of crash  ### Troubleshooting #### Reproduction happens from time to time, not a way to reliably reproduce it.  #### Debugging Data  ``` #0 0x0000000000000000 in ?? () #1 0x000000000049f648 in slow_timer_main () at core/timer.c:1131 #2 0x0000000000424b84 in main_loop () at main.c:1685 #3 0x000000000042b9d3 in main (argc=16, argv=0x7ffe568bcd08) at main.c:2663 (gdb) frame 1 #1 0x000000000049f648 in slow_timer_main () at core/timer.c:1131 1131 ret=tl->f(*ticks, tl, tl->data); (gdb) list 1126 #ifdef TIMER_DEBUG 1127 tl->expires_no++; 1128 #endif 1129 SET_RUNNING_SLOW(tl); 1130 UNLOCK_SLOW_TIMER_LIST(); 1131 ret=tl->f(*ticks, tl, tl->data); 1132 /* reset the configuration group handles */ 1133 cfg_reset_all(); 1134 if (ret==0){ 1135 /* one shot */ (gdb) p *tl $1 = {next = 0x0, prev = 0x0, expire = 938928580, initial_timeout = 80, data = 0x0, f = 0x0, flags = 768, slow_idx = 45488} (gdb) info locals n = 12 ret = 4294967295 tl = 0x7fb2d3c860d0 i = 432 __func__ = "slow_timer_main" ``` #### Log Messages  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` 5.1.7 ``` * **Operating System**:  ``` centos 7 ``` -- 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/1897

2 4

[kamailio/kamailio] kamailio crashes when attempting to query offline database (#1821)
by srinikart 05 Apr '19

05 Apr '19

### Description I am testing how kamailio reacts to various database conditions. One such condition is if the database engine is simply shut down (that is, database server process no longer running, tcp listening socket closed, etc...) I am utilizing the db_unixodbc module to connect to an Informix database engine. I am currently running on Kamailio version 5.0.1. I have a test query that executes against the database engine every 10 seconds. Here is what i have noticed if i shut down the database engine at some point after i run Kamailio. The first test query that attempts to run against the db engine fails; it tries to reconnect and fails. The second test query (10 seconds after the 1st) results in a SIGCHILD and shuts down the entire Kamailio process. I communicated this info to the mailing list and was asked to open an issue regarding this and to also test the more recent version 5 releases. Here is the update on said tests: I have tested the master branch and 5.3.0-dev2 and neither branch resolves the issue. However I did notice in the master branch that there is new code that is related to this issue. https://github.com/kamailio/kamailio/issues/1681 In issue 1681 there is code that allows Kamailio to start even if a database connection can not be established. Queries attempting to run against the offline database fail gracefully. And once the database is back online, a connection is established and queries against it are successful. However, if at some later point I shut down the database, we're back to the original issue that i reported. Kamailio crashes with the same output as listed before except the first query that is attempted against the offline db causes the crash in this master branch unlike previously (branch 5.series) the first attempt fails, tries again and fails, and the second attempt causes the crash. Regardless, the output is more or less the same and Kamailio is down. I suspect this might be the same behavior even if one is not using an odbc driver; but maybe not. ### Troubleshooting #### Reproduction Start Kamailio; kill the database engine; run test query from kamailo to said database engine; Kamailio crashes. This can be replicated using the db_unixodbc module; not sure if it's the same for other types of database drivers. #### Log Messages Jan 17 20:07:25 [29297]: INFO: (s) SQL query: FIRST TEST QUERY Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:135]: db_unixodbc_submit_query(): rv=-1. Query= FIRST TEST QUERY Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLExecDirect=08S01:1:-11020:[Informix][Informix ODBC Driver]Communication link failure. Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:59]: reconnect(): Attempting DB reconnect Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:74]: reconnect(): failed to connect Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLDriverConnect=08002:1:0:[unixODBC][Driver Manager]Connection name in use Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLDriverConnect=HY010:2:-11067:[Informix][Informix ODBC Driver]Function sequence error. Jan 17 20:07:25 [29297]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jan 17 20:07:25 [29297]: ERROR: sqlops [sql_api.c:265]: sql_do_query(): cannot do the query FIRST TEST QUERY Jan 17 20:07:25 [29297]: INFO: (s) [123] SQL ret: fail (-1) Jan 17 20:07:25 [29297]: INFO: (s) [123] SQL res: no rows Jan 17 20:07:35 [29297]: INFO: (s) [123] SQL query: 10 seconds later the SECOND TEST QUERY (it's the same query as the first one) Jan 17 20:07:35 [29301]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 28 Jan 17 20:07:35 [29283]: ALERT: <core> [main.c:744]: handle_sigs(): child process 29297 exited by a signal 11 Jan 17 20:07:35 [29283]: ALERT: <core> [main.c:747]: handle_sigs(): core was not generated Jan 17 20:07:35 [29283]: INFO: <core> [main.c:759]: handle_sigs(): terminating due to SIGCHLD Jan 17 20:07:35 [29301]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29295]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29291]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29288]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29300]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29284]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29286]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29293]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29289]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29287]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29292]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29296]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29298]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29299]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29285]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29294]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29290]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29283]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ### Additional Information version: kamailio 5.0.1 (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 on 11:25:09 May 2 2018 with gcc 4.1.2 version: kamailio 5.3.0-dev2 (x86_64/linux) 30857d-dirty flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 30857d -dirty compiled on 14:30:54 Jan 22 2019 with gcc 4.1.2 * **Operating System**: Red Hat Enterprise Linux Server release 5.11 (Tikanga) Linux 2.6.18-404.el5 #1 SMP Sat Mar 7 04:14:13 EST 2015 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/1821

3 16

[kamailio/kamailio] cannot build rpm on OpenSUSE (#1915)
by sergey-safarov 04 Apr '19

04 Apr '19

### Description Cannot build postgres module on openSUSE Tumbleweed ### Troubleshooting #### Reproduction Package kamailio on openSUSE Tumbleweed. #### Debugging Data N/A #### Log Messages ``` [ 434s] xsubpp -typemap `perl -MConfig -e 'print $Config{installprivlib}'`/ExtUtils/typemap -typemap typemap kamailioxs.xs > kamailioxs.c [ 434s] CC (gcc) [M app_perl.so] kamailioxs.o [ 435s] LD (gcc) [M app_perl.so] app_perl.so [ 436s] CC (gcc) [M db_perlvdb.so] perlvdbfunc.o [ 437s] CC (gcc) [M db_perlvdb.so] perlvdb_oohelpers.o [ 437s] CC (gcc) [M db_perlvdb.so] perlvdb_conv.o [ 438s] CC (gcc) [M db_perlvdb.so] db_perlvdb.o [ 439s] make[3]: 'libsrdb1.so.1.0' is up to date. [ 439s] LD (gcc) [M db_perlvdb.so] db_perlvdb.so [ 439s] which: no pg_config in (/usr/local/bin:/usr/bin:/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin) [ 439s] which: no pg_config in (/usr/local/bin:/usr/bin:/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin) [ 439s] CC (gcc) [M db_postgres.so] pg_uri.o [ 439s] CC (gcc) [M db_postgres.so] pg_sql.o [ 439s] CC (gcc) [M db_postgres.so] pg_res.o [ 439s] In file included from pg_res.c:33: [ 439s] pg_res.h:40:10: fatal error: libpq-fe.h: No such file or directory [ 439s] #include <libpq-fe.h> [ 439s] ^~~~~~~~~~~~ [ 439s] compilation terminated. [ 439s] make[2]: *** [../../Makefile.rules:100: pg_res.o] Error 1 [ 439s] make[1]: *** [Makefile:511: modules] Error 1 [ 439s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/kamailio-5.3.0-dev4/src' [ 439s] make: *** [Makefile:30: every-module] Error 2 [ 439s] error: Bad exit status from /var/tmp/rpm-tmp.dwfwP1 (%build) [ 439s] [ 439s] [ 439s] RPM build errors: [ 439s] bogus date in %changelog: Tue Feb 21 2019 Sergey Safarov <s.safarov(a)gmail.com> 5.3.0-0 [ 439s] Bad exit status from /var/tmp/rpm-tmp.dwfwP1 (%build) [ 439s] [ 439s] build80 failed "build kamailio.spec" at Sat Mar 30 09:44:29 UTC 2019. [ 439s] ``` #### SIP Traffic N/A ### Possible Solutions Add ability to use pkgconfig file from Makefile ``` d90393c7d32a:/ # cat /usr/lib64/pkgconfig/libpq.pc Name: libpq Description: PostgreSQL libpq library Url: http://www.postgresql.org/ Version: 11.2 Requires: Requires.private: Cflags: -I/usr/include/pgsql Libs: -lpq Libs.private: -lssl -lcrypto -lgssapi_krb5 -lcrypt -lldap_r ``` ### Additional Information Current master * **Operating System**: ``` d90393c7d32a:/ # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20190327" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20190327" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20190327" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" ``` -- 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/1915

2 10

[kamailio/kamailio] dialog: segfault with db_mode = 1 and broken SIP message (#1899)
by Bastian Triller 04 Apr '19

04 Apr '19

### Description `dialog` module is configured with `db_mode` 1 (realtime). When receiving following broken SIP `200` response (missing 6 bytes between header and body), Kamailio crashes: ``` SIP/2.0 200 OK Via: SIP/2.0/UDP 1.2.3.4;branch=z9hG4bKa185.ad1e5804a90a4f79fa2b09b3b2118053.0 Via: SIP/2.0/UDP 2.3.4.5:7016;received=2.3.4.5;branch=z9hG4bK370933d4;rport=7016 Record-Route: <sip:1.2.3.4;lr=on;did=c41.dee> From: "1234" <sip:1234@example.com>;tag=as4cbf81fd To: <sip:2345@example.com>;tag=3450065082 Call-ID: 727ca44f1e962eb321143475380dfbd9(a)example.com CSeq: 102 INVITE Contact: <sip:2345@3.4.5.6:12500> Content-Type: application/sdp Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE Content-Length: 2170 o=- 20568 20568 IN IP4 3.4.5.6 s=SDP data c=IN IP4 3.4.5.6 t=0 0 m=audio 13002 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=ptime:20 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv ``` Crash happens in [dlg_db_handler.c](https://github.com/kamailio/kamailio/blob/master/src/modu… ``` LM_DBG("sock_info is %.*s\n", cell->bind_addr[DLG_CALLER_LEG]->sock_str.len, cell->bind_addr[DLG_CALLEE_LEG]->sock_str.s); SET_STR_VALUE(values+7, cell->bind_addr[DLG_CALLER_LEG]->sock_str); SET_STR_VALUE(values+8, cell->bind_addr[DLG_CALLEE_LEG]->sock_str); ``` #### Debugging Data ``` Thread 1 (Thread 0x7fc64b620700 (LWP 2333)): +bt #0 0x00007fc641675b63 in update_dialog_dbinfo_unsafe (cell=0x7fc619a71ff8) at dlg_db_handler.c:784 #1 0x00007fc641676852 in update_dialog_dbinfo (cell=0x7fc619a71ff8) at dlg_db_handler.c:881 #2 0x00007fc64167c861 in dlg_onreply (t=0x7fc61d7888f0, type=1048576, param=0x7ffe1ce712f0) at dlg_handlers.c:509 #3 0x00007fc6443f4f17 in run_trans_callbacks_internal (cb_lst=0x7fc61d788960, type=1048576, trans=0x7fc61d7888f0, params=0x7ffe1ce712f0) at t_hooks.c:260 #4 0x00007fc6443f5144 in run_trans_callbacks_with_buf (type=1048576, rbuf=0x7fc61d7889b0, req=0x7fc61ec43928, repl=0x7fc646dcbd80, flags=0) at t_hooks.c:305 #5 0x00007fc6443aaabc in relay_reply (t=0x7fc61d7888f0, p_msg=0x7fc646dcbd80, branch=0, msg_status=200, cancel_data=0x7ffe1ce71580, do_put_on_wait=1) at t_reply.c:1950 #6 0x00007fc6443ae844 in reply_received (p_msg=0x7fc646dcbd80) at t_reply.c:2521 #7 0x000055fd54405df6 in do_forward_reply (msg=0x7fc646dcbd80, mode=0) at core/forward.c:749 #8 0x000055fd5440784b in forward_reply (msg=0x7fc646dcbd80) at core/forward.c:851 #9 0x000055fd544522d2 in receive_msg (buf=0x55fd5492d080 <buf> "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP ...", len=960, rcv_info=0x7ffe1ce71ad0) at core/receive.c:341 #10 0x000055fd5436e207 in udp_rcv_loop () at core/udp_server.c:515 #11 0x000055fd542dc608 in main_loop () at main.c:1623 #12 0x000055fd542e46a9 in main (argc=13, argv=0x7ffe1ce71f78) at main.c:2642 ``` ### Possible Solutions Check `bind_addr` before accessing. ### Additional Information Version was 5.0.x, but at least code in `dlg_handler.c` wasn't modified in `master` since then. -- 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/1899

2 4

[kamailio/kamailio] kamailio 5.0.6 segfault in pike module (#1822)
by lschweizer 01 Apr '19

01 Apr '19

### Description Hello, I get a segfault with kamailio 5.0.6 on a centos 7 (gdb) #0 0x00007f8d37f1c35e in clean_routine (ticks=43668909, param=0x0) at pike_funcs.c:206 #1 0x000000000047deb2 in compat_old_handler (ti=698702557, tl=0x7f8d38ed01a8, data=0x7f8d38ed01a8) at core/timer.c:997 #2 0x000000000047e92d in slow_timer_main () at core/timer.c:1131 #3 0x0000000000422fc4 in main_loop () at main.c:1679 #4 0x0000000000429e4d in main (argc=7, argv=0x7ffe1787ac98) at main.c:2642 (gdb) bt full #0 0x00007f8d37f1c35e in clean_routine (ticks=43668909, param=0x0) at pike_funcs.c:206 mask = "\000\000\000\000\000\000\000\000\000 \000\020\000\000\000\000\000\000\000\000\000\000\004\002\000\000\000\000\000\000\000" head = {next = 0x7f8d3aa110f8, prev = 0x7f8d39d36470} ll = 0x0 dad = 0x29a55ad00a4c9c0 node = 0xfffffffffffffff0 i = 77 __FUNCTION__ = "clean_routine" __PRETTY_FUNCTION__ = "clean_routine" #1 0x000000000047deb2 in compat_old_handler (ti=698702557, tl=0x7f8d38ed01a8, data=0x7f8d38ed01a8) at core/timer.c:997 t = 0x7f8d38ed01a8 #2 0x000000000047e92d in slow_timer_main () at core/timer.c:1131 n = 12 ret = 4294967295 tl = 0x7f8d38ed01a8 i = 925 __FUNCTION__ = "slow_timer_main" #3 0x0000000000422fc4 in main_loop () at main.c:1679 i = 20 pid = 0 si = 0x0 si_desc = "udp receiver child=19 sock=185.190.125.3:6000\000\000\000\006\000\000\000\000\000\000\000H\342\370r\231\177\000\000\060\251\207\027\376\177\000\000p'\355\070\215\177\000\000\240\262<m\231\177\000\000\210\330Et\231\177\000\000 \202<m\231\177\000\000\003\000\000\000\000\000\000\000\004\000\000\000\000\000\000\000\000\200\066\070\215\177\000" nrprocs = 20 woneinit = 1 __FUNCTION__ = "main_loop" #4 0x0000000000429e4d in main (argc=7, argv=0x7ffe1787ac98) at main.c:2642 cfg_stream = 0x183e010 c = -1 r = 0 tmp = 0x7ffe1787b86e "" tmp_len = 0 port = 0 proto = 2496 options = 0x7387e0 ":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 = 1816923433 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7ffe1787ab50 p = 0x7f997c3cb9ad <intel_check_word+173> "H\205\300t\025\017\266P\003\017\266\312D9\371\017\204", <incomplete sequence \316> st = {st_dev = 20, st_ino = 30979, st_nlink = 2, st_mode = 16832, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1530437017, tv_nsec = 316150519}, st_mtim = {tv_sec = 1542572308, tv_nsec = 811767469}, st_ctim = {tv_sec = 1542572308, tv_nsec = 811767469}, __unused = {0, 0, 0}} __FUNCTION__ = "main" (gdb) info locals cfg_stream = 0x183e010 c = -1 r = 0 tmp = 0x7ffe1787b86e "" tmp_len = 0 port = 0 proto = 2496 options = 0x7387e0 ":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 = 1816923433 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7ffe1787ab50 p = 0x7f997c3cb9ad <intel_check_word+173> "H\205\300t\025\017\266P\003\017\266\312D9\371\017\204", <incomplete sequence \316> st = {st_dev = 20, st_ino = 30979, st_nlink = 2, st_mode = 16832, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1530437017, tv_nsec = 316150519}, st_mtim = {tv_sec = 1542572308, tv_nsec = 811767469}, st_ctim = {tv_sec = 1542572308, tv_nsec = 811767469}, __unused = {0, 0, 0}} __FUNCTION__ = "main" (gdb) list 201 continue; 202 203 lock_tree_branch( i ); 204 for( ll=head.next ; ll!=&head ; ) { 205 node = ll2ipnode( ll ); 206 ll = ll->next; 207 /* skip nodes from a different branch */ 208 if (node->branch!=i) 209 continue; 210 (gdb) I have no SIP traffic and no idea how to reproduce for the moment Laurent -- 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/1822

2 4

[kamailio/kamailio] usrloc: core dump (#1900)
by Bastian Triller 01 Apr '19

01 Apr '19

### Description Kamailio crashes while querying for unexpired contacts in a location table while it is saving contacts to db. Seems to be a regression, since this didn't happened with Kamailio 4.4. #### Reproduction Constantly flush many locations and simultaneously get location statistics from `usrloc` module via `kamcmd ul.db_users`: ```sh shell1 % while kamcmd ul.flush ; do : ; done ``` ```sh shell2 % curl -H content-type:\ application/json -s -d '{"jsonrpc":"2.0", "method":"ul.db_contacts", "params": ["location"]}' localhost:5060/JSONRPC ``` #### Debugging Data ``` #0 0x00007f600e3345ad in ul_rpc_db_contacts (rpc=0x7f6004f8b960 <func_param>, ctx=0x7f6004f8b8e0 <_jsonrpc_ctx>) at ul_rpc.c:774 #1 0x00007f6004d6c15c in jsonrpc_dispatch (msg=0x7ffc7fc4e250, s1=0x0, s2=0x0) at jsonrpcs_mod.c:1251 #2 0x000055c674d60eb9 in do_action (h=0x7ffc7fc4e170, a=0x7f6012607828, msg=0x7ffc7fc4e250) at core/action.c:1054 #3 0x000055c674d6ea4d in run_actions (h=0x7ffc7fc4e170, a=0x7f6012607828, msg=0x7ffc7fc4e250) at core/action.c:1552 #4 0x000055c674d60e25 in do_action (h=0x7ffc7fc4e170, a=0x7f6012607ac8, msg=0x7ffc7fc4e250) at core/action.c:1045 #5 0x000055c674d6ea4d in run_actions (h=0x7ffc7fc4e170, a=0x7f6012600b28, msg=0x7ffc7fc4e250) at core/action.c:1552 #6 0x000055c674d60e25 in do_action (h=0x7ffc7fc4e170, a=0x7f6012607d00, msg=0x7ffc7fc4e250) at core/action.c:1045 #7 0x000055c674d6ea4d in run_actions (h=0x7ffc7fc4e170, a=0x7f60125fecf8, msg=0x7ffc7fc4e250) at core/action.c:1552 #8 0x00007f6004f913b4 in xhttp_process_request (orig_msg=0x7f6012622410, new_buf=0x7f6012638ad0 "POST /JSONRPC HTTP/1.1\r\nVia: SIP/2.0/TCP 127.0.0.1:58590\r\nHost: localhost:5060\r\nUser-Agent: curl/7.52.1\r\nAccept: */*\r\nContent-Length: 67\r\nContent-Type: application/x-www-form-urlencoded\r\n\r\n{\"jsonrpc\": \"2.0\", \"method\":\"ul.db_contacts\",\"params\":[\"location\"]}", new_len=256) at xhttp_mod.c:282 #9 0x00007f6004f9253b in xhttp_handler (msg=0x7f6012622410) at xhttp_mod.c:357 #10 0x000055c674e4be83 in nonsip_msg_run_hooks (msg=0x7f6012622410) at core/nonsip_hooks.c:111 #11 0x000055c674e944d7 in receive_msg (buf=0x7f5feac686a8 "POST /JSONRPC HTTP/1.1\r\nHost: localhost:5060\r\nUser-Agent: curl/7.52.1\r\nAccept: */*\r\nContent-Length: 67\r\nContent-Type: application/x-www-form-urlencoded\r\n\r\n{\"jsonrpc\": \"2.0\", \"method\":\"ul.db_contacts\",\"params\":[\"location\"]}", len=222, rcv_info=0x7f5feac683c8) at core/receive.c:202 #12 0x000055c674f2e43c in receive_tcp_msg (tcpbuf=0x7f5feac686a8 "POST /JSONRPC HTTP/1.1\r\nHost: localhost:5060\r\nUser-Agent: curl/7.52.1\r\nAccept: */*\r\nContent-Length: 67\r\nContent-Type: application/x-www-form-urlencoded\r\n\r\n{\"jsonrpc\": \"2.0\", \"method\":\"ul.db_contacts\",\"params\":[\"location\"]}", len=222, rcv_info=0x7f5feac683c8, con=0x7f5feac683b0) at core/tcp_read.c:1263 #13 0x000055c674f30a70 in tcp_read_req (con=0x7f5feac683b0, bytes_read=0x7ffc7fc4ee68, read_flags=0x7ffc7fc4ee6c) at core/tcp_read.c:1478 #14 0x000055c674f339bb in handle_io (fm=0x7f60126506b0, events=1, idx=-1) at core/tcp_read.c:1652 #15 0x000055c674f23d9b in io_wait_loop_epoll (h=0x55c6753e0fa0 <io_w>, t=2, repeat=0) at core/io_wait.h:1065 #16 0x000055c674f359b0 in tcp_receive_loop (unix_sock=54) at core/tcp_read.c:1822 #17 0x000055c674e14095 in tcp_init_children () at core/tcp_main.c:4802 #18 0x000055c674d216e1 in main_loop () at main.c:1713 #19 0x000055c674d286a9 in main (argc=13, argv=0x7ffc7fc4f4f8) at main.c:2642 ``` #### Log Messages ``` ERROR: usrloc [urecord.c:431]: wb_timer(): updating contact in db failed (aor: 1234(a)example.com) ERROR: db_mysql [km_dbase.c:127]: db_mysql_submit_query(): driver error on query: Commands out of sync; you can't run this command now (2014) ERROR: <core> [db_query.c:339]: db_do_update(): error while submitting query ERROR: usrloc [ucontact.c:1378]: db_update_ucontact_instance(): updating database failed ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.0.7 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, 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 6.3.0 ``` * **Operating System**: ``` Debian 9.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/1900

2 3

[kamailio/kamailio] Frequently TCP/TLS sessions remain in CLOSE_WAIT (#1881)
by kvrban 01 Apr '19

01 Apr '19

### Description On our setup with Kamailio 5.2.1 with users connected via TLS. i see frequently TCP/TLS sessions remain in CLOSE_WAIT: netstat -ntp |grep CLOSE tcp 238 0 172.17.217.10:5061 xxx.xxx.xxx.218:52613 CLOSE_WAIT 117912/kamailio tcp 4681 0 172.17.217.10:5061 xxx.xxx.xxx.125:8892 CLOSE_WAIT 117912/kamailio In tcpdump i see, that the client send a TCP FIN,ACK and and the OS which is hosting the Kamailio send TCP ACK. But Kamailio is not closing. So the session remain in CLOSE_WAIT for a long time (over a hour) We also have configured: tcp_connection_lifetime=65 modparam("tls", "connection_timeout", 63) Which should finally close after 65 second. But no effect. ### Troubleshooting #### Reproduction Register SIP clients via TLS, and then let the client close the TCP session ia TCP FIN,ACK * **Operating System**: Debian GNU/Linux 9 -- 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/1881

3 8

[kamailio/kamailio] Run kamcmd failed. (#1909)
by aleczmw 01 Apr '19

01 Apr '19

### Description  ### Troubleshooting #### Reproduction  [root@kamailio-665b74f766-sv4mx /]# kamcmd ERROR: connect_unix_sock: connect(/var/run/kamailio//kamailio_ctl): No such file or directory [2] #### Debugging Data  ``` [root@kamailio-665b74f766-sv4mx /]# kamcmd ERROR: connect_unix_sock: connect(/var/run/kamailio//kamailio_ctl): No such file or directory [2] ``` #### Log Messages [root@kamailio-665b74f766-sv4mx /]# kamcmd ERROR: connect_unix_sock: connect(/var/run/kamailio//kamailio_ctl): No such file or directory [2]  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (paste your output here) ``` * **Operating System**:  ``` (paste your output here) ``` -- 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/1909

3 7

git:master:a7660333: core: action.c - use system time to compute execution duration
by Daniel-Constantin Mierla 31 Mar '19

31 Mar '19

Module: kamailio Branch: master Commit: a7660333c790572201d8bc2f8c19fb72d3cb442b URL: https://github.com/kamailio/kamailio/commit/a7660333c790572201d8bc2f8c19fb7… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2019-03-31T12:54:34+02:00 core: action.c - use system time to compute execution duration --- Modified: src/core/action.c --- Diff: https://github.com/kamailio/kamailio/commit/a7660333c790572201d8bc2f8c19fb7… Patch: https://github.com/kamailio/kamailio/commit/a7660333c790572201d8bc2f8c19fb7… --- diff --git a/src/core/action.c b/src/core/action.c index 83b1f708cd..06775a88fc 100644 --- a/src/core/action.c +++ b/src/core/action.c @@ -1527,7 +1527,9 @@ int run_actions(struct run_act_ctx* h, struct action* a, struct sip_msg* msg) { struct action* t; int ret; - unsigned int ms = 0; + struct timeval tvb, tve; + struct timezone tz; + unsigned int tdiff; ret=E_UNSPEC; h->rec_lev++; @@ -1555,8 +1557,11 @@ int run_actions(struct run_act_ctx* h, struct action* a, struct sip_msg* msg) } for (t=a; t!=0; t=t->next){ - if(unlikely(cfg_get(core, core_cfg, latency_limit_action)>0)) - ms = TICKS_TO_MS(get_ticks_raw()); + + if(unlikely(cfg_get(core, core_cfg, latency_limit_action)>0) + && is_printable(cfg_get(core, core_cfg, latency_log))) { + gettimeofday(&tvb, &tz); + } _cfg_crt_action = t; if(unlikely(log_prefix_mode==1)) { log_prefix_set(msg); @@ -1566,16 +1571,19 @@ int run_actions(struct run_act_ctx* h, struct action* a, struct sip_msg* msg) if(unlikely(log_prefix_mode==1)) { log_prefix_set(msg); } - if(unlikely(cfg_get(core, core_cfg, latency_limit_action)>0)) { - ms = TICKS_TO_MS(get_ticks_raw()) - ms; - if(ms >= cfg_get(core, core_cfg, latency_limit_action)) { + if(unlikely(cfg_get(core, core_cfg, latency_limit_action)>0) + && is_printable(cfg_get(core, core_cfg, latency_log))) { + gettimeofday(&tve, &tz); + tdiff = (tve.tv_sec - tvb.tv_sec) * 1000000 + + (tve.tv_usec - tvb.tv_usec); + if(tdiff >= cfg_get(core, core_cfg, latency_limit_action)) { LOG(cfg_get(core, core_cfg, latency_log), "alert - action [%s (%d)]" - " cfg [%s:%d] took too long [%u ms]\n", + " cfg [%s:%d] took too long [%u us]\n", is_mod_func(t) ? ((cmd_export_t*)(t->val[0].u.data))->name : "corefunc", - t->type, (t->cfile)?t->cfile:"", t->cline, ms); + t->type, (t->cfile)?t->cfile:"", t->cline, tdiff); } } /* break, return or drop/exit stop execution of the current

1 0

← Newer
1
...
6
7
8
9
10
11
12
...
33
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev March 2019