<!-- Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment). -->
### Description I have sent malformed data to kamailio server and its getting crashed. <!-- Explain what you did, what you expected to happen, and what actually happened. -->
### Troubleshooting
#### Reproduction This can be easily reproducable by remove .(eol) from each line of invite packet <!-- If the issue can be reproduced, describe how it can be done. -->
#### Debugging Data
<!-- If you got a core dump, use gdb to extract troubleshooting data - full backtrace, local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile bt full info locals list
If you are familiar with gdb, feel free to attach more of what you consider to be relevant. -->
``` (paste your debugging data here) ```
#### Log Messages
<!-- Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site). -->
``` 32(78) CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 13 0(46) ALERT: <core> [main.c:745]: handle_sigs(): child process 47 exited by a signal 11 0(46) ALERT: <core> [main.c:748]: handle_sigs(): core was generated 0(46) INFO: <core> [main.c:771]: handle_sigs(): terminating due to SIGCHLD 2(48) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 6(52) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 8(54) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 12(58) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 13(59) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 15(61) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 17(63) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 18(64) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 20(66) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 22(68) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 24(70) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 26(72) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 28(74) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 32(78) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 25(71) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 21(67) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 23(69) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 14(60) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 3(49) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 29(75) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 19(65) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 30(76) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 11(57) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 7(53) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 31(77) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 16(62) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 9(55) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 27(73) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 10(56) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 4(50) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 5(51) INFO: <core> [main.c:826]: sig_usr(): signal 15 received 0(46) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized 2019/08/26 06:14:51.186871 [ERR] (cli) child process died with exit code 1 ```
#### SIP Traffic
<!-- If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site). -->
``` INVITE sip:9631793333@10.130.72.178:5060 SIP/2.0 Max-Forwards: 66 From: "9631791999" sip:9631791999@test.santhos.com;tag=8BpeDNKX9g7ZN To: sip:12254431343@52.77.251.154 Call-ID: 0e61d723-400b-1238-5ea2-029e611e72cc CSeq: 8715558 INVITE Supported: timer, path, replaces Allow-Events: talk, hold, conference, refer Content-Type: application/sdp Content-Disposition: session Content-Length: 248 Remote-Party-ID: "9631791999" sip:9631791999@test.santhos.com;party=calling;screen=yes;privacy=off Contact: sip:btpsh-5d5dab4f-36-1@3.82.91.199;alias=10.130.74.48~5060~1 User-Agent: NewServer Accept: application/sdp Allow: INVITE,ACK,CANCEL,BYE,UPDATE
v=0 o=- 1566538700029766 7092256907260767331 IN IP4 3.220.58.181 s=X-Lite release 5.6.1 stamp 99140 c=IN IP4 3.220.58.181 t=0 0 m=audio 10030 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv ```
### Possible Solutions
<!-- If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix. -->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
``` root@test-server:/# kamailio -v version: kamailio 5.1.4 (x86_64/linux) cc647d 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: cc647d compiled on 10:09:16 Jul 29 2019 with gcc 5.4.0 ```
* **Operating System**:
<!-- Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...; Kernel details (output of `uname -a`) -->
``` root@test-server:/# cat /etc/debian_version stretch/sid
root@test-server:/# uname -a Linux test-server 4.14.77-69.57.amzn1.x86_64 #1 SMP Tue Nov 6 21:32:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ```
I see that the core was generated. Can you send the full backtrace from gdb (`bt full` output)?
k sure will get it.
Did you managed to get the backtrace?
I am running Kamailio as Docker container.. so core file is not available on the setup where the issue is seen.. I am planning to have kamailio on standalone instance and will share the core file as soon as I have it.
Any update on this one?
Please reopen if you get further troubleshooting data.
Closing as I could not reproduce with packets without eol and is more than 1 month and a half since the reporter gave updates.
Closed #2044.