[SR-Users] Kamailio suddenly stopes responding to sip messages
Daniel-Constantin Mierla
miconda at gmail.com
Thu Nov 19 21:39:14 CET 2020
The backtraces are incomplete because you need to install kamailio
debugging symbols -- there is a package named kamailio-dbg or so that
has to be installed.
Then it seems to be some protection on the system preventing loading
other libraries, based on the content of the file you sent. Apparently
you have to disable this security protection by adding:
set auto-load safe-path /
line to your configuration file "/root/.gdbinit".
Then reproduce the case and grab again the kamctl trap. After that you
can eventually revert the change in /root/.gdbinit.
Cheers,
Daniel
On 19.11.20 20:48, Uttam Giri wrote:
> Thanks Daniel for your response.
>
> Please find attached the "kamctl trap" output file, we were able to
> recreate that issue again.
> Traffics are not blocked as I can see messages are received on the
> kamailio listen interface by using sngrep tool.
> Also, the pike module is not in effect as WITH_ANTIFLOOD is not
> defined in the default configuration.
>
> Thanks,
> Uttam
>
> On Thu, Nov 19, 2020 at 10:17 AM Daniel-Constantin Mierla
> <miconda at gmail.com <mailto:miconda at gmail.com>> wrote:
>
> Hello,
>
> install gdb and when the kamailio stops responding send here the
> file generated by the next command:
>
> kamctl trap
>
> The path to the file is printed when the command is executed. Note
> that it can take a bit to generate the file, if you have a lot of
> kamailio processes. The file contains the gdb backtrace for each
> process, showing what they do at that moment.
>
> For a few of other hints, be sure you don't block the traffic with
> the firewall/fail2ban or with pike module in kamailio.cfg.
>
> Cheers,
> Daniel
>
> On 19.11.20 16:46, Uttam Giri wrote:
>> Hi,
>> We are using Kamailio with Jitsi client where we observed
>> sometimes Kamailio stops responding to sip messages. As a result,
>> my Jitsi client goes offline and never back online. Also in the
>> Kamailio syslog there are no error logs(debug enabled) related to
>> this issue. As a temporary workaround, we had to restart the
>> Kamailio server all the time.
>> Does anyone observed a similar issue and can suggest any resolution.
>>
>> Kamailio version:-
>> version: kamailio 5.3.5 (x86_64/linux)
>> flags: 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,
>> TLS_PTHREAD_MUTEX_SHARED
>> 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: unknown
>> compiled with gcc 7.5.0
>>
>> UDP process when Kamailio stops responding:-.
>>
>> root at ip-10-68-16-14:/home/ugiri# kamctl ps
>> {
>> "jsonrpc": "2.0",
>> "result": [
>> {
>> "IDX": 0,
>> "PID": 15436,
>> "DSC": "main process - attendant"
>> }, {
>> "IDX": 1,
>> "PID": 15442,
>> "DSC": "udp receiver child=0 sock=10.68.16.14:5060
>> <http://10.68.16.14:5060> (100.26.5.214:5060
>> <http://100.26.5.214:5060>)"
>> }, {
>> "IDX": 2,
>> "PID": 15443,
>> "DSC": "udp receiver child=1 sock=10.68.16.14:5060
>> <http://10.68.16.14:5060> (100.26.5.214:5060
>> <http://100.26.5.214:5060>)"
>> }, {
>> "IDX": 3,
>> "PID": 15444,
>> "DSC": "udp receiver child=2 sock=10.68.16.14:5060
>> <http://10.68.16.14:5060> (100.26.5.214:5060
>> <http://100.26.5.214:5060>)"
>> }, {
>> "IDX": 4,
>> "PID": 15445,
>> "DSC": "udp receiver child=3 sock=10.68.16.14:5060
>> <http://10.68.16.14:5060> (100.26.5.214:5060
>> <http://100.26.5.214:5060>)"
>> }, {
>> "IDX": 5,
>> "PID": 15446,
>> "DSC": "udp receiver child=4 sock=10.68.16.14:5060
>> <http://10.68.16.14:5060> (100.26.5.214:5060
>> <http://100.26.5.214:5060>)"
>> }, {
>> "IDX": 6,
>> "PID": 15447,
>> "DSC": "udp receiver child=5 sock=10.68.16.14:5060
>> <http://10.68.16.14:5060> (100.26.5.214:5060
>> <http://100.26.5.214:5060>)"
>> }, {
>> "IDX": 7,
>> "PID": 15448,
>> "DSC": "udp receiver child=6 sock=10.68.16.14:5060
>> <http://10.68.16.14:5060> (100.26.5.214:5060
>> <http://100.26.5.214:5060>)"
>> }, {
>> "IDX": 8,
>> "PID": 15449,
>> "DSC": "udp receiver child=7 sock=10.68.16.14:5060
>> <http://10.68.16.14:5060> (100.26.5.214:5060
>> <http://100.26.5.214:5060>)"
>> }, {
>> "IDX": 9,
>> "PID": 15450,
>> "DSC": "slow timer"
>> }, {
>> "IDX": 10,
>> "PID": 15451,
>> "DSC": "timer"
>> }, {
>> "IDX": 11,
>> "PID": 15452,
>> "DSC": "secondary timer"
>> }, {
>> "IDX": 12,
>> "PID": 15453,
>> "DSC": "JSONRPCS FIFO"
>> }, {
>> "IDX": 13,
>> "PID": 15454,
>> "DSC": "JSONRPCS DATAGRAM"
>> }, {
>> "IDX": 14,
>> "PID": 15455,
>> "DSC": "ctl handler"
>> }, {
>> "IDX": 15,
>> "PID": 15456,
>> "DSC": "Http Async Worker"
>> }, {
>> "IDX": 16,
>> "PID": 15457,
>> "DSC": "Http Async Worker"
>> }, {
>> "IDX": 17,
>> "PID": 15458,
>> "DSC": "TIMER NH"
>> }, {
>> "IDX": 18,
>> "PID": 15459,
>> "DSC": "tcp main process"
>> }
>> ],
>> "id": 17709
>> }
>>
>> Thanks,
>> Uttam
>>
>>
>>
>>
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at lists.kamailio.org <mailto:sr-users at lists.kamailio.org>
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
>
> --
> Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com>
> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
> Funding: https://www.paypal.me/dcmierla <https://www.paypal.me/dcmierla>
>
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20201119/3aaab2f1/attachment.htm>
More information about the sr-users
mailing list